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 volhist?
For
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
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
".. 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 updated..
-H.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
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
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 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
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 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.
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
We recently upgraded our TSM server (running on AIX) from 5.3.5 to 5.4.3.
Since the upgrade, we have noticed a few of our Windows clients have
started to backup more data than usual. Looking at the sched log with
quiet turned off, we can see TSM backing up files that have not been
changed/modified
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]>:
>
>
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
13 matches
Mail list logo
