Testking VCP-410

o When you restore the standard switch, a new virtual adapter is created and the management network uplink that is currently connected to vNetwork Distributed Switch is migrated to the new virtual switch. o The software creates these partitions: o One 4GB VFAT scratch partition for system swap. o One VMFS3 partition on the remaining free space. o The installer creates a 110MB diagnostic partition for core dumps. o The scratch partition is not required (but created by default during the installation). It is used to store vm-support output, which you need VCP-410 questions when you create a support bundle. o Lockdown mode prevents remote personnel from logging in to the ESXi host by using the root login name. By default, lockdown mode is disabled. o Resetting the configuration does not remove virtual machines on the ESXi host. After you reset the configuration defaults, the virtual machines are not visible, but you can retrieve them by reconfiguring storage and reregistering the virtual machines. o When you perform a configuration backup, the serial number is backed up with the configuration and is restored when you restore the configuration. The serial number is not preserved when you run the Recovery CD (ESXi Embedded) or perform the repair operation (ESXi Installable). o When you restore the configuration, the target host must be in maintenance mode, which means all virtual machines (including the vSphere CLI virtual appliance) must be powered off. o Run the vicfg-cfgbackup command with the -s flag to save the host configuration to the specified backup filename. o When you restore configuration data, the build number currently running on the host must be the same as the build number that was running when you created the backup file. You can override this requirement by including the -f (force) flag with the vicfg-cfgbackup command. o Run the vicfg-cfgbackup command with the -l flag to load the host configuration from the specified backup file. o You can restore the ESXi Installable software by running the ESXi installation CD in repair mode. All host configuration data is overwritten by VCP-410 dumps system defaults. o During the repair operation, your existing ESXi 4.0 Installable VMFS datastore is preserved if it is in its original location on the ESXi 4.0 boot disk, or if it is located on another disk (separate from the boot disk). If you changed the VMFS location on the boot disk, it is preserved if it is located beyond the 900MB partition. vSphere upgrade guide o When you upgrade from ESX 3.x/ESXi 3.5 to ESX 4.0/ESXi 4.0, you can use either the vSphere Host Update Utility or vCenter Update Manager. o EDIT – you can also use the upgrade script (esxupgrade.sh – KB 1009440). VMware doesn’t mention the option of a fresh install at any point; they are pushing the upgrade option as much as possible. You can’t seem to do an upgrade with the ESX4 install CD. o Host Update Utility is used for upgrading ESX 3.x/ESXi 3.5 standalone hosts to ESX 4.0/ESXi 4.0 and for patching ESXi 4.0 standalone hosts. It is a standalone Microsoft Windows application recommended for smaller deployments with fewer than 10 ESX/ESXi hosts, without vCenter Server or Update Manager. o vCenter Update Manager is for upgrading and updating ESX/ESXi hosts that are managed in vCenter Server. o Orchestrated upgrades can be used to upgrade the VM hardware and VMware Tools. o No VMFS upgrade is required if you are upgrading from ESX 3.x o You must upgrade VMware Tools before upgrading virtual hardware. o After you upgrade to vCenter Server, you cannot revert to VirtualCenter 2.x. Take appropriate backups before starting the upgrade. o Upgrade VirtualCenter 2.x to vCenter Server 4.0: o Make sure your database is compatible o Have required permissions Passed VCP-410 o Take a full backup of the VirtualCenter 2.x database o Back up the VirtualCenter 2.x SSL certificates o Install the vSphere Client o vCenter Converter, upgrade o vCenter Guided Consolidation upgrade o Upgrade to vCenter Update Manager 4.0. o Use vCenter Update Manager to upgrade ESX 3.x hosts to ESX 4.0. (or use host update utility) o Use vCenter Update Manager to upgrade your VMs. vCenter Update Manager ensures that the VMware Tools upgrade and the virtual hardware upgrade happen in the correct order o Upgrade your product licenses o ESX 2.x hosts cannot be added to clusters. o Oracle 9i is no longer supported. o Microsoft SQL Server 2000 is no longer supported. o To Back Up VirtualCenter 2.x: o Make a full backup of the VirtualCenter 2.x database.