Status Code: 5

The restore failed to recover the requested files

This Status Code is a general indication that a restore has failed. This can be due to any number of reasons. Initially, it is important to view the detailed status of the failed restore job in Activity Monitor for a more specific reason on why the job has failed. Then, check the All Log Entries or Problems reports in the Administration Console for additional information on the failure. It should then be possible to follow the recommended troubleshooting procedures for that particular error. If the specific problem still hasnt been determined, view the relevant process logs below for the most detailed and accurate information on why the restore failed. If backups complete successfully for the client in question, then the cause of the failure is more likely to be configuration oriented (Section 1). For Database related restore issues, it is often necessary to consult the process logs for further data on why the restore fails ( Section 2).

Status 5

Type of Restore?

Process Logs Process Logs

The NetBackup log paths are Thefollowing following NetBackup log paths used when troubleshooting a restore .

Normal File Restore

Database Restore

are used when troubleshooting a

restore. Master Server Logs UNIX: /usr/openv/Netbackup/logs/bprd Master Server Logs /usr/openv/Netbackup/logs/bpdbm UNIX: /usr/openv/Netbackup/logs/bpsched /usr/openv/netbackup/logs/bprd Windows : /usr/openv/netbackup/logs/bpdbm <install_path>\Netbackup\logs\bprd Windows: <install_path>\Netbackup\logs\bpdbm <install_path>\NetBackup\logs\bprd <install_path>\Netbackup\logs\bpsched

View the Activity Monitors Detailed Status of the Job.

Netbackup Configuration Issues Section 1

<install_path>\NetBackup\logs\bpdbm

Media server Logs UNIX : Server Logs Media /usr/openv/Netbackup/logs/bpbrm UNIX: /usr/openv/Netbackup/logs/bptm /usr/openv/netbackup/logs/bpbrm /usr/openv/Netbackup/logs/bpdm /usr/openv/netbackup/logs/bptm /usr/openv/Netbackup/logs/bpcd /usr/openv/netbackup/logs/bpdm Windows : /usr/openv/netbackup/logs/bpcd <install_path>\Netbackup\logs\bpbrm Windows: <install_path>\Netbackup\logs\bptm <install_path>\NetBackup\logs\bpbrm <install_path>\Netbackup\logs\bpdm <install_path>\NetBackup\logs\bptm <install_path>\Netbackup\logs\bpcd

View the All Log Entries and Problem Reports within the Admin Console

Database Restore Issues Section 2

Netbackup Configuration Issues Section 1

<install_path>\NetBackup\logs\bpdm

Client Logs <install_path>\NetBackup\logs\bpcd UNIX: /usr/openv/Netbackup/logs/bpbkar Client Logs /usr/openv/Netbackup/logs/bpcd UNIX: /usr/openv/Netbackup/logs/tar /usr/openv/netbackup/logs/bpbkar Windows : /usr/openv/netbackup/logs/bpcd <install_path>\Netbackup\logs\bpbkar /usr/openv/netbackup/logs/tar <install_path>\Netbackup\logs\bpcd <install_path>\Netbackup\logs\tar Windows:

Note: The following process logs, introduced in VERITAS NetBackup 6.0, may also contain error information on this issue: All Servers: PBX Master Server: nbpem, nbjm EMM Server: nbrb, nbemm The vxlogview utility is used to view these logs. Vxlogview is located in the following directory: UNIX: /usr/openv/netbackup/bin/ Windows: <install_path>\NetBackup\bin Please see the VERITAS NetBackup 6.0 Troubleshooting Guide for further information on using the vxlogview utility to view these logs.

<install_path>\NetBackup\logs\bpbkar <install_path>\NetBackup\logs\bpcd <install_path>\NetBackup\logs\tar

Status Code: 5 The restore failed to recover the requested files

Page 1 of 9

