How to backup a Domain Controller in Windows 2012 server
Hi,
I have a Domain controller called “BobaDC1”. It is in Dell PowerEdge R 310.
I want to remove the existing OS from this Machine, and install Window 2019 Server (I have done these activities to Dell R510 & R430 Successfully).
Before I am able to do the above, I have to backup this Domain Controller. Somebody show me how to do this backup please.
Thanks,
Tjie
I have a Domain controller called “BobaDC1”. It is in Dell PowerEdge R 310.
I want to remove the existing OS from this Machine, and install Window 2019 Server (I have done these activities to Dell R510 & R430 Successfully).
Before I am able to do the above, I have to backup this Domain Controller. Somebody show me how to do this backup please.
Thanks,
Tjie
Forgot the link for the wbadmin make sure Windows backup is installed on the server.
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/wbadmin
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/wbadmin
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Agree with Seth.
You really should have more than one domain controller.
If you do have another domain controller, upgrade that one. That will update the schema as necessary on BobaDC1.
If you don't have another domain controller, get one!! Install Server 2019 on it. Join it to the domain then promote it. You don't have to purchase a new physical server. You could install Hyper-V on an existing server and create a VM on it to use as the second domain controller. A Windows Server standard license will license you to run two VMs on a physical server.
Once you have a second domain controller in place, you can upgrade BobaDC1 (after transferring the FSMO roles to the second server). If you have any problems with upgrading BobaDC1 , you'll be ok because you have the second domain controller in place.
You really don't want to be relying on restoring a backup to recover your Active Directory if you have any problems upgrading a single domain controller.
You really should have more than one domain controller.
If you do have another domain controller, upgrade that one. That will update the schema as necessary on BobaDC1.
If you don't have another domain controller, get one!! Install Server 2019 on it. Join it to the domain then promote it. You don't have to purchase a new physical server. You could install Hyper-V on an existing server and create a VM on it to use as the second domain controller. A Windows Server standard license will license you to run two VMs on a physical server.
Once you have a second domain controller in place, you can upgrade BobaDC1 (after transferring the FSMO roles to the second server). If you have any problems with upgrading BobaDC1 , you'll be ok because you have the second domain controller in place.
You really don't want to be relying on restoring a backup to recover your Active Directory if you have any problems upgrading a single domain controller.
Wbadmin is the tool to use.
You should practice and test by creating a non-network connected VM and tests your ability to install Os 2012 and then restore the systemstate backup...
Note since you are planing to go to 2019, you should prestage and run adprep fro. The win2k19 on the existing 2012 update forest, domain, GPO. As well as rodp....
If you do not prep, it could run into issues when...
Consider what the cost of the added items is compared to a cost of getting a used newer equivalent version?
What are your environment setup is?
Ever consider running a DC in a core OS install, lower resource requirements and demand.