Once you establish a replication job, when the file system is synchronizing its data to the target file system, it tends to create a balloon effect where it creates a file system that grows as the new data is synchronizing. It would be very helpful if the replication job could incorporate a self-cleaning job after the synchronization job completes to reduce the size of the file system in the target automatically. Very often, we have to run a script called “SavVolReclaim” to clean up space consumed while the replication is in progress. If the replication job hits its maximum capacity of 16TB while synchronizing, it stops the replication job. By adding this reclaim process natively, it would eliminate additional unnecessary work for the storage administrators. It would be very helpful to get an automated report that shows you the size of the checkpoints and get warnings when a checkpoint is reaching either maximum capacity per a file system or hitting the ceiling on the SavVol pool consumption.