gagakety

The backup software performs an ordinary backup of the VM snapshot moving the data to a backup medium.
o The backup software calls the post-backup script:
o Unmounts the VM snapshot from the backup proxy.
o Takes the VM out of snapshot mode.
o Types of VCB backups:
o Image-level backup
o File-level backup
o Full file backup
220 702 o Differential backup
o Incremental backup
o VCB proxy:
o Windows 2003 SP1 (32-bit or 64-bit)
o Windows 2003 R2 (32-bit or 64-bit)
o Windows 2003 SP2 (32-bit or 64-bit)
o Windows 2008 - Server Core (command line) not supported.
o Disable automatic drive-letter assignment to newly seen volumes:
o diskpart
o automount disable
o Clean out entries of previously mounted volumes: automount scrub
o VCB configuration file: C:Program FilesVMwareVMware Consolidated Backup Frameworkconfigconfig.js
o You need to specify a user name.
o Use the same password you use for logging in to the vCenter host or ESX Server host.
o If you do not specify the password, VCB checks if the password is set in the registry.
o You can configure VCB to use Security Support Provider Interface (SSPI) for authentication.
o When VCB communicates with the vCenter server or ESX Server host, it can transfer data over an encrypted SSL connection or use an
unencrypted network channel.
o VCB supports a maximum of 60 concurrently mounted VMs disks.
o In the Hot-Add mode, you need to create a shadow VM for VCB to use internally. The shadow VM has the same name as your virtual VCB
proxy with the (VCB-HELPER) suffix added.
o If you are using VCB in the Hot-Add mode, in addition to the VCB User role, you need to create the VMware VCB Proxy role.
o You cannot perform a file-level backup simultaneously with an image-level backup for the same VM.
o When you perform a first backup for a VM, the VM has to be powered on, otherwise the backup fails.
o You do not need to power on a VM if your integration module is configured to use VM display names instead of IP addresses or DNS names.
o VMware VSS Component. Guest operating systems:
o Windows Server 2003 32-bit/64-bit
o Windo 9L0-403 ws Vista 32-bit/64-bit
o Windows Server 2008 32-bit/64-bit
o VCB uses the VMware VSS component to create quiesced snapshots of the VM volumes.
o 2003 - VSS snapshots are application-consistent.
o Vista & Windows Server 2008, the snapshots are file-system consistent.
o SYNC Driver
o XP 32-bit
o 2000 Server 32-bit
o 2003 32-bit
o SYNC driver holds incoming I/O & flushes all dirty data to a disk, making snapshots file-system consistent.
o Locations of Custom Quiescing Scripts:
o Pre-freeze - C:Program FilesVMwareVMware ToolsbackupScripts.d or /usr/sbin/pre-freeze-script - All scripts are invoked in ascending
alphabetical order with freeze as the first argument.
o Post-thaw - C:Program FilesVMwareVMware ToolsbackupScripts.d or /usr/sbin/post-thaw-script - All scripts are invoked in
descending alphabetical order with thaw or freezeFail as the first argument.
o Cleaning Up After a Failed Backup Job: run vcbCleanup at the end of your backup cycle.
Appendix A: Using Service Console to Back Up & Restore VMs (valid for ESX4?)
o /etc/vmware/backuptools.conf configuration file to set the most common parameters
o You can use vcbMounter to back up an entire VM in the service console. The vcbMounter utility creates a quiesced snapshot of the VM &
exports the snapshot into a set of files, which can be later used to restore the VM.
o To search for a particular VM & get information about it, use vcbVmName.
o You can back up a VM to a local dir 9L0-510 ectory or to a remote server using scp.
o Use vcbSnapAll to create an archive of groups of VMs in the service console. The vcbSnapAll utility has the same functionality as vcbMounter,
but, in addition, can identify groups of VMs.

