5.5
Table Of Contents
- Site Recovery Manager Administration
- Contents
- About VMware vCenter Site Recovery Manager Administration
- SRM Privileges, Roles, and Permissions
- Replicating Virtual Machines
- How the Recovery Point Objective Affects Replication Scheduling
- Replicating a Virtual Machine and Enabling Multiple Point in Time Instances
- Configure Replication for a Single Virtual Machine
- Configure Replication for Multiple Virtual Machines
- Replicate Virtual Machines By Using Replication Seeds
- Reconfigure Replications
- Stop Replicating a Virtual Machine
- Creating Protection Groups
- Creating, Testing, and Running Recovery Plans
- Testing a Recovery Plan
- Performing a Planned Migration or Disaster Recovery By Running a Recovery Plan
- Differences Between Testing and Running a Recovery Plan
- How SRM Interacts with DPM and DRS During Recovery
- How SRM Interacts with Storage DRS or Storage vMotion
- How SRM Interacts with vSphere High Availability
- Protecting Microsoft Cluster Server and Fault Tolerant Virtual Machines
- Create, Test, and Run a Recovery Plan
- Export Recovery Plan Steps
- View and Export Recovery Plan History
- Cancel a Test or Recovery
- Delete a Recovery Plan
- Reprotecting Virtual Machines After a Recovery
- Restoring the Pre-Recovery Site Configuration By Performing Failback
- Customizing a Recovery Plan
- Recovery Plan Steps
- Specify the Recovery Priority of a Virtual Machine
- Creating Custom Recovery Steps
- Types of Custom Recovery Steps
- How SRM Handles Custom Recovery Steps
- Create Top-Level Command Steps
- Create Top-Level Message Prompt Steps
- Create Command Steps for Individual Virtual Machines
- Create Message Prompt Steps for Individual Virtual Machines
- Guidelines for Writing Command Steps
- Environment Variables for Command Steps
- Customize the Recovery of an Individual Virtual Machine
- Customizing IP Properties for Virtual Machines
- Advanced SRM Configuration
- Configure Protection for a Virtual Machine or Template
- Configure Resource Mappings for a Virtual Machine
- Specify a Nonreplicated Datastore for Swap Files
- Recovering Virtual Machines Across Multiple Hosts on the Recovery Site
- Resize Virtual Machine Disk Files During Replication Using Replication Seeds
- Resize Virtual Machine Disk Files During Replication Without Using Replication Seeds
- Reconfigure SRM Settings
- Change Local Site Settings
- Change Logging Settings
- Change Recovery Settings
- Change Remote Site Settings
- Change the Timeout for the Creation of Placeholder Virtual Machines
- Change Storage Settings
- Change Storage Provider Settings
- Change vSphere Replication Settings
- Modify Settings to Run Large SRM Environments
- Troubleshooting SRM Administration
- Limitations to Protection and Recovery of Virtual Machines
- SRM Events and Alarms
- vSphere Replication Events and Alarms
- Collecting SRM Log Files
- Access the vSphere Replication Logs
- Resolve SRM Operational Issues
- SRM Doubles the Number of Backslashes in the Command Line When Running Callouts
- Powering on Many Virtual Machines Simultaneously on the Recovery Site Can Lead to Errors
- LVM.enableResignature=1 Remains Set After a SRM Test Failover
- Adding Virtual Machines to a Protection Group Fails with an Unresolved Devices Error
- Configuring Protection fails with Placeholder Creation Error
- Planned Migration Fails Because Host is in an Incorrect State
- Recovery Fails with a Timeout Error During Network Customization for Some Virtual Machines
- Recovery Fails with Unavailable Host and Datastore Error
- Reprotect Fails with a vSphere Replication Timeout Error
- Recovery Plan Times Out While Waiting for VMware Tools
- Reprotect Fails After Restarting vCenter Server
- Rescanning Datastores Fails Because Storage Devices are Not Ready
- Scalability Problems when Replicating Many Virtual Machines with a Short RPO to a Shared VMFS Datastore on ESXi Server 5.0
- Application Quiescing Changes to File System Quiescing During vMotion to an Older Host
- Reconfigure Replication on Virtual Machines with No Datastore Mapping
- Configuring Replication Fails for Virtual Machines with Two Disks on Different Datastores
- vSphere Replication RPO Violations
- vSphere Replication Does Not Start After Moving the Host
- Unexpected vSphere Replication Failure Results in a Generic Error
- Generating Support Bundles Disrupts vSphere Replication Recovery
- Recovery Plan Times Out While Waiting for VMware Tools
- Index
Licensing Events
Licensing events provide information about changes in SRM licensing status.
Table 10‑11. Licensing Events
Type Description Content
LicenseExpiringEvent
The SRM License at the specified site
expires in the specified number of
days.
Every 24 hours, non-evaluation,
expiring licenses are checked for the
number of days left. This event is
posted with the results.
EvaluationLicenseExpiringEvent
The SRM Evaluation License at the
specified site expires in the specified
number of days.
Every 24 hours, evaluation licenses are
checked for the number of days left.
This event is posted with the results.
LicenseExpiredEvent
The SRM license at the specified site
license has expired.
Every 30 minutes, expired (non-
evaluation) licenses will post this
event.
EvaluationLicenseExpiredEvent
The SRM Evaluation License at the
specified site license has expired.
Every 30 minutes, evaluation licenses
will post this event.
UnlicensedFeatureEvent
The SRM license at the specified site
is overallocated by the specified
number of licenses.
Every 24 hours and upon the
protection or unprotection of a virtual
machine, this event will be posted if
the total number of licenses exceeds
the capacity in the license.
LicenseUsageChangedEvent
The SRM license at the specified site
is using the specified number out of
the total number licenses.
Every 24 hours and upon the
protection or unprotection of a virtual
machine, this event will be posted if
the total number of licenses does not
exceed the capacity in the license.
Permissions Events
Permission events provide information about changes to SRM permissions.
Table 10‑12. Permissions Events
Type Description Content
PermissionsAddedEvent
Permission created for the entity on
SRM.
A permission for the entity was
created using the role specified. The
IsPropagate flag indicates whether
the permission is propagated down the
entity hierarchy.
PermissionsDeletedEvent
Permission rule removed for the
entity on SRM.
A permission for the entity was
deleted.
PermissionsUpdatedEvent
Permission changed for the entity on
SRM.
A permission for the indicated entity
was modified.
SNMP Traps
SRM sends SNMP traps to community targets defined in vCenter. You can configure them using the
vSphere Client. When you enter localhost or 127.0.0.1 as a target host for SNMP traps, SRM uses the IP
address or host name of the vSphere server as configured by the SRM installer.
SNMP traps for SRM 5.x are backward compatible with SRM 4.0 and later releases.
Site Recovery Manager Administration
104 VMware, Inc.