vSphere DR and Migration Improvements
Since introducing the support for dedicated vSphere clouds as a replication destination, we have extended the list of available features with every new release. This one is no exception and brings several significant improvements:
- Recovery Plans to define the failover order of the replicated VMs the same way it is done for VMware Cloud Director clouds
- Bandwidth throttling to enforce traffic limits on a specific network interface of the Tunnel appliance
- Public API, which was missing before.
In VMware Cloud Director Availability 4.3.1, we enabled migrating templates from one catalog to another in the same or a remote VMware Cloud Director cloud.
In 4.6, we enhanced that feature to check for template changes and perform an automated migration if a modification is detected. It can result in overwriting the existing template at the destination catalog or creating a newer version.
Along with all mentioned, we have also improved product management and operability.
For clouds running VMware Cloud Director 10.3 or later, VMware Cloud Director Availability 4.6 now supports replicating:
- The DHCP service on vApp isolated networks
- Routed vApp networks
- vApp network services
This means VMware Cloud Director Availability no longer converts routed vApp networks to direct with all network services removed. The same is valid for the isolated where DHCP support is no longer dropped.
There are also some enhancements to the Recovery Settings, leading to a more unified look and feel for all cases:
- For on-premises to cloud replications (Cloud Director destination clouds), the source and the destination networks can be mapped, similarly to cloud-to-cloud replications
- For vSphere DR and migration:Recovery settings are validated based on the replication settings
- Source and destination network mappings allow network mapping per VM. Another new feature is the Guest Customization Global Setting, which can control the Guest Customization Settings – activated or deactivated for all new replications. It can still be overwritten through the Recovery Settings of each replication. Auditing is also improved with all the new events added to the VMware Cloud Director audit trail, such as logins/logouts, settings changes, appliance configuration, etc. You can review and export these from the VMware Cloud Director Events console. This is extremely useful around the Sovereign Cloud initiative.The notifications also get refined in VMware Cloud Director Availability 4.6. The email channel is extended and can now be used for transmitting messages about all the available events and activities, including replication-related information.VMware Cloud Director Availability 4.6 supports direct upgrades from 4.4.x and 4.5.x. for Cloud Director clouds and from 4.5.x for vSphere clouds.
E.R
Comments
Post a Comment