Some Nightly Jobs Start for All Protected Machines at the Same Time After an Upgrade from AppAssure (4039585)

After upgrading to Rapid Recovery from AppAssure, you notice that some nightly jobs perform at the same time with each other.  This mainly affects Attachability Checks and Roll Up jobs.

In AppAssure, a parent roll up job had multiple child jobs when expanded. New rollup logic is introduced in Rapid Recovery, which makes each individual protected machine's roll up job a separate parent job. After upgrading to Rapid Recovery from AppAssure, you noticed that the roll up jobs are running for all protected machines at the same time instead of one after the other, as it designed too. This severely impacts other Core functions such as blocking replication and exports or causing backups to fail.

The same issue may occur with attachability checks for the protected SQL servers and would be present if more than one SQL server is protected and enabled for attachability checks.

WORKAROUND

To workaround this issue, reset Rollup and Attachability Checks in Nightly Jobs. In the Rapid Recovery user interface:

1. Navigate to Settings (gear icon in the upper left hand corner)
2. Go to Nightly Jobs and click Change
3. Uncheck Rollup, uncheck Check attachability of SQL databases, and click OK
4. Go to Nightly Jobs and click Change
5. Check Rollup, check Check attachability of SQL databases, and click OK

NOTE:  If the a Rollup script from AppAssure 5 is active in your environment, disable and remove it. The script is no longer needed in Rapid Recovery. If the script is enabled it may cause this behavior.  

STATUS

This issue is resolved in Rapid Recovery 6.0.2 and can be downloaded at the Download Software page.