NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

NetBackup status code: 647

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

Media Manager status code 147

Examine command output, debug logs, and system logs for a more detailed message on the error. See Setting debug logging to a higher level in the Troubleshooting Guide Specify an off-site slot value within the range of 0 to 2,147,483, 647 .
HOWTO104512 | 2014-11-20
How To | CMS-XML

Media Manager status code 148

Examine command output, debug logs, and system logs for a more detailed message on the error. See Setting debug logging to a higher level in the Troubleshooting Guide Specify an off-site session ID within the range of 0 to 2,147,483, 647 .
HOWTO104513 | 2014-11-20
How To | CMS-XML

Media Manager status code 141

Examine command output, debug logs, and system logs for a more detailed message on the error. See Setting debug logging to a higher level in the Troubleshooting Guide Specify a number of mounts value within the acceptable range of 0 to 2,147,483, 647 .
HOWTO104506 | 2014-11-20
How To | CMS-XML

Media Manager status code 74

Examine command output, debug logs, and system logs for a more detailed message on the error. See Setting debug logging to a higher level in the Troubleshooting Guide Specify a number of cleanings value within the acceptable range of 0 to 2,147,483, 647 .
HOWTO104454 | 2014-11-20
How To | CMS-XML

Media Manager status code 114

Examine command output, debug logs, and system logs for a more detailed message on the error. See Setting debug logging to a higher level in the Troubleshooting Guide Specify a maximum mounts value within the range of 0 to 2,147,483, 647 .
HOWTO104484 | 2014-11-20
How To | CMS-XML

Device management status code 36

Examine command output, debug logs, and system logs for a more detailed message on the error. See Setting debug logging to a higher level in the Troubleshooting Guide Specify a maximum-mounts value within the range of 0 to 2,147,483, 647 .
HOWTO104664 | 2014-11-20
How To | CMS-XML

BUG REPORT: Backup fails with status 13 when bpbkar hangs processing /dev files on VxFS 5.0.

08:57:46.644 [10271] 2 bpbkar SelectFile: INF - resolved_path = /dev/log 08:57:46.644 [10271] 4 bpbkar SelectFile: INF - VxFS filesystem is / for /dev/log 08:57:46. 647 [10271] 4 bpbkar SelectFile: INF - Unable to backup VxFS Named Data Streams, VxFS 5.0 or later required.
TECH70708 | 2009-01-15
Technical Solutions | CMS-XML

few streams failed with status code 49 client did not start 12/02/2014 09:58:23 - end writing | Symantec Connect

few streams failed with status code 49 client did not start 12/02/2014 09:58:23 - end writing 17:06:58.517 [10476] <2> schild: wait2() ECHILD 17:07:17. 647 [10476] <2> vnet_pbxacceptsocket: Accepted sock[10] from 10.224.16.104:45137 17:07:17.648 [10476] <2> bprd: socket fd from accept() is 10
Connect Forums | HTML

Status Code Chart

646 647 648
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

NetBackup messages

validation of synthetic image failed See NetBackup status code : 647 vault already exists
HOWTO103773 | 2014-11-20
How To | CMS-XML

About the binary catalog format

(231 ) - 1 files = 2,147,483, 647 files = 7FFFFFFF files The maximum number of different user IDs and group IDs (combined):
HOWTO105946 | 2014-11-19
How To | CMS-XML

Can NetBackup image expiration dates be set past January 19, 2038?

NetBackup uses the UNIX CTIME clock to calculate time, including the date and time used for the expiration of images. This is a 32-bit clock counting the number of seconds since January 1, 1970, and runs out at CTIME of 2,147,483, 647 which translates to January 19, 2038 at 03:14:07 UTC.
TECH190497 | 2012-08-31
Technical Solutions | CMS-XML

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?