o To restore a VM: vcbRestore -s
o Identify the folder that will store the VM: vcbUtil -c vmfolders
o Use vcbResAll to restore all the VMs from the archive you created using vcbSnapAll.
Appendix B - Restoring VMs from ESX Server 2.5.x to ESX Server 3.x
Supplementary Documentation
vSphere Management Assistant Guide (vMA)
o The vSphere Management VCP-410 exam Assistant (vMA) is a VM that includes a Linux distribution, the vSphere command-line interface, & the vSphere SDK
for Perl. vMA allows administrators to run scripts or agents that interact with ESX/ESXi & vCenter systems without having to explicitly
authenticate each time. vMA can also collect ESX/ESXi & vCenter logging information and store the information on vMA for analysis.
o vMA comes preconfigured with two accounts, vi-admin & vi-user.
o You can use the vima-update utility from inside vMA to download updates & VMware components, including the operating system.
Configuration file: /etc/vmware/esxupdate/vimaupdate.conf
o You can move files from the ESX/ESXi host to the vMA console (and back) using the vifs command.
o vMA also includes an authentication component (vi-fastpass) & a logging component (vi-logger).
o When you add an ESX/ESXi system as a target server, vi-fastpass creates two users with obfuscated passwords on the target server:
o vi-admin (administrator privileges)
o vi-user (read-only privileges)
o After the target server has been added, you must initialize vi-fastpass. Use one of the following methods:
o Run vifpinit.
o Call LoginByFastpass in a Perl or Java program.
o vi-logger consists of a log daemon (vilogd) that collects & processes log files & the vilogger CLI that supports logger configuration.
o By default, vilogd places the logs in /var/log/vmware. To specify a different log location, change the /etc/vmware/viconfig/vilogdefaults.xml
file.
o You can use vMA to target ESX/ESXi 3.5 VCP-410 exam questions Update 2 or later, ESX/ESXi 4.0, or vCenter Server 4.0 systems.
o The root user account is disabled on vMA. To run privileged commands, use sudo. By default, only vi-admin can run commands that require
sudo.
o You cannot upgrade from VIMA 1.0 to vMA 4.0. You must deploy the vMA 4.0 OVF instead.
o You cannot use the vi-user account until you have specified a password.
o The vi-user account has limited privileges on target ESX/ESXi systems & cannot run any vilogger commands or any commands that require
sudo execution.
o On vCenter Server targets, vi-user is not supported.
o Add Target Servers:
o sudo vifp addserver
o Initialize vi-fastpass: vifpinit
o Verify that the target server has been added: vifp listservers
o If the name of a target server changes, you must remove the target server using vifp removeserver with the old name, then add the server
using vifp addserver with the new name.
o Running vifpinit always initializes all current target servers. If you add multiple servers in sequence, you do not have to call vifpinit for each
server.
o The directory /opt/vmware/vima/samples VCP-410 study guide contains examples in Perl & Java.
o Commands with options:
o vifpinit
o vifp (administrative interface)
o addserver
o removeserver
o rotatepassword
o listservers
o vilogger (logging interface)
o enable
o disable
o updatepolicy
o list
o vifplib (library)
o vilogger interface - collect log files from the target ESX/ESXi or vCenter Server hosts.
o The vifplib library allows you to programmatically connect to vMA targets using Perl or Java.
12/24/2009
