NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 190

NetBackup status code : 190
HOWTO104108 | 2014-11-20
How To | CMS-XML

Media Manager status code 190

Media Manager status code 190
HOWTO104541 | 2014-11-20
How To | CMS-XML

Storage Lifecycle Policies fail with Status 190

Storage Lifecycle Policies fail with Status 190
TECH185132 | 2013-09-16
Technical Solutions | CMS-XML

Duplication jobs ending with Status 190, parent job ends with Status 191 when image is on a DSSU.

Duplication jobs ending with Status 190 , parent job ends with Status 191 when image is on a DSSU.
TECH190087 | 2012-11-30
Technical Solutions | CMS-XML

Status 190 when the maximum copies prevents duplicating any images in BID list

Status 190 when the maximum copies prevents duplicating any images in BID list
TECH126126 | 2012-06-12
Technical Solutions | CMS-XML

Image corruption can cause status 190's on duplications.

If images are corrupt, it s possible that the SLP duplication jobs will not be able to properly duplicate the image, which will trigger status 190 s.
TECH188711 | 2012-06-14
Technical Solutions | CMS-XML

SLP Duplication jobs are failing with "Status Code 190: found no images or media matching the selection criteria" bpduplicate reports an error in admin log "<16> bpduplicate: INF - Skipping backup id client_1327335218; specified destination copy numbers are not available."

/usr/openv/netbackup/bin/admincmd/bpimagelist -L -backupid backup_id If copy # exists in the image DB, but nbstlutil reported that the status was incomplete, nbstserv will attempt to duplicate that image and it will fail with the status 190 . 3. Run a verify of the copy # to make sure its a good copy
TECH181975 | 2012-03-13
Technical Solutions | CMS-XML

SLP duplication job is failing with status 190.

Status 190 , found no images or media matching the selection criteria
TECH139476 | 2011-08-15
Technical Solutions | CMS-XML

Disk staging fails: Status Code 190

Error Code Found no images or media matching the selection criteria ( 190 ) Resolution
TECH60572 | 2010-01-25
Technical Solutions | CMS-XML

STATUS CODE: 190 occurs when trying to backup the NetBackup catalog

16 collect_catlog_backup_media_information: db_get_image_info() failed ( 190 ) 16 flist_complete: collect_catalog_backup_media_information() failed: found no images or media matching the selection criteria (190)
TECH48222 | 2008-01-09
Technical Solutions | CMS-XML

GENERAL ERROR: Restore of large (190+ GB) amounts of data to Veritas File System (tm) is extremely slow.

: Restore of large ( 190 + GB) amounts of data to Veritas File System (VxFS) is extremely slow. The initial restore speed begins well, but slows drastically.
TECH44786 | 2007-01-07
Technical Solutions | CMS-XML

Disk staging fails with a Status Code 190

found no images or media matching the selection criteria( 190 )
TECH29482 | 2005-01-04
Technical Solutions | CMS-XML

SLP duplication status 190 | Symantec Connect

SLP duplication status 190
Connect Forums | HTML

Backup of client behind firewall fails with status code 24 (socket write failed) despite port 13782 and 13724 being open.

bpbrm log: 10:17:17. 190 [23963] 2 bpbrm handle_backup: client MYCLIENT EXIT STATUS = 24: socket write failed 10:17:17.400 [11180] 2 bpbrm brm_sigcld: child 23963 exited with status 24: socket write failed
TECH202245 | 2013-12-02
Technical Solutions | CMS-XML

GENERAL ERROR: Certain reports in Veritas NetBackup (tm) Advanced Reporter cause out of memory errors

at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java: 190 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
TECH27726 | 2013-10-23
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?