-
Title
Replication fails to start with incorrect RPFS file size error -
Description
Rapid Recovery Replication jobs fail to start correctly as the volume image metadata is rewritten by the replication transfer itself. When this very rare event happens, you should see similar events in the AppRecovery.log
ERROR 2017-09-28T03:15:30 [800] - Replay.Core.Implementation.DedupeVolumeManager.RpfsFileExtensions (Job Id = 2186da34-639b-4161-bc6c-f63fd3036d69:ReplicationJob 1787a2ec-0d7f-46e3-bba3-f834277b6d15:ReplicationTransferJob)
Failing to read Replay.Core.Implementation.Repositories.FileAbstraction.DataContracts.CustomMetadataSpecification data contract from RPFS file 4503599629683502 because the file size (55616 bytes) is more than the buffer size (55526 bytes)ERROR 2017-09-28T03:15:30 [2236] - Replay.Core.Implementation.Replication.Jobs.ReplicationTransferJob (Job Id = 2186da34-639b-4161-bc6c-f63fd3036d69:ReplicationJob 1787a2ec-0d7f-46e3-bba3-f834277b6d15:ReplicationTransferJob)
Job 'Transferring' failedSystem.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 1) System.InvalidOperationException depth 2: Unable to read data contract from stream due to incorrect RPFS file size (0x80131509) -
Resolution
Workaround:
There is a patch available for the 6.1.3 Rapid Recovery Core to correct this defect. Please contact the Support to request patch P-2286.
-
Defect ID
RR-105048