5.0
Table Of Contents
- Site Recovery Manager Administration Guide
- Contents
- About This Book
- Administering VMware vCenter Site Recovery Manager
- Installing and Updating Site Recovery Manager
- Configuring the SRM Database
- About the vSphere Replication Management Database
- Install the SRM Server
- Upgrading SRM
- Install Storage Replication Adapters
- Install the SRM Client Plug-In
- Connect the Sites
- Revert to a Previous Release
- Repair or Modify the Installation of a Site Recovery Manager Server
- Install the SRM License Key
- Establishing Inventory Mappings and Placeholder Datastores
- Configuring Array-Based Protection
- Installing vSphere Replication Servers
- Creating Protection Groups and Replicating Virtual Machines
- Limitations to Protection and Recovery of Virtual Machines
- Create Array-Based Protection Groups
- Create vSphere Replication Protection Groups
- Configure Replication for a Single Virtual Machine
- Configure Replication for Multiple Virtual Machines
- Replicate Virtual Machines Using Physical Couriering
- Move a Virtual Machine to a New vSphere Replication Server
- Apply Inventory Mappings to All Members of a Protection Group
- Recovery Plans and Reprotection
- Customizing Site Recovery Manager
- Customizing a Recovery Plan
- Configure Protection for a Virtual Machine or Template
- Configure Resource Mappings for a Virtual Machine
- Configure SRM Alarms
- Working with Advanced Settings
- Troubleshooting SRM
- Index
n
Batch files or commands that produce output that contains characters with ASCII values greater than 127
must use UTF-8 encoding. Only the final 4KB of script output is captured in log files and recovery history.
Scripts that produce more output can redirect the output to a file rather than sending it to the standard
output to be logged.
Execution Environment for Command Steps
Command steps run with the identity of the LocalSystem account on the SRM server host at the recovery site.
When a command step runs, a number of environment variables are available for it to use. Table 8-1 lists the
environment variables that are available to all command steps.
Table 8-1. Environment Variables Available to All Command Steps
Name Value Example
VMware_RecoveryName Name of the recovery plan that is
executing.
Plan A
VMware_RecoveryMode Recovery mode. test or recovery
VMware_VC_Host Host name of the vCenter host at the
recovery site.
vc_hostname.example.com
VMware_VC_Port Network port used to contact the
vCenter host.
443
The environment variables listed in Table 8-2 are also set if the command step is executing on a recovered
virtual machine.
Table 8-2. Environment Variables Available to Command Steps Running on Recovered Virtual Machines
Name Value Example
VMware_VM_Uuid UUID used by vCenter to uniquely identify
this virtual machine.
4212145a-eeae-a02c-e525-ebba70b0d4f3
VMware_VM_Name Name of this virtual machine, as set at the
protected site.
My New Virtual Machine
VMware_VM_Ref Managed object ID of the virtual machine. vm-1199
VMware_VM_GuestName Name of the guest OS as defined by the VIM
API.
otherGuest
VMware_VM_GuestIp IP address of the virtual machine, if known. 192.168.0.103
Vmware_VM_Path Path to this virtual machine's VMDK file. [datastore-123] jquser-vm2/jquser-
vm2.vmdk
Customize Recovery Plan Steps
You can customize many recovery plan steps to extend the basic functions provided by a default recovery plan.
To customize recovery plan steps, open the Recovery Steps page of a recovery plan.
Procedure
1 Click Recovery Plans, and click the plan that you want to customize.
2 Click the Recovery Steps tab.
3 Right-click the step that you want to modify, and select an option from the menu.
To export the entire plan as an HTML document for your reference, right-click any step and click
Export. To edit the properties of the plan, right-click any step and click Edit Recovery Plan.
Chapter 8 Customizing Site Recovery Manager
VMware, Inc. 77