Brocade Communications Systems StorageWorks 4400 - Enterprise Virtual Array Instrukcja Użytkownika Pobierz pdf (Strona 9)

For example, a disk group configuration using 300 GB drives, single sparing, and Vraid 5 for a total

estimated VM disk space of 8 TB breaks down as follows:

Number of drives needed =

8000GB

DATA

+ (8000GB * .20

Vraid 5

)

+ 558.78GB

SPARING

= 37 Disks

279.39 GB

Note: It is a best practice to round up the produce of the performance or capacity

sizing formulas to a multiple of 8 disks

Planning for DR group write history log (WHL)

The DR group WHL is a virtual disk that stores a DR group host write data. The log is automatically created

when you create the DR group. Once the log is created, it cannot be moved. You must plan for the

additional disk capacity required for each DR group WHL. For more information on DR group log size, see

the HP StorageWorks Continuous Access EVA Implementation Guide.

Determining the number of disk groups

To determine if the default disk group will meet your remote replication needs, consider the following:

 Separate disk groups can help ensure that data is recoverable if a disk group fails. However, multiple

disk groups result in a slightly higher cost of ownership and potentially lower performance.

 In general, distributing the workload across the greatest number of disks in a single disk group provides

the best performance. However, separate disk groups can improve performance for sequential workloads

such as database logs and rich content.

 Disk groups must provide sufficient free space for snapshots and snapclones (if used), and for Continuous

Access DR group WHLs.

Configure DR groups in HP Command View

 On the source EVA, create one or more DR group(s) for all existing ESX Vdisks. Multiple groups should be

created to balance the replication load between EVA controllers and Fabric ISLs.

 Leave the default Synchronous write mode and Destination Hosts Access settings at = None

 On the destination EVA (for this test, EVA 2), present all protected Vdisks to the recovery ESX host(s) with

the same LUN IDs as are on the source EVA 1.

 Repeat the above actions to configure the EVA array in the remote data center if you are configuring

bidirectional replication.

VMware vCenter Site Recovery Manager and Continuous Access EVA

Setting up the Storage Replication Adapter and Command View EVA

VMware vCenter Site Recovery Manager controls and orchestrates failover and test operations on the array

thru a software component called the Storage Replication Adapter (SRA).

The HP StorageWorks Command View EVA Software suite is required to manage and configure EVA

arrays. It provides centralized management, provisioning, health monitoring, and control of EVA in a SAN.

The EVA Storage Replication Adapter (EVA SRA) provides the communication layer between Site Recovery

Manager and Command View EVA.

The EVA SRA must be installed on both the local (protected) server and the remote (recovery) Site Recovery

Manager servers. For instructions, see the HP StorageWorks EVA Virtualization SRM Adapter administrator

guide. It is recommended to deploy the Site Recovery Manager server and vCenter server components into

separate machines. However, with small environments (typically less than 40 VMs), the Site Recovery

Manager server and vCenter server can reside alongside on the same machine. Similarly, they can share

the same SQL or Oracle server instance to house their backend databases. The communication between the

Site Recovery Manager Array Manager and the EVA arrays is out-of-band using an SSL network connection

1 2 3 4 5 6 7 8 9 10 11 12 13 14 ... 37 38

Komentarze do niniejszej Instrukcji

Brak uwag

Brocade Communications Systems StorageWorks 4400 - Enterprise Virtual Array Instrukcja Użytkownika Strona 9

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Switche sieciowe Brocade Communications Systems StorageWorks 4400 - Enterprise Virtual Array