If creating a DVM repository on a DR appliance, for example by CIFS share, the repository will become corrupted over a short period of time. Rollups will start to fail with the following stack trace:
System.AggregateException: One or more errors occurred. ---> Replay.Core.Contracts.DedupeVolumeManager.DedupeVolumeOperationException: A bad record has been read. There may be a problem with the repository or the underlying storage device
In addition to eventual corruption, performance will be very slow with many unmanaged.Dvm performance-related errors in logs stating some operations are running for longer than 30 seconds.
Due to intense random input/output (I/O) operations, it is advised that a non-deduplicated disk subsystem is used for the any DVM repository. AppAssure and Rapid Recovery cannot use the DR Series appliances as a location for a DVM repository. It is not supported.