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
Reprotection State Reference
As the process of reprotection proceeds, there are several states that can be observed in the recovery plan in
the vSphere client SRM plug-in in the vSphere Client.
Table 7-1. Reprotection States
State Description
Reprotect In Progress SRM is attempting to complete the process of reprotection. If
reprotection fails, the result is the state "Reprotect
Interrupted".
Partial Reprotect Occurs if multiple recovery plans share the same protection
groups and some groups have already been reprotected in
some plans, but some have not. If this occurs, run reprotect
for partially reprotected plans and all groups that were not
reprotected will be reprotected.
Incomplete Reprotect Occurs because of failures during reprotect. For example, this
state might occur due to a failure to synchronize storage or
a failure to create placeholder virtual machines.
n
If a reprotect operation fails to synchronize storage,
ensure sites are connected, review the reprotect step
progress in the vSphere client SRM plug-in, and begin
the reprotect task again.
n
If placeholder virtual machines are not created,
recoveries are now possible, but you may wish to review
the reprotect step progress in the vSphere client SRM
plug-in, resolve any open issues, and begin the reprotect
task again.
Reprotect Interrupted If one of the SRM servers crashes during the reprotect, this
state occurs. Make sure both SRM servers are running and
begin the reprotect task again.
Chapter 7 Recovery Plans and Reprotection
VMware, Inc. 73