Status Code: 2

None of the requested files were backed up.

The backup or archive could not backup any files in the file list. This should not occur for standard file system backups. This error code is typically seen with backups using the Lotus Notes or SQL database agents.

Status Code 2: None of the requested files were backed up

Page 1 of 10

Table of Contents
1 Exit Status 2 for File System Backups...................................................................................................... 3 2 NetBackup for Lotus Notes database extension for UNIX........................................................................3 2.1 The directive BACKUP_TRANSACTION_LOGS is in the file list.......................................................3 2.2 A backup of the transaction logs was already active..........................................................................3 3 NetBackup for Microsoft SQL Server database extension for Windows...................................................4 3.1 New installations................................................................................................................................ 4 3.1.1 Using standard SQL Server security............................................................................................ 4 3.1.2 Using integrated SQL Server security.......................................................................................... 5 3.1.3 Hostname resolution problems.................................................................................................... 6 3.1.4 SQL Server in a cluster configuration.......................................................................................... 7 3.1.5 Backup is failing on the master database....................................................................................7 3.1.6 Backup works from client but fails when scheduled by master....................................................7 3.2 The problem began after a 4.5 MP1 (or newer) upgrade of a working installation.............................8 3.3 An existing installation stopped working............................................................................................. 8 3.3.1 The batch file is corrupted or missing mandatory parameters.....................................................9 4 Other NetBackup database agent............................................................................................................. 9 5 Logs to gather for a NetBackup support case........................................................................................... 9 5.1 Lotus Notes on UNIX.......................................................................................................................... 9 5.2 SQL Server on Windows.................................................................................................................... 9 6 Search.................................................................................................................................................... 10

Status Code 2: None of the requested files were backed up

Page 2 of 10

1 Exit Status 2 for File System Backups

This error should no longer occur for file system backups when using a current version of NetBackup (version 4.5 or later). If this error is encountered for a UNIX or Windows file system backup, please open a NetBackup support case and reference this document. For older versions of NetBackup (version 3.4 and prior): This error could occur if the file name ended with a space or a tab. This condition no longer causes an error processing these files in the current release. An exclude list on the client that would exclude all of the files in the file list would cause this condition. The current exit status for this condition is exit status 71. This error could occur if the user account of the backup did not have read permissions on the file. For Windows, this could also be due to attempting to backup a mounted file system using the local system account for the NetBackup Client Service. The current exit status for this condition is exit status 1.

2 NetBackup for Lotus Notes database extension for UNIX

A Status 2 can occur when the Domino archive logs are not enabled or when another backup of the transaction logs is already in progress.

2.1 The directive BACKUP_TRANSACTION_LOGS is in the file list.

The most common reason for this problem is that the directive BACKUP_TRANSACTION_LOGS is in the file list, but the Domino server is not configured to use archive style logging. Archive style logging is required in order to use the BACKUP_TRANSACTION_LOGS directive in the file list. To correct this, enable archive style logging on the Domino server or remove BACKUP_TRANSACTION_LOGS from the backup policy directives list. Example from the UNIX /usr/openv/netbackup/logs/bpbkar/log.<date> file:
<2> : INF - NBLN_GetTransLogStyle() <Exit> TransLogStyle: 0x1 <8> lotus_validate_translog_style: WRN - Transaction Log backup was requested but Archive Logging is not configured (0x1) <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 2: none of the requested files were backed up

Another example from the UNIX /usr/openv/netbackup/logs/bpbkar/log.<date> file:

<2> : INF - NBLN_GetTransLogStyle() <Exit> TransLogStyle: 0x2 <8> lotus_validate_translog_style: WRN - Transaction Log backup was requested but Archive Logging is not configured (0x2)

2.2 A backup of the transaction logs was already active

A Status 2 can be caused by a hung bpbkar processes on the client. Check for a hung backup bpbkar process on the NetBackup client. Kill the backup job with the activity monitor if the job is still running and the client appears to be hung. Kill the bpbkar process on the client if there is no backup job associated with the bpbkar process. Prior to NetBackup version 4.5 MP6 or 4.5 FP6, the backup process would run as the root user. Running this process as root could result in this hung condition if a Lotus database file was corrupt and the Lotus host was also the media server for the backup. This caused conflicts between Domino and NetBackup in the use of shared memory. The Domino server could crash and never reply to the backup agent which is hung waiting for Domino.

Status Code 2: None of the requested files were backed up

Page 3 of 10

