This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Stop currently running rollup

I am having hardware issues with the storage that houses one of the 3 extents for my repository (Appassure 5.4.3.106).  A rollup of all 75 agents is currently running, but looks likes it's going to take another 6 hours at least.  Can I stop this rollup without corrupting the repository?

  • Yes, you can cancel rollup. It may take a long time to cancel as it has to complete the current action it is doing, but it will cancel. It will not revert any of the changes it made to recovery points and it will not corrupt the repository. Do NOT stop or kill the core service until rollup has cancelled successfully as that is highly likely to cause repository corruption.
  • Hi Alices:
    In Appassure 5.4.3.106 + P-1612 it is safe to stop rollups. However, please note that after rollups finish or are cancelled another set of background jobs called deferred deletes are performed and it is not advisable cancelling them. (Some times they are in the hundreds so it is almost impossible to cancel them manually, they need to be performed to free space on your repository and they will find one way or another to re-run upon the completion of other operations).
    We recommend a rollup script (KB#137049 for AppAssure) that implements a different rollup logic, running rollups one by one as opposed to a block-job and allow other operations to be performed in parallel.

    The version for 6.1.1 is able to rollup protected machines beginning with the machines that were rolled up the longest ago and run parallel rollups on multiple repositories -- which may suggest yet another reason to upgrade.

  • Thanks for the info. Will Core version 6.1.1 work with my existing 5.4.3.106 agents, at least for now?
  • Yes, it will. I have quite a few customers that are doing it. BTW, the KB with the 6.1 rollup script is here: support.quest.com/.../219952