Check out the below thread
http://forums.symantec.com/discussions/thread.jspa...
I think either the FORCE statement or the interface.

Thanks Dennis.

I've restored some files yesterday (about 200 worth about 250MB) and it went fine. Today, I tried doing a larger restore amount and ran into this issue.

It looks like it's toggling back and forth between drives. It's very odd behavior...

Thank you for the reply.
Phil.

So does it think the rest of the image is on another tape?

Thank you for replying, Dennis.

I think it must be spanning 2 tapes. Is there a command I can use to query the mediadb and find out for sure? Will this happen to all images that span multiple tapes? I have some large clients that have TBs so they will span mutliple tapes as well. Glad I"m testing this out now, but I don't know if this is a large issue or isolated to this image and client ...

Command for checking related media groups containing spanned backup images -

bpimmedia -spangroups

to list the images on the particular media in a span group -

bpimmedia -mediaid

Rakesh, thank you for the command, that's exactly what I needed.

I'm still a little confused as to why it would suspend or make the restore go into Incomplete mode while doing this restore. Any thoughts on that?

Here's the output of 1 of the 2 tapes:

IMAGE sanmediaserv02 7 sanmediaserv02_1170493494 cifc_nbsms02_1 13 weekend_full 0 1 68377 1174122294 0 0
FRAG 1 1 494079616 0 2 14 1 NDA063 sanmediaserv02 65536 2 1170493494 3 0 *NULL* 1174122294 0 1
FRAG 1 2 32147576 0 2 14 1 NDA472 sanmediaserv02 65536 2 1170493494 0 0 *NULL* 0 0 1

Notice the fragment size in bold. I changed the STU from default (1TB, right) to 2GB (2048). If this were recognizing the 2GB framentation of hte STU, wouldn't there be many more FRAGs? or am I incorrect that this fragmentation size is related to the STU size?

Thanks again for your help!
Phil.

Since, you are in DR environment, I am assuming you performed Phase1 and Phase2 impot on all your tapes or did catalog recovery

Do you have media server names same as in your other environment from where you received the tapes? Is sanmediaserv02 is the name for your media server at DR site too? If not then you need to either use FORCE_RESTORE_MEDIA_SERVER in your bp.conf file. Syntax is

FORCE_RESTORE_MEDIA_SERVER =

OR

bpmedia -movedb -m -newserver

Also, make sure that you have media server name in your bp.conf file.

You are right, numbers in bold are the Fragment size but these are representing the Fragment size at the time of backup (on the backup server, where you had performed the backup not on this server).

You can check your fragment size on your STU/s by running

bpstulist -UMessage was edited by:
RK

Rakesh,

I've imported teh catalog so all the tapes are in the mediaDB. The actual host names of the DR servers are different (sanmediaserv02 (production) dr-sanmediaserv02 (DR)).

All the systems have their host files aliased and referenced in DNS so that when talking or pinging sanmediaserv02, you are actually talking and pinging the dr-sanmediaserv02.

I can do other restores, even very large ones; i restored 450 GB last night with a hitch. And while that image was spanned on 2 tapes, the fies were all on 1 tape.

I can't find the bp.conf file and it sounds like a unix/linux file, I'm running all windows. I will, however, try the restore again with the FORCE RESTORE and see how it goes.

Thank you for your help and I'll keep you posted!
Phil.

We had this same problem and found a NIC duplex mismatch and changing the NIC driver from a Microsoft default to the manufacturers driver  corrected our issue.