You can configure Site Recovery Manager to present messages for notification and accept acknowledgement to users. Site Recovery Manager also provides a mechanism to run commands and scripts as necessary when running a recovery plan.
You can insert pre-power-on or post-power-on messages and commands in the recovery plans. These messages and commands are not specific to Site Recovery Manager, but support pausing the execution of the recovery plan to complete other procedures, or running customer-specific commands or scripts to enable automation of recovery tasks.
Site Recovery Manager Messages
Some additional steps might be required before, during, and after running a recovery plan. For example, you might set up the environment so that a message appears when a recovery plan is initiated, and that the administrator must acknowledge the message before the recovery plan continues. Messages are specific to each IT organization.
Consider the following example messages and confirmation steps:
- Verify that IP address changes are made on the DNS server and that the changes are propagated.
- Verify that the Active Directory services are available.
- After the management applications are recovered, perform application tests to verify that the applications are functioning correctly.
Additionally, confirmation steps can be inserted after every group of services that have a dependency on other services. These conformations can be used to pause the recovery plan so that appropriate verification and testing be performed before subsequent steps are taken. These services are defined as follows:
- Infrastructure services
- Core services
- Database services
- Middleware services
- Application services
- Web services
Details on each message are specified in the workflow definition of the individual recovery plan.
Site Recovery Manager Commands
You can run custom scripts to perform infrastructure configuration updates or configuration changes on the environment of a virtual machine. The scripts that a recovery plan runs are located on the Site Recovery Manager server. The scripts can run against the Site Recovery Manager server or can impact a virtual machine.
If a script must run on the virtual machine, Site Recovery Manager does not run it directly, but instructs the virtual machine to do it. The audit trail that Site Recovery Manager provides does not record the execution of the script because the operation is on the target virtual machine.
Scripts or commands must be available in the path on the virtual machine according to the following guidelines:
- Use full paths to all executables. For example c:\windows\system32\cmd.exe instead of cmd.exe.
- Call only.exe or .com files from the scripts. Command-line scripts can call only executables.
- To run a batch file, start the shell command with c:\windows\system32\cmd.exe.
The scripts that are run after powering on a virtual machine are executed under the Windows Servers Local Security Authority of the Site Recovery Manager server. Store post-power-on scripts on the Site Recovery Manager virtual machine. Do not store such scripts on a remote network share.