Forum Discussion

siri416's avatar
siri416
Level 4
11 years ago

bpimmedia throwing error the database contains conflicting or erroneous entries

Hi Al,

 

I'm trying to figure out what was backedup on physical tape, but getting below error

the database contains conflicting or erroneous entries

 

Thanks

7.1.x and Earlier
Backup and Recovery
NetBackup
Solaris
  • Marianne's avatar
    Marianne
    11 years ago

    ...  -backupid client_1220222843 ....

    This is your timestamp: 1220222843

    UNIX time 1220222843 is 08/31/2008 10:47pm GMT.

    So, if you go to /usr/openv/netbackup/db/images folder, you should see a folder for client name.
    In this folder, there should be a 1220000000 folder. Look in there for all file names that correspond with the timestamp: 1220222843.

    If I look at the policy name in bpimagelist above, the policy type may have been MS-Windows or Lotus Notes.
    'bpimagelist -backupid client_1220222843 -L' will confirm.

  • Deb_Wilmot's avatar
    Deb_Wilmot
    Level 6
    11 years ago

    What are you doing in order to try to figure out what was backed up?

     

    Are you running a verification of the media or an import? (those are in the catalog tab in the gui)

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    Please show us exact command you are typing with exact error message.
    (Copy the text and paste here, please.)

    You will probably need bpdbm log on master to find problematic image id's.

    Ensure this folder exists under /usr/openv/netbackup/logs.
    If not, create it and restart NBU to enable the logs.

    When error message is seen again, copy the log file in above folder to bpdbm.txt and upload here as File attachment.

  • siri416's avatar
    siri416
    Level 4
    11 years ago

    Hi,

    this tape AXXXX has got infinity retention, trying to see what all images it had . But its giving below error

    $ /usr/local/bin/sudo /usr/openv/netbackup/bin/admincmd/bpimmedia -mediaid AXXXX -L                                                                                      
    Password:
    the database contains conflicting or erroneous entries

    Catalog section also throwing same error and Images on tape also

     

     

     

  • siri416's avatar
    siri416
    Level 4
    11 years ago

    Hi Marianne,

    In bpdbm lo,i tried searching for the ID,but dont find it

    you want me to post <16> error ones from bpdbm log ?

  • Deb_Wilmot's avatar
    Deb_Wilmot
    Level 6
    11 years ago

    Try running a media contents report (aka bpmedialist -mcontents -m <media_id> -L just to see whats on the media.

    If it's what you expect, you may want to consider expiring the media and then reimporting it.

    If not - you should probably open up a support case and have them investigate.

     

     

     

  • Deb_Wilmot's avatar
    Deb_Wilmot
    Level 6
    11 years ago

    Yes - that physically reads the contents of the media and reports it.

     

  • siri416's avatar
    siri416
    Level 4
    11 years ago

    tape got damaged ,so we're trying to run another backup for that cient if we know what got backed up on that tape

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    Best to read bpdbm log from the timestamp when bpimmedia command was issued.
    The information preceding <16>'s will be debug info - <2> and will tell us what lead up to error message.
    If PID can be determined, follow that.
    Can you see the "conflicting or erroneous " message in the log?

    How long does it take from issuing bpimmedia command till you see the error?
    This will determine the section of bpdbm log to look at.

    If not image id, the client name should appear in the log.

    Another log that may be helpful is admin. 
    No need to restart NBU after creating this log folder.
    Just run bpimmedia again.
     

    My next action would be to examine client folder(s) under db/images.
    I would look for folder structure and/or symbolic links that may be incorrect.

    bpdbm -consistency and/or nbcc to check catalog consistency may be a good idea.