5.0

Table Of Contents
n
SRM object permissions in vSphere
n
Custom alarms and alarm actions
n
Test plan histories
n
Security certificates
n
Mass IP customization files (CSVs)
New Behavior for 5.0
Because of the significant changes introduce in SRM 5.0, including modifications to the database schemas, an
upgrade while the system is running is not possible.
As a result, the upgrade process involves taking an existing installation offline, upgrading the SRM server and
vSphere Clients, and then migrating existing 4.1 inventory information to the SRM database.
Upgrade Workflow
The steps required to complete an upgrade are as follows:
1 Back up the SRM database at the protected site.
2 Upgrade vCenter Server to version 5.0 at the protected site.
3 Upgrade SRM server to version 5.0 at the protected site. Keep the Storage Report displayed by the installer.
4 Upgrade the database, vCenter Server, and SRM server on the recovery site.
5 At each site, install version 2.0 SRAs (compatible with SRM 5.0).
6 Upgrade the SRM plug-in used by the vSphere Client.
7 Pair the sites.
8 At each site, configure the array manager (using the Storage Report that was generated when the SRM 5.0
installer finished).
9 At only one site, run the srm-migration.exe utility using the vmware-dr.xml configuration file to import
SRM 4.1 inventory.
As the srm-migration.exe utility completes its tasks, the exported XML data files are imported into the SRM
installation.
Prepare for SRM Upgrade
You must complete this process for all SRM sites and assumes all SRM servers are version 4.1 or later.
As part of the upgrade process, vCenter Servers that support SRM servers must be upgraded to version 5.0,
as well. For details about upgrading vCenter Servers, see the vSphere Upgrade Guide. Three upgrade
approaches are available.
Site Recovery Manager Administration Guide
34 VMware, Inc.