Quest has identified an issue with the Rapid Recovery 6.1.x product that may fail backups for customers using Hyper-V agentless protection, resulting in corrupt backup images.
You could be affected if you agentlessly protect Microsoft Hyper-V environments using Rapid Recovery 6.1.0, 6.1.1, 6.1.2, or 6.1.3 GA releases AND meet one or more of the following 2 criteria:
If you are affected, then your backup transfers will fail from the protected machine and the error message “A bad record has been read” will be seen on the core server(s) associated with the protected machine at the point in time the transfer fails.
If you are currently creating agentless backups for Microsoft Hyper-V, do not change your backup schedules or re-protect machines until you install the preventive patch as described below.
The patches for this issue are being validated for inclusion in a future release. If you are affected by this issue or wish to change your agentless Hyper-V protection schedule, please contact Quest support to obtain the patches and apply them in your environment.