bpimmedia throwing error the database contains conflicting or erroneous entries

[siri416]

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

[Deb_Wilmot]

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]

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]

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

[Marianne]

You need bpdbm log as per my previous post.

[siri416]

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]

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.

[siri416]

Hi deb,

That needs tape to be in library ?

[Deb_Wilmot]

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

[siri416]

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]

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.

[mph999]

If you run bpimagelist -l -d mm/dd/yyyy  |grep <media id>

This will show the FRAG lines, you will need to look back a few lines (1 or more) to see the corresponding IMAGE line that contains the backupid.

Use a date that is 'before' the tape was written (bpimagelist by default only returns the last 24hrs of backups).

NOTE.

Bearing in mind you suggest you have other catalog errors this might not show all results, so Debs idea of mcontents should be foolproof.

[siri416]

Thanks mph999

I have tried bpimgaelist ..listed fragments and have got server name. checked viz CLI for particular serevr using backup date and it listed damaged tape , but Backup,archive,restore window of that client not showing that tape..do youknow why ?

[Marianne]

... but Backup,archive,restore window of that client not showing that tape..do youknow why ?

What is the timestamp on the image seen in bpimagelist output?
Can you see policy type?

To see images/files in BAR and then check for media id, all of the following must match:
Client name (must match exactly)
Policy type
Date/time of backup

You can also check as follows:
bpimagelist -client  <client_name> -d <start-date> -e <end-date> -media -U

The other possibility is that the image header exist but that the 'files file' is missing or damaged.

If you share info, we can point you to the path where you can go to in order to check for header and other files that are needed.

[siri416]

I dont see any timestamp, policy type is MS-Windows .

used below command only to check media for that client , and it listed media which is damaged

bpimagelist -client  <client_name> -d <start-date> -e <end-date> -media -U

And I dont see the time stamp in BAR ,which I have from CLI 

 /usr/openv/netbackup/bin/admincmd/bpimagelist -backupid client_1220222843 -U

Backed Up         Expires       Files       KB  C  Sched Type   Policy

----------------  ---------- -------- --------  -  ------------ ------------
08/31/2008 18:47  INFINITY       1712 743100171  N  Full Backup  mns_Windows_Notes

[Marianne · Accepted solution]

...  -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.

[siri416]

That helped Marriane. 

Got the image in BAR and media too..Thanks...