o WebOperator – a demo web interface
o Emuneration
o Net – provides Telnet, FTP & POP3
o XML
o Database – JDBC
o Refactoring
o Other plugins:
o Microsoft (separate d 220 701 ownload) – WMI & Active Diretory.
o VI3 (separate download) –backward compatibility
o VI3.5 (Add-on located in <Install_Directory>/extras/plugins) –backward compatibility
o By default, Orchestrator client search returns 20 objects at a time.
o By default the Orchestrator JavaScript engine can access only the classes in the java.util.* package. Full access to the Java virtual machine
(JVM) presents potential security issues. If you require JavaScript access to a wider range of Java classes, you must set an Orchestrator system
property to grant this access.
o Use the Troubleshooting tab to globally reset the server & remove all traces of previous runs. Before you click a troubleshooting option, make
sure the vCO server is stopped.
o The default size of the server log is 5MB.
VMware Consolidated Backup - Virtual Machine Backup Guide
o Backup terminology:
o Differential backup - Backs up only those files that have changed since the last full backup.
o File-level backup - A type of backup that is defined at the level of files & folders.
o Full backup - Backs up all selected files.
o Full VM backup - Backs up all files that comprise the entire VM. These files include disk images, .vmx files, & so on.
o Image-level (volume-level) backup - Backs up an entire storage volume.
o Incremental backup - Backs up only files that have changed since the last backup, whether it is a full or incremental backup.
o Quiescing - A process of bringing the on-disk data of a physical or virtual computer into a state suitable for backups. This process might
include such operations such as flushing dirty buffers from the operating system’s in-memory cache to disk, or other higher-level
application-specific tasks.
o VCB proxy - A physical or VM running Microsoft Windows Server 2003, VCB, & third-party backup software. Used to perform file-level &
image-level VM backups.
o Traditional backup approach - You deploy a backup client to every system that requires backup services. You can then regularly schedule
automatic backups.
o VMware VCB - enables offloaded & impact-free backups for VMs. This approach lets you use the VM snapshot technology & SAN-based data
transfer in 220 702 conjunction with traditional file-based backup software. If you do not have SAN, you can use VCB in the LAN mode.
o Key features of VCB:
o Most major backup applications integrate with VCB.
o Eliminates the need for having a backup agent installed in each VM.
o Can read virtual disk data directly from your SAN storage device using Fibre Channel or iSCSI, or through the ESX Server I/O stack or use a
network connection to an ESX Server host.
o Can run in a VM.
o Supports file-level full & incremental backups for VMs running Microsoft Windows operating system & image-level backups for VMs
running any operating system.
o You can use VCB against a single ESX Server host or with a vCenter.
o The third-party software, integration module, & VCB run on the VCB proxy, a physical or VM that has Microsoft Windows operating system
installed.
o Methods of accessing VM disk data:
o SAN Mode – Use with Fibre Channel & iSCSI storage to completely off-load backups to a physical VCB proxy.
o Hot-Add Mode – Use with any type of storage to perform backups by a VCB proxy set up in a VM. including NAS or local storage. The only
exception is that it does not back up any disks of the VM that has any independent disk, Physical Compatibility RDM, or IDE.
o LAN Mode (NBD Mode) – Use when your environment does not permit the use of the SAN or Hot-Add modes. Your virtual disks cannot
be larger than 1TB each.
o Workflow:
o Backup software calls the pre-backup script:
o (Optional) Runs your custom pre-fr 220 701 eeze script in the VM.
o Quiesces the VM.
o Puts the VM into snapshot mode.
o Unquiesces the VM that was quiesced.
o (Optional) Runs your custom post-thaw script in the VM

o Orchestrator Default Ports:
Purpose Port Description
Lookup 8230 The main port to communicate with the Orchestrator server (JNDI port).
Command 8240 The application communication port (RMI container port) used for remote invocations
Messaging 8250 The Java messaging port used to dispatch events.
Data 8244 The port used to access all Orchestrator data models, such as workflows and policies.
640 802 Dumps /> HTTP server 8280 The port for the HTTP connector used to connect to the Web front-end.
HTTPS server 8281 To connect to the Web front-end and to communicate with vCenter API.
HTTP access 8282 The access port for the Web UI of Orchestrator configuration.
HTTPS access 8283 The SSL access port for the Web UI of Orchestrator configuration. To enable configure Jetty to use SSL.
LDAP 389 The look up port of your LDAP Authentication server.
LDAP using SSL 636 The look up port of your secure LDAP Authentication server.
PostgreSQL 5432 PostgreSQL Server for Orchestrator database.
SQL Server 1433 Microsoft SQL Server for Orchestrator database.
Oracle 1521 Oracle Database for Orchestrator database.
MySQL 3306 MySQL for Orchestrator database.
SMTP Server 25 Email notifications.
o The Orchestrator configuration interface uses a secure connection to communicate with vCenter. You can import the required SSL certificate
from a URL or file.
o The users in the Developers role have editing privileges on all elements.
o Plug-in file extensions are .vmoapp (can contain several .dar files) and .dar (contains all the resources associated with one plug-in).
o You must import the vCenter Server license. The set of plug-ins delivered with Orchestrator do not require a license
vCenter Orchestrator 4.0 – Administration Guide
o VMware vCenter Orchestrator is a development & process-automation platform that provides a library of extensible workflows to allow you to
create & run automated, configurable processes to manage the VMware vCenter infrastructure.
o Orchestrator is composed of three distinct layers: an orchestration platform that provides the common features required for an orchestration
tool, a plug-in architecture to integrate control of subsystems, & a library of preexisting processes.
o Three global user roles: Administrators, Developers (creates applications, customizes/creates new workflows & customizes web front ends), &
End Users (can run & schedule workflows & policies.).
o You can access Orchestrator through the Orchestrator client interface, through a Web browser, or through Web services.
o The Orchestrator client is a desktop application to perform daily administration tasks such as importing packages, running & scheduling
workflows & policies, & managing user permissions. It also serves as an IDE for creating or customizing workflows.
o Workflows consist of actions, attributes, parameters, & schemas.
o Read-only workflow attributes act as global constants for a workflow. Writeable attributes act as a workflow’s global variables.
o You use attributes to transfer variables between workflow elements.
o A workflow schema is a graphical representation of a workflow that shows the workflow as a flow diagram of interconnected workflow
elements.
o A workflow token represents a workflow that is running or has run.
o Ac 640-802 ons are JavaScript functions that take multiple input parameters & have a single return value.
o Action referencing is based on the action module name & action name. Make sure that all elements that reference this action are still valid
after you move the action.
o The Find Elements that Use this Element function checks all packages, workflows, & policies, but it does not check in scripts.
o You can use a task to schedule a workflow once, or multiple times.
o Policies are event triggers that monitor the activity of the system. Policies run predefined events in response to changes in the status or
performance of certain defined objects.
o Packages are for transporting content from one Orchestrator server to another. Packages can contain workflows, actions, policies, Web views,
configurations, or resources.
o Orchestrator signs packages & encrypts the packages for data protection. Packages use X509 certificates to monitor which users export &
redistribute elements.
o Orchestrator client interface allows you to add, import, export, & synchronize packages.
o The naming convention for packages is <domain.your_company>.category.<package_name>.
o Packages from Orchestrator 4.0 are not backwards compatible with Orchestrator 3.2.
640 802 braindumps o Plugins installed by default:
o vCenter 4.0
o vCO library – provides workflows that act as templates
o Mail – SMTP
o SSH