Create the touch file /usr/openv/netbackup/NOSHM on the Lotus client and retry the backup. This will disable the use of shared memory. Upgrade NetBackup to version 4.5 MP6 or 4.5 FP6 so that the backup will run as the Domino administrator account. This change was required for compatibility with Domino version 6. The Domino server may have crashed during a backup leaving NetBackup waiting for Domino to reply.

An active backup example from the UNIX /usr/openv/netbackup/logs/bpbkar/log.<date> file:

<2> : INF - NBLN_GetTransLogStyle() <Exit> TransLogStyle: 0x4 <2> : INF - NBLN_ArchiveLogStart() <Enter> <2> : ERR - NBLN_ArchiveLogStart() NSFBeginArchivingLogs() Failed: 0xEAE:Archiving of transaction logs already in progress. <2> : INF - NBLN_ReturnLastErrorString() <Enter> <2> : INF - NBLN_ReturnLastErrorString() <Exit> (Error code:3758) <16> lotus_enumerate_transaction_logs: ERR - Failure when processing Lotus Notes transaction logs: 0xEAE:Archiving of transaction logs already in progress.

3 NetBackup for Microsoft SQL Server database extension for Windows

A Status 2 can occur when SQL authentication did not work or when there are hostname resolution problems. This can be seen with new, upgrade or existing installations.

3.1 New installations

3.1.1 Using standard SQL Server security.
Change the properties of the NetBackup Client service to set the Log On As to a Windows account name. The Windows account name must be mapped to a SQL Server account with backup privileges for the SQL Server. It is recommended to use the local administrator account. Log on to Windows using this account. Start the NetBackup for SQL Server GUI. Go to DBMS login parameters and enter the SQL user account and password that has backup privileges for the database, usually the SQL account sa.

