Tom,
Yes, that's exactly how it works. Just make sure you list enough volumes
to always have one of them in your library, plus maybe a buffer. I had a 7
day retention on my database backups, plus one day transit back from the
vault, so I used 10 volumes, and never had an issue.
Nick Cassim
The devclass is just a name in TSM identifying type of volumes (in your
case files). The parameter in "backup db" points to *which* type of
volumes you want your backup be sent - 3570 tape, file or something else.
In a devclass of type FILE there is DIRectory parameter which identifies
the director
DRM will also make those additional dumps for you, if you have it setup.
--Justin
"Seay, Paul"
cc:
Sent by: "ADSM: Subject: Re: backup database
The devclass option is there to specify what sort of device you want
the backup to goto. In our environment for example we have an IBM 3494
library so I state devclass: "3590dev" and it directs my backup to media
belonging to that devclass. Below is the a procedure I typed up for
backing it
That is the command.
However, after you run any backup database command you should run a:
backup volhistory
This will dump the volume history of the database to a sequential file.
That file can be used to figure out what tapes to mount to recover the
database if the database gets destroy
