Normally the backup will complete with warnings but the hard drive in question will not be fully backed up. When a restore is attempted from these backups, it will not restore which renders the backup useless in a disaster recovery situation. Thus it is critical to test backups on a regular basis to ensure that the backups can be used if and when needed.
To rectify the problematic drive the following can be done:
- Scan the disk using the Scandisk utility provided by the operating system. If the drive in question is the C: drive, a restart will be necessary and a boot scan needs to be performed.
- After completion of the scan, the Virtual Machine must be exported using the Export utility in Hyper-V Manager, ideally to a different hard drive as to where the current Virtual Machine is hosted. It is critical to export the Virtual Machine as soon as possible to ensure the integrity of the drive and the Virtual Machine.
- After the export has completed, a full backup of the Virtual Machine must be attempted so see if the backup will succeed.
- If the backup succeeds and the Virtual Machine is fully backed up, the Virtual Machine can then be moved to a different storage location to prevent this error from reoccurring.
- In the event of the backup not succeeding, the Virtual Machine must be switched off and renamed to a specific name which will identify it as the VM with CRC errors.
- An import of the Virtual Machine exported in step no. 2. Ensure that the Virtual Machine is not imported onto the physical drive that caused the CRC errors.
- After the import is completed, ensure that all services are started and the server is back up and fully functional.
- A full server backup must then be conducted to ensure that a most recent backup is available.
Wonderful blog.. Thanks for sharing informative blog
ReplyDeleteDivorce Attorneys Pretoria
Sign up bonus casino no deposit are offered for registration, without replenishing your account and with the ability to withdraw profits.
ReplyDelete