6.1
Table Of Contents
- Site Recovery Manager Administration
- Contents
- About VMware Site Recovery Manager Administration
- Updated Information
- Site Recovery Manager Privileges, Roles, and Permissions
- How Site Recovery Manager Handles Permissions
- Site Recovery Manager and the vCenter Server Administrator Role
- Site Recovery Manager and vSphere Replication Roles
- Managing Permissions in a Shared Recovery Site Configuration
- Assign Site Recovery Manager Roles and Permissions
- Site Recovery Manager Roles Reference
- Replicating Virtual Machines
- Configuring Mappings
- About Placeholder Virtual Machines
- Creating and Managing Protection Groups
- About Array-Based Replication Protection Groups and Datastore Groups
- About vSphere Replication Protection Groups
- About Storage Policy Protection Groups
- Create Protection Groups
- Organize Protection Groups in Folders
- Add or Remove Datastore Groups or Virtual Machines to or from a Protection Group
- Apply Inventory Mappings to All Members of a Protection Group
- Configure Inventory Mappings for an Individual Virtual Machine in a Protection Group
- Modifying the Settings of a Protected Virtual Machine
- Remove Protection from a Virtual Machine
- Protection Group Status Reference
- Virtual Machine Protection Status Reference
- Creating, Testing, and Running Site Recovery Manager 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
- Performing Test Recovery of Virtual Machines Across Multiple Hosts on the Recovery Site
- Create, Test, and Run a Recovery Plan
- Export Recovery Plan Steps
- View and Export a Recovery Plan History
- Delete a Recovery Plan
- Recovery Plan Status Reference
- Configuring a Recovery Plan
- Recovery Plan Steps
- Creating Custom Recovery Steps
- Suspend Virtual Machines When a Recovery Plan Runs
- Specify the Recovery Priority of a Virtual Machine
- Configure Virtual Machine Dependencies
- Enable vSphere vMotion for Planned Migration
- Configure Virtual Machine Startup and Shutdown Options
- Limitations to Protection and Recovery of Virtual Machines
- Customizing IP Properties for Virtual Machines
- Reprotecting Virtual Machines After a Recovery
- How Site Recovery Manager Reprotects Virtual Machines with Array Based Replication
- How Site Recovery Manager Reprotects Virtual Machines with vSphere Replication
- How Site Recovery Manager Reprotects Virtual Machines with Storage Policy Protection
- Preconditions for Performing Reprotect
- Reprotect Virtual Machines
- Reprotect States
- Restoring the Pre-Recovery Site Configuration By Performing Failback
- Interoperability of Site Recovery Manager with Other Software
- Site Recovery Manager and vCenter Server
- Using Site Recovery Manager with VMware Virtual SAN Storage and vSphere Replication
- How Site Recovery Manager Interacts with DPM and DRS During Recovery
- How Site Recovery Manager Interacts with Storage DRS or Storage vMotion
- How Site Recovery Manager Interacts with vSphere High Availability
- How Site Recovery Manager Interacts with Stretched Storage
- Using Site Recovery Manager with VMware NSX
- Site Recovery Manager and vSphere PowerCLI
- Site Recovery Manager and vRealize Orchestrator
- Protecting Microsoft Cluster Server and Fault Tolerant Virtual Machines
- Using Site Recovery Manager with SIOC Datastores
- Using Site Recovery Manager with Admission Control Clusters
- Site Recovery Manager and Virtual Machines Attached to RDM Disk Devices
- Site Recovery Manager and Active Directory Domain Controllers
- Advanced Site Recovery Manager Configuration
- Reconfigure Site Recovery Manager Settings
- Change Connections Settings
- Change Site Recovery Manager History Report Collection Setting
- Change Local Site Settings
- Change Logging Settings
- Change Recovery Settings
- Change Remote Manager Settings
- Change Remote Site Settings
- Change Replication Settings
- Change SSO Setting
- Change Storage Settings
- Change ABR Storage Policy Setting
- Change Storage Provider Settings
- Change vSphere Replication Settings
- Modify Settings to Run Large Site Recovery Manager Environments
- Reconfigure Site Recovery Manager Settings
- Site Recovery Manager Events and Alarms
- Collecting Site Recovery Manager Log Files
- Troubleshooting Site Recovery Manager
- Site Recovery Manager 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 Site Recovery Manager Test Recovery
- Adding Virtual Machines to a Protection Group Fails with an Unresolved Devices Error
- Configuring Protection fails with Placeholder Creation Error
- Rapid Deletion and Recreation of Placeholders Fails
- 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
- Synchronization Fails for vSphere Replication Protection Groups
- Rescanning Datastores Fails Because Storage Devices are Not Ready
- Recovery Sticks at 36% During Planned Migration
- Operations Fail with Error About a Nonreplicated Configuration File
- Index
Option Action
Enable Site Recovery Manager to
wait to discover datastores after
recovery.
Select the storageProvider.waitForDeviceRediscovery check box.
Set the timeout in seconds to wait
for the Virtual Center to report
newly discovered datastores. The
default value is 30 seconds.
Enter the new value in the
storageProvider.waitForRecoveredDatastoreTimeoutSec text box.
Set the time interval in seconds that
Site Recovery Manager waits for
VMFS volumes to become mounted.
The default value is 30 seconds.
Enter the new value in the
storageProvider.waitForVmfsVolumesMountedStateTimeoutSec text
box.
5 Click OK to save your changes.
Change vSphere Replication Settings
You can adjust global settings to change how Site Recovery Manager interacts with vSphere Replication.
Procedure
1 In the vSphere Web Client, click Site Recovery > Sites, and select a site.
2 On the Manage tab, click Advanced Settings.
3 Click vSphere Replication.
4 Click Edit to modify the vSphere Replication settings.
Option Description
Allow vSphere Replication to
recover virtual machines that are
included in Site Recovery Manager
recovery plans independently of
Site Recovery Manager. The default
value is false.
If you configure vSphere Replication on a virtual machine and include the
virtual machine in a Site Recovery Manager recovery plan, you cannot
recover the virtual machine by using vSphere Replication independently of
Site Recovery Manager. To allow vSphere Replication to recover virtual
machines independently of Site Recovery Manager, select the
allowOtherSolutionTagInRecovery check box.
Keep older multiple point in time
(PIT) snapshots during recovery.
The default value is true.
If you configure vSphere Replication to take PIT snapshots of protected
virtual machines, Site Recovery Manager only recovers the most recent
snapshot when you perform a recovery. To recover older PIT snapshots
during recovery, select the preserveMpitImagesAsSnapshots check box.
Change the timeout period for
vSphere Replication
synchronization operations. The
default value is 7200.
Enter a new value in the synchronizationTimeout text box. Change this
value if you experience timeout errors when vSphere Replication
synchronizes virtual machines on the recovery site.
Change the default RPO setting for
replications. The default value is
240.
Enter a new value in the vrReplication.timeDefault text box. The default
value is 240 minutes (4 hours). This value is selected when you configure
replications, but you can specify a different RPO in the Configure
Replication wizard when you configure replication for an individual
virtual machine or for a group of virtual machines.
5 Click OK to save your changes.
Site Recovery Manager Administration
146 VMware, Inc.