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
Creating the SRM Database 3
The SRM Server requires its own database, which it uses to store data such as recovery plans and inventory
information.
The SRM database is a critical part of an SRM installation. You must create the SRM database and establish a
database connection before you can install SRM.
SRM cannot use the vCenter Server database because it has different database schema requirements. You
can use the vCenter Server database server to create and support the SRM database.
Each SRM site requires its own instance of the SRM database. Use a different database server instance to run
the individual SRM databases for each site. If you use the same database server instance to run the databases
for both sites, and if the database server experiences a problem, neither SRM site will work and you will not
be able to perform a recovery.
SRM does not require the databases on each site to be identical. You can run different versions of a
supported database from the same vendor on each site, or you can run databases from different vendors on
each site. For example, you can run different versions of Oracle Server on each site, or you can have an
Oracle Server database on one site and an SQL Server database on the other.
If you are updating SRM to a new version, you can use the existing database. Before you attempt an SRM
environment upgrade, make sure that both SRM Server databases are backed up. Doing so helps ensure that
you can revert back to the previous version after the upgrade, if necessary.
For the list of database software that SRM supports, see the Site Recovery Manager Compatibility Matrixes.
n
Configure Microsoft SQL Server for SRM on page 23
When you create a Microsoft SQL Server database, you must configure it correctly to support SRM.
n
Configure Oracle Server for SRM on page 24
When you create a Oracle Server database, you must configure it correctly to support SRM.
n
Create an ODBC System DSN for SRM on page 24
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.
Configure Microsoft SQL Server for SRM
When you create a Microsoft SQL Server database, you must configure it correctly to support SRM.
You use SQL Server Management Studio to create and configure an SQL Server database for SRM to use.
This information provides the general steps that you must perform to configure an SQL Server database for
SRM to use. For specific instructions, see the SQL Server documentation.
VMware, Inc.
23