When the repository is running out of space, an error occurs;
The rollups, snapshot or base images are not running because of full repository.
The next logs may appear at the core events
2nd Example.
ERROR 2015-02-16T09:29:11 [77] - Replay.Core.Implementation.Transfer.TransferJob (Transfer ID 'agent ID' of volumes [\\?\Volume{Volume ID}\,\\?\Volume{volume ID}\] from 'Agent computer name')
Assigned agent 'agent ID' repository is full.
Note: Once the repository is full the only tasks available are the repository check and delete base images. All other tasks required more initial space at the repository to be completed.
Note: In some scenarios the space is not enough to run the background job, to clear the space from the repository after deleting a base image. For this reason if a base image has been deleted and the space is not reclaimed call to support for additional troubleshooting.
Note: When the repository is full is needed to check two things, if there are several base images created and those are taking all the repository space, or the core is retaining more recovery points than the available space at the repository.
To understand the process rollup and retention policy please access this document. click here
WORKAROUND:
1. Pause all protection or incoming replications.
2. Check at all the protected machines for any additional base images created, these will be listed at last at the recovery point list. If there are additional recovery points with base images created which are not needed, then it is necessary to delete them.
Alternate scenarios: If for business needs it is not possible to delete any base image, it is necessary shorten the retention policies or adding more space to the repository. If it is not possible to add more space to the repository, then archive the recovery point from one agent in order to proceed deleting the base image.
3. After deleting a base image It’s necessary to wait until seen the available space. For core build 5.4.X the background process which clears the space out can be verified with this process click here
4. Once the space is reclaimed its necessary identify if you had several base images filling the space, you can contact support to identify the reason of those base images, or if everything is normal probably the retention are configure to keep more data than available space, to solve that is necessary either evaluate if it is necessary to add more space to the repository or shorten the retention policy.
5. After reconfigure retention policy it is necessary force a roll up.
To force the roll up, highlight the agent, go to configuration, find retention policy and click on the “Force roll up”button.
To run the roll up to all the machines at the same time, the only way is changing the nightly jobs to an earlier time. Click on core “configuration”, “Settings”, “Nightly Jobs” and change the time settings.
6. Import the archive taken.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center