Consider the following scenarios where A is the Primary System, C the Asynchronous Periodic Backup System, and B the Synchronous Backup System, and SRM/SRA is configured between HP 3PAR StoreServ Storage systems A and C.

•All the links are up:

SRM initiates the data transfer from A to C through HP 3PAR SRA. After the sync is complete, SRA stops the RC groups between A—B and also between A—C. Then SRA initiates failover at C so that C becomes the Failover System and takes the role of the Primary System.

•A—C link is down:

HP 3PAR SRA initiates the data transfer from B to C.

After the sync is complete, SRA stops the RC groups between A—B. Then SRA initiates failover at C so that C becomes the Failover System and takes the role of the Primary System. Also see the “Limitations of SLD configuration” (page 38) section.

•A—B link is down:

When the A—C link is up:

SRM initiates the data transfer from A to C through HP 3PAR SRA. Once the sync is complete, SRA stops the RC groups between A—C. SRA then initiates a failover at C so that C becomes the Failover System and takes the role of the Primary System.

When A—C link is down:

Depending on the situation, either B or C will have the most current data since the synchronous link between A—B is down. In such a scenario, as per the design, HP 3PAR SRA does not initiate any data transfer from B to C. With the available data, C becomes the failover system and takes the role of the primary system.

CAUTION: If C does not contain the most current data then any data replicated to B that is not replicated to C is discarded.

•B—C link is down: When A—C link is up:

SRM initiates the data transfer from A to C through HP 3PAR SRA. Once the sync is complete, SRA stops the RC groups between A—B and also between A—C. SRA then initiates failover at C so that C becomes the failover system and takes the role of the primary system.

When the A—C link is down:

HP 3PAR SRA will not initiate the data transfer between B—C, because the B—C standby link is not available for data transfer. SRA stops the RC groups between A—B. SRA then initiates failover at C. With the available data, C becomes the Failover System and takes the role of the Primary System.

CAUTION: If C does not contain the most current data and any data replicated to B that is not yet replicated to the C is discarded.

Reprotect

Perform the reprotect operation to configure protection in the reverse direction (from Site B to Site A), as a preparation for failback to the original state. The SRA operations are similar to the planned migrations, and deletes the earlier snapshots that were created during failover from Site A to Site B.

For SLD configurations, the reprotect operation requires that the remote copy links between the new primary and both the targets to be up. If the array C is the new primary system and if the links

24 Recovery and failback

Page 23 Page 25
Page 24
Image 24
HP System Replication Adapter Software QL227 for VMware manual Reprotect
Page 23 Page 25

System Replication Adapter Software QL227 for VMware specifications

HP System Replication Adapter Software QL227 for VMware is a sophisticated tool designed to enhance data protection and availability for virtualized environments. This software enables seamless replication of virtual machines (VMs) across different locations, ensuring business continuity even in the face of disasters or system failures.

One of the main features of QL227 is its ability to integrate tightly with VMware environments. It supports VMware vSphere, which is a leading virtualization platform, allowing users to leverage their existing infrastructure while benefiting from HP’s data replication technology. The adapter simplifies the process of setting up and managing replication tasks, which can be critical for organizations with stringent uptime requirements.

Another notable characteristic of the HP System Replication Adapter is its support for block-level replication. This technology ensures that only the changed data blocks are transferred to the secondary site, optimizing bandwidth usage and minimizing the impact on system performance. This feature is especially valuable for businesses that operate in environments with limited network capacity.

QL227 also includes advanced monitoring and reporting capabilities. Administrators can easily track the status of replication tasks, with real-time notifications and insights that help ensure data integrity and availability. Additionally, the software offers various recovery options, allowing users to initiate failover or failback processes with minimal disruption to operations.

The adapter’s compatibility with HP’s Enterprise Virtual Array (EVA) storage systems enhances its functionality even further, providing a robust infrastructure for managing replicated data. It is designed to work in conjunction with HP’s other data protection solutions, creating a comprehensive strategy for safeguarding critical business information.

Moreover, HP System Replication Adapter Software QL227 features automated policy management, which simplifies the administration of data replication tasks. This allows organizations to set predefined rules for how, when, and where data should be replicated, reducing the risk of human error and ensuring consistency across environments.

In conclusion, the HP System Replication Adapter Software QL227 for VMware is an essential solution for businesses looking to improve their data replication processes. Its integration with VMware, efficient block-level replication, advanced monitoring capabilities, and compatibility with HP storage systems make it a powerful tool for enhancing data protection and ensuring business continuity. With its innovative features and user-friendly interface, QL227 stands out as a vital component for any organization aiming to secure their virtualized infrastructure.
Top Page Image Contents