So, put simply, after a disk size change, the next replication will remove all restore points except the most recent, then the job continues normally. From that point, restore points will build up again until they meet the criteria. There is no 'full replica' on the next pass, it will still be incremental after the disk size is changed, but only one restore point. The 'replica' is still there, but it will effectively have only a single restore point (the most recent one), after the replication is finished. SnapShot is disk imaging software that enables the user to back up, restore and view backed up hard disk data, easily and safely. Whenever a change to a source VM disk is made, all restore points for that replica must be deleted so that we can change the size of the disk (VMware does not allow a VM with snapshots to change this disk size). Each 'replica' also has a number of restore points, based on the settings for the replication job. Replica's refer to the individual VMs that are replicated. I'd just like to clarify a few things for future readers of this thread because there a confusing mix of terminology.Ĭhanging the disk size does not 'blow away' all of your replicas. This means that the next time a replica runs it will be a full replica? So I should run this manually off schedule so the SBS is not tied up during business hours? Cliffm wrote:So I gather that if I expand the disk all the replicas will be blown away.

Drive snapshot 1.4