5.5
Table Of Contents
- Site Recovery Manager Installation and Configuration
- Contents
- About Site Recovery Manager Installation and Configuration
- Overview of VMware vCenter Site Recovery Manager
- Site Recovery Manager System Requirements
- Creating the SRM Database
- SRM Authentication
- Installing SRM
- Upgrading SRM
- Configuring Array-Based Protection
- Installing vSphere Replication
- Deploy the vSphere Replication Appliance
- Configure vSphere Replication Connections
- Reconfigure the vSphere Replication Appliance
- Reconfigure General vSphere Replication Settings
- Change the SSL Certificate of the vSphere Replication Appliance
- Change the Password of the vSphere Replication Appliance
- Change Keystore and Truststore Passwords of the vSphere Replication Appliance
- Configure vSphere Replication Network Settings
- Configure vSphere Replication System Settings
- Reconfigure vSphere Replication to Use an External Database
- Use the Embedded vSphere Replication Database
- Deploy an Additional vSphere Replication Server
- Register an Additional vSphere Replication Server
- Reconfigure vSphere Replication Server Settings
- Unregister and Remove a vSphere Replication Server
- Uninstall vSphere Replication
- Unregister vSphere Replication from vCenter Server if the Appliance Was Deleted
- Upgrading vSphere Replication
- Creating SRM Placeholders and Mappings
- Installing SRM to Use with a Shared Recovery Site
- Limitations of Using SRM in Shared Recovery Site Configuration
- SRM Licenses in a Shared Recovery Site Configuration
- Install SRM In a Shared Recovery Site Configuration
- Install SRM Server on Multiple Protected Sites to Use with a Shared Recovery Site
- Install Multiple SRM Server Instances on a Shared Recovery Site
- Install the SRM Client Plug-In In a Shared Recovery Site Configuration
- Connect to SRM in a Shared Recovery Site Configuration
- Connect the SRM Sites in a Shared Recovery Site Configuration
- Configure Placeholders and Mappings in a Shared Recovery Site Configuration
- Use Array-Based Replication in a Shared Recovery Site Configuration
- Use vSphere Replication in a Shared Recovery Site Configuration
- Troubleshooting SRM Installation and Configuration
- Cannot Restore SQL Database to a 32-Bit Target Virtual Machine During SRM Upgrade
- SRM Server Does Not Start
- vSphere Client Cannot Connect to SRM
- Site Pairing Fails Because of Different Certificate Trust Methods
- Error at vService Bindings When Deploying the vSphere Replication Appliance
- OVF Package is Invalid and Cannot be Deployed
- vSphere Replication Appliance or vSphere Replication Server Does Not Deploy from the SRM Interface
- Connection Errors Between vSphere Replication and SQL Server Cannot be Resolved
- 404 Error Message when Attempting to Pair vSphere Replication Appliances
- vSphere Replication Service Fails with Unresolved Host Error
- Increase the Memory of the vSphere Replication Server for Large Deployments
- vSphere Replication Appliance Extension Cannot Be Deleted
- Uploading a Valid Certificate to vSphere Replication Results in a Warning
- vSphere Replication Status Shows as Disconnected
- vSphere Replication Server Registration Takes Several Minutes
- vSphere Replication is Inaccessible After Changing vCenter Server Certificate
- Index
If you install SQL Server on a different machine to SRM Server, both of the SRM Server and SQL Server
machines must belong to the same domain. You then create a domain user that has the SQL Server login and
that also has access to SRM Server.
For information about database sizing, see the Sizing calculator for vCenter Site Recovery Manager databases -
MSSQL at http://www.vmware.com/products/site-recovery-manager/resource.html.
Procedure
1 Select an authentication mode when you create the database instance.
Option Description
Windows authentication
The database user account must be the same user account that you use to
run the SRM service.
SQL Authentication
Leave the default local system user.
2 Create the SRM database user account.
3 Grant the SRM database user account the bulk insert, connect, and create table permissions.
4 Create the database schema.
The SRM database schema must have the same name as the database user account.
5 Set the SRM database user as the owner of the SRM database schema.
6 Set the SRM database schema as the default schema for the SRM database user.
7 (Optional) If you are using SQL Server 2012, configure the NT AUTHORITY\SYSTEM login.
Option Action
General:: Default database
Type the database name.
Server Roles
Select the Public and Admin roles.
User Mapping
Select the check box to map the login to the database.
Configure Oracle Server for SRM
When you create a Oracle Server database, you must configure it correctly to support SRM.
You create and configure an Oracle Server database for SRM by using the tools that Oracle Server provides.
This information provides the general steps that you must perform to configure an Oracle Server database
for SRM. For instructions about how to perform the relevant steps, see the Oracle documentation.
For information about database sizing, see the Sizing calculator for vCenter Site Recovery Manager databases -
Oracle at http://www.vmware.com/products/site-recovery-manager/resource.html.
Procedure
1 When creating the database instance, specify UTF-8 encoding.
2 Create the SRM database user account.
3 Grant the SRM database user account the connect, resource, create session privileges and permissions.
Create an ODBC System DSN for SRM
You must provide SRM with a system database source name (DSN) for a 64-bit open database connectivity
(ODBC) connector. The ODBC connector allows SRM to connect to the SRM database.
You can create the ODBC system DSN before you run the SRM installer by running Odbcad32.exe, the 64-bit
Windows ODBC Administrator tool.
Site Recovery Manager Installation and Configuration
24 VMware, Inc.