5.0
Table Of Contents
- Site Recovery Manager Administration Guide
- Contents
- About This Book
- Administering VMware vCenter Site Recovery Manager
- Installing and Updating Site Recovery Manager
- Configuring the SRM Database
- About the vSphere Replication Management Database
- Install the SRM Server
- Upgrading SRM
- Install Storage Replication Adapters
- Install the SRM Client Plug-In
- Connect the Sites
- Revert to a Previous Release
- Repair or Modify the Installation of a Site Recovery Manager Server
- Install the SRM License Key
- Establishing Inventory Mappings and Placeholder Datastores
- Configuring Array-Based Protection
- Installing vSphere Replication Servers
- Creating Protection Groups and Replicating Virtual Machines
- Limitations to Protection and Recovery of Virtual Machines
- Create Array-Based Protection Groups
- Create vSphere Replication Protection Groups
- Configure Replication for a Single Virtual Machine
- Configure Replication for Multiple Virtual Machines
- Replicate Virtual Machines Using Physical Couriering
- Move a Virtual Machine to a New vSphere Replication Server
- Apply Inventory Mappings to All Members of a Protection Group
- Recovery Plans and Reprotection
- Customizing Site Recovery Manager
- Customizing a Recovery Plan
- Configure Protection for a Virtual Machine or Template
- Configure Resource Mappings for a Virtual Machine
- Configure SRM Alarms
- Working with Advanced Settings
- Troubleshooting SRM
- Index
Configuring the SRM Database
Each SRM server requires its own database to store recovery plans, inventory information, and similar data.
Before installing the SRM server, you must configure and initialize the SRM database.
If you are updating SRM to a new release, you can use the existing database. Before attempting an SRM
environment upgrade, ensure both SRM server databases are backed up. This helps ensure you can revert after
the upgrade, if required.
SRM cannot use the vCenter database because it has different database schema requirements, though you can
use the vCenter database server to create and support the SRM database. Each SRM site requires its own
instance of the SRM database. The database must exist before SRM can be installed.
NOTE If you reinitialize the database after you install SRM, you must run the SRM installer in maintenance
mode and specify a new database connection.
Microsoft SQL Server Configuration
A Microsoft SQL Server configuration must meet specific requirements to support SRM.
SRM requires that the Microsoft SQL Server must have a 32-bit DSN. Microsoft SQL Server has the following
configuration requirements when used as the SRM database.
n
The database schema has three requirements:
n
It must be owned by the SRM database user (the database user name you supply when configuring
the SRM database connection).
n
It must be the default schema for the SRM database user.
n
The DB schema name must be the same as the DB user name.
n
You must grant the SRM database user the following permissions:
n
bulk insert
n
connect
n
create table
n
If you are using Windows authentication, the database user account must be the same user account that
you use to run the SRM service.
n
If you are using SQL Authentication, you can leave the default local System user.
n
If the SRM server and database server run on different hosts, you must use mixed mode authentication.
n
If SQL Server is installed locally, you might need to disable the Shared Memory network setting on the
database server.
Oracle Server Configuration
An Oracle Server configuration must meet specific requirements to support SRM.
Oracle Server has the following configuration requirements when used as the SRM database.
n
When creating the database instance, specify utf-8 encoding.
n
You must grant the following permissions to the SRM database user (the database user name you supply
when configuring the SRM database connection):
n
connect
n
resource
Site Recovery Manager Administration Guide
28 VMware, Inc.