Problem 1:

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

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.

______________________________________________________________________________________________________________
Problem 2:
NetBackup SQL backups fail with status code 2 if initiated from the master. User based backups initiated from the client work
fine.
Error Message

Consult the DBCLIENT log on the SQL client:

13:54:48.523 [2140.7224] <16> OpenParmFile: ERR - Failed trying to get read access to P:\Program
Files\Veritas\NetBackup\DbExt\MsSql\full.bch 13:54:48.524 [2140.7224] <1> OpenParmFile: CONTINUATION: - The system cannot find the
file specified. 13:54:48.524 [2140.7224] <4> CDBbackmain::dbbackup: INF - Results of executing
Cause

This can occur if the batch (*.bch) file as named on the file system of the client does not accurately match the batch file name configured in the
NetBackup policy.
For example, consider a scenario where Windows Explorer on the client is configured with the option to 'Hide extensions for known file types.'
There is the potential that the file, as viewed in Windows Explorer, would be named something like:
Full.bch
However, since *.bch is a 'known' file type, there is a 2nd .bch attached to the filename that is not visible in Windows Explorer. Thus, the actual
name of the file is not 'Full.bch' but is instead:
Full.bch.bch
If the Backup Selection in the policy is configured to use Full.bch, the backup will fail with a status 2 as outlined above.

Solution

Rename the batch file to have only one extension (Full.bch rather than Full.bch.bch) or correct the name as configured in the NetBackup policy.
_________________________________________________________________________________________________________________________
Problem 3:

STATUS CODE 2: NetBackup 7.x catalog backup fails with status 2 (none of the
requested files were backed up) reported
Problem

After upgrading to 7.0, NetBackup Catalog Backups fail with status code 2 (none of the requested files were backed up) due to an error
validating NBDB backup in the staging directory.

Error Message

Messages similar to the following may be seen in the job details:

7/18/2010 7:50:50 AM - Info bpdbm(pid=3808) staging relational database files for catalog backup
7/18/2010 7:50:50 AM - Info bpdbm(pid=3808) staging NBDB backup to E:\Veritas\NetBackupDB\staging
7/18/2010 7:50:53 AM - Info bpdbm(pid=3808) done staging NBDB backup to E:\Veritas\NetBackupDB\staging
7/18/2010 8:18:07 AM - Info bpdbm(pid=3808) validating NBDB backup in E:\Veritas\NetBackupDB\staging
7/18/2010 8:18:08 AM - Error bpdbm(pid=3808) error validating NBDB backup in E:\Veritas\NetBackupDB\staging

none of the requested files were backed up(2)

Database validation failure messages may be found in the bpdbm log. For example:
10:28:00.828 [4240.6352] <16> validate_database: Database validation failed for database NBDB

Cause

To determine if the issue is caused by the existence of a NBDB.m.mlg file within the staging directory, view the staging directory after the
catalog backup and look for the file NBDB.m.mlg.
The NetBackup mirror log name convention is NBDB.m.log. The default Sybase mirror naming convention is <db>.m.mlg. When a new
catalog backup is initiated, NetBackup cleans the staging directory only for the files NetBackup recognizes...which is why NBDB.m.mlg was
left behind. The next Catalog Backup validation will fail due to the existence of the NBDB.m.mlg file.

Solution

Remove mirroring of the NBDB.db by running:

Windows: dblog -r "<install path>\NetBackupDB\data\NBDB.db"
UNIX: /usr/openv/db/bin/dblog -r /usr/openv/db/data/NBDB.db
Example:
E:\Veritas\NetbackupDB\win64>dblog -r "E:\Veritas\NetBackupDB\data\NBDB.db"
SQL Anywhere Transaction Log Utility Version 11.0.1.2250
"E:\Veritas\NetBackupDB\data\NBDB.db" is using log file "NBDB.log"

"E:\Veritas\NetBackupDB\data\NBDB.db" was using log mirror file "NBDB.m.mlg"

"E:\Veritas\NetBackupDB\data\NBDB.db" is now using no log mirror file
Transaction log starting offset is 016553580528
Transaction log current relative offset is 0008608506
After restarting NetBackup, run backups and then confirm that the transaction log NBDB.log is growing in size but not the .m.mlg mirror.
After confirming that the .m.mlg mirror is not growing in size, delete it.
Workaround:
If the solution above is unfeasible, please contact Symantec technical support, referencing this document ID and Etrack 2110798 to obtain a fix
for this issue.
____________________________________________________________________________________________________________________
Problem 4:

GRT enabled backups complete with status code 1 (partially successful) and Nbfsd
shows mkdir failed (2)
Problem

When using the Active Directory or Exchange Granular Restore option, backups complete with status code 1 (Partial Success). The message
"Exchange granular restore from this image may not work" occurs in the Activity Monitor Job Details. NBFSD log on the Media Server will
show the following 'mkdir failed (2) - D:\NBU\temp/nbfsd_ivfs_tempfiles/ivfs__7060_0004'

Error Message

Activitiy Monitor Job Detailed Status will show:

"Exchange granular restore from this image may not work" and "the requested operation was partially successful(1)" Status 1
Nbfsd Log on Media Server showing:
16:24:51.301 [7060.11988] <4> nfs3_mkdir: MKDIR REQUEST _vv_MOHE-02-BE050 mode 0755, atime 1334928290+835853900, mtime
1334928290+835853900 /NBUFS_A_559FEB23CED32B69_000/backups/mohe-02-be05/allusers/full/1334833077
16:24:51.301 [7060.11988] <2> get_pre_op_attr: for id 2/1: size 8192, time m 1334928291+1, c 1334928290+0, tarino
16:24:51.301 [7060.11988] <2> vfs::vfs: new vfs 0000000001DE9CE0
16:24:51.301 [7060.11988] <16> tmpfs::tmpfs: mkdir failed (2) - D:\NBU\temp/nbfsd_ivfs_tempfiles/ivfs__7060_0004
16:24:51.301 [7060.11988] <16> tmpfs::tmpfs: THROWING 2 mkdir failed
*Bpgetconfig on Media Server:
C:\Program Files\Veritas\netbackup\bin\admincmd\bpgetconfig" -g Media_Server_Name -L shows:
NBFSD_STAGING_DIR = D:\NBU\temp
*Registry on the Media Server also shows:
HKEY_LOCAL_MACHINE/Software/VERITAS/NetBackup/CurrentVersion/Config
NBFSD_STAGING_DIR = REG_SZ = "D:\NBU\temp"

Cause
The Nbfsd process required for Granular (GRT) to function uses a Temporary Staging area to store temporary files. The default location will go
to %install_path%\Netbackup\Temp. If this directory does not exist or the location has moved using the NBFSD_STAGING_DIR registry
workaround, or if NetBackup does not have access to this location then the Nbfsd process will fail causing the NetBackup Job to complete with a
status 1. This only affects the Granular part of the job and the non Granular data will still be recoverable.

Solution

Make sure the NBFSD staging path exists on the Media Server and is writtable by NetBackup.
Check the path either using the bpgetconfig command or for NBU_STAGING_DIR in the following registry key
HKEY_LOCAL_MACHINE/Software/VERITAS/NetBackup/CurrentVersion/Config on the Media Server

Applies To
This affects all GRT enabled backups where the NBFSD staging area no longer exists