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‑1. DR IP Customizer Options (Continued)
Option Description Mandatory
--cmd arg
You specify different commands to
run DR IP Customizer in different
modes.
n
The apply command applies the
network customization settings
from an existing CSV file to the
recovery plans on the
SRM Server instances.
n
The generate command
generates a basic CSV file for all
virtual machines that SRM
protects for a vCenter Server
instance.
n
The drop command removes the
recovery settings from virtual
machines specified by the input
CSV file.
Always provide the same
vCenter Server instance for the apply
and drop commands as the one that
you used to generate the CSV file.
Yes
--csv arg
Path to the CSV file to use as input.
Yes, when running the apply and
drop commands.
-o [ --out ] arg
Name of the new CSV output file that
the generate command creates. If
you provide the name of an existing
CSV file, the generate command
overwrites its current contents.
Yes, when you run the generate
command.
--vc arg
vCenter Server host name. Virtual
machine IDs for the protected virtual
machines are different at each site.
Use the same vCenter Server instance
when you generate the CSV file and
when you apply it.
Yes
-i [ --ignore-thumbprint ]
Ignore the vCenter Server
thumbprint confirmation prompt.
No
-e [ --extra-dns-columns ]
Obsolete. No
-v [ --verbose ]
Enable verbose output. You can
include a --verbose option on any
dr-ip-customizer.exe command
line to log additional diagnostic
messages.
No
Structure of the DR IP Customizer CSV File
The DR IP Customizer comma-separated value (CSV) file consists of a header row that defines the meaning
of each column in the file, and one or more rows for each placeholder virtual machine in a recovery plan.
Configuring IP settings for both sites is optional. You can provide settings for only the protected site, or
settings for only the recovery site, or settings for both sites. You can configure each site to use a different set
of network adapters in a completely different way.
Certain fields in the CSV file must be completed for every row. Other fields can be left blank if no
customized setting is required.
Chapter 8 Customizing IP Properties for Virtual Machines
VMware, Inc. 69