The DVM repository is full therefore transfers, rollups or replication is not possible. Errors found in AppRecovery logs:
ERROR 2017-04-27T20:48:01 [1411] - Replay.Core.Implementation.Transfer.VolumeDataWriter (Job Id = 6d33359a-4993-45f5-802d-c6b7f45cae24:TransferJob a8c22740-9b8f-4552-a118-89b51bb8be3a:VolumeTransferJob)
Error writing block offset 0x453d3b9, block length 0x2 for volume S:\
System.AggregateException depth 0: One or more errors occurred. (0x80131500) ---> (Inner Exception #0 depth 0) System.AggregateException depth 1: One or more errors occurred. (0x80131500) ---> (Inner Exception #0 depth System.InvalidOperationException Replay.Core.Contracts.DedupeVolumeManager.DedupeVolumeOperationException depth 2: The repository is full. Adjust your retention policy or delete the old recovery point chains to free up space, or add a new storage location to the existing repository.
The repository is out of space.
There are a number of ways to resolve repository full issue.
Note: repository space can also be taken by machines in the Recovery Points Only section. This type of data is absolutely static, not affected by rollups and cannot be replicated to another Core. Still, that data can be deleted from repository using Delete All or Delete Range actions, if necessary
Note 1: Delete Range may fail if there's no free space in the repository. Delete Range can be called as "targeted rollup", which requires free repository space to rebuild the Recovery Points' chain properly.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center