Table of Contents
1 NetBackup Configuration...............................................................................................3 1.1 Restore Configuration...............................................................................................3 1.1.2 Destination Client..............................................................................................3 1.2 Server List.................................................................................................................3 1.3 Media Server Configuration.....................................................................................4 2 Database Agent Troubleshooting....................................................................................5 2.1 NetBackup for Microsoft Exchange Server...............................................................5 2.1.1 Exchange Services down...................................................................................5 2.1.2 Exchange Database is not dismounted................................................................5 2.1.3 Logical Store Name does not match the original................................................5 2.1.4 The Mailbox name no longer exists....................................................................5 2.2 NetBackup for Microsoft SQL Server.......................................................................6 2.2.1 Client Read Timeout not set high enough..........................................................6 2.2.2 Other users are still connected to the database..................................................6 2.2.3 Folder structure has not been created..................................................................6 2.3 NetBackup for Lotus Notes.......................................................................................6 2.3.1 Restore initiated from an Administration console.................................................6 2.4 NetBackup For Oracle..............................................................................................7 2.4.1 Rman Log ..........................................................................................................7 2.5 NetBackup for SAP ..................................................................................................7 2.6 NetBackup for DB2...................................................................................................8 2.7 NetBackup for Informix............................................................................................8 3 Links...............................................................................................................................8

Status Code: 5 The restore failed to recover the requested files

Page 2 of 9

1 NetBackup Configuration
1.1 Restore Configuration
If settings in the Backup, Archive Restore GUI are set incorrectly, a Status 5 can occur. If backups have recently worked for the client in question, the issue may simply be a NetBackup configuration problem. Below are the most common configuration options that cause a Status 5 error if set incorrectly.

1.1.1 Destination Path

If the destination path must be changed, ensure that this destination restore path is typed with the proper path and syntax. UNIX example: /usr/restore Windows example: c:\restore NetApp NDMP host example: /vol/vol1/restore Regardless of the destination path, check the ownership and permissions on directories where files will be restored. For restores of UNIX and Windows Clients, the bpcd daemon/NetBackup Client Service must have access to the directory structure where the files will be restored to. Otherwise, a status 5 will occur.

1.1.2 Destination Client

Ensure that the destination client name has been specified properly in the Backup, Archive, and Restore console. To access the destination client settings, do the following: Java console: Click Actions > Specify NetBackup Machines -> Destination Client Windows console: Click File > Specify NetBackup Machines -> Destination Client

1.2 Server List

Verify that the NetBackup Master and Media Servers hostname are in the server list on the Client. The Master and Media Server may be the same host. Follow the appropriate platform-specific instructions to verify that the Master or Media Servers name(s) are in the Clients server list. UNIX Machines Edit the /usr/openv/netbackup/bp.conf file and ensure that there is a SERVER= line for any Master and Media Servers that connect to the Client. The Master Server name must be the first SERVER entry in this server list, followed by an entry for any Media Servers that will connect to the host. Example bp.conf excerpt: SERVER = NBUMASTER SERVER = NBUMEDIA01 SERVER = NBUMEDIA02
Status Code: 5 The restore failed to recover the requested files

Page 3 of 9

NetWare Clients The instructions for Netware are nearly the same. Add a SERVER entry in the Sys\openv\netback\bp.ini file as needed. Windows Clients Add server entries on Windows Clients by doing the following: 1. Open the Backup, Archive, and Restore interface on the client. 2. Select File > Specify NetBackup Machines and Policy Type. 3. Select the Servers tab. 4. Verify that all Master/Media Server(s) are added to this server list, and that the Master Server is set as current. 5. Click OK and exit Backup, Archive and Restore. Note for all platforms: It may also be necessary to perform this same procedure on the Media Server that is performing the restore. Incorrect server list configuration on a Media Server can also cause restore issues. If server entries are modified on a NetBackup Master Server, it is necessary to stop and restart NetBackup Services/processes. Services or processes do not need to be restarted on a Media Server or Client after updating the server list.

1.3 Media Server Configuration

