Author: Scott McCambly <scottad AT UNOPSYS DOT COM>
Date: Thu, 24 Jul 1997 14:40:39 -0400
Hello ADSMers, Has anyone out there come up with a script to parse the Volume History file in order to determine how far back you can go with a DELETE VOLHIST TYPE=ALL, and not affect any volumes cur
No need to write your own. What you want to do is issue the command: Delete VOLHIST Today-nn Type=all This will delete all entries in the volume history file that are older than nn days old - you can
Author: "Nicholas, Murray, Haltek/AU" <MurrayNi AT HALTEK.COM DOT AU>
Date: Mon, 28 Jul 1997 16:02:51 +1000
This implies that all entries older than "nn" days will be deleted. I am just a little unclear on what the purpose of this file is but I think I now understand. Please correct me if the following pro
No need to write your own. What you want to do is issue the command: Delete VOLHIST Today-nn Type=all This will delete all entries in the volume history file that are older than nn days old - you can
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Mon, 28 Jul 1997 08:47:57 -0400
Actually all volume history *is* stored in the database. The volume history files themselves are "write-only" during normal ADSM operations, and read only when doing a database restore. Thus when you
Based on your last paragraph, I would agree, but in a conservative practice, I might give it a couple of extra days, just to be sure. Your second paragraph is not exactly correct.... In a nutshell, h
Author: Brian Jones <brian.jones AT NY.UBS DOT COM>
Date: Mon, 28 Jul 1997 09:40:34 -0400
Guys, If I may humbly join your ongoing conversation with a question of my own. I usually keep 2 full copies of data base backup tapes. I recently issued a del volh type=dbb tod=07/23/1997. This comm