6.1
Table Of Contents
- Site Recovery Manager Installation and Configuration
- Contents
- About VMware Site Recovery Manager Installation and Configuration
- Updated Information
- Overview of VMware Site Recovery Manager
- Site Recovery Manager System Requirements
- Creating the Site Recovery Manager Database
- Site Recovery Manager Authentication
- Creating SSL/TLS Server Endpoint Certificates for Site Recovery Manager
- Installing Site Recovery Manager
- Site Recovery Manager and vCenter Server Deployment Models
- Site Recovery Manager in a Two-Site Topology with One vCenter Server Instance per Platform Services Controller
- Site Recovery Manager in a Two-Site Topology with Multiple vCenter Server Instances per Platform Services Controller
- Site Recovery Manager in a Single Site Topology with a Shared Platform Services Controller
- Prerequisites and Best Practices for Site Recovery Manager Server Installation
- Install Site Recovery Manager Server
- Connect the Site Recovery Manager Server Instances on the Protected and Recovery Sites
- Establish a Client Connection to the Remote Site Recovery Manager Server Instance
- Install the Site Recovery Manager License Key
- Site Recovery Manager Server Does Not Start
- Unregister an Incompatible Version of vSphere Replication
- Site Recovery Manager and vCenter Server Deployment Models
- Modifying and Uninstalling Site Recovery Manager
- Modify a Site Recovery Manager Server Installation
- Reconfigure the Connection Between Sites
- Break the Site Pairing and Connect to a New Remote Site
- Repair a Site Recovery Manager Server Installation
- Rename a Site Recovery Manager Site
- Uninstall Site Recovery Manager
- Uninstall and Reinstall the Same Version of Site Recovery Manager
- Upgrading Site Recovery Manager
- Information That Site Recovery Manager Upgrade Preserves
- Types of Upgrade that Site Recovery Manager Supports
- Upgrade Site Recovery Manager
- Order of Upgrading vSphere and Site Recovery Manager Components
- Prerequisites and Best Practices for Site Recovery Manager Upgrade
- In-Place Upgrade of Site Recovery Manager Server
- Upgrade Site Recovery Manager Server with Migration
- Configure and Verify the Upgraded Site Recovery Manager Installation
- Revert to a Previous Release of Site Recovery Manager
- Installing Site Recovery Manager to Use with a Shared Recovery Site
- Shared Recovery Sites and vCenter Server Deployment Models
- Limitations of Using Site Recovery Manager in Shared Recovery Site Configuration
- Site Recovery Manager Licenses in a Shared Recovery Site Configuration
- Install Site Recovery Manager In a Shared Recovery Site Configuration
- Use vSphere Replication in a Shared Recovery Site Configuration
- Install Site Recovery Manager Server on Multiple Protected Sites to Use with a Shared Recovery Site
- Install Multiple Site Recovery Manager Server Instances on a Shared Recovery Site
- Connect the Site Recovery Manager Sites in a Shared Recovery Site Configuration
- Use Array-Based Replication in a Shared Recovery Site Configuration
- Configure Placeholders and Mappings in a Shared Recovery Site Configuration
- Upgrade Site Recovery Manager in a Shared Recovery Site Configuration
- Index
Creating the Site Recovery Manager
Database 3
The Site Recovery Manager Server requires its own database, which it uses to store data such as recovery
plans and inventory information.
Site Recovery Manager provides an embedded vPostgreSQL database that you can use with minimal
configuration. You can select the option to use the embedded database when you install
Site Recovery Manager. The Site Recovery Manager installer creates the embedded database and a database
user account according to the information that you specify during installation.
You can also use an external database. If you use an external database, you must create the database and
establish a database connection before you can install Site Recovery Manager.
Site Recovery Manager 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
Site Recovery Manager database.
Each Site Recovery Manager site requires its own instance of the Site Recovery Manager database. Use a
different database server instance to run the individual Site Recovery Manager 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 Site Recovery Manager site will work and you will not be able to perform a
recovery.
Site Recovery Manager 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 the embedded database on the other.
If you are updating Site Recovery Manager to a new version, you can use the existing database. Before you
attempt an upgrade, make sure that both Site Recovery Manager 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 Site Recovery Manager supports, see the Compatibility Matrixes for Site
Recovery Manager 6.1 at https://www.vmware.com/support/srm/srm-compat-matrix-6-1.html.
n
Requirements when Using Microsoft SQL Server with Site Recovery Manager on page 18
When you create a Microsoft SQL Server database, you must configure it correctly to support
Site Recovery Manager.
n
Requirements for Using Oracle Server with Site Recovery Manager on page 19
When you create an Oracle Server database, you must configure it correctly to support
Site Recovery Manager.
n
Back Up and Restore the Embedded vPostgres Database on page 19
If you select the option to use an embedded database for Site Recovery Manager, the
Site Recovery Manager installer creates a vPostgres database during the installation process. You can
back up and restore the embedded vPostgres database by using PostgreSQL commands.
VMware, Inc.
17