Installation guide

n
/etc/motd
n
/etc/initiatorname.vmkiscsi
n
/etc/vmkiscsi.conf
NOTE To migrate other files, consider using a postupgrade script. For example, you might want to create a
script that copies the .ssh directory for root.
Non-Preserved Configuration Components
When you upgrade to ESX 4.1/ESXi 4.1, some components that might have been modified in the ESX 3.5/ESXi 3.5
or ESX 4.0/ESX 4.0 configuration are not preserved.
ESXi
For ESXi, if you modified certain files in the ESXi 3.5 or ESXi 4.0 configuration, the modified configuration is
not retained after the upgrade to ESXi 4.1. Modifications to the following files are not retained after the upgrade.
n
/etc/sfcb/sfcb.cfg
n
inetd.conf
n
motd
n
issue
n
inittab
n
chkconfig.db
ESX
For ESX, if you modified certain files in the ESX 3.5 or ESX 4.0 configuration, the modified configuration is not
retained after the upgrade to ESX 4.1. Modifications to the following files are not retained after the upgrade.
n
/etc/sfcb/sfcb.cfg
n
/etc/vmware/firewall/services.xml
Resource Pool settings configured in ESX 3.5 might not be preserved after upgrade. This loss of configuration
can happen in upgrade scenarios where there are no free resources.
Back Up the ESX Host Configuration
Before you upgrade an ESX host, back up the local VMFS file system. This backup ensures that you will not
lose data during the upgrade.
Procedure
n
Back up the files in the /etc/passwd, /etc/groups, /etc/shadow, and /etc/gshadow directories.
The /etc/shadow and /etc/gshadow files might not be present on all installations.
n
Back up any custom scripts.
n
Back up local images, such as templates, exported virtual machines, and .iso files.
vSphere Upgrade Guide
60 VMware, Inc.