After an upgrade or a new installation of NetBackup 7.1, the hot catalog backup may intermittently fail with a Status Code 2: none of the requested files were backed up. A hotfix to correct this issue is attached to this document.
This condition only applies to Windows Media Servers performing the backup.
A typical catalog backup contains four (4) jobs.
1. The parent job.
2. The DB Staging Job.
3. The DB staging backup job.
4. The image database and legacy databases job.
The second job or DB staging job will complete successfully, however the third job may fail which in turn fails the parent.
The Image Database and legacy database job is not affected by this condition and should complete successfully.
From the all logs report:
"E:\Program Files\Veritas\NetBackup\Bin\admincmd\bperror" -all -U
TIME SERVER/CLIENT TEXT
03/02/2011 09:02:45 master_server/master_server catalog backup exited with status 2
(none of the requested files were backed up)
09:02:41.500 [828.4492] <2> get_long: (1) cannot read (byte 1) from network: An existing connection was forcibly closed by the remote host.
09:02:41.500 [828.4492] <16> dbc_get_string: Read of file list info failed
09:02:41.500 [828.4492] <16> bsa_ntBackupThread: WSA error returned from closesocket() nameSock: 10038
09:02:41.500 [828.4492] <16> bsa_ntBackupThread: ERR - backup failed: 23 <socket read failed>
09:02:42.140 [828.6400] <16> bsa_a_backup_completed: ERR - thread <4492> backup failed: 23 <socket read failed>
09:02:43.140 [828.6400] <4> ASA_XBSA_file_backup: All backup jobs have failed.
09:02:43.140 [828.6400] <16> do_online_nbdb_backup: Error backing up files in E:\Program Files\Veritas\NetBackupDB\staging
09:02:43.140 [828.6400] <2> job_monitoring_exex: ACK disconnect
09:02:43.140 [828.6400] <2> job_disconnect: Disconnected
09:02:43.140 [828.6400] <4> empty_staging_dir: Emptying staging directory: E:\Program Files\Veritas\NetBackupDB\staging
09:02:43.140 [828.6400] <16> exec_catalog_backup: exec_asa_database_backup() failed (2)
The bpbrm (NetBackup Backup and Restore Manager) process is closing communication links before the successful completion of the backup.
1. To work around the problem, use a UNIX storage unit to perform the hot catalog backup.
Also note that Microsoft fix KB971383 should also be installed if it applies to your Windows version:
Data loss occurs when the Winsock "recv" function returns 0 bytes if both the client-side and the server-side applications run on the same computer that is running Windows Server 2003
All fixes included in this bundle are included in the following release:
- NetBackup 7.1 Maintenance Release 1 (18.104.22.168)
Note: This TechNote contains legacy information only. This hotfix is no longer publicly available, as its fixes are included in a more recent NetBackup release. If this issue is experienced, the supported resolution is to upgrade NetBackup to the latest version and apply the latest maintenance release.
Symantec Bug ID: 2304611
Installation Location: Master Server
(ET2304611) Hot Catalog Backup fails with Status Code 2
Note: This package is intended to address a specific condition or issue within an environment which meets the criteria documented above. DO NOT install this package if your environment is not experiencing the specific issue or does not match the criteria in which the issue could occur.
Please follow the EEB Installer instructions available on http://www.symantec.com/docs/TECH64620
Please choose the appropriate platform after download:
eebinstaller.2304611.1.AMD64.exe Windows x64
eebinstaller.2304611.1.x86.exe Windows x86
3498054022 1331712 AMD64/bpbrm.exe
2617649460 995328 x86/bpbrm.exe
Recommended service state:
Stop the services on the NetBackup Master before applying
Microsoft Windows Server 2003 Standard x64 with SP2
Microsoft Windows Server 2003 R2 Standard x86 with SP2
Note: This condition is limited to only Windows Servers that perform the hot catalog backup.