2V0-33.22 - VMware Cloud Professional

RAID-1 is a mirror configuration that provides high availability by creating multiple copies of a VMDK. RAID-5 and RAID-6 are erasure coding configurations that provide fault tolerance by distributing data and parity across multiple hosts.

The number of failures to tolerate (FTT) determines how many copies or parity blocks are created for each VMDK. For example, RAID-1 FTT = 2 means that there are three copies of each VMDK.

Therefore, based on your requirements, a possible VM storage policy setting could be RAID-1 FTT = 2, which would provide redundancy at the highest level possible with six hosts.

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vsphere.vmc-aws-manage-data-center-vms.doc/GUID-EDBB551B-51B0-421B-9C44-6ECB66ED660B.html

Managing Costs:

With its capacity and cost management features, vRealize Operations Cloud can predict future demand and provide actionable recommendations to help in managing costs.

Reclamation of Existing Resources:

Assess workload status and resource contention in data centers across your environment:

• Determine the time remaining until CPU, memory, or storage resources run out.
• Realize cost savings when underutilized VMs are identified and reclaimed to be deployed more effectively.

Future Infrastructure Requirements

Run what-if scenarios:

• Identify how much capacity remains after you add or remove VMs or hosts.
• Add hyperconverged infrastructure (HCI) nodes.
• Get a recommendation based on the cost relative to workload placement on different hosts, clusters, data centers, and even different clouds.

Cloud Migration Planning:

Migration planning shows you the capacity and cost information after the migration to a cloud-based infrastructure.

Cost Overview

vRealize Operations Cloud supports costing for private clouds, public clouds, and VMware Cloud infrastructure.

You can track expenses for a single virtual machine, and identify how these expenses attribute to the overall cost associated with your private cloud accounts and VMware Cloud infrastructure accounts.

On the Cost Overview home page in vRealize Operations Cloud, you can find details about the costs associated with your VMware Cloud infrastructure accounts, public cloud accounts, and your private cloud accounts.

You can view the Total Cost of Ownership, Potential Savings, and Realized Savings for your VMware Cloud infrastructure cloud accounts and vSphere private cloud accounts, and Total Cost of Ownership for your private cloud accounts.

Port mirroring is a VMware Cloud tool that an administrator can use to forward all the monitored traffic to a network appliance for analysis and remediation. The network appliance can then analyze the mirrored traffic and take the appropriate remedial action. Port mirroring can also be used to identify and troubleshoot network issues, as well as monitor network activities.

Port mirroring lets you replicate and redirect all of the traffic coming from a source. The mirrored traffic is sent encapsulated within a Generic Routing Encapsulation (GRE) tunnel to a collector so that all of the original packet information is preserved while traversing the network to a remote destination.

Port mirroring is used in the following scenarios:

• Troubleshooting - Analyze the traffic to detect intrusion and debug and diagnose errors on a network.
• Compliance and monitoring - Forward all of the monitored traffic to a network appliance for analysis and remediation.

Port mirroring includes a source group where the data is monitored and a destination group where the collected data is copied to. The source group membership criteria require VMs to be grouped based on the workload such as web group or application group. The destination group membership criteria require VMs to be grouped based on IP addresses. Port mirroring has one enforcement point, where you can apply policy rules to your SDDC environment.

The traffic direction for port mirroring is Ingress, Egress, or Bi Directional traffic:

• Ingress is the outbound network traffic from the VM to the logical network.
• Egress is the inbound network traffic from the logical network to the VM.
• Bi Directional is the traffic from the VM to the logical network and from the logical network to the VM. This is the default option.

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-networking-security/GUID-3268A0D3-89D0-406F-B44F-156DD1A30E00.html