Rollups are not happening automatically. When trying to force a rollup, the error message is shown that the repository is not mounted. It continues to save new snapshots on schedule without any issues. Repository is working properly on the Core.
Forcing rollup can also generate a different error: "Unable to connect to the remote server"
To resolve the issue, please make sure that:
- target Core is up and running and is on the same version of Rapid Recovery
- target Core repository is mounted and doesn't have words "Integrity Check" in repository's drop-down menu
- source Core can communicate with the target Core properly (status is green)
If there are networking issues, or target Core is down for any reason and rollup must be performed as soon as possible then:
- click on the Replication icon
- expand the target Core
- remove the agent from the replication list
- or -
- delete the whole replication link. Link can be reestablished once the target Core will be fully operational
Note: deleting replication link is a safe operation and won't cause any loss of data. Replication link need to be deleted on both replicating Cores.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center