Example: Restarting a failed NetBackup for SAP backup job (Windows)
This example shows how to restart a failed backup job. In this example, assume the following:
The backup job was deliberately cancelled from the activity manager. In a real user case, a job might fail for different reasons.
You enabled checkpoint (the option in the policy).
You ran the backup according to the following brbackup command:
brbackup -d util_file -t offline -m all -c force
The following is an excerpt from the output log:
BR0280I BRBACKUP time stamp: 2006-02-28 21.07.59 BR0057I Backup of database: SUD BR0058I BRBACKUP action ID: bdsbecnl BR0059I BRBACKUP function ID: aff BR0110I Backup mode: ALL BR0077I Database files for backup:
C:\oracle\SUD\origlogA\log1_m1.dbf C:\oracle\SUD\origlogB\log2_m1.dbf C:\oracle\SUD\origlogA\log3_m1.dbf C:\oracle\SUD\origlogB\log4_m1.dbf C:\oracle\SUD\saparch\cntrl\cntrlSUD.dbf
BR0061I 29 files found for backup, total size 853.604 MB
The previous output log shows the 29 files for backup. brbackup calls the NetBackup SAP agent for backup.
In this example, we have configured the checkpoint frequency for 5 minutes. By the time first checkpoint was taken (that is, in the first 5 minutes), 13 files were backed up. The user killed the job from the NetBackup activity monitor after NetBackup took the first checkpoint. backint returned #SUCCESS messages to brbackup for 13 files that were backed up. For the files that were yet to be backed up, backint retuned #ERROR. The following are the output messages from the brbackup log:
BR0280I BRBACKUP time stamp: 2006-02-28 21.08.04 BR0229I Calling backup utility with function 'backup'...
BR0278I Command output of 'backint.exe -u SUD -f backup -I C:\oracle\SUD\sapbackup\.bdsbecnl.lst -t file -p C:\oracle\ora920\dbs\initSUD.utl -c':
*******************************************************************
Program: backint 6.5 Input File: C:\oracle\SUD\sapbackup\.bdsbedhj.lst Profile: C:\oracle\ora920\dbs\initSUD.utl
Function: BACKUP Backup Type: BACKUP_FILE ******************************************************************* BR0280I BRBACKUP time stamp: 2006-02-28 21.15.50
#FILE..... C:\oracle\SUD\sapdata1\btabd_1\btabd.data1
#SAVED.... VXF1141141105 BR0280I BRBACKUP time stamp: 2006-02-28 21.15.50
#FILE..... C:\oracle\SUD\sapdata2\btabi_1\btabi.data1
#SAVED.... VXF1141141105 …. …. BR0233E Backup utility has reported an error while saving file
C:\oracle\SUD\saparch\cntrl\cntrlSUD.dbf
******************************************************************* BR0280I BRBACKUP time stamp: 2006-02-28 21.15.50
BR0279E Return code from 'backint -u SUD -f backup -I C:\oracle\SUD\sapbackup\.bdsbecnl.lst -t file -p C:\oracle\ora920\dbs\initSUD.utl -c': 2
BR0232E 13 of 29 files saved by backup utility BR0280I BRBACKUP time stamp: 2006-02-28 21.15.50 BR0231E Backup utility call failed BR0280I BRBACKUP time stamp: 2006-02-28 21.15.52 BR0304I Starting and opening database instance SUD ... BR0280I BRBACKUP time stamp: 2006-02-28 21.16.00 BR0305I Start and open of database instance SUD successful BR0056I End of database backup: bdsbecnl.aff 2006-02-28 21.15.50 BR0280I BRBACKUP time stamp: 2006-02-28 21.16.00 BR0054I BRBACKUP terminated with errors
You can then restart the preceding job with following command:
brbackup -d util_file -t offline -m all -f last -c force
The brbackup command examined the last backup log and found that the backup failed for some files. It writes following messages in the beginning of output log for this session:
BR0051I BRBACKUP 6.40 (22) BR0055I Start of database backup: bdsbedhj.aff 2006-02-28 21.16.35
BR0453W Error message found in C:\oracle\SUD\sapbackup\bdsbecnl.aff:
'BR0233E Backup utility has reported an error while saving file C:\oracle\SUD\sapdata5\datafile.4' BR0453W Error message found in C:\oracle\SUD\sapbackup\bdsbecnl.aff: 'BR0233E Backup utility has reported an error while saving file C:\oracle\SUD\sapdata5\datafile.5'
…. ….
BR0453W Error message found in C:\oracle\SUD\sapbackup\bdsbecnl.aff: 'BR0279E Return code from 'backint -u SUD -f backup -I C:\oracle\SUD\sapbackup\.bdsbecnl.lst -t file -p C:\oracle\ora920\dbs\initSUD.utl -c': 2'
BR0453W Error message found in C:\oracle\SUD\sapbackup\bdsbecnl.aff:
'BR0232E 13 of 29 files saved by backup utility'
BR0453W Error message found in C:\oracle\SUD\sapbackup\bdsbecnl.aff:
'BR0231E Backup utility call failed'
BR0459W Backup C:\oracle\SUD\sapbackup\bdsbecnl.aff terminated with errors
…. …. BR0280I BRBACKUP time stamp: 2006-02-28 21.16.36 BR0057I Backup of database: SUD BR0058I BRBACKUP action ID: bdsbedhj BR0059I BRBACKUP function ID: aff BR0110I Backup mode: ALL BR0077I Database files for backup:
C:\oracle\SUD\origlogA\log1_m1.dbf C:\oracle\SUD\origlogB\log2_m1.dbf C:\oracle\SUD\origlogA\log3_m1.dbf C:\oracle\SUD\origlogB\log4_m1.dbf C:\oracle\SUD\saparch\cntrl\cntrlSUD.dbf
BR0061I 16 files found for backup, total size 283.502 MB BR0091I 13 files were already saved in: bdsbecnl.aff
As the preceding output log shows, 13 files were already backed up. The following is the output of a successful brbackup restart job. This job is the one that backed up the remaining 16 files:
BR0280I BRBACKUP time stamp: 2006-02-28 21.16.41 BR0229I Calling backup utility with function 'backup'...
BR0278I Command output of 'backint -u SUD -f backup -I C:\oracle\SUD\sapbackup\.bdsbedhj.lst -t file -p C:\oracle\ora920\dbs\initSUD.utl
-c': *******************************************************************
Program: backint 6.5 Input File: C:\oracle\SUD\sapbackup\.bdsbedhj.lst Profile: C:\oracle\ora920\dbs\initSUD.utl
Function: BACKUP Backup Type: BACKUP_FILE ******************************************************************* BR0280I BRBACKUP time stamp: 2006-02-28 21.21.38
#FILE..... C:\oracle\SUD\sapdata5\datafile.4
#SAVED.... VXF1141141607 …. …. BR0280I BRBACKUP time stamp: 2006-02-28 21.21.38
#FILE..... C:\oracle\SUD\saparch\cntrl\cntrlSUD.dbf
#SAVED.... VXF1141141607 ******************************************************************* BR0280I BRBACKUP time stamp: 2006-02-28 21.21.38 BR0232I 16 of 16 files saved by backup utility BR0230I Backup utility called successfully