Rapid Recovery Product Notification

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.

How does this affect me?

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:

1. Have changed the backup schedule
2. Have re-protected MS Hyper-V machines

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.

Resolution

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.
Quest development has created a pair of patches for this issue that are available through Quest Support that can 1) repair any previously backed up base and incremental images from the point in time in which 1 of the 2 conditions were introduced and 2) prevent any future incremental backups from failing from this issue once applied. For snapshots affected with this issue, there are no options for repairing and recovering them.
Please contact Quest Support for further assistance if you protect machines using Microsoft Hyper-V agentlessly to at a minimum, apply the patch as prevention.

Status

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.
Please review the Knowledge Base article for any additional details.  

We apologize for the inconvenience this issue may have caused and we are working quickly to correct it.