5.0

User Name and
Password
This authentication information is required so that SRM can use the database.
Connection Count
The initial connection pool size. If all connections are in use and a new one is
needed, a connection is created as long as it does not exceed the maximum
number of connections allowed. It is faster for SRM to use a connection from
the pool than to create a new one. In most cases, it is not necessary to change
this setting. Before changing this setting consult with your database
administrator.
Max Connections
The maximum number of connections to open to the database at one time. If
the database administrator has restricted the number of connections that the
database can have open, this value cannot exceed that number. In most cases,
it is not necessary to change this setting. Before changing this setting consult
with your database administrator.
SRM and VMware vCenter Server
The SRM server operates as an extension to the vCenter Server at a site. Because the SRM server depends on
vCenter Server for some services, you must install and configure vCenter Server at a site before you install
SRM.
SRM takes advantage of vCenter services, such as storage management, authentication, authorization, and
guest customization. SRM also uses the standard set of vSphere administrative tools to manage these services.
How Changes to vCenter Server Inventory Affect SRM
Because SRM protection groups apply to a subset of vCenter inventory, changes to the protected inventory
made by vCenter administrators and users can affect the integrity of SRM protection and recovery. SRM
depends on the availability of certain objects, such as virtual machines, folders, resource pools, and networks,
in the vCenter inventory at the protected and recovery sites. Deletion of resources such as folders or networks
that are referenced by recovery plans can invalidate the plan. Renaming or relocating objects in the vCenter
inventory does not affect SRM, unless it causes resources to become inaccessible during test or recovery.
SRM can tolerate the following changes at the protected site without disruption:
n
Deleting protected virtual machines.
n
Deleting an object for which an inventory mapping exists.
SRM can tolerate the following changes at the recovery site without disruption:
n
Moving placeholder virtual machines to a different folder or resource pool.
n
Deleting an object for which an inventory map exists.
SRM and the vCenter Database
If you update the vCenter installation that SRM extends, do not reinitialize the vCenter database during the
update. SRM stores identification information about all vCenter objects in SRM's database. If you reinitialize
the vCenter database, the identification data that SRM has stored no longer matches identification information
in the new vCenter and objects are not found.
Chapter 1 Administering VMware vCenter Site Recovery Manager
VMware, Inc. 17