The privileges of the account chosen for the NetBackup Client Service will also be used when performing file system backups, archives and restores for this host. Ensure that the account chosen for the NetBackup Client Service has full privileges for all local and mounted file systems that are to be backed up, archived or restored using a Windows policy. For NetBackup prior to version 4.5 MP1, a User DSN must be created for each database instance. See the NetBackup for Microsoft SQL Server manual for more information. Login failure example for sa user from the Windows logs: <install_path>\VERITAS\NetBackup\logs\dbclient\<date>.LOG (5.0 and later) <install_path>\VERITAS\NetBackup\logs\dbbackup\<date>.LOG (4.5, 3.4)
<4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_3048_3368>, SQL userid <sa>. <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC message. ODBC return code <-1>, SQL State <28000>, Message Text <[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'.> <32> CGlobalInformation::CreateDSN: ERR - Unable to login into SQL instance <ALGOL\> as user <sa> using standard connection

Status Code 2: None of the requested files were backed up

Page 4 of 10

<4> CGlobalInformation::DeleteDSN: INF - SQLConfigDataSource: SQL Server <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keywordvalue pair : DSN=NBMSSQL_3048_3368 <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keywordvalue pair : SERVER=ALGOL <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keywordvalue pair : DESCRIPTION=NetBackup MS SQL Server <32> CDBbackrec::CDBbackrec: ERR - Error 64 has been returned from GetCurrentDSN ... <32> CGlobalInformation::DeleteCurrentDSN: ERR - Error removing ODBC data source name CONTINUATION: - Invalid DSN CONTINUATION: - Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed <4> CGlobalInformation::DSNCleanUp: INF - SQLDataSources did not fetch any ODBC user data source names

Login failure example for SYSTEM user from the Windows logs: <install_path>\VERITAS\NetBackup\logs\dbclient\<date>.LOG ( 5.0 and later) <install_path>\VERITAS\NetBackup\logs\dbbackup\<date>.LOG (4.5, 3.4)
<4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_2620_1580>, SQL userid <SYSTEM>. <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC message. ODBC return code <-1>, SQL State <28000>, Message Text <[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.> <4> CGlobalInformation::ModifyDSN: INF - SQLConfigDataSource: SQL Server . <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC message. ODBC return code <-1>, SQL State <28000>, Message Text <[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'.> <32> CGlobalInformation::CreateDSN: ERR - Unable to login into SQL instance <ALGOL\> as user <sa> using standard connection . <32> CGlobalInformation::DeleteCurrentDSN: ERR - Error removing ODBC data source name CONTINUATION: - Invalid DSN CONTINUATION: - Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed

3.1.2 Using integrated SQL Server security.

Change the properties of the NetBackup Client service to set the Log On As account to a Windows account that has backup privileges for the SQL Server. The account entered in the NetBackup DBMS login parameters is not used. The batch file user id and password are also ignored. The privileges of this account will also be used when performing file system backup for this host. Ensure that the account chosen has backup privileges for the SQL Server and for all local file systems. This only needs to be changed if BUILTIN\Administrators is removed from the logins or is somehow removed from backup operations. If BUILTIN\Administrators was removed from the SQL Logins, add this group back as SQL Administrators for the instance or change the NetBackup Client service as stated above.

Status Code 2: None of the requested files were backed up

Page 5 of 10

Login failure example for sa user from the Windows logs: <install_path>\VERITAS\NetBackup\logs\dbclient\<date>.LOG (5.0 and later) <install_path>\VERITAS\NetBackup\logs\dbbackup\<date>.LOG (4.5, 3.4)
<16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC message. ODBC return code <-1>, SQL State <28000>, Message Text <[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.> <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC message. ODBC return code <-1>, SQL State <28000>, Message Text <[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection.> <32> CDBbackrec::CDBbackrec: ERR - Error 64 has been returned from GetCurrentDSN <32> CGlobalInformation::DeleteCurrentDSN: ERR - Error removing ODBC data source name CONTINUATION: - Invalid DSN CONTINUATION: - Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed <4> CGlobalInformation::DSNCleanUp: INF - SQLDataSources did not fetch any ODBC user data source names

3.1.3 Hostname resolution problems

Ensure that the SQL Server client and NetBackup servers have consistent and correct hostname resolution. Use the NetBackup command bpclntcmd, as documented in the NetBackup Troubleshooting Guide, for help in diagnosing hostname resolution problems. Ensure that the master and all media servers are listed in the clients server list. Also, ensure that the client name used in the NetBackup SQL policy on the master server is the same name used to configure the client and is the name resolved by the NetBackup servers when translating the clients IP address to a hostname. Ensure that the NBSERVER entry in the SQL backup batch file, if it exists, equates to the proper NetBackup master server. Example from the Windows <install_path>\NetBackup\logs\dbclient\<date>.LOG file:
<2> bprd_get_features: Cannot parse product and feature IDs from EXIT STATUS 23 <16> bsa_checkFeatureId: unable to check if feature <33> is licensed <16> bsa_checkFeatureId: Server exit status = 43: unexpected message received

Another example from the Windows <install_path>\NetBackup\logs\dbclient\<date>.LOG file:

<4> serverResponse: 10:43:03 INF - Server status = 230 <16> serverResponse: ERR - server exited with status 230: the specified policy does not exist in the configuration database <16> CreateNewImage: ERR - serverResponse() failed

Another example from the Windows <install_path>\NetBackup\logs\dbclient\<date>.LOG file:

<2> nb_getsockconnected: unable to connect() to MASTER, Connection timed out. <2> bprd_connect: Cannot connect to server MASTER <2> bprd_get_features: bprd_connect(MASTER) failed, cannot connect on socket (25) <16> bsa_checkFeatureId: unable to check if feature <33> is licensed <16> bsa_checkFeatureId: Server exit status = 25: cannot connect on socket <16> VxBSAInit: ERR - The license for the requested feature is not available.

Status Code 2: None of the requested files were backed up

Page 6 of 10

Another example from the Windows <install_path>\NetBackup\logs\dbclient\<date>.LOG file:

<16> readCommFile: ERR - timed out after 900 seconds while reading from C:\Program Files\VERITAS\NetBackup\Logs\user_ops\mssql\logs\0827104084313-22722236-000-000-prg <32> serverResponse: ERR - could not read from comm file <C:\Program Files\VERITAS\NetBackup\Logs\user_ops\mssql\logs\0827104084313-2272-2236-000000-prg> <16> CreateNewImage: ERR - serverResponse() failed

3.1.4 SQL Server in a cluster configuration

Use the virtual SQL Server name as the NetBackup client name in the SQL backup policy. Ensure that the master can properly resolve the virtual name and each physical hostname. Verify that the master can do both forward and reverse hostname resolution of the physical nodes and forward resolution of the virtual SQL Server. The cluster physical names must be recognized as client names in the masters NetBackup domain. The masters altnames database must allow the clusters physical names to browse the virtual SQL Server backup images.

3.1.5 Backup is failing on the master database.

This will occur if the object type of filegroups or files is used when the SQL master database is selected. An object type of database must be used when selecting the master database for backup. Example Windows log entry from: <install_path>\VERITAS\NetBackup\logs\dbclient\<date>.LOG (5.0 and later) <install_path>\VERITAS\NetBackup\logs\dbbackup\<date>.LOG (4.5, 3.4)
<16> Dbbackrec::PerformNBOperation: USER - Operation inhibited by NetBackup for Microsoft SQL Server: Only a full backup can be performed on the master database.

3.1.6 Backup works from client but fails when scheduled by master.
Check path and spelling of the .bch file in the backup policy. Ensure that file specified in the backup policy includes the .bch extension. Example Windows log from the <install_path>\VERITAS\NetBackup\logs\bphdb\<date>.LOG file:
<2> logparams: -sb -rdbms sql_server -S donaldduck -to 300 -c algol-sql-server -s Full -clnt algol -FULL -b algol_1111167317 -jobid 3717 <4> bphdb sync_server: INF - BACKUP START <4> bphdb sync_server: INF - CONTINUE BACKUP message received. <2> bphdb get_filelist: INF - Read filename: <full> <2> bphdb get_filelist: INF - Read filename: <CONTINUE> <4> bphdb.do_launch_ex: INF - Processing f <16> bphdb.CreateProcessForNT: ERR - command failed: none of the requested files were backed up (2) <16> bphdb.do_launch_ex: ERR - exit status : (2) <16> bphdb Exit: ERR - bphdb exit status = 2: none of the requested files were backed up <4> bphdb Exit: INF - EXIT STATUS 2: none of the requested files were backed up

Status Code 2: None of the requested files were backed up

Page 7 of 10

<2> logparams: -sb -rdbms sql_server -S donaldduck -to 300 -c algol-sql-server -s Full -clnt algol -FULL -b algol_1111167519 -jobid 3718 <4> bphdb sync_server: INF - BACKUP START <4> bphdb sync_server: INF - CONTINUE BACKUP message received. <2> bphdb get_filelist: INF - Read filename: <C:\program files\mssql\backup_scripts\full.bch> <2> bphdb get_filelist: INF - Read filename: <CONTINUE> <4> bphdb.do_launch_ex: INF - Processing C <16> bphdb.CreateProcessForNT: ERR - command failed: none of the requested files were backed up (2) <16> bphdb.do_launch_ex: ERR - exit status : (2) <16> bphdb Exit: ERR - bphdb exit status = 2: none of the requested files were backed up

3.2 The problem began after a 4.5 MP1 (or newer) upgrade of a working installation.
Delete User DSNs created prior to the upgrade. User DSNs are now created as needed by the agent. Existing User DSNs must be removed after the upgrade. Do this by deleting the files in: <install_path>\NetBackup\dbext\mssql\dsns <install_path>\NetBackup\dbext\mssql\logins. Edit the existing batch files to remove the DSN entries. Add entries for SQLHOST and SQLINSTANCE (if appropriate). The following log entries can appear if user DSNs are not deleted after the upgrade. Example Windows log entry from: <install_path>\VERITAS\NetBackup\logs\dbclient\<date>.LOG (5.0 and later) <install_path>\VERITAS\NetBackup\logs\dbbackup\<date>.LOG (4.5, 3.4)
<16> CDBbackrec::CDBbackrec: USER - SQL host\instance not available in batch file, registry, or NetBackup\dbext\mssql\DSN

Delete and recreate the existing batch files using the NetBackup SQL GUI if the suggestions above did not completely resolve the problem. Were the production batch files left in the default directory when the previous version was uninstalled? If so, recreate the batch files as this directory is cleared during the uninstallation of the older product. The following log entries can appear if the batch files were removed during the upgrade. Example Windows log entry from: <install_path>\VERITAS\NetBackup\logs\dbclient\<date>.LOG (5.0 and later) <install_path>\VERITAS\NetBackup\logs\dbbackup\<date>.LOG (4.5, 3.4)
<16> OpenParmFile: USER - Failed trying to get read access to C:\Program Files\VERITAS\NetBackup\dbext\mssql\full.bch <32> OpenParmFile: ERR - Error in access: 2. The text follows: CONTINUATION: - The system cannot find the file specified. <4> CDBbackmain::dbbackup: INF - Results of executing <full.bch>: <0> operations succeeded. <0> operations failed.

3.3 An existing installation stopped working

The following directories must be present for the agent to work. They are created by the agent during an installation but are not automatically recreated if they have been deleted.

Status Code 2: None of the requested files were backed up

Page 8 of 10

Recreate these directories if they are missing.

<install_path>\veritas\netbackup\logs\user_ops\mssql\logs <install_path>\veritas\netbackup\logs\user_ops\mssql\jobs

Example Windows log entry if the directories do not exist: <install_path>\VERITAS\NetBackup\logs\dbclient\<date>.LOG (5.0 and later) <install_path>\VERITAS\NetBackup\logs\dbbackup\<date>.LOG (4.5, 3.4)
<32> CProgress::CreateProgress: ERR - Error. Could not access jobs directory: C:\Program Files\VERITAS\NetBackup\Logs\user_ops\mssql\jobs\ <4> CDBbackmain::dbbackup: INF - Results of executing <full.bch>: <0> operations succeeded. <0> operations failed. <32> TerminateJobsFile: ERR - Error generated from CoreWrite writing 1BEGIN 0 1110569504 <32> CDBbackmain::dbbackup: ERR - Error generated while terminating jobs file (TerminateJobsFile)

3.3.1 The batch file is corrupted or missing mandatory parameters.

Create a new batch script from the GUI to resolve this problem.

4 Other NetBackup database agent

This error should not occur for agents other than SQL Server and Lotus Notes. If this error is encountered for a different database agent, please open a NetBackup support case and reference this document.

5 Logs to gather for a NetBackup support case

Logs on UNIX host are located in: /usr/openv/netbackup/logs Logs on a Windows host are located in: <install path>\VERITAS\NetBackup\logs The log directories may need to be created in the above paths. Useful logs will be set to their maximum verbosity before recreating the problem. Logs can grow very large, be sure to allow adequate space for verbose logs if logs are enabled for other directories than those listed below. In the case of Exit Status 2 errors, the logs listed below are relatively small, normally 10s of Kbytes or less for each log for each backup job. For a successful backup, the dbclient log is the only one listed below that is likely to become very large at high verbose settings.

5.1 Lotus Notes on UNIX

Gather the following logs and files for Lotus Notes on UNIX. The /usr/openv/netbackup/logs/bpbkar/log.<date> file. The /usr/openv/netbackup/logs/user_ops/dbext/logs/* files. The /usr/openv/netbackup/bp.conf file. The notes.ini file for each instance or partition. The location of the notes.ini is determined by the LOTUS_NOTES_PATH variable in the clients bp.conf file.

5.2 SQL Server on Windows

Gather the following logs and files for SQL Server on Windows. The <install_path>\NetBackup\logs\bphdb\<date>.LOG file.

Status Code 2: None of the requested files were backed up

Page 9 of 10

The <install_path>\NetBackup\logs \dbbackup\<date>.LOG file for NetBackup 4.5 and earlier) The <install_path>\NetBackup\logs \dbclient\<date>.LOG file. The <install_path>\NetBackup\logs\user_ops\MsSql\logs\* files.

On the SQL Server host, find and run the sqldiag.exe command. This creates a SQLdiag.txt file in the log folder of the SQL Server installation. Gather the SQLdiag.txt, VDI.log, and ERRORLOG from the SQL log directory and forward them to the Support Engineer.

6 Search
Click here to Search for other documents on Status 2
Also, click below to perform a search on the following relevant items: http://support.veritas.com/docs/256684 VERITAS NetBackup (tm) for SQL Server backups fail with "Status 2: none of the requested files were backed up" in the activity monitor when processing the SQL Server "master" database. http://support.veritas.com/docs/264618 When initiating a backup from the master server of a Microsoft SQL database policy using the VERITAS NetBackup (tm) MS SQL client running on Windows 2000 or Windows 2003 32-bit and Windows 2003 64-bit operating system, the backup fails with a status 2. http://support.veritas.com/docs/267870 VERITAS NetBackup (tm) for MS SQL Server backups fail with a status 2 when the number of databases that are being backed up exceeds 32. http://support.veritas.com/docs/247473 VERITAS NetBackup for MS-SQL Server database extension backup fails with Exit Status Code 2. http://support.veritas.com/docs/251375 VERITAS NetBackup for Microsoft SQL Server backups fail with a status 2 in the master server job monitor, and the same backup job fails with a status -1 in the Netbackup for MS SQL Server Client job monitor.

Status Code 2: None of the requested files were backed up

Page 10 of 10