Each vCenter Converter server must be associated with only one vCenter Server.
o You can install vCenter Converter on:
o Windows Server 2000 SP4 with Update Rollup 1
o Windows Server 2003 SP2 (32 bit & 64 bit)
o Windows Server 2003 R2 SP2 (32 bit & 64 bit)
o Windows Server 2008 (32 bit &am vcp 4 64 bit)
o Windows XP Professional SP3 (32 bit & 64 bit)
o You can install the vCenter Converter CLI on Linux computers.
o The operating system on which you install vCenter Converter server determines which VMs & third-party images you can import, export, &
reconfigure.
o VMs must be powered off before you import them. You cannot import suspended VMs.
o Ports required by vCenter Converter:
Communication path Port
vCenter Converter server to remote physical machine TCP– 445, 139 UDP– 137, 138
vCenter Converter server to vCenter Server 443
vCenter Converter client to vCenter Converter server 443
Physical machine to vCenter Server 443
Physical machine to ESX/ESXi 902
o You must install the Microsoft Sysprep tools on your vCenter Server machine in the appropriate location: C:Documents & SettingsAll
UsersApplication DataVMwareVMware VCENTERsysprep.
o You can export VMs that vCenter Server manages to managed formats or hosted vmware vcp 4 formats.
o You can download & use the VMware peTool to add storage & network drivers to the boot CD ISO image.
o You can migrate physical & virtual source machines by using the converter-tool executable file & the command-line interface (CLI). This
provides access to functionality without requiring the vSphere Client plug-in. Can run on Windows & Linux computers.
o The vCenter Converter installer does not support Linux. You must download the latest version of the Linux installer.
vCenter Orchestrator 4.0 – Installation and Configuration Guide
o vCenter Orchestrator is a development and process-automation platform that provides a library of extensible workflows.
o Orchestrator exposes every operation in the vCenter Server API.
o Three global user roles: Administrators, Developers, and End Users.
o Support for several OS:
o Server 2003 R2, 32bit, 64bit
o Server 2008, 32bit, 64bit
o Supported directory service types:
o Active Directory
o OpenLDAP
o eDirectory
o Sun Java Directory Server
o Supported browsers:
o IE 6.0 and 7.0
o Firefox 3.0.6 or later
o Safari 3.x (experimental)
o The database is separate from the standard vCenter database.
o Microsoft SQL Server 2005 Enterprise (SP2) and x64 and (SP1)
o Microsoft SQL Server 2005 Standard (SP2), (SP1)
o Microsoft SQL Server 2000 Enterprise (SP4)
o Microsoft SQL Server 2000 St 640 802 andard (SP4)
o Oracle 10g Enterprise Release 2 (10.2.0.3.0) x32 and x64
o Orchestrator does not support IPv6 operating systems.
o Orchestrator Configuration Service startup type is set to Manual by default.
o http://<computer_DNS_name_or_IP_address>:8282.
o HTTPS connection through port 8283, you must configure Jetty to use SSL.
o You cannot change the vmware default user name.

