madinina
asked on
restore 2003 AD from symantec backupexec 12
Dear Expert,
I have a DC (DNS, DHCP...) that crashes following an electric storm. Could you give any step by step to successfully perform the AD restoration on an new hardware to recover the DC as it was before crashing.
Backup exec will be installed on the new hardware.
The domain controller is belong to a forest where others domain are sitting. The others domain are not on the same physical site than the one that has been failed
thks in advance
There
I have a DC (DNS, DHCP...) that crashes following an electric storm. Could you give any step by step to successfully perform the AD restoration on an new hardware to recover the DC as it was before crashing.
Backup exec will be installed on the new hardware.
The domain controller is belong to a forest where others domain are sitting. The others domain are not on the same physical site than the one that has been failed
thks in advance
There
ASKER
Mike,
I already read this article but I am confuse. Do I have to restore the system state from a non-DC or DC?
Thks
I already read this article but I am confuse. Do I have to restore the system state from a non-DC or DC?
Thks
Bring the new box up as a member server and promote it to become a DC/DNS server in that case
you do not need to restore the system state from a non-DC or DC.
you do not need to restore the system state from a non-DC or DC.
From a DC but really I'd just go with the metadata cleanup and then promote the new box.
metadata cleanup instructions http://www.petri.co.il/delete_failed_dcs_from_ad.htm
Did that box have any FSMO roles?
Thanks
Mike
metadata cleanup instructions http://www.petri.co.il/delete_failed_dcs_from_ad.htm
Did that box have any FSMO roles?
Thanks
Mike
ASKER
I would like to keep the same name of the failed server on the new hardware. So, restoring the system state will be faster to do that cleanup the metadata and promote the new box.
Yes, the failed server have teh FSMO roles.
Yes, the failed server have teh FSMO roles.
Here is how it was done with system state with Windows backup http://support.microsoft.com/kb/263532 you would need the system state from that downed DC, but again the different hardware with backup exec 12 is something I haven't tried.
You could use the same name after the metadata cleanup.
Thanks
Mike
You could use the same name after the metadata cleanup.
Thanks
Mike
Anyway you need to perform metadata cleanup(Remove record from DNS, ADSIEDIT, FRS to do so follow the article provided by mkline71), then you can use same name.
new installation with dcpromo is better option instead of restoring the system state, but Its also depend on you.
new installation with dcpromo is better option instead of restoring the system state, but Its also depend on you.
ASKER
The server was a file server for users. If dcpromo the replacment do you think user will connect succesfully to it without making any change from the user desktop like it was before failing
ASKER
metadata cleanup should be done before the restoration or dcpromo, correct?
Yes and you will also need to seize the FSMO roles
http://www.petri.co.il/seizing_fsmo_roles.htm
Thanks
Mike
http://www.petri.co.il/seizing_fsmo_roles.htm
Thanks
Mike
1. do you think user will connect succesfully to it without making any change from the user desktop like it was before failing -Yes.
2. metadata cleanup should be done before the restoration or dcpromo- Yes.
2. metadata cleanup should be done before the restoration or dcpromo- Yes.
ASKER
I don't understand why I have to seize the FSMO role as the failed DC was the only one DC in the domain. And I replace it by an other with the same name.
wait a second this was the only DC in the domain? That changes things, I thought you had other DCs in this domain.
Ohh... I thought you have another DC, new installation with dcpromo will not work for you.
Or bring up new box with different name then transfer roles to new server then decom the old server.
In that you do not need to run metadata cleanup.
Or bring up new box with different name then transfer roles to new server then decom the old server.
In that you do not need to run metadata cleanup.
Bring up new box up with different name then transfer roles to new server then decom the old server.
In that case you do not need to perform metadata cleanup.
In that case you do not need to perform metadata cleanup.
ASKER
In summary
I want to keep the same server name again.
This is the only one DC in the domain and it hold the FSMO role. So the new hardware will be also a DC and handle the FSMO roles
I want to restore AD from backup exec on the new hardware as it was before the server failed.
I want to keep the same server name again.
This is the only one DC in the domain and it hold the FSMO role. So the new hardware will be also a DC and handle the FSMO roles
I want to restore AD from backup exec on the new hardware as it was before the server failed.
You are going to have to try the restore, because a new DC would be a new domain.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I followed the suggestions and get rid with it
http://seer.support.veritas.com/docs/236661.htm
The tricky part is going to be the new hardware, never tried or tested it with backup exec
If you have other DCs in the same domain you could also just do a metadata cleanup on that box that crashed (since you couldn't demote it gracefully) and then bring the new box up as a member server and promote it to become a DC/DNS server.
Thanks
Mike