- Newest
- Most votes
- Most comments
Not only that - full image restore will create a domain joined instance with the same GUID which will wreck havoc into your AD. This is not a cloud issue (as you mentioned) but it might be easier to deal with in the cloud since you can perform restore to isolated subnet and then deal with domain membership or even create an image by sysprepping the restored instance
There are a number of ways to work around these issues. Can you provide more context? As an example, I restored a domain controller (PDC emulator) and didn't have any issues and was up and running in less then 10 minutes.
Imagine you have a legacy application hosted on a Windows Server. Periodically you must bring that whole server back (while its production copy is running in the same VPC with the same NetBIOS name) in order to prove your DR strategy is sound and working. Imagine the application hosts medical records or financial data, and you have to simulate a nurse or accountant using the application for a single user session pulling a patient record like an x-ray, or a trial balance - and you have to prove that said record was intact each time. This all happens at the same time as production is running as stated before.
Relevant content
- asked 2 years ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
I have confirmed that if the instance was domain joined to AWS AD as part of the original launch configuration with a domain role role...when its restored it comes back identically and is part of the domain automatically...with duplicate funness.
For future posters...any actual references here would be super helpful.