VMware VC-SRM4-A - vCenter Site Recovery Manager Spécifications télécharger pdf (Page 41)

41 Deploying VMware vCenter Site Recovery Manager with NetApp FAS/V-Series Storage Systems

Delete the sched.swap.derivedName option. This line will be automatically recreated by ESX when

the virtual machine is powered on. It is set to the physical path name of the vswp file location.

c. workingDir = "."

This is the default setting for this option. Leave this setting as is. Changing the workingDir variable

moves the location of VMware Snapshot delta files, which is not supported by SRM, as SRM requires

that Snapshot delta files be on replicated datastores due to the fact that these files contain virtual

machine data.

3. Save the vmx file and power on the virtual machine.

4. Browse the vmware_swap datastore and verify a new vswp file was created there when the virtual

machine powered on.

5. Make sure there is a nonreplicated datastore at the DR site also named vmware_swap with adequate

capacity to contain the vswp files.

PROTECTING VMS WITH NONREPLICATED WINDOWS PAGE FILES

By default Windows hosts store the virtual memory pagefile on the system drive, but they can be configured

to store the pagefile on a second virtual disk. This virtual disk can be stored in a nonreplicated datastore;

however, to prevent Windows from placing the pagefile back in the default location when it’s recovered at

the DR site, steps must be taken to provide a virtual disk for the pagefile to be placed there.

If the pagefile does get placed back on the system disk, then that amount of capacity must be resynced back

to the primary site, or extra downtime for the virtual machines and complicated administrative work would be

required to remove the pagefile from the system drive prior to resyncing the environments.

SRM can be configured to connect a preexisting vmdk to a recovered virtual machine at the DR site. To

make sure that this disk is recognized by the Windows virtual machine as the same disk where the pagefile

was stored at the primary site, the pre-created disk must have the same disk signature as the disk at the

primary site. VMware disk cloning can be used in a procedure to accomplish this.

The process below is an example of configuring Windows virtual machines and SRM to utilize nonreplicated

storage for Windows pagefiles.

1. At the primary site edit a temporary Windows virtual machine configuration. Create a virtual disk and

store this disk in a location where virtual machine templates would typically be stored: for example,

/vmfs/volumes/templates/pagefile_disks/pagefile.vmdk. This virtual disk will serve as the basis for all

other pagefile virtual disks to be cloned from.

2. In the virtual machine, enter Disk Management, rescan for storage, and allow Windows to write a

signature on the disk. Create a partition on the disk and format it.

3. Disconnect the Windows host from the disk.

4. Create a clone of the virtual disk for each Windows virtual machine by using the vmkfstools

command. Store these virtual machines in a nonreplicated datastore such as vmware_swap. In this

example, a clone is created for Win2k3-VM2, and the clone is stored in a directory for that virtual

machine.

[root@vmcoe-ppe01 vmware_swap]# mkdir /vmfs/volumes/vmware_swap/vm2_pagefile

[root@vmcoe-ppe01 vmware_swap]# vmkfstools -i

/vmfs/volumes/templates/pagefile_disks/pagefile.vmdk

/vmfs/volumes/vmware_swap/vm2_pagefile/pagefile.vmdk

5. In vCenter, connect each pagefile.vmdk to the appropriate virtual machine.

6. Connect to each virtual machine console, open Disk Management, and rescan for storage. Assign a

drive letter to the disk; in this process P: is assigned.

7. Configure each Windows virtual machine to use P: for its virtual memory location. The change requires

a reboot. After Windows has stopped using the system drive for virtual memory, the pagefile.sys file

might be deleted from the system disk. An example of a regedit file with the appropriate keys to

1 2 ... 36 37 38 39 40 41 42 43 44 45 46

Commentaires sur ces manuels

Pas de commentaire

VMware VC-SRM4-A - vCenter Site Recovery Manager Spécifications Page 41

Commentaires sur ces manuels

Produits connexes et manuels pour Logiciel VMware VC-SRM4-A - vCenter Site Recovery Manager