VMware 2V0-33.22 - VMware Cloud Professional

vCenter Mapping Mapping vCenters in a DR plan consists of selecting source vCenters that are registered to the protected site. Choosing a target vCenter for a Failover SDDC is simple; each SDDC contains a single vCenter instance. For VMware Cloud Disaster Recovery, keep in mind that a protected site can have multiple registered vCenters, but you can only map one vCenter on VMware Cloud on AWS per-DR plan. https://vmc.techzone.vmware.com/resource/introduction-vmware-cloud-disaster-recovery#inventory-and-resource-mapping https://vmc.techzone.vmware.com/resource/protection-groups-and-recovery-plans-vcdr#create-a-disaster-recovery-plan

https://docs.vmware.com/en/VMware-Cloud-Disaster-Recovery/services/vmware-cloud-disaster-recovery/GUID-8AE1DC05-46D1-410C-99F6-7687FEB876B5.html

The three types of gateways that can be found in VMware Cloud on AWS are Option A: Distributed Tier-1, Option B: Standard Tier-1, and Option D: Compute Tier-1.

Distributed Tier-1 gateways are used for secure access between on-premises networks and the VMware Cloud on AWS SDDC network. Standard Tier-1 gateways are used for secure access between the VMware Cloud on AWS SDDC network and the public internet. Compute Tier-1 gateways are used for secure access between the workloads running on the VMware Cloud on AWS SDDC and the public internet.

For more information, please refer to the official VMware documentation on VMware Cloud on AWS Gateways: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.networking/GUID-1F2D1BFC-F5C7-4534-8B49-39F9D08E7F1A.html

The two use cases that can be met with VMware Cloud on Dell EMC and VMware Cloud on AWS Outposts are Option C: Applications needing local data processing and/or low latency integrations, and Option D: Critical workloads that use restricted data.

VMware Cloud on Dell EMC and VMware Cloud on AWS Outposts both provide local data processing and low latency integrations, making them ideal for applications that require quick and efficient access to data. Additionally, the highly secure infrastructure of both solutions make them a great choice for critical workloads that use restricted data.

For more information, please refer to the official VMware documentation on VMware Cloud on Dell EMC: https://www.vmware.com/products/vmware-cloud-on-dellemc.html And the official VMware documentation on VMware Cloud on AWS Outposts: https://www.vmware.com/products/vmware-cloud-on-aws-outposts.html

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-ED8B84E8-BF1C-47EE-BB60-8D5741351822.html

By default, the management gateway firewall is set to deny all traffic between the internet and vCenter Server. Verify that the appropriate firewall rules are in place.

The administrator can create an NSX firewall rule in the VMware Cloud data center that allows access to the vCenter from the on-premises data center. This would allow the VPN connection to connect to the vCenter, allowing the administrator to access and manage the VMware Cloud environment.

https://docs.vmware.com/en/VMware-Cloud-Disaster-Recovery/services/vmware-cloud-disaster-recovery/GUID-11C83D2A-A478-4823-B9B3-275AF6DD31CC.html

A protection group in VMware Cloud Disaster Recovery (VCDR) consists of members (virtual machines or VMs) and policies for snapshots. These policies define the consistent point-in-time copies of the VMs, which are used for disaster recovery. The protection group also includes virtual machine file system (VMFS) datastores, which are used to store the copies of the VMs, and VM customizations, which are used to customize the VMs. Clusters are not part of a protection group in VCDR.

Route-based IPSec VPNs provide the flexibility to dynamically learn when new networks are created, making them the ideal choice for establishing connectivity between an on-premises data center and VMware Cloud. Route-based IPSec VPNs use the Border Gateway Protocol (BGP) to dynamically learn and propagate routes over the VPN tunnel, allowing for scalable and secure connectivity. [1]

[1] https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.networking/GUID-EDA5A6E5-6C5B-4F66-9C2F-2C6D4F6EF8F6.html

Planning your Azure VMware Solution deployment is critical for a successful production-ready environment for creating virtual machines (VMs) and migration. During the planning process, you'll identify and gather what's needed for your deployment. As you plan, make sure to document the information you gather for easy reference during the deployment. A successful deployment results in a production-ready environment for creating virtual machines (VMs) and migration.

In this how-to article, you'll do the following tasks:

Identify the Azure subscription, resource group, region, and resource name

Identify the size hosts and determine the number of clusters and hosts

Request a host quota for eligible Azure plan

Identify the /22 CIDR IP segment for private cloud management

Identify a single network segment

Define the virtual network gateway

Define VMware HCX network segments

The best option for a cloud administrator who wants to deploy a VMware Cloud software-defined data center (SDDC) on a cloud provider and requires a consistent 4.5 Gbps bandwidth from applications to communicate from on-premises to the SDDC is a Route-Based Virtual Private Network (VPN). This type of connection offers enhanced performance [1][2], flexibility, scalability, and security compared to other options, such as Policy-Based Virtual Private Network (VPN), Private L2 Virtual Private Network (VPN), or Private Line.

According to the VMware official site, "Route-based VPN enables a secure connection between two or more sites, or between a site and a mobile user, and provides better performance and scalability than a policy-based VPN. Route-based VPNs are also more secure than policy-based VPNs, because the traffic is encrypted with a unique encryption key for each tunnel, rather than relying on a shared key for all tunnels. This allows for secure and reliable connections for devices and applications located in different physical locations." [1]

[1] https://docs.vmware.com/en/VMware-NSX-Data-Center/2.4/com.vmware.nsx.admin.doc/GUID-D6B7B9E9-E134-4C8A-8F2E-1C60A2FEDC1A.html

An extended network segment is required for a cloud administrator to create a virtual machine that requires layer 2 connectivity to an on-premises workload. Extended networks allow for the virtual machines to communicate directly with the on-premises workload while remaining isolated from the public cloud. This allows for the virtual machines to access the same services and workloads as the on-premises workloads while still remaining secure.

For the source and destination host to have shared access to the storage that contains the VM, they must be able to access the same datastore. This requires that the datastore be available to both hosts and that the datastore has the same name on both hosts.

The status of VMware Tools on the VM should also be checked before performing a hot migration. VMware Tools is a suite of utilities that enhances the performance of a virtual machine's guest operating system and improves the management of the virtual machine. If VMware Tools is not installed or not up to date, the hot migration may fail.

Finally, the status of the guest operating system in the VM should also be checked before performing a hot migration. The guest operating system should be up and running and not in a suspended state. If the guest operating system is in a suspended state, the hot migration may fail.

The CPU instruction set required by the VM and the vGPU configuration of the VM are not items to consider when performing a hot migration of a virtual machine. The source and destination host management network IP address families do not need to match for the hot migration to be successful.

References: [1] https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-B2B7F78A-5D5F-4A3E-BEA9-9F6A02A7E1B2.html  [2] https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-EAAE04A9-9DAF-4DAC-B4A0-F35A4F4F2A6A.html  [3] https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-9FADCD7E-F4A8-4F29