Restore suspended state of a VM after failover
Remove option to revert a replica's clones
Remove option to mount a replica
BUGFIX: These changes also eliminate the possibility where active data on a replicated datastore could be overwritten by a replication
Made F&F more robust
BUGFIX: Failover target "forgets" the failover source
BUGFIX: Temporary snapshots created during permanent failover are not deleted
BUGFIX: F&F metadata sometimes got corrupted
BUGFIX: Failover fails when suspending or shutting down the source VM takes more than 30 seconds
Clarify the system behavior
Clarify email when a crash consistent snapshot is created instead of app consistent
Clarify email when the replication fails due to the target being low on space
Clarify email when the replication fails due to the target being unreachable
Improve clarity of certain UI action labels
Clarify when failover process fails due to the source host losing connectivity
Clarify in the logs when failover process fails due to being unable to suspend the source VM
Clarify when the snapshotting process fails because it was unable to write a snapshot to disk
BUGFIX: Replication target state missing from the UI
Features for power users:
Add support for configuring a dedicated storage network in more complex LANs
Post-thaw hook/script is not mandatory for application consistent snapshots
Make the snapshot and replication feature more resilient:
Clean up hanging VMware snapshots created by previous schedule runs
BUGFIX: When datastore name contains special characters, some snapshots are skipped
BUGFIX: When replication target is offline, sometimes the local snapshots are not created as well
Finally, some plain and simple bug fixes in other areas:
BUGFIX: postgresql service was failing on system startup
BUGFIX: Sometimes a user can see files created by another user, even though they don't have the permission (SMB share)
BUGFIX: Sometimes a user can't see files created by another user, even though they have the permission (SMB share)