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
This generated CSV file shows two virtual machines, vm-3-win and vm-1-linux. The virtual machines are
present on the protected site and on the recovery site, vcenter-server-site-B, and vcenter-server-site-A. DR IP
Customizer generates an entry for each virtual machine and each site with Adapter ID 0. You can add
additional lines to customize each NIC, once you are aware of how many NICs are on each virtual machine.
Example: Setting Static IPv4 Addresses
You can modify the generated CSV file to assign two network adapters with static IPv4 addresses to one of
the virtual machines, vm-3-win, on the protected site and the recovery site.
For readability, the example CSV file in the following table omits empty columns. The DNS Domain,
NetBIOS, IPv6 Address, IPv6 Subnet Prefix length, and IPv6 Gateway(s) columns are all omitted.
Table 8‑3. Setting Static IPv4 Addresses in a Modified CSV File
VM ID
VM
Name
vCent
er
Server
Adapt
er ID
Primar
y
WINS
Secon
dary
WINS
IP
Address
Subnet
Mask
Gatewa
y(s)
DNS
Server(s
)
DNS
Suffix(es)
protecte
d-
vm-1030
1
vm-3-
win
vcenter
-
server-
site-B
0 example.c
om
protecte
d-
vm-1030
1
vm-3-
win
vcenter
-
server-
site-B
0 eng.exam
ple.com
protecte
d-
vm-1030
1
vcenter
-
server-
site-B
1 2.2.3.4 2.2.3.5 192.168.1
.21
255.255.2
55.0
192.168.1
.1
1.1.1.1
protecte
d-
vm-1030
1
vcenter
-
server-
site-B
2 2.2.3.4 2.2.3.5 192.168.1
.22
255.255.2
55.0
192.168.1
.1
1.1.1.2
protecte
d-
vm-1030
1
vm-3-
win
vcenter
-
server-
site-A
0 1.1.0.1 example.c
om
protecte
d-
vm-1030
1
vm-3-
win
vcenter
-
server-
site-A
0 1.1.0.2 eng.exam
ple.com
protecte
d-
vm-1030
1
vcenter
-
server-
site-A
1 192.168.0
.21
255.255.2
55.0
192.168.0
.1
protecte
d-
vm-1030
1
vcenter
-
server-
site-A
2 1.2.3.4 1.2.3.5 192.168.0
.22
255.255.2
55.0
192.168.0
.1
The information in this CSV file applies different static IPv4 settings to vm-3-win on the protected site and
on the recovery site.
n
On the vcenter-server-site-B site:
n
Sets the DNS suffixes example.com and eng.example.com for all NICs for this virtual machine.
n
Adds a NIC, Adapter ID 1, with primary and secondary WINS servers 2.2.3.4 and 2.2.3.5, a static
IPv4 address 192.168.1.21, and DNS server 1.1.1.1.
Chapter 8 Customizing IP Properties for Virtual Machines
VMware, Inc. 73