An already established virtual standby can fail with an error message similar to:
"Tevo Library Error Exception: TevoSetFailoverFileClean failed with error -2147024873 (0x80070017 - Data error (cyclic redundancy check))"
Subsequent attempts by the core server generate the same error.
Removing Virtual Standby from core console and target hypervisor, and re-creating the virtual standby produce the same error.
Running a new base snapshot, followed by recreating the Virtual Standby as mentioned above results in the same error from the VS process.
The same issue may affect the restoration process (virtual export or BMR)
It was determined in most cases that the "cyclic redundancy check" part of the error points to disk issues passed unto the recovery point chain by the volume image backups, and possibly, recovery points integrity check may not be enabled for that server's recovery points in the core console settings (if there are no other error messages pointing to the affected server in the core console).
The root cause may very well be disk inconsistency at the source protected server.
Confirm and correct by using CHKDSK (from an admin command prompt - example: "CHKDSK C:") at the source machine.
Running CHKDSK without parameters is a "read only" process. Make sure you review how to use CHKDSK from Microsoft information sources online before you proceed.
If CHKDSK finds errors, use the CHKDSK fix parameters /F /R to correct (depending on the volume, you may need to reboot the server).
Once that corrects that issue, and you have confirmed that a standard CHKDSK will show no errors, force a new base snapshot at the core console, remove the virtual standby, make sure it is removed at the hypervisor target, and re-create the virtual standby.
If you need assistance/guidance with the above, please reach out for support.