When you remediate hosts against baseline groups containing upgrade & patch baselines, the upgrade is performed first. Host upgrade in a
high-latency network in which Update Manager & the hosts are at different locations might take a few hours because the upgrade file is
copied from the Update Manager server repository to the host before the upgrade.
vcp-410 o When you upgrade a host, no third-party management agents or software applications are migrated to the ESX 4.0/ESXi 4.0 host.
o In the ESX 3.5 patch remediation process, cumulative rollups & updates are considered patches. If a rollup contains two patches installed on
the host, the state of the host is noncompliant against the rollup until the rollup itself is installed on the host.
o In the ESX 4.0 patch remediation process, Update Manager operates with vSphere Installation Bundles (*.vib files). A bundle is the smallest
installable unit on an ESX 4.x host. A bulletin defines a specific fix for a host, a rollup that aggregates previous fixes, or an update release.
When a host is compliant with all bundles in a bulletin, it is compliant with the vSphere bulletin that contains the bundles.
o Before the ESX host upgrade remediation, Update Manager runs a script on the host to check whether the host can be upgraded. If the host
can be upgraded, Update Manager copies the ISO file to the host. The ISO file contains the bits that are to be installed as well as a Linux kernel
& ramdisk, which serve as the installer environment. The host reboots into the installer, & the installer creates a service console virtual disk
(VMDK) to install the packages into the console VMDK. The host is rebooted, upgraded to ESX 4.0, & reconnected to the vCenter system. If the
upgrade fails, you can roll back to the previous version.
o For ESXi hosts, updates are all-inclusive.
o The ESXi image on the host maintains two copies. The first copy is in the active boot & the second one is the standby boot.
o The active boot contains the patched image & the standby boot contains the previous version of the ESXi host image.
o Take snapshots of templates before remediation, especially if the templates are sealed.
o After a template is started & remediated, the registry keys are restored, & the machine is shut down, returning the template to its sealed
state.
o Staging patches for ESX/ESXi hosts allows you to download the patches from the Update Manager server to the ESX/ESXi hosts, without
applying the patches immediately.
o Staging patches does not require that the hosts enter maintenance mode.
o Update Manager stores data about events. You can review this event data to gather information about operations that are in progress or that
have finished.
o Because of limitations in the ZIP utility used by the Update Manager, the cumulative log file size cannot exceed 2GB, although the script seems
to complete successfully.
o To generate Update Manager log files, exclude the generation of the vCenter logs using the vumsupport. wsf script file:
o C:Program FilesVMwareInfrastructureUpdate Managercscript vum-support.wsf /n
o When you upgrade an ESXi host with less than 10MB of free space in its /tmp directory, although Update Manager indicates that the
remediation process completes successfully, the ESXi host is not upgraded.
vCenter Converter Administration Guide
o vCenter Converter does not support creating thin-provisioned target disks on ESX/ESXi 4.0.
o vCe vmware vcp 410 nter Converter Components:
o vCenter Converter server
o vCenter Converter CLI
o vCenter Converter agent
o vCenter Converter client
o vCenter Converter Boot CD
o When you import a physical system, vCenter Converter uses cloning & system reconfiguration steps.
o When you hot clone dual-boot systems, you can clone only the default operating system to which the boot.ini file points.
o You can clone remotely, as long as it is running & accessible to the network. With local cloning, vCenter Converter runs on the source machine
to perform the migration.
o During hot cloning, the machine you are cloning experiences no downtime.
o Disk-based cloning for cold cloning & importing existing VMs. Supports all basic & dynamic disks.
o Volume-based cloning for hot & cold cloning & for importing existing VMs. All volumes in the destination VM are basic volumes, performed at
the file level or block level, depending on your size selections.
o Only master boot record (MBR) disks are supported. GUID partition table (GPT) disks are not supported.
o Hot cloning supports all types of source volumes that Windows recognizes.
o You cannot schedule reconfiguration tasks.
o Converter can restore VCB images of any guest operating system type on an ESX/ESXi host that vCenter Server manages. However, only disks
are preserved. It does not preserve certain hardware backup information from the original image, but rather substitutes default settings.
o You can schedule an unlimited number of physical-to-virtual recurring tasks & specify how the existing VMs are to be retained.For recurring
tasks, the vCenter Converter agent must be installed permanently on the source machine.
o You can keep multiple VMs as backups to an existing machine
o VM names have an 80-character limit. V vmware vcp 410 Mware recommends a maximum of 60 characters because the time stamp might make the name
exceed the limit.
o Applications might not work if they depend on specific characteristics of the underlying hardware

