NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 133

Media Manager status code 133
HOWTO104498 | 2014-11-20
How To | CMS-XML

NetBackup status code: 133

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

STATUS CODE 133: Clustered Windows Oracle client backups fail with Status Code: 133

10:53:18.092 [2924.2400] 16 VxBSAQueryObject: ERR - dbc_get_string() failed 133
TECH45809 | 2013-04-26
Technical Solutions | CMS-XML

user-directed backup, restore, and image list operations fail with status 133 if the client database exits.

user-directed backup, restore, and image list operations fail with status 133 if the client database exits.
TECH67669 | 2013-03-21
Technical Solutions | CMS-XML

Restore job from Backup, Archive, and Restore (BAR) application fails with error "restore not initiated: invalid request (133)"

Restore job from Backup, Archive, and Restore (BAR) application fails with error "restore not initiated: invalid request ( 133 )"
TECH179938 | 2012-02-19
Technical Solutions | CMS-XML

Informix backup fails with a VERITAS NetBackup (tm) error 6, and onbar return code 133.

/opt/informix9.40/bin/onbar_d complete, returning 133 (0x85)
TECH29535 | 2005-01-01
Technical Solutions | CMS-XML

NDMP backup of EqualLogic fs7500 filer fails with status 13

15:12:41.028 [9714] 2 bpbrm main: end write catalog 15:12:42. 133 [9714] 2 bpbrm main: start to write catalog ...snip...
TECH192541 | 2014-12-01
Technical Solutions | CMS-XML

Restore of Bare Metal Restore (BMR) Windows client fails with error message "Unable to Verify Backup" or "Failed to Verify Backup"

file, or invalid routing back to the client. The master server does not see the restoring client as a valid client (rc=131, 133 , 135) The IP address used by the client resolves to a different name than in the configuration or the client does not have permission to perform list/restore requests.
TECH87087 | 2014-11-14
Technical Solutions | CMS-XML

When attempting to browse for SQL backups a window with 'Error encountered trying to read database images.' is popped up.

10:40:22. 133 [4312.5026] 32 CDBbackcat::GetDBImages: ERR - Read invalid number of parameters 1 read from file C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\__12_48_22_925.img. Bad line 1006proddblogicalfile2 1009proddblogicalfilegroup2 0052c:\Program Files\Microsoft SQL Server\mssql10_50.PRODMSSQL\MSSQL\DATA\logicalfg2
TECH205300 | 2013-11-11
Technical Solutions | CMS-XML

AIX media server backup failing with STATUS CODE 83 with the message "No passthru access to this drive" in the backup job details.

logs shows a scsi reserve failure followed by the error message No passthru access to this drive 14:57:42.622 [2162854] 4 expandpath: /usr/openv/netbackup/db/media/tpreq/drive_hp.ultrium2-scsi. 133 : :
TECH168470 | 2013-10-25
Technical Solutions | CMS-XML

nbfdrv64 dies on new FT media servers, erroring with "InitPipe returned 983081"

pci1077,100 pci1077,101 pci1077,102 pci1077,104 pci1077,105 pci1077,109 pci1077,10a pci1077,10b pci1077, 133 pci1077,134 pci1077,137 pci1077,138 pci1077,140 pci1077,141 pci1077,144 pci1077,145 pci1077,146 pci1077,148 pci1077,14b pci1077,154 pci1077,2312.0e11.100 pci1077,2312.0e11.101 pci1077,2312.0e11.102
TECH144936 | 2013-10-16
Technical Solutions | CMS-XML

CORBA connection failures and status 25 after upgrading media server to 7.5.0.6 or 2.5.3

But if there are multiple local IP addresses, e.g. bond0 and bond1 , and remote hosts that should be connected to via those both interface, then asymmetrical routing will occur to some hosts which may not be successful per the bullet items noted in (A). Note: user-directed operations initiated from the host will use local_hostname as the requesting_client and may result in status 131, 133 , or 135 unless the master server is able to resolve local_ip to a peername that is recognized as a valid server.
TECH208869 | 2013-09-24
Technical Solutions | CMS-XML

Backups fail with status 25 after appliance 52x0 2.5.3 or NetBackup 7.5.0.6 upgrade

But if there are multiple local IP addresses, e.g. bond0 and bond1 , and remote hosts that should be connected to via those both interface, then asymmetrical routing will occur to some hosts which may not be successful per the bullet items noted in (A). Note: user-directed operations initiated from the host will use local_hostname as the requesting_client and may result in status 131, 133 , or 135 unless the master server is able to resolve local_ip to a peername that is recognized as a valid server.
TECH208752 | 2013-08-15
Technical Solutions | CMS-XML

Inconsistent name resolution behavior causes intermittent status 46 and status 59

...snip... 14:06:16. 133 [11279] 2 bpcd exit_bpcd: exit status 46 ----------- exiting
TECH204794 | 2013-04-06
Technical Solutions | CMS-XML

Restore fails with status 37: operation requested by an invalid server

...snip... 15:00:04. 133 [27641] 2 hosts_equal: hostnames DO NOT compare 15:00:04.133 [27641] 2 hosts_equal: addresses DO NOT match
TECH155673 | 2012-01-12
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?