4.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 Protected and Recovery Sites
- Test Recovery, Recovery, and Failback
- Customizing Site Recovery Manager
- Assign Roles and Permissions
- Customizing a Recovery Plan
- Configure Protection for a Virtual Machine or Template
- Configure SRM Alarms
- Working with Advanced Settings
- Avoiding Replication of Paging Files and Other Transient Data
- Troubleshooting SRM
- Index
d Power off and then power or the virtual machine so that it writes its paging file to the new location
on the cloned disk.
At this point, the protected virtual machine is writing its paging file to a disk on a nonreplicated
datastore at the protected site. Until you specify a recovery site location for this disk, the virtual
machine does not have a valid protection configuration.
e Assign recovery site storage for the paging file disk to one of the clones that you copied from the
protected site.
See “Configure Protection for a Virtual Machine or Template,” on page 54.
Initially, the paging file disk has a Recovery Location that is Not Configured. Click Browse, and then
browse to the cloned vmdk file at the recovery site.
After you have configured the virtual machine to use the nonreplicated disk at the recovery site, SRM considers
the virtual machine’s storage properly configured and returns it to the protection group.
What to do next
After the changes at the protected site are replicated to the recovery site, you can test the recovery plan to verify
that the recovered virtual machines are using the nonreplicated paging file.
After you reconfigure a virtual machine to use a paging file disk, you can delete the old, unused paging file
from its system disk.
Site Recovery Manager Administration Guide
62 VMware, Inc.