Unable to change expiry date of backup
Hello everyone, I have a problem I hope you can help me with. I'm participating in a disaster recovery test and am responsible for recovering Oracle databases that run on Solaris servers and am referencing the backups on my Windows NetBackup server. My backups go to a local DataDomain (DD) box and are replicated to a DataDomain box at my DR site and to physical tapes which ares stored offsite. Our system is configured so that NetBackup can see both of the DD devices and in theory allows for different retention periods between my local DD versus the remote DD. Due to capacity constraints both DD backups are configured with the same retention period: one week. One more item: In order to mazimize the DD deduplication capabilities, each Oracle database file is backed up seperately - no interleaving of files is allowed.
The problem is that the recovery of my databases takes place after the recovery of our document management system and MS Exchange. _IF_ everything works perfectly, I can get my Oracle restores done before the backups expire however it is easily possible that a problem with some of the restores would delay my database recovery to past the one week backup retention period.
OK, during the disaster recovery test, we disconnect the DataDomain device at the DR site so it appears as if our main office has been destroyed and is unaccessible - this means that I need to be able to restore from just the backups at the remote DataDomain device. I don't want to risk having my backups expire so I want to add a step to the beginning of my disaster recovery documentation where I change the expiration of my backups from 1 week to 3 months. My plan is to make this change while waiting for the other restores to complete. Below is a sample of what I see for backups. Backups with MediaID @aaaae are on the remote DataDomain device.
D:\Program Files\Veritas\NetBackup\bin\admincmd> bpimmedia -policy ORA_PASPROD -client st31bora01 -d 3/6/2013 00:00:00 -e 3/20/2013 00:00:00 -t UBAK -L Backup-ID Policy Type RL Files C E T PC Expires Copy Frag KB Type Density FNum Off Host DWO MPX Expires RL MediaID ------------------------------------------------------------------------------------------------ st31bora01_136363320 ORA_PASPRO UBAK 0 1 N N R 2 13:00 03/25/2013 1 1 31264 Disk - - - inf-srv17 - N 13:00 03/25/2013 0 @aaaac 2 1 31264 Disk - - - inf-srv17 - N 13:00 03/25/2013 0 @aaaae 3 1 31264 RMed hcart 870 27321361 inf-srv17 9 N 13:00 03/25/2013 0 APA083 st31bora01_136363311 ORA_PASPRO UBAK 0 1 N N R 2 12:58 03/25/2013 1 1 288 Disk - - - inf-srv17 - N 12:58 03/25/2013 0 @aaaac 2 1 288 Disk - - - inf-srv17 - N 12:58 03/25/2013 0 @aaaae 3 1 288 RMed hcart 869 27321354 inf-srv17 9 N 12:58 03/25/2013 0 APA083 ... repeated for another 1000+ files
So I don't want to have to build 1000+ commands to change the retention period of each individual backup. The problem is that when I try to alter the retention based on the policy, I get "unable to process". I've tried using both "-ret" and "-d" flags of the bpexpdate without success:
D:\Program Files\Veritas\NetBackup\bin\admincmd> bpexpdate -recalculate -copy 2 -client st31bora01 -policy ORA_PASPROD -ret 3 -sched 2 Are you SURE you want to recalculate expiration dates on all images that meet the following criteria: client st31bora01 policy ORA_PASPROD scheduletype 2 copy 2 retention will be changed to 3(1 month) Continue?(y/n)y unable to process request D:\Program Files\Veritas\NetBackup\bin\admincmd> bpexpdate -recalculate -copy 2 -client st31bora01 -policy ORA_PASPROD -d 04/20/2013 00:00:00 -sched 2 Are you SURE you want to recalculate expiration dates on all images that meet the following criteria: client st31bora01 policy ORA_PASPROD scheduletype 2 copy 2 to expire on 4/20/2013 12:00:00 AM Continue?(y/n)y unable to process request
Does anyone have a recommendation why this isn't working? Any help would be greatfully appreciated.