Active Directory Disaster Recovery on Windows Server 2019

HomeOther ContentActive Directory Disaster Recovery on Windows Server 2019
Active Directory Disaster Recovery on Windows Server 2019
Active Directory Disaster Recovery on Windows Server 2019
Active Directory Disaster Recovery on Windows Server 2019.
This work week is dedicated to backing up and restoring Windows Server Active Directory. In today's video I talk about a situation where our environment is cratered. A meteor strike. Every domain controller in the company is lost. We need a way to get everything back. I'm a big fan of locally saving the system state of domain controllers in key data centers in the environment. This backup should be copied to a secure file share where we can always count on a recent copy. The warranty on the stock should be very limited, to only those who need to get it back. You also need to consider that if Active Directory is completely down, how will you access the system state backup. Cloud storage can be a good choice using a break glass cloud account. I highly recommend scripted builds for domain controllers to ensure consistent configuration of each domain controller. When we go to recover this domain controller, we want to recreate the storage volumes and drive letters to match the original server. ok, as far as disasters go, it wasn't that bad. Be sure to document your environment, configurations, credentials used for access, and anything else you think might be needed in this situation and keep it somewhere safe that you can access even if everything is cratered. Leave a comment below on your worst disaster stories. Give this video a like. Before watching other videos on Administering My Windows Server, please click subscribe. Thank you so much.
Windows Server Admin Reading List:
https://www.youtube.com/playlist?listPLVPBipeObwMOBYlM__StdIZzJrrsLXkt1

Please take the opportunity to connect and share this video with your friends and family if you find it useful.

No Comments

Leave a Reply

Your email address will not be published. Required fields are marked *