NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 2014

NetBackup status code : 2014
HOWTO104842 | 2014-11-20
How To | CMS-XML

Accelerator job fails with status: 24: socket write failed

Error captured in Activity Monitor Job Details: 12/16/ 2014 2:18:12 PM - end writing 12/16/2014 2:18:17 PM - Info bpbrm(pid=7473) nbclient2.nbulab.symc is the host to backup data from
TECH227138 | 2014-12-16
Technical Solutions | CMS-XML

VMware restore failing with "VMware policy restore error(2820)" due to timeout in bptm child pid "wait for child pid #### timeout"

Error in the Detail Status: 11/25/ 2014 11:29:10 AM - Info tar32(pid=10124) INF - Transport Type = nbd 11/25/2014 11:29:33 AM - Info tar32(pid=10124) INF - Transport Type = nbd
TECH227068 | 2014-12-12
Technical Solutions | CMS-XML

VMWare Application State Capture backup fails with the following error: host is unreachable

Job Details 6/25/ 2014 4:43:54 PM - begin Application State Capture, Application State Capture Status 47
TECH194457 | 2014-12-03
Technical Solutions | CMS-XML

NetBackup backups intermittently fail with status 83 when writing to a Media Server Deduplication storage unit hosted on Windows 2012 R2 with a "Teredo Tunneling pseudo-interface" and the Windows firewall disabled.

will show bptm exiting with status 83. The client process may exit with a status 83, status 6, or other status depending on client type and exactly when in the process flow the failure occurs. 06/30/ 2014 18:38:54 - Critical bptm (pid=5184) sts_get_lsu_prop_byname on LSU PureDiskVolume failed: 2060038 no such device 06/30/2014 18:38:54 - Critical bptm (pid=5184) Invalid storage device: PureDiskVolume no such device
TECH223550 | 2014-12-05
Technical Solutions | CMS-XML

Accelerator backup produces Status 1 due to: WIN32 13: The data is invalid

One or multiple instances of the following message is observed in Activity Monitor Job Details resulting in a Status 1: 11/25/ 2014 9:01:03 PM - Error bpbrm(pid=634) from client MyClient: ERR - failure reading file
TECH226852 | 2014-12-09
Technical Solutions | CMS-XML

Exchange Backup using VMware Application Protection option fails with status 1

20/11/ 2014 11:59:39 AM - Info nbjm(pid=30914) starting backup job (jobid=17301) for client msexchange.nbulab.local, policy msexchange, schedule FULL
TECH226480 | 2014-11-19
Technical Solutions | CMS-XML

All virtual machine backups failing with Status 4239

The NetBackup Activity monitor job details for the snapshot jobs shows the following indicating an issue logging in to the vCenter server: 11/19/ 2014 2:13:46 PM - snapshot backup of client vm_name using method vmware_v2 11/19/2014 2:13:46 PM - Info bpbrm(pid=6844) INF - vmwareLogger: LoginAPI: sym_vmc_error: soap_error
TECH226472 | 2014-11-19
Technical Solutions | CMS-XML

Exchange 2013 Mailbox Restore fails with Error "ERR - Exchange 2013 GRT restores require the Exchange Credentials to be configured in the NetBackup Client Host Properties." Status code 103 and status code 2810 are also reported.

8/7/ 2014 9:19:36 AM - Info tar32(pid=0) done. status 103
TECH223647 | 2014-11-18
Technical Solutions | CMS-XML

Backup to Windows master server fails with status code 12 when using long client or policy names

Job Details show that bpbrm detected a premature exit by the client process and that bpbkar exited with status 12. 1/21/ 2014 6:44:28 AM - Critical bpbrm(pid=2516) unexpected termination of client image-level-small-linux-01%20(e38ebe5e-8176-4270-ab37-95126a56d7f7)
TECH214234 | 2014-11-06
Technical Solutions | CMS-XML

MS SQL and other XBSA Backups fail with status code 239 reported after applying the NetBackup 7.5.0.7 maintenance release.

is 300 seconds. Backup started Tue Feb 18 18:39:38 2014 nbpem
TECH215866 | 2014-11-11
Technical Solutions | CMS-XML

When Auto Image Replication is configured in NetBackup 7.6.0.x, import jobs may fail intermittently with a status code 226 (the entity already exists) reported.

Document History: August 8, 2014 : Initial publication September 8, 2014: Added additional hotfix for Appliances
TECH223243 | 2014-11-10
Technical Solutions | CMS-XML

NDMP backup behavior change in 7.6 causing backup failures with status code 25.

10/20/ 2014 12:00:02 - begin writing
TECH225572 | 2014-11-11
Technical Solutions | CMS-XML

VMware Backup getting snapshot error encountered (156)and status: 4207: Could not fetch snapshot metadata

10/21/ 2014 13:43:33 - Info bpfis (pid=1392) done. status: 4207
TECH225781 | 2014-11-06
Technical Solutions | CMS-XML

A backup of a large DFSR data set intermittently finishes with Status 1

The Activity Monitor shows this message in the Job Details, one time for every Replicated Folder experiencing a problem: 10/2/ 2014 4:12:53 PM - Warning bpbrm(pid=8686) from client fileserver1: WRN - can t open object: Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\Data (BEDS 0xe000fedd: A failure occurred accessing the object list.)
TECH225512 | 2014-10-20
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?