We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Backup Exec 12.5 bare-metal restore - doesn't restore system state

NormBr
NormBr asked
on
Medium Priority
3,632 Views
Last Modified: 2013-12-01
I'm following the 12.5 Admin doc on doing a disaster recovery restore to a server via agent. This is a test, not production. Hardware is identical. Server is in domain but not a domain controller. So I have a full backup, system state, shadow copy as my source. The target is a server with newly installed server'03 and the backup agent pushed to it. Target server name is the SAME as source except it's in Workgroup, not domain.

I configure restore to use the source backup, system state, shadow copy items. Although the doc does not make reference to  File Redirection, since the target is not in the domain now, file redirection is needed to locate the target - and I drill down to the target server with agent,   C: and \ root. I specify that files are to be overwritten and registry overwritten. The idea being that the source will overwrite target files and system state.

I launch the restore. It runs - file restore, shadow components, system state. From the agent panel on the target I can see the agent is at work. It ends with a message: complete and reboot the target server. I reboot the target server. It comes up. Files are there. Registry overwrite has not happened. Server identity and application associations are those of the bare target, not the fully loaded source. It's like the system state restore did not run - yet there are no errors posted.

There is one odd thing: in the file restore there is a warning message to the effect that restores should be done to an agent otherwise the restore might not be complete. It's odd because there is an agent, the media server sees it and the agent panel shows its engaged in the restore.

This has been replicated several times and the target server rebuild from scratch several times.

Where do I go with this? Thanks for any/all assistance.
Comment
Watch Question

Have you tried creating an IDR bootable CD, boot the target server with that CD and restore by pointing to the drive where the backup is?

Author

Commented:
IDR is not part of our backup scheme. We are testing the documented restore process to a remote server with agent. We've done this with CA Arcserve; our consultant has done this elsewhere with Backup Exec. We're trying to figure what's wrong with our config or our process. Thanks for the alternative.
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Ok, I didn't know the target wasn't part of the domain. That changes the entire situation. I'm glad you found a solution.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.