IDR restore problem

[Michael_LoCoco]

Environment:
-Media server windows 2003 standard server
-Backup Exec 9.1

Restoring to windows 2000 server pro machine using IDR boot disk

I've created the book disk and everything appears to be running perfectly until we get to the point in the IDR process that goes to restore data. I'm using a remote media server method and I have a current full backup. I have updated .DR files and the whole lot. There is connectivity to the media server due to the fact it starts a job on it from the machine I'm attempting to restore. My problem is that the restore doesn't work.

I used to get the error: There was an error installing RAWS however I fixed that by reinstalling the client through the rant32/setupaa install by mapping a drive etc.

So now I have a problem that the job although it says it's running from the client machine restoring data menu it sits for around 10 minutes before it fails, not one byte of data is restored.

I get this message: Network control connection is established between 190.9.8.242:4595 <--> 190.9.12.147:10000
Network data connection is established between 190.9.8.242:4596 <--> 190.9.12.147:1040
Connection to the restore target has been lost. Operation canceled.

Or this one:

Final error: 0xa000848c-unable to attach to one of the drives.

I've tried all of the following tech fixes:

http://seer.support.veritas.com/docs/266177.htm
http://seer.support.veritas.com/docs/269426.htm
http://seer.support.veritas.com/docs/255174.htm

Thanks in advance for any help you can offer.

[padmaja_rajopad]

Hi,

Haver you entered the remote IDR licence number on the media server?

Is there a firewall between the media server and the remote server?

Check whether port number 10000 is free on the media server an d the remote server as well?

Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm


NOTE : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to the ‘answered questions’ pool.

[Michael_LoCoco]

Thank you for the reply. I found that you need to have the same exact IP address as it previously was.

This wasn't easy because the netsh command doesn't allow you to change your IP statically to what you need due to the really weird given INTERFACE names such as:

{F9587oyi-938u8dr-d234r3}

So once I set it static through our DHCP server it worked.