I have found that sometimes you have to include the "oldserver" option on 
the bpmedia -movedb command, especially when your media server is not 
responding.  You can also put a "-v" on the command to see more of what it's 
doing.  You might try something like this:

bpmedia -movedb -ev 100108 -newserver master1 -oldserver media1 -v



>Message: 3
>Date: Mon, 30 Aug 2004 18:22:17 -0400
>From: "Kleinman, David" <David.Kleinman AT applicamail DOT com>
>To: <veritas-bu AT mailman.eng.auburn DOT edu>
>Subject: [Veritas-bu] Importing Tapes from a downed Media Server
>
>This is a multi-part message in MIME format.
>
>------_=_NextPart_001_01C48EDF.CF27CDA9
>Content-Type: text/plain;
>       charset="us-ascii"
>Content-Transfer-Encoding: quoted-printable
>
>
>Our media server (media1) crashed at a remote facility. We brought the
>media to another datacenter facility and I'm unable to import the media
>from the downed media server into the master server (master1) b/c the
>master can't contact the media server.
>
>=0D
>
>The following command returns the prompt immediately:
>
>C:\Program Files\VERITAS\NetBackup\bin\admincmd>bpmedia -movedb -ev
>100108 -new server master1
>
>=0D
>
>These commands return errors:
>
>C:\Program Files\VERITAS\NetBackup\bin\admincmd>bpmedialist -m 100108
>
>requested media id was not found in NB media database and/or MM volume
>database
>
>C:\Program Files\VERITAS\NetBackup\bin\admincmd>bpmedialist -m list -l
>-h media1
>
>Could not obtain report from host media1, handshaking failed with server
>backup restore manager
>
>=0D
>
>I can see the tapes in the robot but can't see them when I run a media
>report on the master server. A report on the downed media server hangs.
>
>=0D
>
>

_________________________________________________________________
Don?t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/