Backup of 2003 DC
I have PDC running in WIN 2003 SP2 .I need to backup the entire thing from this DC to a test environment .How can I backup and restore this DC with no down time?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok my question is If I wanted to backup the entire ting in my DC .I have The same HAL .So first I need to create full backup(entire computer ) then create system restore and restor ethe full backup in test lab abd then restore the system state through directry service restore mode?
How many DCs do you have in production?
ASKER
only one
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The name of the test DC should be the same as the one in prod. It's important that those two can't see each other.
i would create an additional DC then make a image of it (Acronis , symantect backup recovery etc)
Then simply restore that image on another machine NOT connected to your production environment.
Then seize all the roles. How to transfer or seize roles
If you have Vmware ESX etc it would make things much simpler. I simply clone it but then connect the clone to a DR network which doesn't have any physical NICS associated with it. Works like a charm.
Then simply restore that image on another machine NOT connected to your production environment.
Then seize all the roles. How to transfer or seize roles
If you have Vmware ESX etc it would make things much simpler. I simply clone it but then connect the clone to a DR network which doesn't have any physical NICS associated with it. Works like a charm.
What about using SCVMM & Hyper-V?
Convert the DC to virtual machine P2V, don't make the virtual machine connected to your LAN, you can make a real simulation of what you want.
Convert the DC to virtual machine P2V, don't make the virtual machine connected to your LAN, you can make a real simulation of what you want.
ASKER
snusgubben,
I have tried this and it is good way .May I know how to take the backup of a exchange server also? I am running in a exchange server 2003 (Single) to test with the PDC?
I have tried this and it is good way .May I know how to take the backup of a exchange server also? I am running in a exchange server 2003 (Single) to test with the PDC?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'm not so much into Exchange to give you any qualified recomendations. I guess eugene20022002 gave you a possible way :)
ASKER
ok guys I will try these and let you know
ASKER
Hi ,
I have done this
1. Take a full backup of the DC along with System State.
2. Install the same OS and SP level on the test server. Disc space should be equal or larger.
3. Restart the DC in DSRM, start NTbackup (assuming Win2003) and retrive the backup catalog.
4. Check to restore C-drive and System State and restore to "same location".
5. Choose "Advanced", check Primary restore, Restore security, junction points, volume mount points.
and found that the dc is working when joining new clients but when I connecto asystem from my production to the lab .I cant login its says the domain controller is not availbale.
I have done this
1. Take a full backup of the DC along with System State.
2. Install the same OS and SP level on the test server. Disc space should be equal or larger.
3. Restart the DC in DSRM, start NTbackup (assuming Win2003) and retrive the backup catalog.
4. Check to restore C-drive and System State and restore to "same location".
5. Choose "Advanced", check Primary restore, Restore security, junction points, volume mount points.
and found that the dc is working when joining new clients but when I connecto asystem from my production to the lab .I cant login its says the domain controller is not availbale.
but when I connecto asystem from my production to the lab
hold on... Your production should not be able to see the lab! The Lab should be isolated!
hold on... Your production should not be able to see the lab! The Lab should be isolated!
ASKER
yes Th alab is aisolated bt what I am talkin is .I have restore the systemstate backup of py PDC to testsetup and it is up and running now .Then I need to make sure the exixitng client is sbale to connec to this.So what I have done is took alaptop from the roduction NW to test setup and tried to login to the same domain and then I ma getting the error message
Does the restored DC have the same IP as it had in the production?
This sounds like a DNS issue.
This sounds like a DNS issue.
ASKER
The same IP . I can ping the fqdn from the client
when you create a new lab.. you dont need to have the same Domain name. Only your AD infrastructure must be the same configuration (for real testing process).
If you restore you systeme state, all you sysvol and NTDS share folder will try to join all your real domain DC... and it can't because it's a test environnement.
Alexis
(sorry for my french english)
If you restore you systeme state, all you sysvol and NTDS share folder will try to join all your real domain DC... and it can't because it's a test environnement.
Alexis
(sorry for my french english)
If you restore you systeme state, all you sysvol and NTDS share folder will try to join all your real domain DC...
The author have only one DC in production, so it has not any replication partners.
The author have only one DC in production, so it has not any replication partners.
ASKER
BUt I am trying to figure out what are the steps for restring a DC when my PDC goes down? In this steps .The exsiting clinet needs rejoin?
What is your goal with this "lab"?
If you're seeking how to have a backup plan if your DC goes down, the best solution is to make an additional DC in the production!
If you take a host from the production environment and connect it to the lab, its machine account password (stored on the DC) will not match and the host need to rejoin.
If you're seeking how to have a backup plan if your DC goes down, the best solution is to make an additional DC in the production!
If you take a host from the production environment and connect it to the lab, its machine account password (stored on the DC) will not match and the host need to rejoin.
ASKER
If you take a host from the production environment and connect it to the lab, its machine account password (stored on the DC) will not match and the host need to rejoin.
I think this is incorrect
I think this is incorrect
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Try with NT backup. That is also good.
http://www.ilopia.com/Articles/WindowsServer2003/Backup.aspx
or symantec, if you can purchase a license copy then symantec backup with full feature is also good.
Regards,
Tushar Kaskhedikar