STATUS CODE 2: Microsoft SQL backups fail with a NetBackup Status Code 2 "none of the requested files were backed up"

Article:TECH31961  |  Created: 2004-01-05  |  Updated: 2013-10-23  |  Article URL http://www.symantec.com/docs/TECH31961
Article Type
Technical Solution

Product(s)

Environment

Issue



STATUS CODE 2: Microsoft SQL backups fail with a NetBackup Status Code 2 "none of the requested files were backed up"

Error



Error bpsched(pid=XXXXX) backup of client SQLHOST exited with status 2 (none of the requested files were backed up)

Solution



Overview:
Veritas NetBackup (tm) for MS SQL Server backups fail with status code 2. This normally caused by incorrect login configuration settings for the NetBackup Client service and Set DBMS login parameters.

Troubleshooting:
Enable the dbclient log file on the SQL server.

Veritas NetBackup (tm) SQL Agent is not configured to use Windows NT Authentication.

Log Files:
The dbclient log file on the SQL server shows the following:
16:39:08.015 [3028.2960] <16> OpenParmFile: USER - Failed trying to get read access to C:\Program Files\VERITAS\NetBackup\dbext\mssql\<database_name>
16:39:08.015 [3028.2960] <32> OpenParmFile: ERR - Error in access: 2. The text follows:
16:39:08.015 [3028.2960] <1> OpenParmFile:     CONTINUATION: - The system cannot find the file specified.

Resolution:
Configure Veritas NetBackup (tm) SQL Agent to use Windows NT Authentication.

Before starting, an account that has Local Administrator privileges on the NetBackup SQL client is needed.  Local Administrator rights are necessary to authenticate into the SQL Server instance.  By default, BUILTIN\Administrator has System Administrator role to the SQL server.  Once an account has been created, log off and then log in as the new account.

SQL Client Configuration:
1. Configure the NetBackup client service (Admin Tools\Services) to run as the account that you are logged in as and then restart the service (Figure 1).
Figure 1
 

2. Open the NetBackup MS SQL GUI a prompt to 'set your DBMS Login Parameters' will appear.  Reenter the same account info that the NetBackup client service is running as (Figure 2).
Figure 2
 

3. Choose Actions\Backup\Database and select the database(s) to be backed up, enter the policy name (this is optional) and select 'save for later execution' and then click on OK.  Enter a file name and then save.  If the script is saved in the default location, only the script name is necessary to be referenced in the policy.

4. Client configuration portion is now completed, please perform the next steps from the NetBackup Administration Console.

MS-SQL-Server Policy Configuration:
1. Open\Create a MS-SQL-Server policy.  Verify that the Default-Application-Backup schedule is set to 24 x 7 and add a new schedule type 'automatic backup' and set the start window to the desired schedule in which SQL backups are to be run.
2. On the Clients tab add\verify that the client name is entered correctly.
3. On the Backup Selections tab, enter the name of the backup script that was created on the client (i.e. backup.bch).  NetBackup will look for this script in the default location on the client to run it.

NOTE:  If backing up multiple clients with a single policy then there must be a common script name on each of the clients listed!  The contents of each script will be unique for each client. For example: a policy exists on one SQL client with a script named DailyFull.bch in the default directory of 'C:\Program Files\VERITAS\NetBackup\DbExt\MsSql'.  A month later, another SQL server is added with the above client configuration steps. The .bch file is saved on the new client as DailyFull.bch in the default directory.  At this point, it is only necessary to add the client name to the 'Clients' tab of the MS-SQL-Server policy.  Figure 3 is an example of an MS-SQL-Server policy properly configured to backup multiple clients.
Figure 3
 

NetBackup SQL agent backup configuration is now completed, right click on the policy and choose 'Manual Backup' to test.


Supplemental Materials

SourceError Code
Value02
Descriptionnone of the requested files were backed up

Legacy ID



267869


Article URL http://www.symantec.com/docs/TECH31961


Terms of use for this information are found in Legal Notices