Lisa,  

I run a dataless savevg weekly on all my non-root VGs to save in a file on the 
rootvg.
To recreate the VG you just run a restorevg and presto its defined as it was 
ready to restore the data from TSM

Here's my script.  Warn and abort are a couple of ksh functions.

#!/usr/bin/ksh
#
# This script runs weekly on all AIX machines
# its purpose is to take a dataless backup of all VGs
# this enables them to be easily reallocated in the event of loss

# Steve Harris March 2001

# We'll save them to a local file first
savedir=/var/local/savevg
# Clear last weeks stuff
if cd $savedir; then
        :
else
    abort $0 Unable to cd to $savedir
    exit 2
fi

rm $savedir/*

for i in $(lsvg -o)
do
    exclude=/etc/exclude.$i
    if [[ -x $exclude ]] ; then
        mv $exclude $exclude.save
    fi
    echo ".*" > $exclude
    if savevg -emX -f $savedir/$i $i; then
        :
    else
        warn $0 savevg of $i failed
    fi
    rm $exclude
    if [[ -x $exclude.save ]]; then
        mv $exclude.save $exclude
    fi
done

Regards

Steve Harris

AIX and TSM Admin
Queensland Health,
Brisbane Australia

>>> Lisa Cabanas <CABANL AT MAIL.MODOT.STATE.MO DOT US> 09/08/2001 23:55:00 >>>
Thanks for your reply, Herfried.  It brings to mind some other questions
regarding other volume groups.  Say you have all your Oracle stuff on one
or two different vgs.  Would you need to have done a savevg sometime in
the past to get the vg back, or at bare metal time would you need to
manually create the volume group and lvs and fss associated with it, and
then fill it with the data from TSM?

I went and looked for a bare metal Redbook for AIX and found the one from
1997 that deals with AIX 4.1-- is it still pretty applicable to 4.3.3?  I
wonder if TSM still "supports" a bare metal for AIX, or if it is now
unsupported like Win2K is?


thanks
lisa




Herfried Abel <ha7 AT DAIMLERCHRYSLER DOT COM>
08/09/2001 01:52 AM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU 
        cc:     (bcc: Lisa Cabanas/SC/MODOT)
        Subject:        Re: AIX 4.3.3 list of excludable files & filesystems



Lisa,

All the filesystems within the rootvg are backed up with a mksysb as long
as they are not explicit excluded from rthe mksysb. In general AIX does
not
delete (major) files on reboot as other UNIX's do ( eg /tmp ).
This is how we do the restore of an AIX machine :
1) restore mksysb
2) restore "OS-definitions" via TSM ( rootvg filesystems eg. /etc ) ( TSM
Client already restored by mksysb )
3) restore filesystems (non rootvg) via TSM
4) restore application-data ( DBs eg. ORACLE,SAPDB, MSSQL etc ) via TDP
Agents in necessary.

Step 2) depends on the time-difference between the mksysb and the last
config changes of AIX. Should not be necessary if you make a mksysb after
every config change , as all of the sysadmins do :-)

So what we do, we dont exclude files from the rootvg in the TSM backup (
AIX-OS is not really need much space ) but we exclude lots of temporary
application files. We think that at this point we can find a lot of
temporary data (eg. SAP rollfiles ).Of cause you have to know your
application / Datebase very well, so that you dont exclude a file by
mistake.

herfried





Lisa Cabanas <CABANL AT MAIL.MODOT.STATE.MO DOT US>@VM.MARIST.EDU> on 08.08.2001
18:20:26

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU 
cc:

Subject:  AIX 4.3.3 list of excludable files & filesystems


Has anyone ever compiled a list of files and/or file systems that can be
excluded from backup either because they are dynamically created by the OS
at
reboot/syncvg etc
or because they are included in a mksysb?






****************************************************************************

The information contained in this transmission, which may be
confidential and proprietary, is only for the intended recipients.
Unauthorized use is strictly prohibited. If you receive this
transmission in error, please notify me immediately by telephone
or electronic mail and confirm that you deleted this transmission
and the reply from your electronic mail system.
****************************************************************************


**********************************************************************
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.
**********************************************************************