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
Connection Monitor Algorithm
Connection related events are produced according to this algorithm:
1 When administrative connection between two paired SRM servers is established SRM server that initiated
the connection raises RemoteSiteUpEvent.
2 When SRM detects that a monitored connection is down it starts a periodic connection check. Time interval
for these pings is configurable through the remoteSiteStatus.pingInterval advanced setting.
a Connection monitor skips a configurable number of failed pings. You can control this number through
the remoteSiteStatus.pingFailedDelay advanced setting.
b When the number of skipped failed pings exceeds the allowed value SRM posts
RemoteSitePingFailedEvent.
c When the number of skipped failed pings becomes more than another configurable limit SRM raises
RemoteSiteDownEvent on each failed ping and stops raising RemoteSitePingFailedEventevents. The
second limit of failed pings is configurable through remoteSiteStatus.panicDelay advanced setting.
d SRM continues to raise connection down events until connection is reestablished.
Site Status Events
Site status events provide information about the status and connection between protected and recovery sites.
Table 9-1. Site Status Events
Event Key Event Description Cause
UnknownStatusEvent SRM server status is not available
RemoteSiteDownEvent Remote SRM site is down This event is signaled when the SRM
server loses its connection with the
remote SRM server.
RemoteSitePingFailedEvent Remote SRM site is not responding to
pings
This may be due to failures at the site or
network connectivity.
RemoteSiteCreatedEvent Remote SRM site has been created This occurs when a site is established.
RemoteSiteUpEvent Remote SRM site is responsive This occurs when the SRM server re-
establishes its connection with the
remote SRM server.
RemoteSiteDeletedEvent Remote SRM site has been deleted.
Protection Group Events
Protection Group events provide information about actions and status related to protection groups.
These events have three categories:
n
Protection Group Replication Informational Events
n
Protection Group Replication Warning Events
n
Protection Group Replication Error Events
Site Recovery Manager Administration Guide
94 VMware, Inc.