Patch
o Patch baseline can be either dynamic or fixed.
o You can create baseline groups that contain both patch & upgrade baselines.
o Update Manager settings:
o When to check for updated patch information.
o When to scan or remediate.
o How Passed VCP410 to handle pre-remediation snapshots of VMs.
o How to handle failures to put hosts in maintenance mode.
o How to handle rebooting virtual appliances after remediation.
o Hardware Requirements:
o 2 or more logical cores
o 2GB RAM if Update Manager & vCenter are on different machines
o 4GB RAM if Update Manager & vCenter are on the same machine
o Supported Database Formats
o SQL Server 2005 SP1 (Use SQL Native Client driver for the client)
o SQL Server 2005 Express (Use SQL Native Client driver for the client)
o SQL 2008
o Oracle 10g Release 1 (10.1.0.2)
o Oracle 10g Release 2 (10.2.0.3)
o Oracle 11g Release 1 (11.1.0.6.0)
o It is not recommended to install Update Manager & vCenter on a VM that is managed by the same vCenter system. Upon scanning &
remediating, the VM on which Update Manager & vCenter are installed can reboot & the whole deployment system will shut down.
o If Update Manager does not have access to the Internet, install the Update Manager Download Service (UMDS) to download patches.
o You can export downloaded patches to a specific location that serves as a shared repository for Update Manager: C:Program
FilesVMwareInfrastructureUpdate Managervmware-umds --export –dest <repository_path>
o To set up a download of all available updates: vmware-umds --set-config --enable-host 1 --enable-win 1 --enable-lin 1
o Download the selected patches: vmware-umds --download.
o The Update Manager Web server listens on 9084 TCP & 9087 TCP. The Update Manager SOAP server listens on 8084 TCP.
o To obtain metadata for the patches, Update Manager must be able to connect to https://www.vmware.com & https://xml.shavlik.com, &
requires outbound ports 80 & 443.
o Update Manager connects to vCenter on port 80.
o ESX/ESXi hosts connect to the Update Manager Web server listening on HTTP port 9084 for host patch downloads.
o Update Manager connects to ESX/ESXi hosts on port 902 for pushing the VM patches & host upgrade files.
o The Update Manager Client plug-in connects to the Update Manager SOAP server listening on port 8084. It also connects to the Update
Manager Web server on HTTP port 9087 for uploading the host upgrade files
Passed VCP 4 o Update Manager 4.0 supports Internet Protocol version 6 (IPv6) environment for scanning & remediating ESX/ESXi 4.0 hosts. For VM
scanning & remediation IPv6 is not supported.
o If you have ESX 3.X hosts in your inventory & the Update Manager is installed on a computer with IPv6, the scan & remediation operations on
the hosts fail.
o You can configure Update Manager to take snapshots of VMs before applying patches & Upgrades. You can choose to keep these snapshots
indefinitely or for a fixed period of time.
o Configure how Update Manager responds to failure to put hosts in Maintenance Mode:
o Fail
o Retry
o Power Off VMs & Retry
o Suspend VMs & Retry
o Smart rebooting selectively reboots the virtual appliances & VMs in the vApp to maintain startup dependencies & possibly reboots the
appliances that are not remediated. Smart rebooting is enabled by default
o Update Manager includes four default dynamic patch baselines & four upgrade baselines. You cannot edit or delete default baselines.
o Critical VM Patches
o Non-Critical VM Patches
o Critical Host Patches
o Non-Critical Host Patches
o VMware Tools Upvcp 410 grade to Match Host
o VM Hardware Upgrade to Match Host
o VA Upgrade to Latest
o VA Upgrade to Latest Critical
o Compliance status is displayed based on permissions.
o For ESX/ESXi hosts in a cluster, the remediation process is sequential.
o For multiple clusters under a datacenter, the remediation processes run in parallel.

ESX4 Patch Management Guide
o Bulletin - grouping of one or more VIBs (vSphere Installation Bundle).
o Depot - logical grouping of VIBs – online.
o Offline Bundle zip - archive that encapsulates VIBs.
o Patch - bulletin that groups one or more VIBs together to address a particular issue or enhancement.
o Roll-up - collection of patches that is gro VCP-410 questions uped for ease of download and deployment.
o Update - periodic release of an ESX image.
o VIB - single software package.
o A record of each installed bulletin is written to the /etc/vmware/esxupdate
o Four basic modes of esxupdate:
o Inspection mode
o esxupdate query - display a list of bulletins installed.
o esxupdate info - display information on the contents of one or more bulletins.
o Scan mode - determines which bulletins are applicable.
o Test mode - go through all installation operations without installing.
o Update mode - installs bulletins.
o The installation process is recorded in the esxupdate.log file. By default, this file is located in the /var/log/vmware directory.
o esxupdate never reboots your host.
Optional vSphere Products and Modules
vCenter Update Manager Administration Guide
o Update Manager can:
o Scan for compliance & apply updates for guests, appliances, & hosts.
o Directly upgrade hosts, VM hardware, VMware Tools, & virtual appliances.
o Update third-party software on hosts.
o Update Manager requires network connectivity with vCenter. Each installation of the Update Manager must be associated (registered) with a
single vCenter instance
o The Update Manager Client has two main views, Administrator's view & Compliance view.
o Administrator's view you can:
o Configure the Update Manager settings
o Create & manage baselines & baseline groups
o View Update Manager events
o Review the patch repository & add or remove patches from a baseline
o Compliance view you can:
o View compliance & scan results for each selected inventory object
o Attach & detach baselines & baseline groups from a selected inventory object
o Scan a selected inventory o VCP-410 dumps bject
o Stage patches for hosts
o Remediate a selected inventory object
o The Update Manager process begins by downloading information about a set of security patches. One or more of these patches are
aggregated to form a baseline. Multiple baselines can be added to a baseline group. A baseline group is a composite object that consists of a
set of non-conflicting baselines. You can use baseline groups to combine different types of baselines & then scan & remediate an inventory
object against all of them as a whole. If a baseline group contains both upgrade & patch baselines, the upgrade executes first.
o A collection of VMs, virtual appliances, & ESX/ESXi hosts or individual inventory objects can be scanned for compliance with a baseline or a
baseline group & later remediated (updated). You can initiate these processes manually or through scheduled tasks.
o You can configure the Update Manager server to download patches either from the Internet or from a shared repository.
o Types of scan:
o Patch scan – ESX 3.0.3 & later, ESX 3i version 3.5 & later, VMs running Windows or Linux.
o Host upgrade scan – ESX 3.0.0 & later & ESX 3i version 3.5 & later.
o VMware Tools scan –Windows or Linux.
o VM hardware upgrade scan.
o Virtual appliance upgrade scan –VMware Studio registered Red Hat, Ubuntu, SUSE, & CentOS Linux virtual appliances.
o Staging patches for ESX/ESXi 4.0 hosPassed VCP-410 ts allows you to download the patches from the Update Manager server to the ESX/ESXi hosts without
applying the patches immediately.
o Remediation applies patches & upgrades after a scan is complete.
o Baselines can be:
o Upgrade

