NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

hp-ux 11.31 Itanium backups fail with BPTM Error "External event caused rewind during write"

NetBackup 7.0.1 is not yet fully compatible with the new structures of the Agile paths on hp-ux 11. 31 Itanium edition. As a result, when NetBackup 7.0.1 is installed as a media server and IBM LTO drives are used with the IBM ATDD driver, on closing out the last backup fragment, the ATDD driver will fail to correctly write the End Of Tape (EOT) marker after the empty backup header.
TECH155113 | 2011-12-09
Technical Solutions | CMS-XML

Device configuration status code 31

Device configuration status code 31
HOWTO104574 | 2014-11-20
How To | CMS-XML

NetBackup status code: 31

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

STATUS CODE 31: When running a user initiated backup of a client with NetBackup, a status code 31 occurs.

A user-directed backup from a client fails with a Status 31 . A second backup attempt of the client will finish successfully. This can occur when the NetBackup (tm) Client Service on Windows is not configured to start automatically.
TECH38002 | 2013-10-23
Technical Solutions | CMS-XML

Enterprise Vault backup fails with status code 31 - could not set user id for process

11/02/2011 3:11:06 AM - end Enterprise Vault Resolver, End Notify Script; elapsed time: 00:00:00 Status 31 11/02/2011 3:11:06 AM - end Parent Job; elapsed time: 00:13:02
TECH184574 | 2013-09-24
Technical Solutions | CMS-XML

hp-ux Servers running 11.31 fail to connect with Error "master server request failed ( Status 149); Backup policy may also fail with Status 59.

/usr/openv/netbackup/bin/bpclntcmd -ip client_server_ip_address If all the above outputs come back as expected, it is possible the issue is related to a setting within hp-ux 11. 31 . The option expand_node_host_names may need to be set to 0. As this is the default setting, HP has provided information in regards to the possible incompatibilites.
TECH168260 | 2011-09-29
Technical Solutions | CMS-XML

User initiated backup from client side fails with EXIT STATUS 31

User initiated backup from client side fails with EXIT STATUS 31
TECH87495 | 2010-01-15
Technical Solutions | CMS-XML

Backups of the root file system on hp-ux 11.31 clients fail with error 13

Clients running hp-ux 11. 31 cannot backup the root file system onto a media server running hp-ux. The clients are able to do a root file system back up on Windows and Linux media servers. Other file systems of the hp-ux clients can be successfully backed up on the hp-ux media server.
TECH65101 | 2010-01-08
Technical Solutions | CMS-XML

BUG REPORT: When using the bp or bpadm interface on hp-ux 11.23 or 11.31 systems on Integrity (ia-64) architecture, a DATE ERROR will be returned during attempts to change dates.

Symptoms: On Integrity (ia-64) systems running hp-ux 11v2 (11.23) or 11v3 (11. 31 ), when attempting to change the start and end date range from within the bp or bpadm
TECH63501 | 2009-01-01
Technical Solutions | CMS-XML

SAP backups failing with status 6 due to truncation of client name at 31 characters after upgrading to NBU 6.0

The NetBackup SAP extension is obtaining the client name from the bp.conf and init SID .utl file on the client host, but truncating the name at 31 characters. The truncated name is then presented to the master server for scheduling of the application backup job, which understandably does not start successfully.
TECH56693 | 2009-01-09
Technical Solutions | CMS-XML

NetBackup EXIT STATUS 10: allocation failed

bpbkar log snippet from the client: 12: 31 :45.020 PM: [3316.5148] 2 Packer::open(): DBG - Started Backup... (../Packer.cpp:273)
TECH203268 | 2014-10-15
Technical Solutions | CMS-XML

DOCUMENTATION: Explanation of bpclntcmd options and recommended troubleshooting when the commands return errors.

option returned client_01 with an IP address of 192.168.0. 31 . This may indicate incorrect information within the name resolution configuration, if the client host is not multi-homed, and the client and master server hosts are resolving the client s name to two different IP addresses.
TECH50198 | 2013-10-08
Technical Solutions | CMS-XML

Cloud storage backups fail with status code 84 or 87

_1373526632, offset=3584, length=141976576, error = 2060022, error message: software error Critical bptm(pid=28291) image write failed: error 2060022: software error Error bptm(pid=28291) cannot write image to disk, Invalid argument end writing; write time: 0:02: 31 Info bptm(pid=28291) EXITING with status 84 Info bpbkar (pid=6044) done. status: 84: media write error media write error(84)
HOWTO91992 | 2013-10-02
How To | CMS-XML

Snapshot errors encountered with ibm4000 arrays (NetBackup status code 156)

Mon Mar 31 2008 14:25:23.036588 Pid - 1065104 / Thread id - 1 FlashCopy could not be created. command [create FlashCopyLogicalDrive baseLogicalDrive= drive-claix11-1 userLabel= drive-claix11-1_flcp ;].
HOWTO88357 | 2013-09-30
How To | CMS-XML

GENERAL ERROR: How to troubleshoot robot communication issues in Windows

(Messages similar to the following may appear): 20041108 11: 31 :09 NetBackup TLD Control Daemon I13892 NA TLD(0) [3096] opening robotic path \\.\scsi3: (bus 0, target 1, lun 1) 20041108 11:41:19 NetBackup TLD Control Daemon E5122 NA DeviceIoControl() error on bus 0, target 1, lun 1: The semaphore timeout period has expired.
TECH38829 | 2010-09-07
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?