Hello, What is the normal time for keeping volhist? Not indefinitely ? Thanks, Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860)862-8164 (cell) (860
I usually keep db backup volumes about 5 days, for other volhist entries I'd say that 30-60 days is about the maximum usefull time. Thanks, Avy Wong Business Continuity Administrator Mohegan Sun 1 M
Thanks Remco, it gives me some idea. Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860)862-8164 (cell) (860)961-6976 Remco Post <r.post AT PLCS DOT N
Author: Howard Coles <Howard.Coles AT ARDENTHEALTH DOT COM>
Date: Wed, 23 Apr 2008 14:10:00 -0500
If you are talking about the actual volhist.out backup file, I'd keep one for every dbbackup. If you are talking about volume entries in the volhist, I'd go with Remco's post. Not that DBBackups are
For STGNEW, STGDELETE, STGREUSE entries, there is no use for them once your oldest DB backup has expired, but it's OK to keep them around longer. Be careful though, clearing out the VOLHIST, if you o
Whats the knock on effect of not clearing your volhist anyway? Short of getting a large text file hanging around. Jim For STGNEW, STGDELETE, STGREUSE entries, there is no use for them once your oldes
Whats the knock on effect of not clearing your volhist anyway? Short of getting a large text file hanging around. The large, flat file doesn't just hang around: it is completely rewritten at each vo
Quoting Richard Sims <rbs AT BU DOT EDU>: Whats the knock on effect of not clearing your volhist anyway? Short of getting a large text file hanging around. The large, flat file doesn't just hang arou
Author: Henrik Vahlstedt <SHWL AT STATOILHYDRO DOT COM>
Date: Fri, 25 Apr 2008 13:52:49 +0200
".. but is it also updates for each time a volume is added or deleted from a storagepool?" Might consider doing a q volhist and check modification date on volhist.out to get an answer if it gets upda
Is this true? I know the volhist files are updated each time a database backup is completed, but is it also updates for each time a volume is added or deleted from a storagepool? ... You're thinking
Quoting Richard Sims <rbs AT BU DOT EDU>: Is this true? I know the volhist files are updated each time a database backup is completed, but is it also updates for each time a volume is added or delete
Been there done that, you are right. Now, explain, why do we need a backup volhist command then? ... My next test... Perhaps because the new, novice system administrator at Spacely's Sprockets, Inc.
Hi Richard, Quoting Richard Sims <rbs AT BU DOT EDU>: Been there done that, you are right. Now, explain, why do we need a backup volhist command then? ... My next test... Perhaps because the new, nov
These would be valid if we were able to set the location of the output for backup volhist dynamically (would be nice), but I haven't found one. How about the Filenames operand of the BAckup VOLHisto
Quoting Richard Sims <rbs AT BU DOT EDU>: These would be valid if we were able to set the location of the output for backup volhist dynamically (would be nice), but I haven't found one. How about the
And now for an opinion completely different: I don't like to let VOLHISTORY get too large because when you do a PREPARE, the volhistory gets included in the output. Unwieldy.
I don't like to let VOLHISTORY get too large because when you do a PREPARE, the volhistory gets included in the output. Unwieldy. So very true. At SARA we used to grep the volhist for dbb, dbi and db
Like the appendix on our large intestine. Vestigial? Someone suggested "Well, now we write those every time something changes, let's remove the BACKUP VOLHIST command", and someone else at IBM had a
One can also specify the location(s) of the volhist files in dsmserv.opt, for example, I have it write to files in two different filesystems: * == * * VOLUMEHISTORY * * ** * VOLUMEHistory <filename>