NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

NetBackup status code: 2037

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

BUG REPORT: When using NetBackup 6.0, media queries cause EMM Server SQL syntax errors due to a required change to the value of infinity.

NetBackup 4.5 and 5.x used a value of 2147483647 which is Mon Jan 18 03:14:07 2038 GMT . NetBackup 6.0 shortened this value to be 2145916799 which is Thu Dec 31 23:59:59 2037 GMT . This change was made in order for underlying Sybase date functions to work correctly.
TECH44720 | 2007-01-18
Technical Solutions | CMS-XML

Status Code Chart

2036 2037 2038
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

Exit Status: 48 (client hostname could not be found) | Symantec Connect

08:56:02.271 [3412.752] <8> do_pbx_service: [vnet_connect.c: 2037 ] cr->vcr_servic
Connect Forums | HTML

NetBackup messages

drive is not ready See NetBackup status code : 2037 DSM has already mounted the volume
HOWTO103773 | 2014-11-20
How To | CMS-XML

RMAN Backup failing after backup "begin writing" | Symantec Connect

08:06:14.463 [42860712] <8> do_pbx_service: [vnet_connect.c:2036] use_vnetd 1 0x1 08:06:14.463 [42860712] <8> do_pbx_service: [vnet_connect.c: 2037 ] cr->vcr_service vnetd 08:06:14.463 [42860712] <8> async_connect: [vnet_connect.c:1630] do_service failed 18 0x12
Connect Forums | HTML

imported media not showing up on bpmedialist | Symantec Connect

Strangely have lost 1 second on the expiration time, but if these tapes are about by 2037 ( or me for that matter ) i'll eat them myself. Once i've merged the others i'll go and run the nbcc, haven't done a consistency test for many years so probably worth the effort.
Connect Forums | HTML

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?