NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Status 227 "no entity was found error" when attempting to browse files with a parent folder that has Japanese or non-ascii characters on Linux Master Servers

We can see in that out put that Directory çµå¶ãªãã¼ã has files with in it. When the directory is listed specifically a status 227 occurs:
TECH218100 | 2014-06-09
Technical Solutions | CMS-XML

NDMP Backups fail with a (636) error and a (227) error

NDMP backup jobs receiving a (636) error during the backup may not fail until a (227) error occurs during the same time frame as image cleanup. Status 227 Status 636
TECH214335 | 2014-01-27
Technical Solutions | CMS-XML

NetBackup for Informix restore is failing with status 227 even though the bplist output shows that the backup of the Informix dbspace exists.

INFXBSA log on the Client: -this 227 error is sent to the Client which then passes it back to ONBAR 19:46:36.882 [1617606] 16 serverResponse: ERR - server exited with status 227: no entity was found
TECH154564 | 2013-10-30
Technical Solutions | CMS-XML

Unable to restore the database Error 227 - Error bprd (pid=55610) Block incremental image with backup time 1248077342 is missing.

Unable to restore the database Error 227 - Error bprd (pid=55610) Block incremental image with backup time 1248077342 is missing.
TECH73127 | 2013-10-24
Technical Solutions | CMS-XML

Restore of duplication receives error "unexpected return value from db_flistreceive: no entity was found 227

unexpected return value from db_flistreceive: no entity was found 227 bpdbm log:
TECH191404 | 2013-10-28
Technical Solutions | CMS-XML

STATUS CODE 227: Backups fail intermittently with Status 227 when the NetBackup catalog volume is at or near capacity.

STATUS CODE 227 : Backups fail intermittently with Status 227 when the NetBackup catalog volume is at or near capacity.
TECH28304 | 2013-10-23
Technical Solutions | CMS-XML

3rd PARTY: When attempting an alternate client restore of Oracle 8.0.x on Windows NT4, the restore fails with NetBackup Status Code 227.

3rd PARTY: When attempting an alternate client restore of Oracle 8.0.x on Windows NT4, the restore fails with NetBackup Status Code 227 .
TECH39135 | 2013-10-23
Technical Solutions | CMS-XML

bpimage fails with "EXIT status = no entity was found (227)" when the ID is specified with lower case characters

flag with bpimage , if the barcode is entered with lower case values, it will fail with a 227 as shown below: $ bpimage -newserver servername -oldserver servername -id rbp782
TECH32277 | 2013-10-23
Technical Solutions | CMS-XML

Bug Report: DB2 restore with a redirect option is failing with a "status 227" and reason code 516.

Bug Report: DB2 restore with a redirect option is failing with a " status 227 " and reason code 516.
TECH60815 | 2013-10-24
Technical Solutions | CMS-XML

GENERAL ERROR: When run on the master server, the bppllist command returns "no entity was found (227)" when deleted policy's directory structure has a "foreign" file present.

no entity was found ( 227 )
TECH44566 | 2013-10-23
Technical Solutions | CMS-XML

NetBackup status code: 227

NetBackup status code : 227
HOWTO90639 | 2013-10-02
How To | CMS-XML

bpcatres fails with status 227

Catalog archiving can be performed successfully using bpcatarc. The bpcatlist output will show the associated catarc IDs. But attempts to restore the archived image files files (*.f) will fail with status 227 .
TECH197753 | 2013-06-01
Technical Solutions | CMS-XML

bplist fails with Status Code: 227 No Entity Found

When running bplist from the master server without specifying a directory to search bplist fails with 227 : No entity found or returns unexpected results. Example (the wrong way to do it): C:\Documents and Settings\Administrator bplist -C client_hostname -t 13 -R
TECH125634 | 2013-05-03
Technical Solutions | CMS-XML

STATUS CODE: 227 occurs during a cumulative or differential incremental hot catalog backup in Symantec NetBackup (tm).

This is called the Hot Catalog Backup method and allows regular backups to run during a catalog backup. A Hot Catalog Backup in NetBackup Enterprise Server can fail with a Status 227 (no entity found) if no previous full hot catalog backup image exists. A full hot catalog backup must exist on the master to determine what files must be added to the incremental backup.
TECH42886 | 2013-05-03
Technical Solutions | CMS-XML

NetBackup status code: 227

NetBackup status code : 227
HOWTO50987 | 2012-11-19
How To | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?