Backup and Restore Domain Controller using Symantec System recovery

Hi Experts,

I'm using Symantec System Recovery 10 to Backup and Restore a Domain Controller to a new server (2003).  I also have another domain controller in my network.I had not problem doing the backup and the recovery and now I have a new server with the same name. This server was also my DNS server. I was trying to introduce this server to my network and I disconected the old server and gave the same ip address to the new server. When I ping the new server, I did not get any response either by ip address or the server name.
I disconnected the new server and plug back the old server and everything is working fine.
I don't know if I'm missing something and I should have demoted the original server before creating the image and then remove the server from the domain.

Any ideas,


Thanks

falvaradAsked:
Who is Participating?
 
MichaelVHConnect With a Mentor Commented:
That's seems to be right.

You better add a second DNS server as well to make sure that nothing goes wrong there.
E.g. you could add DNS to the other DC as well.

Grts,

Michael
0
 
MichaelVHCommented:
Hi there,

first of all, is there a specific reason why you do a backup & restore when you try to replace a DC?
It's far less risky to just add a new DC, et it replicate, move the FSMO roles and than to demote the first/source server.

Grts,

Michael
0
 
falvaradAuthor Commented:
Hi,

Yes that will be the right aproach. Unfortunately, this is also a file server and has a bunch o little applications running on it.  It will be a lot of work to install all the programs, create all the shares etc.

What i want to know is how is the approach using Symantec  System Recovery. I was able to do the same with a member server and i had not problem. I just had to make the server member of a workgroup. Delete the computer account from the domain and then add the server back to the domain  but with a domain server I'm not allowed to make it part of a workgroup.

Thanks
0
 
MichaelVHCommented:
Falvarad,

again: doing that with a domain controller is actually not the right way to go, even if that would mean that you have more work to do.
I'd still strongly recommend that you first DEMOTE that server; do your thing with backup & recovery and than promote that server back. That way you'll have less possible issues...

Symantec Backup & Recovery does not allow for an Authoritative restore of Active Directory (you'll have to follow a MSFT-guide for that). Luckily you've got another domain controller, which would permit you to do a non-authoritative restore (don't forget to transfer the FSMO roles first!) or even demote the server before!. Please, also keep in mind that the target hardware has to be EXACTLY the same.

For more information I suggest you take a look here:
http://www.symantec.com/business/support/index?page=content&id=TECH55054

Michael
0
 
falvaradAuthor Commented:
Thanks Michael,  the link was great. I know now that I can not restore a domain controller to a disimilar hardware.  Just to make sure let me know if I have the the rigth steps

1) Move FSMO roles
2) DEMOTE SERVER ( It this ok even when this is the only DNS server?)
3) backup
4) restore to different hardware
5) Promote server




0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.