If the Media Server being used for restore is different from the Media Server that wrote the backup, use Media Host Override. This tells NetBackup which Media Server will perform the actual read operation for the restore. This sort of scenario is common in disaster recovery environments where the original Media Server is not available. UNIX Details: Edit the Master Servers /usr/openv/netbackup/bp.conf file and add the FORCE_RESTORE_MEDIA_SERVER directive. Indicate the name of the Media Server that wrote the tape, then the Media Server that will be reading the tape for the restore. Example:
FORCE_RESTORE_MEDIA_SERVER = original_media_svr_name new_media_svr_name

Windows Details: The media host override settings can be found under the General Server section of the Master Servers host properties.

Status Code: 5 The restore failed to recover the requested files

Page 4 of 9

2 Database Agent Troubleshooting

NetBackup will report a Status 5 upon any failure in the restore process when restoring a database. For further information about the reason behind the failure, log analysis will need to take place. Within one of the NetBackup logs will be one or more actual exit status codes or errors. Once the root status code is found, more details about the failure will be known. Below are the logs for each database type that should reveal the actual status code or specific cause. In addition, it is recommended to enable the process logs noted in the flowchart above as well.

2.1 NetBackup for Microsoft Exchange Server

For Exchange restore issues, enable the following logs to analyze the root cause/error: Exchange Server:
<install path>\Veritas\Netbackup\logs\tar

NetBackup Media Server:

<install path>\Veritas\Netbackup\logs\bpbrm <install path>\Veritas\Netbackup\logs\bptm

Common causes for a Status Code 5 on Exchange restore are:

2.1.1 Exchange Services down

All Exchange 200x Services must be up and running for the restore to finish completely.

2.1.2 Exchange Database is not dismounted

When performing an Exchange 200x restore, the Store must be dismounted prior to a restore attempt. In addition, if the Store is not being restored to its original location, view the properties of the Exchange Database Store that is being restored and check This database can be overwritten by a restore.

2.1.3 Logical Store Name does not match the original

When doing an alternate client restore of an Exchange 200x Store, the logical store name must match the original. If you are attempting to restore a database named Mailbox Store (Server), the new database created must also be named Mailbox Store (Server). In addition, view the properties of the Store that is being restored and check the box This database can be overwritten by a restore.

2.1.4 The Mailbox name no longer exists

The Exchange mailbox must exist prior to attempting the restore.

Status Code: 5 The restore failed to recover the requested files

Page 5 of 9

2.2 NetBackup for Microsoft SQL Server

For SQL restore issues, enable the following logs to analyze the root cause/error: Microsoft SQL Server: <install path>\Veritas\Netbackup\logs\dbclient NetBackup Media Server: <install path>\Veritas\Netbackup\logs\bpbrm <install path>\Veritas\Netbackup\logs\bptm For more information on the restore failure, view the Job Monitor on the NetBackup MSSQL Client GUI and review the verbose listing of the job failure. Often, the monitor will list the exact problem of the failure.

2.2.1 Client Read Timeout not set high enough

When Microsoft SQL Server 7.0/2000 begins to restore a database that does not exist, the physical database files are created. With a larger database, this can take some time to occur. Check the Client Read Timeout setting on the SQL Client, in the Clients Host Properties under timeouts. Increase this from the default of 300 when dealing with a larger database restore.

2.2.2 Other users are still connected to the database

In order to restore a Microsoft SQL Server 7.0/2000 database, NetBackup must be able to obtain exclusive use prior to the restore. Check for any users connected to the database, or take the database offline before beginning the restore.

2.2.3 Folder structure has not been created.

All .ndf, .ldf, and .mdf physical file folder paths must already be created in order for the restore to succeed. Verify that all folder paths for the database exist before attempting a restore.

2.3 NetBackup for Lotus Notes

For Lotus Notes restore issues, enable the following logs to analyze the root cause/error: Lotus Notes Server: <install path>\Veritas\Netbackup\logs\tar NetBackup Media Server: <install path>\Veritas\Netbackup\logs\bpbrm <install path>\Veritas\Netbackup\logs\bptm

2.3.1 Restore initiated from an Administration console

