Quest has identified a potential issue with AppAssure version 188.8.131.52 which can temporarily prevent access to some recovery points on cores which experience certain load or failure conditions. In extreme cases, this issue can cause the loss of some recovery points. All customers using release 184.108.40.206 are advised to upgrade immediately to 220.127.116.11 or later version.
We deem this issue as critical; therefore we are taking steps immediately, and over the next several weeks to ensure customer satisfaction and data integrity.
AppAssure version 18.104.22.168 is the only affected version.
The prior release, 22.214.171.124, is not impacted. All subsequent 5.4 releases, starting with 126.96.36.199, are also not affected.
Details: In 188.8.131.52, a change was made to the rollup logic which hardens it against extreme failure modes, such as power loss or catastrophic storage controller failure. This change inadvertently introduced the possibility that recovery points can be orphaned; if a particular agent has any recovery points that either a) are missing one or more volumes, or b) failed an Exchange mount check or SQL attachability check. Cores that are already operating normally, with no incomplete recovery points or failed recovery point checks, are not affected.
It is likely that the orphan recovery points can be repaired with the assistance of Technical Support. However, in some cases the orphans cannot be recovered. Therefore, all customers are urged to upgrade to 184.108.40.206 immediately. Customers unable to upgrade immediately should disable rollup until such time as upgrading is possible. Note: upgrading from 220.127.116.11 to version 18.104.22.168 requires an update to the Core software only; updating the agent version is not required. Many 22.214.171.124 patches are being recreated for this new update, and will be made available upon request by contacting Technical Support.
In several weeks we will release a new build of AppAssure 5.4.2, with a focus on a collection of other important but less critical 5.4.2 Known Issues. More information will be provided as we approach this release.
Questions or comments