VMware 3V0-22.21 Dumps Questions Answers

• You must have an FTP, FTPS, HTTP, HTTPS, or SCP server up and running with sufficient disk space to store the backup.
• Dedicate a separate folder on your server for each file-based backup.

• In a Web browser, go to the vCenter Server Appliance Management Interface, https://appliance-IP-address-or-FQDN:5480.
• Log in as root.
• In the vCenter Server Appliance Management Interface, click Summary.
• Click Backup.

PrerequisitesProcedureThe Backup Appliance wizard opens.

• Enter the backup protocol and location details.

Option

Description

Backup protocol

Select the protocol to use to connect to your backup server. You can select FTP, FTPS, HTTP, HTTPS, or SCP.

For FTP, FTPS, HTTP, or HTTPS the path is relative to the home directory configured for the service. For SCP, the path is absolute to the remote systems root directory.

Backup location

Enter the server address and backup folder in which to store the backup files.

Port

Enter the default or custom port of the backup server.

User name

Enter a user name of a user with write privileges on the backup server.

Password

Enter the password of the user with write privileges on the backup server.

• (Optional) Select Encrypt Backup Data to encrypt your backup file and enter a password for the encryption.

If you select to encrypt the backup data, you must use the encryption password for the restore procedure.

• Click Next.
• On the Select parts to backup page, review the data that is backed up by default.
• (Optional) Select Stats, Events, and Tasks to back up additional historical data from the database.
• (Optional) In the Description text box, enter a description of the backup and click Next.
• On the Ready to complete page, review the summary information for the backup and click Finish.

The Backup Progress window opens and indicates the progress of the backup operation.

• After the backup process finishes, click OK to close the Backup Progress window.

ResultsYou successfully created a backup file of the vCenter Server Appliance.

VMware vSphere ESXi can use locally attached SSDs (Solid State Disk) and flash devices in multiple ways. Since SSDs offer much higher throughput and much lower latency than traditional magnetic hard disks the benefits are clear. While offering lower throughput and higher latency, flash devices such as USB or SATADOM can also be appropriate for some use cases. The potential drawback to using SSDs and flash device storage is that the endurance can be significantly less than traditional magnetic disks and it can vary based on the workload type as well as factors such as the drive capacity, underlying flash technology, etc.

This KB outlines the minimum SSD and flash device recommendations based on different technologies and use case scenarios.

SSD and Flash Device Use Cases

A non-exhaustive survey of various usage models in vSphere environment are listed below.

• Host swap cache

• Regular datastore
• vSphere Flash Read Cache (aka Virtual Flash)
• vSAN
• vSphere ESXi Boot Disk
• vSphere ESXi Coredump device
• vSphere ESXi Logging device

SSD Endurance Criteria

The flash industry often uses Tera Bytes Written (TBW) as a benchmark for SSD endurance. TBW is the number of terabytes that can be written to the device over its useful life. Most devices have distinct TBW ratings for sequential and random IO workloads, with the latter being much lower due to Write Amplification Factor (WAF) (defined below). Other measures of endurance commonly used are DWPD (Drive Writes Per Day) and P/E (Program/Erase) cycles.

Conversion formulas are provided here:

• Converting DWPD (Drive Writes Per Day) to TBW (Terabytes Written):
• Converting Flash P/E Cycles per Cell to TBW (Terabytes Written):

WAF is a measure of the induced writes caused by inherent properties of flash technology. Due to the difference between the storage block size (512 bytes), the flash cell size (typically 4KiB or 8KiB bytes) and the minimum flash erase size of many cells one write can force a number of induced writes due to copies, garbage collection, etc. For sequential workloads typical WAFs fall in the range of single digits while for random workloads WAFs can approach or even exceed 100. Table 1 contains workload characterization for the various workloads excepting the Datastore and vSphere Flash Read Cache workloads which depend on the characteristics of the Virtual Machines workloads being run and thus cannot be characterized here. A WAF from the table can be used with the above P/E to TBW formula.