v5.x vs. v6.x restore points size

[vfrolov]

Replication now keeps all restore points as regular VM snapshots.
Does it mean much more disk space required for restore points?
Other words: the v5.x restore points are compressed and the v6.x restore points are not compressed?

[foggy]

Yes, with v6, replica restore points will require more space. Actually depends on the amount of changes your VMs provide between replication cycles. Thanks.

[vfrolov]

Thanks Alexander!

After upgrading to v6.0 all existing replicas will continue using compressed vrb-files to keep restore points (pre- and post-upgrade created). So we do not need disk space sizing after upgrade.
But we MUST do disk space sizing before replacing vrb-based restore points by snapshot-based restore points.

Is it correct?

Is there a method to estimate size of snapshot-based restore points using existing vrb-based restore points?

Is it possible to create a new replication job with vrb-based restore points to prevent disk size scarce?

[foggy]

Yes, after the upgrade, all existing jobs will continue to create restore points in VRB format (these jobs will get the 'VMware Legacy Replica' type in VBR UI). All new jobs will create restore points as regular VMware snapshots and you cannot change this behavior.

Regarding required space estimation, the only thing coming to my mind is that the snapshot size will be practically equal to uncompressed and "de-deduped" VRB size, so you can use compression and deduplication ratios for the particular restore point (VRB) to calculate the approximate snapshot-based restore point size.

[vfrolov]

Thanks Alexander!

If VB&R UI Replication Properties show

Code: Select all

  Name                      Data Size     Restore Point Size
  2012-02-15T060039.vrb     13,43 GB      7,81 GB

then additional 13,43-7,81=5,62 GB disk space should be planned for equivalent snapshot-based restore point.

Is it correct?

[foggy]

Yes, I think you could use such estimate.