info
Sent by: ADSM-L@VM.MARIST.EDU
07/19/2011 03:52 AM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L
cc
Subject
Re: [ADSM-L] Determing how much of a tsm server's data is active
Richard,
Your approach will work for file data, but a lot of the TDPs don't
accurately register fi
Richard,
Your approach will work for file data, but a lot of the TDPs don't
accurately register filespace sizes. Only the OP will know what the
impact of that might be in his environment.
I would go for an export allactive preview=yes. It might run for quite
a while.
Regards
Steve
Steven Ha
with a side-note that this figure includes data that may be excluded from
backup. As long as you don't exclude too much, that would be ok. If you have
many databases, and/or long exclude lists YMMV.
On 18 jul 2011, at 20:42, Richard Sims wrote:
> If your clients are doing unfettered incremental
If your clients are doing unfettered incremental backups of file systems, then
the following would yield a MB approximation, very quickly:
SELECT SUM(CAPACITY*PCT_UTIL/100) FROM FILESPACES
which is based upon TSM's information about the file system as gotten from the
last client operation.
Tsm server 5.5.4. running on Suse linux sles9.
I am being asked for how much of my server's data is active data.
I have seen the type=allactive and preview=yes in the export node command.
Is there a better way?
Maybe something like
A query to sum file_size in contents for each active object? No
