Mark Wheeler wrote:
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:
How nice that people actually read the whole discussion-thread before
contributing ;-) Yes you are right.
Thank you for your input :
rist.edu:Dist Stor Manager
cc
04/29/2008 09:58
AMSubject
Re: [ADSM-L] How long should we
keep volhis
Allen S. Rout wrote:
>>> On Fri, 25 Apr 2008 14:20:48 +0200, Remco Post <[EMAIL PROTECTED]> said:
>
>> Been there done that, you are right. Now, explain, why do we need a
>> backup volhist command then?
>
> Like the appendix on our large intestine. Vestigial?
>
> Someone suggested "Well, now we wr
>> On Fri, 25 Apr 2008 14:20:48 +0200, Remco Post <[EMAIL PROTECTED]> said:
> Been there done that, you are right. Now, explain, why do we need a
> backup volhist command then?
Like the appendix on our large intestine. Vestigial?
Someone suggested "Well, now we write those every time something
Wanda Prather wrote:
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.
So very true. At SARA we used to grep the volhist for dbb, dbi and dbs
volumes and mail that ou
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.
On Fri, Apr 25, 2008 at 10:04 AM, Remco Post <[EMAIL PROTECTED]> wrote:
> Quoting Richard Sims <[EMAIL PROTECTED]>:
>
>
Quoting Richard Sims <[EMAIL PROTECTED]>:
On Apr 25, 2008, at 9:40 AM, Remco Post wrote:
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 VOLHistory co
On Apr 25, 2008, at 9:40 AM, Remco Post wrote:
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 VOLHistory command?
R.
Hi Richard,
Quoting Richard Sims <[EMAIL PROTECTED]>:
On Apr 25, 2008, at 8:20 AM, Remco Post wrote:
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
Sprocke
On Apr 25, 2008, at 8:20 AM, Remco Post wrote:
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. ambitiously cleared out a bunch of files which w
Quoting Richard Sims <[EMAIL PROTECTED]>:
On Apr 25, 2008, at 7:24 AM, Remco Post wrote:
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 that
On Apr 25, 2008, at 7:24 AM, Remco Post wrote:
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 that I just made that up? :-)
Just take a look
PROTECTED] On Behalf Of
Remco Post
Sent: den 25 april 2008 13:24
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How long should we keep volhist?
Quoting Richard Sims <[EMAIL PROTECTED]>:
> On Apr 25, 2008, at 5:22 AM, Jim Young wrote:
>
>> Whats the knock on effect of not
Quoting Richard Sims <[EMAIL PROTECTED]>:
On Apr 25, 2008, at 5:22 AM, Jim Young wrote:
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 volume t
On Apr 25, 2008, at 5:22 AM, Jim Young wrote:
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 volume transition, where the TSM server has to run
t
Whats the knock on effect of not clearing your volhist anyway?
Short of getting a large text file hanging around.
Jim
- Original Message -
From: "Wanda Prather" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, April 23, 2008 8:11 PM
Subject: Re: [ADSM-L] How long should we keep
ger" cc
> <[EMAIL PROTECTED]
> .EDU> Subject
> Re: [ADSM-L] How long should we
>
Avy Wong
> Sent: Wednesday, April 23, 2008 11:32 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] How long should we keep volhist?
>
> Hello,
> What is the normal time for keeping volhist? Not indefinitely ?
>
> Thanks,
> Avy Wong
> Business Continuity Adminis
Re: [ADSM-L] How long should we
keep volhist?
04/23/2008 12:38
PM
Please respond to
"ADSM: Dist Stor
Manager"
<[EMAIL PROTECTED]
Avy Wong wrote:
Hello,
What is the normal time for keeping volhist? Not indefinitely ?
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 Mo
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)961-6976
21 matches
Mail list logo
