Hi,
If possible, you can change your config to do only one full db backup to
tape (and send this one off-site allong with your copy tapes) and all
other (incr.) db backups to a devclass type=file, where the file is
pointing to a network share (at another location).
Regards,
Karel
-Original
Thanks guys. Lots of stuff there to get my teeth into.
-Original Message-
From: Len Boyle [mailto:[EMAIL PROTECTED]
Sent: 21 September 2006 16:46
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Total newbie question about DB Backups
Angus,
Look at help query volhist
This will show you t
For protection ensure that the ROLL FORWARD mode is on and there is
enough log space to take account for load during the period between TSM
DB Backups. This can be up to 13.2GB. Also set the Database backup
trigger, and ensure there is always scratch tapes. Put the DB and Log
volumes on different
Angus,
Look at help query volhist
This will show you the db tapes and other special tapes
Query volhist type=dbb
len
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Angus
Macdonald
Sent: Thursday, September 21, 2006 11:36 AM
To: ADSM-L@VM.MARI
Okay, I may rely on mirroring then. If I do a DB backup every 4 hours it'll
cost 6 tapes a day and each one will only have a few MB of data.
For some reason, the tapes used for DB Backup aren't listed when I execute a
Q VOL. Something else to investigate.
Thanks again.
-Original Message-
By setting the DRMDBBACKUPEXPIREDAYS, allows you to automatically
recycle the TSM DB tapes. This is usually set to something like a 5 day
cycle, based on how realsitic it is that you would want to recover your
TSM environment back to. This means there will always be a critical
volume of tapes use
Angus,
You can use the delete volhist command to move your older db backup tapes to
scratch status.
Look at help del volhist. There are various options to control which tapes
handled.
len
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Angus
Hi Angus !
You'll probably get somehow disapointed, but there's no way to do what
you're asking !
TSM wants a new tape for each DB backup, and the only way to spare your
precious scratch volumes would be to use some form of disk storage, thru
the mean of a sequential-on-disk device class ...
HTH
