Important items to backup 3

[Mag0007]

For DR purposes, what are the most important things TSM needs to backup before sending tapes to the DR site?

The only think I can think of is: TSM database.

q db f=d , and the "Last Complete Backup Date/Time" should be current.

Is there anything else?

Thanks!

 

[gsavy]

Yes you'll also need this 4 files

dsmserv.dsk
dsmserv.opt
devcnfg.out
volhist.out

 

[comtec17]

You will only need devcnfg.out, volhist.out, and a copy of your options file.

 

[Mag0007]

Thanks for the good advice. I think these files are being backed up onto tape. Is it a good idea to keep these files on mksysb? How can I check if these files are actually being backedup?

Thanks!

 

[gsavy]

of course these files are backed up but, you will need them to rebuild your server and read your tape

so it might be a good idea to save them floppy or another server

 

[Mag0007]

I can't seem to locate :
devcnfg.out
volhist.out

Where are they usually found?

Thanks

 

[LED888]

From the TSM Server issue: q option
(The q option basicly looks in the dsmserv.opt file.)
or
Open up the file called dsmserv.opt

They should show where the file is located and how they are name.

If you can not find volhist.out or devconfig.log, more than likely we did not issue backup volhist or backup devconfig.

In the TSM Admin Guide there should be two sections about
DRM and a checklist.

Good Luck,
Sias

 

[Mag0007]

For the volhist.out file, does it look something like this:
**************************************
Sequential Volume Usage History
Updated 03/04/05 05:02:46


For the devconfig does it look like this:
/* Device Configuration */
DEFINE DEVCLASS etc..etc..

?

Thanks for all your help!

 

[Mag0007]

Actually, I would also need to know what volume holds my TSM database info. How do I find that out?

 

[LED888]

The devconfig.out will have information like what you are seeing. Servername, Define Library, Define Drive, Define Path and some additional information.

In the volhist should see information about volumes and there type.


Two ways to find out what tape volumes that contains
the dbbbackup.

1. Issue: q volhist t=dbb
This will show all tape volumes that contains the
database backup.

2. Look in the volhist.out file, it should indicate
which volume contains the database backup.
There is a catch.
Once a database backup completes, need to run backup
volhist. This will take the information from the database and place it into the volhist.out file.
If the volhist.out file is not current.
Issue: dsmserv restoredb and hopefully we will encounter
a current database backup.

Good Luck,
Sias

 

[Mag0007]

Both, methods are the same though right?
Which method do you prefer? Why are you running "backup volhist"? Isn't "backup db" supposed to take of this? Also, do you prefer database backup to be full or incremental?

Thanks!

 

[LED888]

Issuing: q volhist or opening the file volhist.out
Will get you the same information.
For me, I issue: q volhist t=dbb

Backing up the database and backing up the volhist
are two different process.

If we only issue backup volhist once and do not issue the command again. Let's say over a 9 month period, during this time we have been performing a database backup every day. And we only keep two weeks worth of the backup.

At the end of the 9 months some thing happen and we have to restore the database. Our tape library have 500+ tape volumes.

Since we only did a backup volhist 9 months ago, it will contain the name of the database backup that was done 9 months ago. During this time database volume have expire and the tape have been reused several times already.

Since we do not know which tape contains the current database backup, we would have to issue 'restore db' and hopefully that we hit a database backup.

The volume history contain information like what tape volume contains the database backup. Without a current volume history, we have no way to determine which tape volume contains the database backup.

If we know the name of the tape volume, then we do not need the volume history and what are the odds of this ocurring?

Unless we have a manual tape drive and we have to manually keep track of all the tapes.

When we backup the database, we are saving all the pointers that the TSM Server use. Within the database it also contain information of what tape volume contains the database backup. To get this information out of the database, need to issue backup volhist.

Once the backupdb completes, need to run backup volhist.

If the database fit on one tape, just perform full backup.
When we perform the restore, there would be only tape mount.

If the database span two tapes, then we may start performing incremental backup.
With incremental backup of the database, can only perform up to 32 incremental backup. Then a full backup must be done.

The Quick Start Guide is a good manual to start with.

The admin guide, it expect the reader to have some knowledge
level.

The reference guide, all the TSM syntax that one would need.

The followng makes good addition to the Admin Guide.

TSM Concepts - SG24-4877-03

http://www.redbooks.ibm.com/redbooks/pdfs/sg244877.pdf

TSM Implementation - SG24-54-16-02

http://www.redbooks.ibm.com/redbooks/pdfs/sg245416.pdf

Good Luck,
Sias

 

[Mag0007]

Thanks for the great info.

Here is what I came up with after you have the AIX VGs, LVs, and FS completed.

1) Put the volumes containing the database.
2) run "audit library checklabel=barcode"
3) run "restore database"
4) Put the rest of the copy pool volumes in
5) checkin all of them as status=PRIVATE
6) Start doing filesystem restores from other servers

Is there anything I am missing like fail and destory tapes from shelf?