o vSphere CLI commands:
Command ESXi 4 ESX 4 VC 4 CLI “esxcfg”
prefix available
Description
esxcli yes yes no Manage pluggable storage architecture (PSA) & native multipathing (NMP).
resxtop yes yes yes Monitors in real time how ESX hosts use resources. Runs in interactive or
VCP-410 exam batch mode. This command is supported only on Linux.
svmotion no no yes Moves a VM’s configuration file & optionally its disks while the VM is
running. Must run against a vCenter Server system.
vicfg-advcfg yes yes yes esxcfg-advcfg Performs advanced configuration including enabling & disabling CIM
providers. Use this command as instructed by VMware.
vicfg-cfgbackup yes no no esxcfg-cfgbackup Backs up the configuration data of an ESXi system & restores previously
saved configuration data.
vicfg-dns yes yes yes esxcfg-dns Specifies an ESX/ESXi host’s DNS (Domain Name Server) configuration.
vicfg-dumppart yes yes yes esxcfg-dumppart Manages diagnostic partitions.
vicfg-iscsi yes yes yes Manages iSCSI storage.
vicfg-module yes yes yes esxcfg-module Enables VMkernel options. Use this command with the options listed in this
document, or as instructed by VMware.
vicfg-mpath yes yes yes esxcfg-mpath Configures storage arrays.
vicfg-mpath35 no no no Configures storage arrays for ESX/ESXi 3.5 hosts.
vicfg-nas yes yes yes esxcfg-nas Manages NAS file systems
vicfg-nics yes yes yes esxcfg-nics Manages the ESX/ESXi host’s physical NICs.
vicfg-ntp yes yes yes esxcfg-ntp Specifies the NTP (Network Time Protocol) server.
vicfg-rescan yes yes yes esxcfg-rescan Rescans the storage configuration.
vicfg-route yes yes yes esxcfg-route Manipulates the ESX/ESXi host’s route entry
vicfg-scsidevs yes yes yes esxcfg-scsidevs Finds available LUNs.
vicfg-snmp yes yes no esxcfg-snmp Manages the Simple Network Management Protocol (SNMP) agent.
vicfg-syslog yes no yes esxcfg-syslog Specifies the syslog server & the port to connect to that server for ESXi
hosts.
VCP-410 exam questions vicfg-user yes yes no Creates, modifies, deletes, & lists local direct access users & groups of users.
vicfg-vmknic yes yes yes esxcfg-vmknic Adds, deletes, & modifies virtual network adapters (VMkernel NICs).
vicfg-volume yes yes yes Supports resignaturing a VMFS snapshot volume & mounting & unmounting
the snapshot volume.
vicfg-vswitch yes yes yes esxcfg-vswitch Adds or removes virtual switches or modifies virtual switch settings.
vifs yes yes no Performs file system operations such as retrieving & uploading files on the
remote server.
vihostupdate yes yes no Manages updates of ESX/ESXi hosts
vihostupdate35 no no no Manages updates of ESX/ESXi 3.5 hosts
vmkfstools yes yes no Creates & manipulates virtual disks, file systems, logical volumes, & physical
storage devices on an ESX/ESXi host.
vmware-cmd yes yes yes Performs VM operations remotely. This includes, for example, creating a
snapshot, powering the VM on or off & getting information about the VM.
o The rest of the booklet is a detailed description of each command in this table. Similar information can also be found in the command’s
corresponding man pages.
License Server Configuration for vCenter Server 4.0 – ESX 3.x licensing
o Using vCenter Server 4.0 to manage ESX 3.x/ESXi 3.5 hosts, you have several options:
o A single license server for vCenter Server 4.0 and the ESX 3.x/ESXi 3.5 hosts.
VCP-410 study guide o One license server for vCenter Server 4.0, and use another license server for the ESX 3.x/ESXi 3.5 hosts.
o A license server for vCenter Server 4.0, and use host-based licensing for the ESX 3.x/ESXi 3.5 hosts.
o Do not use a license server. Upgrade all of your hosts to ESX 4.0/ESXi 4.0.

