NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

STATUS CODE 176: An import of a media fails with "cannot perform specified media import operation" when importing a tape from a different VERITAS NetBackup (tm) environment with Media ID Generation rules in effect for either environment.

9/7/2005 11:15:59 AM - end Import operation; operation time: 00:00:48 cannot perform specified media import operation( 176 ) Media Server Log Files:
TECH43524 | 2013-10-23
Technical Solutions | CMS-XML

Media Manager status code 176

Media Manager status code 176
HOWTO91029 | 2013-10-02
How To | CMS-XML

NetBackup status code: 176

NetBackup status code : 176
HOWTO90593 | 2013-10-02
How To | CMS-XML

Can't perform Phase 1 import of Backup Exec media into NetBackup, getting an error (176).

When attempting to perform a Phase 1 import of a tape from a Backup Exec environment into NetBackup, the import fails with a status 176 .
TECH75464 | 2013-09-18
Technical Solutions | CMS-XML

Media Manager status code 176

Media Manager status code 176
HOWTO51378 | 2012-11-19
How To | CMS-XML

NetBackup status code: 176

NetBackup status code : 176
HOWTO50941 | 2012-11-19
How To | CMS-XML

NetBackup status code: 176

NetBackup status code : 176
HOWTO35051 | 2010-10-29
How To | CMS-XML

Media Manager status code: 176

Media Manager status code : 176
HOWTO35488 | 2010-10-29
How To | CMS-XML

STATUS CODE: 176 "Cannot perform specified media import operation"

STATUS CODE : 176 "Cannot perform specified media import operation"
TECH36597 | 2010-01-08
Technical Solutions | CMS-XML

Media import fails with error 176: cannot perform specified media import operation

Media import fails with error 176 : cannot perform specified media import operation
TECH67466 | 2009-01-22
Technical Solutions | CMS-XML

STATUS CODE: 176: Unable to import media after a barcode change when using an ACS library. Veritas NetBackup (tm) automatically synchronizes the barcode to match the media ID.

The requirement is that the barcode label and media ID in the volume database must always match the recorded media ID (RVSN) on the tape. Any Phase 1 import will fail with a Status 176 due to the difference between the barcode and the media ID. For other type robots, for example TLD or TL8, it is possible to create a mismatch by using the vmchange
TECH43918 | 2008-01-31
Technical Solutions | CMS-XML

STATUS CODE: When trying to import a tape that has expired, it fails with a status 176.

STATUS CODE : When trying to import a tape that has expired, it fails with a status 176 .
TECH34913 | 2006-01-22
Technical Solutions | CMS-XML

Receiving Status 176 when attempting to import VERITAS Backup Exec (tm) 9.0 media to VERITAS NetBackup (tm) 5.0

Receiving Status 176 when attempting to import VERITAS Backup Exec (tm) 9.0 media to VERITAS NetBackup (tm) 5.0
TECH31521 | 2005-01-15
Technical Solutions | CMS-XML

Job fails with status 232 after going active on RHEL media server using NIS/YP

03:49:44.156 [43776] 2 logconnections: BPDBM CONNECT FROM 2.2.2.2.54513 TO 1.1.1.1.1556 fd = 6 03:49:44. 176 [43776] 2 db_end: Need to collect reply ...snip...
TECH145022 | 2014-03-24
Technical Solutions | CMS-XML

GENERAL ERROR: If static Network Address Translation (NAT) is configured on the firewall binding the firewall's external IP with the NetBackup master/media server ports, then the DMZ client must be able to perform reverse name lookups of the firewall's public IP address to the name of the NetBackup master/media server.

22:25:48.031 [2344.2492] 2 vnet_cached_gethostbyaddr: ..\libvlibs\vnet_hosts.c.255: Function failed: 6 0x00000006 22:25:48.031 [2344.2492] 2 vwrap_ipaddr_check: ..\libvlibs\vwrap.c. 176 : Function failed: 4 0x00000004 22:25:52.531 [2344.2492] 2 vnet_cached_gethostbyaddr: ..\libvlibs\vnet_hosts.c.255: Function failed: 6 0x00000006
TECH39431 | 2013-10-29
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?