cancel
Showing results for 
Search instead for 
Did you mean: 

cannot read media header, may not be NetBackup media or is corrupted

Hi,

 

I need some help with a Catalog Recovery (DR Testing) issue please.

I get the following msg when trying to import the DR file of the catalog tape:

"cannot read media header, may not be NetBackup media or is corrupted"

On a previous ocasion with help from tech support we were able to import the DR file from tape to start the catalog recovery

Here is the situation:

Original Site:

Netbackup 6.5.4 with Robotic library - LTO3

DR Site:

- Netbackup 6.5.4 with standalone drive - LTO4 (hcart3)

- I have added the media manually and then ran the following cmd:  install path\Veriats\Netbackup\bin\Admincmd>bpimport -drfile <media id> -drfile_dest <location>

 

I can confirm that the catalog backup which we are trying to recover was made with Netbackup as per Original Site above.

 

Any ideas? Thank you

 

1 Solution

Accepted Solutions
Accepted Solution!

Have you try to verify the

Have you try to verify the catalog backup at the primary master server?

If there is a problem with the tapes, the primary server will not read the tapes. If the primary server can read the backups, then you may have problem with the drives.

I've seen in the past incompatibilities between drives, especially with drives from different manufacturer (IBM to HP and vice versa)

View solution in original post

4 Replies

1.  Have you got the right

1.  Have you got the right tape ?

"cannot read media header, may not be NetBackup media or is corrupted"

The media cannot even be mounted, that is usually preety much the end of the party, there ios no magic fix for this - very simply, the netbackup header cannot be read, either it is damaged/ corrupted, or missing.

Follow this :

http://www.symantec.com/docs/TECH73812

Can you read the media header using the method in the TN

 

This is an example media sheader from a unix server

 

 

0000000   V   O   L   1   E   0   1   0   0   1  \0  \0  \0  \0  \0  \0
0000020  \0  \0  \0  \0  \0  \0  \0 001  \0  \0  \0 006   Q 210   )   R
0000040  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
0000060  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0 001
0000100  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0 004  \0  \0  \0  \0  \0
0000120  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000160   T   h   I   s       I   s       A       B   P       t   A   p
0000200   E       h   E   a   D   e   r  \0  \0  \0  \0  \0  \0  \0  \0
0000220  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0002000
 
When you convert the output from the TN, you should see VOL1<media name> at the beginning.
 
Martin

Hi Martin, I followed that

Hi Martin,

I followed that exact TN without any success. WHat bugs me is that we tried two catalog tapes and got the same result.

We did use the correct tape yes.

Hi, Where was the issue, did

Hi,

Where was the issue, did you get any output at all ....

M

Accepted Solution!

Have you try to verify the

Have you try to verify the catalog backup at the primary master server?

If there is a problem with the tapes, the primary server will not read the tapes. If the primary server can read the backups, then you may have problem with the drives.

I've seen in the past incompatibilities between drives, especially with drives from different manufacturer (IBM to HP and vice versa)

View solution in original post