Brocade Communications Systems StorageWorks 4400 - Enterprise Virtual Array Uživatelský manuál stáhnout pdf (Strana 18)

If virtual machines that have no relationship are consolidated on a single volume, those virtual machines will

have to failover together. With certain I/O-demanding applications, it is sometimes advisable to spread the

data files onto several virtual disks using either VMFS or RDM or a combination of both. Typical examples

where this approach is recommended are MS Exchange or SQL server environments. It is also

recommended to isolate the database files and transaction logs in separate Volumes/LUNs. It helps to

increase data resiliency in the event of a multiple drive failure and can improve performance avoiding

random IOPS in the database to compete with the sequential streams of the transaction logs.

When you configure a new protection group, Site Recovery Manager requires a location to store the

temporary inventory files for the protected virtual machines at the recovery site. Virtual Machine

placeholders are automatically created on the recovery ESX host (The recovery host is designated in the

inventory mapping). A virtual machine placeholder is a stub that represents a protected VM from the

protected site Virtual Center, these are *.vmx files containing the protected VM definition files. The

placeholders appear in VMware Infrastructure Client at the recovery site as any other Virtual Machine;

however, you cannot modify their settings. They are used during the execution of a recovery plan when

registering the recovered VMs. It is preferable to locate these temporary files on a non replicated datastore

at the recovery site.

Once you have identified which virtual machines to protect, you need to configure Continuous Access to

replicate the underlying LUNs and set Site Recovery Manager datastore groups for those protected virtual

machines.

You should only store protected virtual machines on the datastores that are being replicated from the

protected site to the recovery site. A careful review of the current VM locations is an important step in the

preparation for a Site Recovery Manager installation. Most environments are not initially designed with Site

Recovery Manager or Disaster recovery in mind. As a result, some mission critical VMs can possibly share

the same datastore with other non critical VMS. VM placement may need to be revisited to better suit your

business continuity requirements. VMware Storage VMotion can be used to relocate the virtual machines

that must be protected onto Site Recovery Manager datastore groups without any interruption to services

during setup.

Datastore group to Continuous Access DR group mapping

Protected datastores and RDM Vdisks can be replicated using one or more Continuous Access DR groups,

but a given Vdisk can only belong to one DR group. The best practice is to establish a 1:1 relationship

between the Site Recovery Manager datastore groups and Continuous Access DR groups. With

straightforward mapping, the configuration is easier to plan and maintain. Figure 10 shows a symmetric

datastore to DR group configuration.

1 2 ... 13 14 15 16 17 18 19 20 21 22 23 ... 37 38

Žádné komentáře

Brocade Communications Systems StorageWorks 4400 - Enterprise Virtual Array Uživatelský manuál Strana 18