VCP-410 Dumps

o Back up the VirtualCenter 2.x SSL certificates. %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter or %ALLUSERSPROFILE%\VMware\VMware VirtualCenter\. o Note any non-default settings, such as the IP address, the database DSN, user name, password, and assigned ports. o Create a backup copy of vpxd.cfg. o The database upgrade log is at %TEMP%\VCDatabaseUpgrade.log. o By default, a vCenter Server creates a maximum of 10 simultaneous database connections. o Datastores and networks have their own set of privileges that control access to them. o Users are initially granted the No Access role on all new managed objects, including datastores and networks. All existing objects in vCenter Passed VCP410 maintain their permissions after the upgrade. o The upgrade process uses the datacenter's “Read-only” privilege. o If the “Read-only” privilege is nonpropagating (not inherited by child objects), VMware assumes access privileges should not be assigned to datastores and networks. o If the “Read-only” privilege is propagating (inherited by child objects), VMware assumes access privileges should be assigned to datastores and networks so users can view them and perform basic operations that require access. o The “Read-only” propagating permission on a datacenter, as well as all other permissions you have set, will continue to work as expected after the upgrade. o You must change “Read-only” nonpropagating datastore permissions to propagating datastore permissions in order for users to access the datastore. You can assign datastore permissions on datastore or folders containing datastore. The same goes for Network permissions. o The “Database Consumer” sample role assigns the “Allocate Space” privilege to the datastore. “Network Consumer” sample role assigns the “Assign Network” privilege. o Host Update Utility does not upgrade VMFS datastores or VM o Update Manager supports mass remediation. o During host upgrades using the Update Manager, static IP addresses are a requirement. o The upgrade to ESXi4 & ESX4 preserves almost all configuration data, including your networking, security, and storage configuration. The only configuration not preserved is related to licensing. o For ESX only, the upgrade reuses the existing /boot partition to hold the ESX 4.0 boot files. After the upgrade, the ESX 3.x installation is Passed VCP 4 mounted in the new ESX 4.0 installation under the /esx3-installation directory. o Backup the ESX Host Configuration: o Back up the files in the /etc/passwd, /etc/groups, /etc/shadow, and /etc/gshadow directories. o Back up any custom scripts. o Back up your .vmx files. o Back up local images, such as templates, exported VMs, and .iso files. o Backup the ESXi Host Configuration: vicfg-cfgbackup --server --portnumber -- protocol --username username --password -s o You cannot perform an in-place upgrade from ESX to ESXi (or from ESXi to ESX). o The only ESX 2.x version that has upgrade support is ESX 2.5.5 – you can perform a migration upgrade with or without VMotion. o Direct, in-place upgrade from ESX 2.5.5 to ESX 4.0 is not supported, even if you upgrade to ESX 3.x as an intermediary step. The default ESX 2.5.5 installation creates a /boot partition that is too small to enable upgrades to ESX 4.0. As an exception, if you have a non-default ESX 2.5.5 installation on which at least 100MB of space is available on the /boot partition, you can upgrade ESX 2.5.5 to ESX 3.x and then to ESX 4.0. o The upgrade logs are here: o /esx3-installation/esx4-upgrade/ o /var/log/vmware/ o For an unsuccessful ESX upgrade: o /esx4-upgrade/ vcp 410 o /var/log/vmware/ o You may need to reconnect the host to vCenter Server and assign an upgraded license to your product within 60 days after the upgrade. o The host sdX devices might be renumbered after the upgrade. o You must convert LUN masking to the claim rule format. Run the esxcli corestorage claimrule convert command. It converts the /adv/Disk/MaskLUNs advanced configuration entry in esx.conf to claim rules with MASK_PATH as the plug-in. o Web Access service is disabled after you upgrade the host. o vSphere Web Access is not supported on ESXi hosts. o 60-day evaluation count down starts even if the host is licensed and you are not using evaluation mode. o One advantage of using evaluation mode is that it offers full feature functionality. o After you determine that the ESX 4.0 upgrade is stable, you can remove the ESX 3.x boot option from the ESX 4.0 bootloader menu to disable the ability to roll back to ESX 3.x. If you deselected the rollback option, this procedure is not applicable. Run the cleanup-esx3 command with the optional -f (force) flag. o The cleanup-esx3 script removes the following files and references from the ESX 4.0 host: o ESX 3.x references in the /etc/fstab directory o ESX 3.x boot files in the /boot directory o The rollback-to-esx3 script in the /usr/sbin/ directory