ADSM-L

Re: Summary database not containing all information

2004-06-29 12:02:23
Subject: Re: Summary database not containing all information
From: "Cain, Jason (Corporate)" <Jason.Cain AT CONAGRAFOODS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 29 Jun 2004 11:02:07 -0500
Verson 5.2.0.1, and most of our clients are at that level also.  Do you know 
what kind of degragation would be caused to set the summary info to around a 
year.  I don't know how much DB overhead is involved.

Jason 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Prather, Wanda
Sent: Tuesday, June 29, 2004 10:42 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Summary database not containing all information


Jason,

What level is your server and what level are your clients?

There was a bug that caused TSM V4 clients to not update the summary table,
or always record as 0 bytes.
Is it possible that your "sometimes" data is coming from later level
clients, and your "missing" information is from older clients?

When you get the server and the clients to TSM 5.2, the summary information
is recorded correctly again.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Cain, Jason (Corporate)
Sent: Tuesday, June 29, 2004 10:29 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Summary database not containing all information


I have the Activity for Summary Retention period set to 30 days, however
when I run an archive or backup the information does not show up.  It does
however, show up sometimes.  Is there something I must run to update the
summary table?  Also, what kind of extra space or overhead is needed to keep
summary info for a year or so.  I can't seem to find any kind of
calclulation to determine the extra overhead this may cause on the server.

Any help on answering the '2' questions would be greatly appreciated.

Thanks,
Jason Cain

<Prev in Thread] Current Thread [Next in Thread>