NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 67

Media Manager status code 67
HOWTO104447 | 2014-11-20
How To | CMS-XML

Device configuration status code 67

Device configuration status code 67
HOWTO104603 | 2014-11-20
How To | CMS-XML

NetBackup status code: 67

NetBackup status code : 67
HOWTO103995 | 2014-11-20
How To | CMS-XML

Automatic database extension backups fail with status 67: client backup failed to read the file list

Automatic database extension backups fail with status 67 : client backup failed to read the file list
TECH211924 | 2013-11-07
Technical Solutions | CMS-XML

NetBackup 7.5 through 7.5.0.6 hot catalog backup fails status 67 "client backup failed to read the file list" if files over 4GB in size reside in .../NetBackup/db/images/*

NetBackup 7.5 through 7.5.0.6 hot catalog backup fails status 67 "client backup failed to read the file list" if files over 4GB in size reside in .../NetBackup/db/images/*
TECH211302 | 2013-10-07
Technical Solutions | CMS-XML

STATUS CODE: 67, occurs if backup images are manually deleted during a hot catalog backup in NetBackup 6.0

If backup images are manually expired during a hot catalog backup, this can cause the catalog backup to fail with a Status 67 (client backup failed to read the file list). When a hot catalog backup kicks off, the nbgenjob
TECH48050 | 2013-03-27
Technical Solutions | CMS-XML

STATUS CODE: 67, occurs for a catalog backup if catalog archiving has been run on the master and images were not cleaned up properly

A hot catalog backup in NetBackup 6.0 can fail with a Status 67 if catalog files were not properly removed after the catalog archiving process. In order for this to occur the bpcatlist options |bpcatarc |bpcatrm
TECH48468 | 2008-01-09
Technical Solutions | CMS-XML

STATUS CODE 67: When using Veritas NetBackup (tm), the Vault Hot Catalog Backups fail with Status 67 "client backup failed to read the file list".

STATUS CODE 67 : When using Veritas NetBackup (tm), the Vault Hot Catalog Backups fail with Status 67 "client backup failed to read the file list".
TECH48241 | 2007-01-20
Technical Solutions | CMS-XML

STATUS CODE 67: Attempts to initiate hot catalog backups fail with NetBackup Status Code 67 (client backup failed to read the file list).

: Attempts to initiate hot catalog backups fail with NetBackup Status Code 67 (client backup failed to read the file list). When a hot catalog backup is initiated, it backs up the stage information without error , but on the second child job it fails with Status 67 . Troubleshooting
TECH47261 | 2007-01-08
Technical Solutions | CMS-XML

BUG REPORT: When using VERITAS NetBackup (tm) 6.0, hot catalog backups fail with a Status 67 when the Master Server's hostname contains an underscore ( _ ) character.

BUG REPORT: When using VERITAS NetBackup (tm) 6.0, hot catalog backups fail with a Status 67 when the Master Server's hostname contains an underscore ( _ ) character.
TECH45743 | 2006-01-25
Technical Solutions | CMS-XML

Status Code 67, while backing up SQL backup | Symantec Connect

Status Code 67, while backing up SQL backup Tweet Status 67 "client backup failed to read the file list" while backing up SQL DB and no log file is found kindly help??????? Discussion Filed Under:
Connect Forums | HTML

Restores or verification of a limited number of Exchange and Sharepoint images protected using NetBackup 7.1.0.x to PDDO/MSDP storage units fail with the error "invalid tar header encountered, attempting to continue"

(pid=9151) StorageServer=PureDisk:storageserver5020.nbudomain.com; Report=PDDO Stats for (storageserver5020.nbudomain.com): read: 670122093 KB, stream rate: 23. 67 MB/sec, CR received: 670428832 KB, dedup: 0.0%
TECH200000 | 2014-11-04
Technical Solutions | CMS-XML

VMware backup reports error codes 6 and 23 with san transport mode but success with nbd transport mode

08/27/2013 10:11:10 : closeGuest:VixManager.cpp: 67 INFO : Obj: /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.154.7.160.69rdp_1377569438.1.0.nbu_data.xm
TECH209993 | 2014-08-08
Technical Solutions | CMS-XML

RMAN backup to sbt_tape is much slower than backup to DISK, may fail with status 13

.., 67 ) = 67 13097/1:
TECH130209 | 2011-09-21
Technical Solutions | CMS-XML

NetBackup for Microsoft SQL Server completes successful (Status 0) backups and truncates SQL transaction logs, but the amount of physical space on the SQL Server hard drive allocated to the transaction log does not decrease.

tempdb 0.4921875 39.186508 0 model 0.7421875 67 .039474 0 msdb 2.2421875 31.903311 0
TECH29041 | 2010-01-17
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?