There are a few restore limitations specific to Lotus Notes that can result in a Status 5 on a restore. If possible, initiate the restore from the actual Lotus Notes Server. If the restore was initiated as a 'root' user from the Master Server, or from the target
Status Code: 5 The restore failed to recover the requested files

Page 6 of 9

client, the following error may appear in the clients tar log.
ERR - NBLN_Connect() NotesInitExtended() Failed (ErrorCode:0x1ED)

ERR - NBLN_Connect() Cannot connect with Domino as root. INF - TAR EXITING WITH STATUS = 4
Domino does not allow third-party applications to connect to its API as 'root.' Therefore, all restores must be initiated from the restore client (Domino server) while logged onto NetBackup as the Domino administrative user (i.e. the UNIX user running the Domino 'server' process and also owning notes.ini and other files in the Domino Data Directory).

2.4 NetBackup For Oracle

For Oracle restore issues, enable the following logs to analyze the root cause/error: Oracle RMAN RMAN output log - See Section 2.4.1 below. UNIX client:
/usr/openv/netbackup/logs/user_ops/dbext/ /usr/openv/netbackup/logs/dbclient

UNIX Media Server:

/usr/openv/netbackup/logs/bpbrm /usr/openv/netbackup/logs/bptm

Windows Client:
<install path>\Veritas\Netbackup\logs\user_ops/dbext/ <install path>\Veritas\Netbackup\logs\dbclient

Windows Media Server:

<install path>\Veritas\Netbackup\logs\bpbrm <install path>\Veritas\Netbackup\logs\bptm

2.4.1 Rman Log

When Oracles RMAN runs a backup or restore, it creates a log file. If RMAN fails, this log will contain an error stack message. Following this error stack message is a list of RMAN and ORA errors. If an ORA-27xxx series error is listed, NetBackup may have caused RMAN to stop and error. In this case, continue to look in the NetBackup logs noted above for the root cause error or Status Code and follow the appropriate troubleshooting guidelines. If no ORA-27xxx series error is seen, please refer to Oracles support website.

2.5 NetBackup for SAP

For SAP restore issues, enable the following logs to analyze the root cause/error: SAP Database <View the Brrestore log file>
Status Code: 5 The restore failed to recover the requested files

Page 7 of 9

UNIX client
/usr/openv/netbackup/logs/user_ops/dbext /usr/openv/netbackup/logs/backint

UNIX Media Server:

/usr/openv/netbackup/logs/bpbrm /usr/openv/netbackup/logs/bptm

Windows Client
<install path>\Veritas\Netbackup\logs\user_ops\dbext <install path>\Veritas\Netbackup\logs\backint

Windows Media Server:

<install path>\Veritas\Netbackup\logs\bpbrm <install path>\Veritas\Netbackup\logs\bptm

2.6 NetBackup for DB2

For DB2 restore issues, enable the following logs to analyze the root cause/error: UNIX Client
/usr/openv/netbackup/logs/user_ops/dbext /usr/openv/netbackup/logs/bpdb2

UNIX Media Server:

/usr/openv/netbackup/logs/bpbrm /usr/openv/netbackup/logs/bptm

Windows Client:
<install path>\Veritas\Netbackup\logs\user_ops\dbext <install path>\Veritas\Netbackup\logs\bpdb2

Windows Media Server:

<install path>\Veritas\Netbackup\logs\bpbrm <install path>\Veritas\Netbackup\logs\bptm

2.7 NetBackup for Informix

For Informix restore issues, enable the following logs to analyze the root cause/error: Informix Database Logs: Bar debug log Bar_act log UNIX Client:
/usr/openv/netbackup/logs/user_ops/dbext /usr/openv/netbackup/logs/infxbsa

UNIX Media Server:

/usr/openv/netbackup/logs/bpbrm /usr/openv/netbackup/logs/bptm

Windows Client and Media Server: Not applicable.

3 Links
Click here to Search for other documents on Status Code 5
Status Code: 5 The restore failed to recover the requested files

Page 8 of 9

Status Code: 5 The restore failed to recover the requested files

Page 9 of 9