VCP4: Difference between revisions
Jump to navigation
Jump to search
m (→Upgrade VMware ESX/ESXi: Added Upgrade Scenarios) |
m (→Upgrade VMware ESX/ESXi: Added rollback) |
||
Line 60: | Line 60: | ||
| with Host Clusters || Use Update Manager. Upgrade VC, Update Manager, ESX, VM, licenses | | with Host Clusters || Use Update Manager. Upgrade VC, Update Manager, ESX, VM, licenses | ||
|- | |- | ||
| without Host Clusters || Use vSphere Host Update Utility | | without Host Clusters || Use vSphere Host Update Utility (good for estates < 10 ESX's), runs from VC Client | ||
|- | |- | ||
| vMotion || Migrate VM's from ESX v3 to v4, then perform required VM upgrade | | vMotion || Migrate VM's from ESX v3 to v4, then perform required VM upgrade | ||
Line 72: | Line 72: | ||
| VC on new machine || Backup DB, copy across SSL folder to new machine, run install | | VC on new machine || Backup DB, copy across SSL folder to new machine, run install | ||
|} | |} | ||
'''ESX/ESXi Upgrade''' | |||
* DHCP not recommended | |||
* Limited support for v2.5.5, all later versions fully supported | |||
* Need to specify a local VMFS for Service Console VM (not ESXi) | |||
'''Rollback''' | |||
* ESX | |||
** Run <code>rollback-to-esx3</code> command in Service Console, delete ESX v4 Service Console following restart | |||
** Restore backed up files | |||
* ESXi | |||
** During boot, press Shift + R to boot into the Standby (ESX3) build | |||
** Restore backup using <code>vicfg-cfgbackup -l</code> | |||
== Secure VMware ESX/ESXi == | == Secure VMware ESX/ESXi == |
Revision as of 14:05, 3 November 2009
Other Resources
Plan, Install and Upgrade VMware ESX/ESXi
Install VMware ESX/ESXi on local storage
Minimum Hardware Requirements
- 64bit CPU (AMD Opteron, Intel Xenon [inc Nahalem])
- CPU Virtualisation features required to support 64bit VM's
- 2GB RAM
- 1+ NIC
- SCSI, Fibre Channel or Internal RAID controller
- LUN, SAS or SATA (SATA must be connected through a SAS controller)
Notes
- ESX's hardware clock should be set to UTC
- IPv6 not supported during installation
ESXi Specifics
- All blank internal disks are formatted with VMFS (except 4GB VFAT scratch/swap partition, used for vm-support dumps)
- Direct Console is used to
- Configure host defaults
- Set-up administrator access
- Troubleshoot
- If no DHCP found during install, default 169.254.0.0 / 16 address assigned
vSphere Editions
Edition | Features |
---|---|
Standard | 6 cores/CPU, 4way vSMP, 256GB/ESX, Update Manager, HA |
Advanced | 12 cores/CPU, Hot Add, FT, vShield, VMotion |
Enterprise | 6 cores/CPU, Storage vMotion, DRS |
Enterprise Plus | 12 cores/CPU, 8way vSMP, maxGB/ESX, vNetwork Distributed Switch, Host Profiles, 3rd Party Multipathing |
Upgrade VMware ESX/ESXi
Pre-Upgrade Backups
- Backup ESX Host Config
- Back up the files in the
/etc/passwd
,/etc/groups
,/etc/shadow
, and/etc/gshadow
directories (shadow dir's may not exist). - Backup any custom scripts
- Backup any
.vmx
files - Backup any local images etc on local VMFS
- Back up the files in the
- Backup ESXi Host Config
- Use vSphere CLI to run
vicfg-cfgbackup --server <ESXi-host-ip> --portnumber <port_number> --protocol <protocol_type> --username username --password <password> -s <backup-filename>
- Use vSphere CLI to run
- VM backup
- Snapshot before upgrade
Upgrade Scenarios
Method | Notes |
---|---|
with Host Clusters | Use Update Manager. Upgrade VC, Update Manager, ESX, VM, licenses |
without Host Clusters | Use vSphere Host Update Utility (good for estates < 10 ESX's), runs from VC Client |
vMotion | Migrate VM's from ESX v3 to v4, then perform required VM upgrade |
Upgrade vMotion | When upgrading from ESX v2, VM's are migrated from VMFS v2 to v3 and upgraded |
Cold migration (with VC) | Move VM's through VC to v4 ESX's and power-up, then upgrade VM |
Cold migration (without VC) | Manually move VM's to v4 ESX's and power-up, then upgrade VM |
VC on new machine | Backup DB, copy across SSL folder to new machine, run install |
ESX/ESXi Upgrade
- DHCP not recommended
- Limited support for v2.5.5, all later versions fully supported
- Need to specify a local VMFS for Service Console VM (not ESXi)
Rollback
- ESX
- Run
rollback-to-esx3
command in Service Console, delete ESX v4 Service Console following restart - Restore backed up files
- Run
- ESXi
- During boot, press Shift + R to boot into the Standby (ESX3) build
- Restore backup using
vicfg-cfgbackup -l
Secure VMware ESX/ESXi
Install VMware ESX/ESXi on SAN Storage
Identify vSphere Architecture and Solutions
Configure ESX/ESXi Networking
Configure Virtual Switches
Configure vNetwork Distributed Switches
Configure VMware ESX/ESXi Management Network
Configure ESX/ESXi Storage
Configure FC SAN Storage
Configure iSCSI SAN Storage
Configure NFS Datastores
Configure and Manage VMFS Datastores
Install and Configure vCenter Server
Minimum Requirements
- 2x CPU's (2GHz)
- 3GB RAM
- 2GB disk
- Microsoft SQL2005 Express
Scale | VC | CPU | Memory |
---|---|---|---|
50 ESXs, 250 VMs | 32 bit | 2 | 4 GB |
200 ESXs, 2000 VMs | 64 bit | 4 | 4 GB |
300 ESXs, 3000 VMs | 64 bit | 4 | 8 GB |
- Database must be 32bit only, regardless of VC's OS (default database on 64bit SQL is 64bit)