Scribd
Upload
123 views

Code 12

Three problems are described where NetBackup backups or restores fail with Status Code 12 (file open failed). The first involves SAP backups failing after upgrading NetBackup versions. The second is hot catalog backups failing due to improper permissions. The third is Lotus Notes restores with transaction log recovery failing when initiated from a different OS master server. All three provide troubleshooting steps like checking permissions and log files, with resolutions like changing file ownership or initiating restores directly from the client.

Uploaded by

subhrajitm47
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
123 views

Code 12

Three problems are described where NetBackup backups or restores fail with Status Code 12 (file open failed). The first involves SAP backups failing after upgrading NetBackup versions. The second is hot catalog backups failing due to improper permissions. The third is Lotus Notes restores with transaction log recovery failing when initiated from a different OS master server. All three provide troubleshooting steps like checking permissions and log files, with resolutions like changing file ownership or initiating restores directly from the client.

Uploaded by

subhrajitm47
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Problem

STATUS CODE 12: NetBackup SAP backups fail with NetBackup Status Code 12 (file open failed) after upgrading from NetBackup 4.5 to NetBackup 6.0.

Error
file open failed

Solution
Overview: NetBackup SAP backups fail with NetBackup Status Code 12 (file open failed) after upgrading from NetBackup 4.5 to NetBackup 6.0. Troubleshooting: Review the permissions on the backint binary (/usr/openv/netbackup/bin/backint). Log files: The backint log file contains the following:
08:55:21.113 [16845] <4> backint_monitor_log: [16846.00] Could not open progress file /oracle/AGP/sapscript/backint_dir/.backint.log.0.1185803715.16845 for write. 08:55:21.113 [16845] <4> backint_monitor_log: [16846.00] EXIT STATUS 12: file open failed

Resolution: Changed the owner of the /usr/openv/netbackup/bin/backint binary on the SAP client to the database administrator account.

Problem
STATUS CODE 12: Hot catalog backup fails with a NetBackup Status Code 12 (file open failed).

Error
file open failed

Solution
Overview: Hot catalog backup fails with a NetBackup Status Code 12 (file open failed).

Troubleshooting: This has been known to occur if the user_ops directory does not have proper permissions.

Log files: Activity Monitor


4/14/2008 11:01:32 AM - Error bprd(pid=3688) Unable to write progress log </E/VERITAS/NetBackup/Logs/user_ops/dbext/logs/vxbsa.1208185284.6800.8056.pro g.pcb_std> on client backup01. Policy=Online_Catalog Sched=Full 4/14/2008 11:01:32 AM - Error bprd(pid=3688) CLIENT backup01 POLICY Online_Catalog SCHED Full EXIT STATUS 12 (file open failed)

Resolution: Review the permissions on the <install_path>\veritas\netbackup\logs\user_ops directory. If the user_ops directory does not have the correct permissions, add the group "Everyone" with full permissions to the directory

Problem
A master-initiated NetBackup for Lotus Notes restore with full or point-in-time recovery fails with Status Code 12

Error
00/00/00 00:00:00 AM: [789]: Could not open progress file C:\Program Files\VERITAS\NetBackup\logs\user_ops\user\logs\NBWIN001 for write. 00/00/00 00:00:00 AM: [789]: EXIT STATUS 12: file open failed

Solution
Background: A Lotus Domino transaction log recovery may fail if the restore of the logged Lotus Notes

database was initiated from the NetBackup master server whose operating system is different from the client's (i.e., Unix vs. Windows), or if NetBackup is installed in different paths on either system. The issue involves passing the progress log path to bprestore when switching from "Restore" to "Recovery." The restore phase of the job runs at the machine that initiates the job. The recovery phase always runs on the client. If the NetBackup installation path on the master server is the same as that of the client system, the master-initiated restore of a logged Lotus Notes database may result in a successful transaction log recovery. However, if the NetBackup installation path is different between the initiating host and the client, bprestore cannot locate the progress log and the recovery phase of the restore fails. Solution: Initiate restores of logged Lotus Notes databases from the "Backup, Archive and Restore" program on the client.

Problem
GENERAL ERROR: NetBackup Exchange backups of Exchange 2000/2003 exit with Status Code 12. The \netbackup\logs\bpbkar log shows errors that would indicate the Exchange services are not running.

Error
EXCHANGE 0xC7FF0007: Unable to perform the backup. Either you are not connected to the specified backup server or the service you are trying to backup is not running.

Solution
Overview: Exchange backups fail, and indicate the Exchange server is not running, when it is running. Troubleshooting: Please look for the following log messages: Log Files: The bpbkar log file on the client shows an error similar to the following:
FTL - NetBackup Exchange Session initiation failed: EXCHANGE 0xC7FF0007:

Unable to perform the backup. Either you are not connected to the specified backup server or the service you are trying to backup is not running.

or
ERR - NBExBeginBackupDb() HrBackupPrepare() [Exchange DS Database] failed EXCHANGE 0xC7FF0007: Unable to perform the backup. Either you are not connected to the specified backup server or the service you are trying to backup is not running.

Resolution: Further review of the bpbkar log shows the Exchange 5.5 directives, and not the correct Exchange 2000/2003 directives were specified in the policy. Once the directives were correctly specified in the Backup Selection tab of the policy, the backups completed successfully.

You might also like