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

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

Article: 100016348
Last Published: 2013-10-23
Ratings: 1 8
Product(s): NetBackup

Problem

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

Error Message

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 SQLServer backups fail with status code 2. This normally caused by incorrect loginconfiguration settings for the NetBackup Client service and Set DBMS loginparameters.

Troubleshooting:
Enable the dbclient logfile on the SQL server.

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

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

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

Beforestarting, an account that has Local Administrator privileges on the NetBackupSQL client is needed.  Local Administrator rights are necessary toauthenticate into the SQL Server instance.  By default, BUILTIN\Administrator has System Administrator role to the SQLserver.  Once an account has been created, log off and then log in as thenew account.

SQL Client Configuration:
1. Configure the NetBackupclient service ( Admin Tools\Services) to run as the account that you arelogged in as and then restart the service (Figure 1).
Figure1
 

2. Open theNetBackup MS SQL GUI a prompt to ' set your DBMS Login Parameters' willappear.  Reenter the same account info that the NetBackup client service isrunning as (Figure 2).
Figure2
 

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

4. Client configuration portion is nowcompleted, please perform the next steps from the NetBackup AdministrationConsole.

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

Note:  If backing upmultiple clients with a single policy then there must be a common scriptname on each of the clients listed!  The contents of each script will beunique for each client. For example: a policy exists on one SQL client with ascript named DailyFull.bch in the default directory of ' C:\ProgramFiles\VERITAS\NetBackup\DbExt\MsSql'.  A month later, another SQLserver is added with the above client configuration steps. The .bch fileis saved on the new client as DailyFull.bch in the defaultdirectory.  At this point, it is only necessary to add the client name tothe ' Clients' tab of the MS-SQL-Server policy.  Figure 3 is anexample of an MS-SQL-Server policy properly configured to backup multipleclients.
Figure 3
 

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


Was this content helpful?