o Optimize for performance – Acknowledges changes to the virtual disk immediately, but saves them at a later time.
o VMI currently supports only 32-bit guests.
Additional Resources
Setup for Failover Clustering and Microsoft Cluster Service
o Support for Windows Server 2003 SP2, 2000 SP4, or 2008.
o Only two-node clustering VCP-410 dumps .
Storage Type Cluster in a Box Cluster Across Boxes Standby Host
(n+1)
Virtual disks Yes (recommended) No No
Non-pass-through RDM (virtual compatibility mode) Yes Yes No
Pass-through RDM (physical compatibility mode) No Yes (recommended) Yes
o Clusters across physical machines with non-pass-through RDM is supported only for clustering with Windows 2000 Server or Windows Server
2003. It is not supported for clustering with Windows Server 2008.
o Not supported:
o Clustering on iSCSI or NFS disks.
o Clustered virtual machines as part of VMware clusters (DRS or HA).
o MSCS in conjunction with VMware Fault Tolerance.
o Migration with VMotion.
o N-Port ID Virtualization (NPIV)
o With native multipathing (NMP), clustering is not supported when the path policy is set to round robin.
o You must use hardware version 7 with ESX4.
o You can put the boot disk of a virtual machine on a SAN-based VMFS volume.
o Clustered continuous replication (CCR) environment for Microsoft Exchange - Use physical compatibility mode RDMs.
o For boot disks - Select VCP-410 “Support clustering features such as Fault Tolerance” to create a disk in eagerzeroedthick format.
o SCSI Controller Type:
o Windows 2000 and 2003 - Server LSI Logic Parallel (download from the LSI web site).
o Windows 2008 - LSI Logic SAS
o Cluster across boxes:
o Shared storage must be on an FC SAN.
o RDM in physical compatibility (pass-through) or virtual compatibility (non-pass-through) mode. VMware recommends physical
compatibility mode. The cluster cannot use virtual disks for shared storage.
o Failover clustering with Windows Server 2008 is not supported with virtual compatibility mode
o Standby Host (n+1): Use only a single physical path from the host to the storage arrays.
vSphere Command-Line Interface Installation and Reference Guide
o vSphere CLI commands run on top of the vSphere SDK for Perl.
o You can install a vSphere CLI package on either Linux or Microsoft Windows, or deploy the vSphere Management Assistant (vMA).
o If you establish a vCenter Server system as a target server, you can execute most vSphere CLI commands against all ESX/ESXi systems it
manages without additional authentication.
o You can use vSphere CLI commands interactively or in scripts.
o The installation script for the vSphere CLI is supported on:
o Red Hat Enterprise Linux (RHEL) 5.2 (64 bit)
o Red Hat Enterprise Linux (RHEL) 5.2 (32 bit)
o SUSE Enterprise Server 10 SP1 32 bit
o Ubuntu 8.04 32 bit
o vSphere CLI is supported on:
o Windows XP SP2 32 bit
o Windows XP SP2 64 bit
o Windows Vista Enterprise SP1 32 bit
o Windows Vista Enterprise SP1 64 bit
o If you set up a vCenter Server system as a target server, you can specify any of the ESX/ESXi hosts that vCente VCP-410 braindump r Server system manages using
the --vihost option.
o VMware recommends that you use the vSphere CLI commands with the vicfg prefix. Commands with the esxcfg prefix are available mainly for
compatibility reasons & might become obsolete.

o VMware HA Attributes:
Attribute Description
das.isolationaddress[...} Address to ping to determine if a host is isolated from the network. If not specified, the default
gateway of the console network is used. Can specify multiple isolation addresses (up to 10).
das.usedefaultisolationaddress Specifies whether or not this default is used (true|false).
das.failuredetectiontime VCP-410 exam questions Failure detection time for host monitoring. The default is 15000 milliseconds
das.failuredetectioninterval Heartbeat interval among VMware HA hosts. Default is 1000 milliseconds.
das.defaultfailoverhost The host that VMware HA tries to fail virtual machines over to.
das.isolationShutdownTimeout Time the system waits for a VM to shut down before powering it off. Default is 300 seconds.
das.slotMemInMB The maximum bound on the memory slot size.
das.slotCpuInMHz The maximum bound on the CPU slot size.
das.vmMemoryMinMB Memory resource value assigned to a VM if it’s not specified or zero. Default is 0 MB.
das.vmCpuMinMHz Default CPU resource value assigned to a VM if it’s not specified or zero. Default is 256MHz.
das.iostatsInterval I/O stats interval for VM monitoring sensitivity. Default is 120 (seconds).
o If you change the value of any of the following advanced attributes, you must disable and then re-enable VMware HA before your changes
take effect.
o das.isolationaddress[...]
o das.usedefaultisolationaddress
o das.failuredetectiontime
o das.failuredetectioninterval
o das.isolationShutdownTimeout
o On ESX hosts, HA communications travel over service console networks.
o On ESXi hosts, HA communications travel over VMkernel networks.
o HA needs and automatically opens the following firewall ports:
o Incoming port: TCP/UDP 8042-8045
o Outgoing port: TCP/UDP 2050-2250
o VMware Fault Tolerance provides continuous availability for virtual machines by creating and maintaining a Secondary VM that is identical to,
and continuously available to replace, the Primary VM in the event of a failover situation.
o A fault tolerant VM and its secondary copy are not allowed to run on the same host. Fault Tolerance uses anti-affinity rules.
o Fault Tolerance prerequisites:
o VMware HA must be enabled on the cluster. Host Monitoring should also be enabled.
o Host certificate checking must be enabled for all hosts.
o Each host must have a VMotion and a Fault Tolerance Logging NIC configured.
VCP-410 study guide o Hosts must have the same version and patch level.
o Hosts must have processors from the FT-compatible processor group.
o Hosts must have Hardware Virtualization (HV) enabled in the BIOS.
o Virtual machines must be stored in virtual RDM or VM disk (VMDK) files that are thick provisioned with the Cluster Features option.
o Virtual machines must be running on one of the supported guest operating systems.
o Not supported for fault tolerant virtual machines.
o Snapshots.
o Storage VMotion
o DRS features
o SMP virtual machines
o Physical RDMs
o Paravirtualized guests
o NPIV
o NIC passthrough
o EPT/RVI
o You should have no more than four fault tolerant virtual machines (primaries or secondaries) on any single host.
o The recommendation is that you use a maximum of 16 virtual disks per fault tolerant virtual machine.
Appendix – Fault Tolerance Error Messages
vSphere Web Access Administrator’s Guide
o Supported Operating Systems:
o Windows 2003 SP1, XP Pro SP3, XP Home SP2, 2000 SP4
o Linux with standard libraries, but requiring GTK+ 2.
o Supported browsers:
o IE 6, 7 or later
o Firefox 2, 3.0 or later
o The console webAccess service is now vmware-webAccess
o The Alarms tab is available only wh VCP-410 questions en you use vSphere Web Access to connect to vCenter Server.
o You can view the assigned tasks for a virtual machine, but you cannot assign tasks using Web Access.
o New disk policy (not available option from vSphere Client)
o Optimize for safety – Saves all changes to the virtual disk before notifying the system

