Scribd Logo
Upload

Welcome to Scribd!

  • Code 229

    Uploaded by

    subhrajitm47
    59 views2 pages
    The NDMP backups were failing with status code 229, which indicates an "image inconsistency" error. This was likely caused by the filer sending backup data to NetBackup without the necessary directory information for one of the files. Checking the filer's file system for corruption, updating its OS if out of date, or switching the backup policy to use tar backups instead of the default dump backups may resolve the issue.

    Original Description:

    nmmm

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The NDMP backups were failing with status code 229, which indicates an "image inconsistency" error. This was likely caused by the filer sending backup data to NetBackup without the necessary directory information for one of the files. Checking the filer's file system for corruption, updating its OS if out of date, or switching the backup policy to use tar backups instead of the default dump backups may resolve the issue.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    59 views2 pages

    Code 229

    Uploaded by

    subhrajitm47
    The NDMP backups were failing with status code 229, which indicates an "image inconsistency" error. This was likely caused by the filer sending backup data to NetBackup without the necessary directory information for one of the files. Checking the filer's file system for corruption, updating its OS if out of date, or switching the backup policy to use tar backups instead of the default dump backups may resolve the issue.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    of 2

    Problem

    Network Data Management Protocol (NDMP) backups fail with status code 229

    Error

    States Code 229 DETAILS FROM JOB:


    06/24/2009 09:13:41 - granted resource 000401 06/24/2009 09:13:41 - granted resource IBM.ULTRIUM-TD3.003 06/24/2009 09:13:41 - granted resource footiebootie-hcart3-robot-tld-0-filer002 06/24/2009 09:13:43 - mounting 000401 06/24/2009 09:14:10 - mounted 000401; mount time: 0:00:27 06/24/2009 09:14:10 - positioning 000401 to file 1 06/24/2009 09:14:14 - positioned 000401; position time: 0:00:04 06/24/2009 09:14:14 - begin writing 06/24/2009 11:19:12 - Error bpbrm (pid=3081) db_flist_complete failed: events out of sequence - image inconsistency (229) filer002 NDMP_filer002 0 1245858045 06/24/2009 11:19:13 - Error bptm (pid=3095) read of TIR file failed: events out of sequence - image inconsistency 06/24/2009 11:19:18 - end writing; write time: 2:05:04 events out of sequence - image inconsistency (229)

    Here are some characteristics to help in identifying the issue: bpdbm log: 09:06:27.309 [19528] <32> Function: CatImg_FinishBackup: Corrupt .f file, inode entries missing directory info: File: nbe_cat_c_api.cpp Line: 1518: memory map invalid data, ----> This suggests the filer sent a file without the information for its corresponding directory, which would cause a problem during a restore. bptm log: 09:06:28.198 [15083] <16> setup_tir_read: read of TIR file failed: events out of sequence image inconsistency ----> This is NBU reporting a problem with the image.

    Also check the policy's backup selections. This issue has been encountered with policies using the default Set Type=dump and also Set Type=vbb (vbb is EMC's volume-based backup).*

    * NOTES: It is important to note that the status 229 has been encountered with other filer types as well. So this procedure will likely benefit other filer manufactures when referring the customer to open a support ticket with them.

    Environment

    EMC Celerra

    Cause
    This issue may be caused by the following:

    File system corruption Out-of-date OS on the filer Inconsistent data sent to NetBackup by the filer

    Solution

    1. Switch to using "set TYPE=tar" in the policy Backup Selections. Tar does not experience this issue, because it is a path-based history -- the file's directory is part of the path. 2. If file system corruption is the cause, an fsck run on the filer's volume in question may resolve. 3. The filer OS may need to be updated.

    You might also like