Re: DBBackup Tapes never being asked for
2002-01-11 16:19:23
The other thing about this is that if you are making incremental backups to
a local FILE class device along with your full backup series, DRM will not
handle the full backup tapes. Makes sense if you think about it ... DRM
cannot assure the incrementals are "in the vault".
_____________________________
William Mansfield
Senior Consultant
Solution Technology, Inc
Adam J Boyer
<adam.j.boyer@ To: ADSM-L AT VM.MARIST DOT EDU
FRB.GOV> cc:
Sent by: Subject: Re: DBBackup Tapes never
being asked for
"ADSM: Dist
Stor Manager"
<ADSM-L AT VM DOT MAR
IST.EDU>
01/11/2002
02:33 PM
Please respond
to "ADSM: Dist
Stor Manager"
DRM will delete DB backups based on the value set by:
SET DRMDBBACKKUPEXPIREDAYS
I have seen that if you prune the volume history of database entries DRM
loses track of those pruned entries.
William Boyer wrote:
>
> I believe that DRM will only expire DBBackup VIRTUAL volumes, not normal
> DBBackup tape volumes. This is for server-2-server DB backups. You have
to
> do a DEL VOLH T=DBB TOD=TODAY-n. I have this in a server script that does
> all my server backup commands:
>
> ba db type=full devclass=3590off scratch=yes wait=yes
> /*------------------------------------------------------------------*/
> /* If the backup worked, then delete volhistory... */
> /*------------------------------------------------------------------*/
> if(rc_ok) -
> del volh t=dbb tod=today-8
>
> Bill Boyer
> DSS, Inc.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Ed Anderson
> Sent: Friday, January 11, 2002 2:14 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: DBBackup Tapes never being asked for
>
> Folks,
>
> Has anyone experienced DBBackup tapes never going into a VaultRetrieve
> state from DRM?
> Some useful info : TSM Server 4.1.4.0 on Solaris 2.6.
> We're not deleting VolumeHistory nor are we deleting VolumeHistory
> type=backup, DRM is ( supposed to be ) taking care of it. We were
> deleting VolHist volumes where type is backup, but was instructed that
> such (1) didn't need to be done with DRM and (2) was probably why
> DRM was losing track of the DBBackup volumes.
>
> Any ideas that y'all have would be most helpful.. I'm a little lost as
> to what could be causing this to happen..
>
> Here's the output of "q drmstatus"
> Recovery Plan Prefix: /var/tivoli/plans/disaster_plan
> Plan Instructions Prefix: /var/tivoli/plans/instructions
> Replacement Volume Postfix: @
> Primary Storage Pools: TAPEPOOL1
> Copy Storage Pools: DRTAPEPOOL1
> Not Mountable Location Name: NOTMOUNTABLE
> Courier Name: COURIER
> Vault Site Name: VAULT
> DB Backup Series Expiration Days: 15 Day(s)
> Recovery Plan File Expiration Days: 15 Day(s)
> Check Label?: Yes
> Process FILE Device Type?: No
> Command File Name:
>
> Thanks,
> Ed Anderson
> --
> ++++++++++++++++++++++++
> Ed Anderson
> Unix / Backup Administrator
> University of Mississippi Medical Center
> ceanderson AT dis.umsmed DOT edu
> ++++++++++++++++++++++++
|
|
|