ADSM-L

Re: Calculating the size of a backupset

2002-08-25 19:41:17
Subject: Re: Calculating the size of a backupset
From: Steve Harris <Steve_Harris AT HEALTH.QLD.GOV DOT AU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 26 Aug 2002 08:54:59 +1000
Hi Mark,

One approach is to use the export command with preview to calculate how much 
active data you have.

e.g. EXPORT NODE foobar FILEDATA=BACKUPACTIVE PREVIEW=YES

This gives some useful output that you can pick out of the actlog

08/26/2002 08:43:28  ANR0616I EXPORT NODE: Preview processing completed
                      successfully.
08/26/2002 08:43:28  ANR0891I EXPORT NODE: Copied 1 optionset definitions.
08/26/2002 08:43:28  ANR0626I EXPORT NODE: Copied 1 node definitions.
08/26/2002 08:43:28  ANR0627I EXPORT NODE: Copied 7 file space 0 archive files,
                      fsId268504381, 94906 backup files, and 0 space managed
                      files.
08/26/2002 08:43:28  ANR0630I EXPORT NODE: Copied 12954304 kilobytes of data.
08/26/2002 08:43:28  ANR0611I EXPORT NODE started by FREDNURK as process 1833
                      has ended.
08/26/2002 08:43:28  ANR0986I Process 1833 for EXPORT NODE running in the
                      BACKGROUND processed 94915 items for a total of
                      13,265,207,444 bytes with a completion state of SUCCESS
                      at 08:43:28.


HTH

Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia

>>> mark AT MDRCONSULT DOT COM 26/08/2002 7:22:00 >>>
Hi *SMers,

I would like to be able to calculate the size of a backupset prior to
running the "generate backupset" command.  If I could do this the size
could be included in desciption area when I generate the backupset.  I
have played around with some select commands, but I can't seem to link
all the necessary information.  I looked at the "backups" table and from
there I can deermine the list of the "active_version", but there is no
size attribute only an "object_id" which I assumed linked me to another
table but I can't what that table name is.  I looked at the "contents"
table and found a file size, but that is the size of the aggregate file
which could possibly have inactive versions in it.  I know TSM keeps
this info someplace because when you do a "dsm -> restore" with
inactives listed it shows you the files sizes for all the different
versions.  I can only assume (I know that's dangerous) that TSM must
have some either undocumented or inaccessable tables to track this info.

I had been trying an approach where I would bring up "dsm" select "file
level" (therefore including all my filespaces), and then use the
estimate button.  There is 2 problems with this 1 it certainly isn't an
automatic thing ( I would like to do this from a scheduled event ) and 2
the numbers I get from estimate in no way reflect what I got when I
actually did the "generate backupset".

Well, anybody have any ideas?

--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.

===============================================================================
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE
===============================================================================



**********************************************************************
This e-mail, including any attachments sent with it, is confidential 
and for the sole use of the intended recipient(s). This confidentiality 
is not waived or lost if you receive it and you are not the intended 
recipient(s), or if it is transmitted/ received in error.  

Any unauthorised use, alteration, disclosure, distribution or review 
of this e-mail is prohibited.  It may be subject to a statutory duty of 
confidentiality if it relates to health service matters.

If you are not the intended recipient(s), or if you have received this 
e-mail in error, you are asked to immediately notify the sender by 
telephone or by return e-mail.  You should also delete this e-mail 
message and destroy any hard copies produced.
**********************************************************************

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