Protected site journal storage considerations

  • Hi.

    During a regular VPG life cycle, we need to make sure journal sizes are within the target site limits.

    Once we do real failover, does the journals are kept? Or is removed after we commit the failover?


    Other question apply to the failback, does our protected site storage need to have enough space for both journal data and vmdk as well?

    Lets say our protected site has 20TB vmdk data, and we have only 3TB avilable space in the storage.

    Will Reverse protection will put us in an out of space dangerous ?


    These question are “REAL LIFE” issues that came up after a REAL dr event we have operate couple of months ago.


    After a failover live (FOL), all previous journals are applied to the failed-over VM’s disks. This means the journals are not kept as separate disks. They are merged with scratch disks and mirror disks into the failed over VM’s disks.

    After a FOL, a VPG goes into “Needs Configuration” status.
    It can be either removed or you can enable reverse protection on it.
    If reverse protection is enabled, the VPG is deemed as a new one.

    The recovery site of that VPG now is the previous protected site of the previous VM.
    E.g. for a VPG previously replicating from site A to site B, after reverse protection, the replication will be from site B to site A.
    The current recovery site should have the space for accommodating the journal disks.
    You can use the Journal Sizing tool for estimating the datastore space might be required:

    Technical Documentation

    (Please search “Journal Sizing Tool” on the webpage.)

    Thank you.

You must be logged in to create new topics. Click here to login