NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 607

NetBackup status code : 607
HOWTO90801 | 2013-10-02
How To | CMS-XML

NetBackup status code: 607

NetBackup status code : 607
HOWTO51150 | 2012-11-19
How To | CMS-XML

NetBackup status code: 607

NetBackup status code : 607
HOWTO35260 | 2010-10-29
How To | CMS-XML

NetBackup status code 607: no images were found to synthesize

607
TECH59067 | 2009-01-12
Technical Solutions | CMS-XML

STATUS CODE: 607 "No images were found to synthesize"

no images were found to synthesize ( 607 )
TECH38157 | 2009-01-01
Technical Solutions | CMS-XML

Status 607 on Synthetic Backup | Symantec Connect

Status 607 on Synthetic Backup
Connect Forums | HTML

VMware Intelligent Policy Test Query operation is failing with "error parsing discovered XML data(1)"

Raw nbsl log: 0,51216,309,132,1453,1395775593654,53436,139780432148224,0:,127:xml parser fatalerror: invalid byte � at position 1 of a 1-byte sequence at line: 1 column: 81921 (../XmlInterface.cpp: 607 ),32:XmlDocumentInterface::fatalerror,1
TECH216148 | 2014-04-14
Technical Solutions | CMS-XML

GENERAL ERROR: NetBackup 7.x client side deduplication backups of MSCS cluster nodes fail with status 83 but media server-side deduplication backups complete successfully.

10:44:17.343 [4704] 2 TAO: TAO (11147|1) - pbxiop_connector::make_connection, connection to 10.66.17.45:1556:proxyv9svc failed (errno: Operation not supported) 10:53:56. 607 [4704] 16 59255:bpbrm:4704:mediasvrname: [ ERROR ][proxy_get_server_prop_byname_v8]CORBA::SystemException is caught in proxy_get_server_prop_byname_v8, minor = 1330446338, status = 1
TECH138406 | 2013-10-16
Technical Solutions | CMS-XML

NetBackup status code: 1

A synthetic backup job may terminate with a status code 1 under the following conditions: No images were found to synthesize ( status code = 607 ). TIR information has been pruned from component images (status code = 136).
HOWTO90430 | 2013-10-02
How To | CMS-XML

BMR enabled backup job is partially successful (status code 1) after upgrade to Netbackup 7.5.0.4, Parent job fails reporting status code 26

17:48:35.451 [3100.5576] 2 bpbrm spawn_child: C:\Program Files\Verit 17:48:36. 607 [3200.1360] 2 bpbrm spawn_child: C:\Program Files\Verit 17:56:23.739 [2716.6008] 2 logparams: -c pdc-s-1ss-db-03.sibgenco.loc
TECH200322 | 2013-07-01
Technical Solutions | CMS-XML

Application backups fails with status 6 or status 42 when extjob.exe inherits NetBackup sockets

...snip... 16:43:37. 607 [252.5028] 16 fill_buffer: socket operation failed - 10054 (at child.c.1294)
TECH189853 | 2013-03-27
Technical Solutions | CMS-XML

NetBackup status code: 1

A synthetic backup job may terminate with a status code 1 under the following conditions: No images were found to synthesize ( status code = 607 ). TIR information has been pruned from component images (status code = 136).
HOWTO50778 | 2012-11-19
How To | CMS-XML

Netbackup catalog restore fails with status 47 or 25

14:02:55. 607 [6084.4504] 2 vnet_async_connect: vnet_vnetd.c.4172: connect: async CONNECT FROM 10.16.248.151.2068 TO ip_media_server
TECH70578 | 2012-08-18
Technical Solutions | CMS-XML

NetBackup status code: 1

A synthetic backup job may terminate with a status code 1 under the following conditions: No images were found to synthesize ( status code = 607 ). TIR information has been pruned from component images (status code = 136).
HOWTO34887 | 2010-10-29
How To | CMS-XML

Hot Catalog Backup in mixed NetBackup environment Master 6.x/6.5.x and Media Server 5.x fails with Status code 25: cannot connect on socket

log shows that NetBackup Master 6.5.x is trying to connect to a 5.x Media Server: 09:00:02. 607 [22363] 2 bpbackupdb: INITIATING: NetBackup 6.5 created: 0 09:00:02.607 [22363] 2 logparams: -p5x hot_catalog_backup -dpath /usr/openv/netbackup/db/nbu_5xmdb_image/hot_catalog_backup -pjobid 2619616
TECH72153 | 2010-08-28
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?