HP System Replication Adapter Software QL227 for VMware manual Special notes

Page 33

12 Special notes

•If a single virtual machine sits on two datastores and two virtual volumes, it is recommended to include both virtual volumes in the same Remote Copy group.

•In a disaster recovery scenario, when Remote Copy links are down, the Remote Copy group status could still be Started. A failover attempt will not be successful until the Remote Group status becomes Stopped.

•HP 3PAR SRA configuration will not be deleted in the Windows registry when the HP 3PAR SRA package is uninstalled.

•If a virtual machine sits on a spanned datastore, all virtual volumes used for the spanned datastore need to be included in a single Remote Copy group.

•SRM might potentially time out if multiple test failover or recovery operations are run simultaneously. Rerun the operation if the time out error occurs. Alternatively, the time out error might be avoided if the operations are run sequentially.

•If an ESX(i) host has both FC and iSCSI definitions created on the HP 3PAR storage system and vCenter Server also has both FC and iSCSI software adapter configured, per the vCenter Server's request, LUNs will be exposed to both host definitions in the event of failover. However, if only one host definition is presented on the HP 3PAR storage system (either FC or iSCSI), HP 3PAR SRA will only expose LUNs to whichever is defined on the HP 3PAR Storage system.

•It is strongly recommended to configure one protected group per Remote Copy group.

•If multiple Remote Copy groups are included in one protected group, it is recommended to set the same sync time on all of the periodic Remote Copy groups.

•Remote Copy group reserves .r for naming. Do not include the reserved naming in your Remote Copy group name.

•SRM_RO_<VVID>, SRM_RW_<VVID>, SRM_RECOVER_RO_<VVID>, and

SRM_TARGETBK_RO_<VVID> are reserved virtual volume naming convention for HP 3PAR SRA.

•SRM might potentially run into a virtual volume promote operation during re-protect. If this occurs, retry the re-protect operation.

•Devices on the protected storage system should be read-only after prepareFailover and optionally take snapshots of the source devices for restoration if needed. The way to make a device read-only to meet SRM's specification before failover is to remove VLUN exposure so that no one has access to it. Remote Copy will internally manage the snapshot taking in case something goes wrong during the failover process. In addition, HP 3PAR SRA will also take a snapshot of the devices on the protected site of the SRM (Remote Copy role Primary or Primary-Rev) for restore purposes since the user might activate the Remote Copy sync after failback (setrcopygroup restore) which would destroy the data content. The snapshot name will have the following prefix: SRM_RECOVER_RO_<VVID>.

•Devices on the protected storage system should be read-only after failover. This is the same with prepareFailover. The only difference is if the failover is part of the failback workflow, the protected storage system will become secondary after failback using the setrcopygroup restore command. Devices under the secondary Remote Copy group will automatically have read-only access.

•Devices on the recovery storage system should be read-writable after failover. The way to make the recovery storage system devices read-writable is to make the Remote Copy role on the recovery storage system to Primary or Primary-Revwith the setrcopygroup failover/restore or setrcopygroup reverse command.

33

Page 32 Page 34
Image 33
Page 32 Page 34
Contents Abstract Warranty Contents Introduction VMware vCenter Site Recovery Manager overview VMware vCenter Site Recovery Manager overview Supported configurations HP 3PAR SRA installation and configuration prerequisites Installing HP 3PAR SRA Installing HP 3PAR SRAVerifying installation Removing HP 3PAR SRAHP 3PAR storage system setup Page 12 HP 3PAR storage system setup Create virtual volumes on the protected and recovery sites Verify connectivity s230 Initial setup for Remote Copy from the Protected SiteSetting up Remote Copy targets and links Initial setup for Remote Copy from the Recovery SiteCreating Synchronous Remote Copy groups Adding a Virtual Volume to existing Remote Copy groupsDisplaying the Remote Copy groups configuration HP 3PAR SRA Configuring VMware vCenter Site Recovery ManagerConfiguring HP 3PAR SRA Page Validating HP 3PAR StoreServ Storage SSL certificates SLD configurationPage Clean Up Recovery and failbackRecovery TestReprotect Page HP 3PAR SRA for the VMware SRM 5.5 utility SyntaxOptions Cleanstate Partial licensing Gethost Remote Copy failover from Site a to Site BRemote Copy recover Replication begins from Site B to Site a Nostart Remote Copy restore role back without syncTest failover workflow Remote Copy sync from Site a to Site BSpecial notes SRMROVVID, SRMRWVVID, SRMRECOVERROVVID,Srmtargetbkrovvid Primary Array is down or is taken offline SGT Support for virtual volume sets and host sets Support for multiple array pair configurationWorkarounds for SLD error codes Limitations of SLD configurationSupport for SLD Support for SLD Contacting HP Support and other resourcesHP 3PAR documentation Documentation listTroubleshooting Guide HP 3PAR branding information Typographic conventionsRequired Document conventionsDocumentation feedback

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