Periodically (every two seconds by default), the system examines the loads of the various nodes and determines if it should rebalance the load
by moving a virtual machine from one node to another.
o Transparent page sharing has also been optimized for use on NUMA systems.
o The VMkernel.Boot.sharePerNode option controls whether memory pages can be shared (de-duplicated) only within a sVCP-410 ingle NUMA node or
across multiple NUMA nodes. It is turned on by default.
o If you turn off the option, identical pages can be shared across different NUMA nodes. In memory-constrained environments, such as VMware
View this could be very beneficial.
o The systems that offer a NUMA platform include AMD CPUs or the IBM Enterprise X-Architecture.
o You must manually select the boxes for all processors in the NUMA node. CPU affinity is specified on a per-processor, not on a per-node, basis.
o Specify nodes to be used for future memory allocations only if you have also specified CPU affinity.
Appendix A - Performance Monitoring Utilities: resxtop and esxtop
o The esxtop utility reads its default configuration from .esxtop4rc.
o Do not edit the .esxtop4rc file. Instead, select the fields and the order in a running esxtop process, make changes, and save this file using
the W interactive command.
Appendix B – Advanced attributes
vSphere Availability Guide
o The first five hosts added to the cluster are designated as primary hosts, and all subsequent hosts are designated as secondary hosts. The
primary hosts maintain and replicate all cluster state and are used to initiate failover actions. If a primary host is removed from the cluster,
VMware HA promotes another host to primary status.
o One of the primary hosts is also designated as the active primary host and its responsibilities include:
o Deciding where to restart virtual machines.
o Keeping track of failed restart attempts.
o Determining when it is appropriate to keep trying to restart a virtual machine.
o If the active primary host fails, another primary host replaces it.
o If a host stops receiving heartbeats from all other hosts in the cluster for more than 12 seconds, it attempts to ping its isolation addresses. If
this also fails, the host declares itself as isolated from the network.
o Three types of admission control:
o Host
o Resource pool
o HA
o Only VMware HA admission control can be disabled.
o Slot size is a logical representation of t VCP-410 braindump he memory and CPU resources that satisfy the requirements for any powered-on virtual machine in the
cluster.
o The maximum Configured Failover Capacity that you can set is four.
o If your cluster contains any virtual machines that have much larger reservations than the others, they will distort slot size calculation. To avoid
this, you can specify an upper bound for the CPU or memory component of the slot size by using the das.slotCpuInMHz or das.slotMemInMB
advanced attributes, respectively.
o You can configure VMware HA to perform admission control by reserving a specific percentage of cluster resources for recovery from host
failures.
o You can configure VMware HA to designate a specific host as the failover host.
o To ensure that spare capacity is available on the failover host, you are prevented from powering on virtual machines or using VMotion to
migrate virtual machines to the failover host.
o When choosing an admission control policy, you should consider a number of factors:
o Avoiding Resource Fragmentation - The Host Failures Cluster Tolerates policy avoids resource fragmentation by defining a slot as the
maximum virtual machine reservation. The Percentage of Cluster Resources policy does not address the problem of resource
fragmentation. With the Specify a Failover Host policy, resources are not fragmented because a single host is reserved for failover.
o Flexibility of Failover Resource Reservation - The Host Failures Cluster Tolerates policy allows you to set the failover level from one to four
hosts. The Percentage of Cluster Resources policy allows you to designate up to 50% of cluster resources for failovVCP-410 exam er. The Specify a
Failover Host policy only allows you to specify a single failover host.
o Heterogeneity of Cluster - In a heterogeneous cluster, the Host Failures Cluster Tolerates policy can be too conservative because it only
considers the largest virtual machine reservations when defining slot size and assumes the largest hosts fail when computing the Current
Failover Capacity. The other two admission control policies are not affected by cluster heterogeneity