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
Table 8‑2. Columns of the DR IP Customizer CSV File (Continued)
Column Description Customization Rules
Secondary WINS DR IP Customizer validates that
WINS settings are applied only to
Windows virtual machines, but it
does not validate NetBIOS settings.
Customizable. Can be left blank.
IP Address IPv4 address for this virtual machine. Customizable. Cannot be blank.
Virtual machines can have multiple
virtual network adapters. You can
configure each virtual network adapter
with one static IPv4 address or one
static IPv6 address. For example, if you
set a static address for IPv4, you must
set the IPv6 address to DHCP.
Subnet Mask Subnet mask for this virtual machine. Customizable. Can be left blank.
Gateway(s) IPv4 gateway or gateways for this
virtual machine.
Customizable. Can be left blank.
IPv6 Address IPv6 address for this virtual machine. Customizable. Can be left blank if you
do not use IPv6.
Virtual machines can have multiple
virtual network adapters. You can
configure each virtual network adapter
with one static IPv4 address or one
static IPv6 address. For example, if you
set a static address for IPv6, you must
set the IPv4 address to DHCP.
If you run SRM Server on Windows
Server 2003 and you customize IPv6
addresses for a virtual machine, you
must enable IPv6 on the SRM Server
instances. SRM performs validation of
IP addresses during customization,
which requires IPv6 to be enabled on
the SRM Server if you are customizing
IPv6 addresses. Later versions of
Windows Server have IPv6 enabled by
default.
IPv6 Subnet Prefix length Ipv6 subnet prefix length to use. Customizable. Can be left blank.
IPv6 Gateway(s) IPv4 gateway or gateways for this
adapter.
Customizable. Can be left blank.
DNS Server(s) Address of the DNS server or servers. Customizable. Can be left blank.
If you enter this setting in an Adapter
ID 0 row, it is treated as a global
setting. On Windows virtual machines,
this setting applies for each adapter if
you set it in the Adapter ID rows other
than Adapter ID 0.
On Linux virtual machines, this is
always a global setting for all adapters.
This column can contain one or more
IPv4 or IPv6 DNS servers for each
NIC.
DNS Suffix(es) Suffix or suffixes for DNS servers. Customizable. Can be left blank.
These are global settings for all
adapters on both Windows and Linux
virtual machines.
Chapter 8 Customizing IP Properties for Virtual Machines
VMware, Inc. 71