NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Storage Lifecycle Policy (SLP) duplication fails with status 144 (invalid command usage)

Storage Lifecycle Policy (SLP) duplication fails with status 144 (invalid command usage)
TECH209276 | 2013-12-17
Technical Solutions | CMS-XML

When using Backup History to set the date range on a NetBackup 7.5.0.6 Java console, status code 144 may be reported.

bpclimagelist: unrecognized option -first_fragment ( Status 144 )
TECH208236 | 2013-12-16
Technical Solutions | CMS-XML

User initiated restore or file list fails with "EXIT STATUS 144: invalid request." User backups work. The master server can back up and restore the same client.

User initiated restore or file list fails with " EXIT STATUS 144 : invalid request." User backups work. The master server can back up and restore the same client.
TECH31363 | 2013-10-23
Technical Solutions | CMS-XML

Media Manager status code 144

Media Manager status code 144
HOWTO91006 | 2013-10-02
How To | CMS-XML

NetBackup status code: 144

NetBackup status code : 144
HOWTO90562 | 2013-10-02
How To | CMS-XML

Media Manager status code 144

Media Manager status code 144
HOWTO51355 | 2012-11-19
How To | CMS-XML

NetBackup status code: 144

NetBackup status code : 144
HOWTO50910 | 2012-11-19
How To | CMS-XML

NetBackup status code: 144

NetBackup status code : 144
HOWTO35020 | 2010-10-29
How To | CMS-XML

Media Manager status code: 144

Media Manager status code : 144
HOWTO35465 | 2010-10-29
How To | CMS-XML

NDMP backup fails with status 144 invalid command usage db_flistsend failed

NDMP backup fails with status 144 invalid command usage db_flistsend failed
TECH73522 | 2010-01-11
Technical Solutions | CMS-XML

A server group must be specified for each copy - Status 144.

A server group must be specified for each copy - Status 144 .
TECH71014 | 2009-01-20
Technical Solutions | CMS-XML

NetBackup status code 144: invalid command usage

144
TECH58608 | 2009-01-12
Technical Solutions | CMS-XML

BUG REPORT: Unable to restore from the Java GUI. "invalid date specified" error returned - Java is truncating the path.

Protocol Code: 233 Status : 144 Time Taken: 431ms
TECH217485 | 2014-06-08
Technical Solutions | CMS-XML

SAN Client backups failing intermittently with STATUS 174 and nbftsrvr buffer processing failures in [ProcessReadWrite]

BPTM log 11:44:35. 144 [5167] 32 write_data: data buffers out of sequence, expected number 17, received 20 11:44:35.144 [5167] 2 write_backup: write_data() returned, exit_status = 174, CINDEX = 0, twin_index = 0, backup_status = -8
TECH147561 | 2014-05-26
Technical Solutions | CMS-XML

NetBackup automatic remote master replication fails status 84 when target MSDP media server resolves the source MSDP media server hostname to incorrect ipv6/ipv4 address.

... 19:11:33. 144 [30164] 2 ost_proxy_release_read_media: media release of @aaaac succeeded 19:11:33.146 [30164] 4 report_dedup_stats: StorageServer=PureDisk:sourcemsdphostname; Report=PDDO Stats for (sourcemsdphostname): scanned: 4 KB, CR se
TECH209579 | 2014-02-18
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?