Run EC2Rescue on the working instance, and then choose Offline instance.Download the EC2Rescue for Windows Server tool, and then extract the files.Connect to the recovery instance using Remote Desktop Protocol (RDP).Attach the volume to the recovery instance as a secondary volume using the default settings in the Amazon EC2 console.Detach the boot volume of the corrupt instance.Note: You can terminate the recovery instance after the corrupted registry is restored. You will use this new instance as the recovery instance. Launch a new instance (Windows Server 2012 or later) in the same AWS Region and Availability Zone as the inaccessible instance.From the Amazon EC2 console, select your instance. Create an EBS-backed Amazon Machine Image (AMI).Note: If you aren't using an Elastic IP Address, the public IP address will be released when you stop the instance. Be sure to back up the contents of the volume before stopping it. Warning: If this instance has an instance store volume, you'll lose any data on it when the instance is stopped.To use EC2Rescue to restore to the latest registry backup, follow these steps: A corrupt Windows registry can cause an EC2 Windows instance to freeze, slow down, restart randomly, or become unusable.Įven without performing other backup utilities or configurations beforehand, Windows regularly and automatically makes its own backup of the registry in the following location: C:\Windows\System32\config\RegBackĮC2Rescue can restore these previously created backups from the RegBack directory to the current registry of the EC2 instance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |