Home » HP » HP0-J64 » Which HP 3PAR StoreServ architectural feature should you position to address this customer need?
During a customer proposal meeting for a 900 TB HP 3PAR StoreServ 10800, you discover an opportunity to address the lack of disaster recovery for two very critical applications that both require approximately 90 TB of usable storage each. The customer is considering a competitive disaster recovery (DR) solution to meet this requirement in a more cost-efficient manner than a second array.
Which HP 3PAR StoreServ architectural feature should you position to address this customer need?
A. Specify an HP 3PAR StoreServ Synchronous Long Distance configuration utilizing an HP 3PAR StoreServ 7200 synchronous configuration for the best possible RPO and RTO.
B. Highlight the benefits of the HP 3PAR unified architecture and propose a minimally- configured HP 3PAR StoreServ 7200 to provide a cost-effective disaster recovery (DR) solution.
C. Propose an HP 3PAR StoreServ solution that highlights the benefits of duplicated storage.
D. Propose a second HP 3PAR StoreServ 10400 with a 250 TB replication license to cost- effectively meet the disaster recovery (DR) requirement.
Correct Answer: C
Explanation/Reference:
Explanation:
http://h20195.www2.hp.com/V2/GetPDF.aspx%2F4AA3-8318ENW.pdf Replication solutions for demanding disaster tolerant environments HP 3PAR Remote Copy software
Long-distance disaster recovery
Disaster recovery requirements that include low RTOs and zero-data loss RPOs pose a significant challenge.
Adding a requirement for a distant disaster recovery site on the opposite side of a continent rather than in an adjacent town greatly compounds these challenges and the complexity of typical solutions.
PDF Replication solutions for demanding disaster tolerant environments, pp 10 e 11 Synchronous long-distance topology Synchronous long distance combines the ability to make replicas created using synchronous mode over a high-speed low-latency network along with the high-link latency replication capability offered by asynchronous periodic mode to provide a long distance replication solution. An SLD topology has the potential of delivering a zero data loss RPO to the remote asynchronous periodic replication site. This is accomplished by using two backup storage servers: one located near the primary InServ using Synchronous mode (the sync array) and a distant storage server using asynchronous periodic mode (the disaster recovery array). In addition to the HP 3PAR Remote Copy connections from the primary array to the two backup arrays, a passive asynchronous periodic link is configured from the sync array to the disaster recovery array (see figure 8). This is the only HP 3PAR Remote Copy technology that supports replicating the same Remote Copy primary volumes from a source array to two separate target arrays. Only a single Remote Copy volume group (consistency group) is supported in an synchronous long distance topology.
The primary intent of the SLD topology is to provide users with a way of potentially achieving an RPO of zero at the distant asynchronous periodic disaster recovery array in the event a disaster renders the primary array down. If a disaster takes the primary storage array down, on failover to the sync array, the passive asynchronous periodic link between the sync array and the disaster recovery array is activated and any data that was written on the sync array but that has not yet made it to the disaster recovery array is sent from the sync array to the disaster recovery array, bringing the disaster recovery array up to date with the last write that occurred to the primary array. After the disaster recovery array has been made consistent with the state of the primary storage array at the time of failure, operations may be continued using the disaster recovery site with no loss of data suffered (RPO = 0) (or operations can proceed from the sync array if that is desired). The normally passive asynchronous periodic link between the sync array and the disaster recovery array is then reversed so updates to the disaster recovery array are replicated back to the sync array albeit in asynchronous periodic mode. When the original primary array is restored to service, its Remote Copy links are reversed and used to synchronize the primary server’s volumes with changes that occurred during the outage before resuming normal service.
Download Printable PDF. VALID exam to help you PASS.
|
|