Shashikant Gaikwad

Protect Database Oracle 12c with Global-Active Device on Hitachi Virtual Storage Platform G Series

Blog Post created by Shashikant Gaikwad Employee on Nov 13, 2016

Oracle databases are used for many mission-critical enterprise applications. The requirement to make these applications consistently available implies the use of Disaster Recovery (DR) technologies to avoid any unplanned downtime. Customers may want to add DR capabilities to their Oracle environment and want to use Hitachi Global Active Device (GAD) as a common DR implementation for Oracle database and other application. Direct consequences of application downtime and data unavailability are unhappy customers, loss of productivity and revenue and challenges to corporate reputation. In short, enterprise deployments needs protection from unforeseen disasters and natural calamities.

 

An answer to this problem from Hitachi Data Systems (HDS) is Hitachi global-active device. The base “UCP 6000 for Oracle RAC” solution provides a highly available solution, in addition to this GAD provides an explicit DR features. Customers can protect their database in Oracle 12c real application cluster (RAC) environment with global-active device on Hitachi Virtual Storage Platform (VSP) G Series.

Best practice guide "Protect Database Oracle 12c with Global-Active Device on Hitachi Virtual Storage Platform G Series" has demonstrated how GAD can be deployed to add DR capabilities to an ‘UCP 6000 for Oracle RAC’ solution. This best practice guide demonstrates how to use global-active device in VSP G series to protect Oracle Database 12c with RAC in a two-site environment. See how to deploy global-active device to add backup and recovery capabilities in an Oracle environment to achieve zero for a recovery point objective (RPO) and a recovery time objective (RTO) in case of disaster or component failure.

 

GAD ensure continuous operations for your most mission critical data and applications by simplifying and automating high availability. It extends storage virtualization horizontally across multiple enterprise storage systems and achieves active-active clustering and volumes that span physical systems.

Figure 1 shows RAID groups and provisioning pools created for the environment on each VSP G600, each Hitachi Compute Blade 2500 and Hitachi Compute Blade 500 on site 1, site 2 and the quorum site.

Storage_Final.png

Global storage virtualization provides "global active volumes." These are storage volumes with the ability to have read and write copies of the same data in two systems or geographic places at the same time. The active-active storage design enables production workloads on both systems in a local or metro cluster configuration while maintaining full data consistency and protection. Configuring Oracle Real Application Clusters on extended distance with global-active device lets you to create and maintain synchronous, remote copies of data volumes on Hitachi Virtual Storage Platform G series storage.

The evaluated architecture used a synchronous replication model for zero data loss between two Hitachi Virtual Storage Platform G600 storage systems that were separated by 20 km and 100 km for load balancing and active/active availability. A network emulator unit was used to emulate the systems at certain distances apart between the site 1 and site 2 to observe any disaster recovery obstacle due to the increased distance between sites.

 

Table below lists the most common use cases and scenarios evaluated

Use Case

Objectives

Results

Use Case 1 — Recover Oracle Database After Complete Site 1 Failure

Recover from a complete site 1 storage system and Oracle RAC hosts failure while Oracle Database instances still run on the surviving site 2 storage system.

Success

Use Case 2 — Recover Oracle Database After Site 1 Storage Failure

Recover from a site 1 storage system failure while Oracle Database instances are running on the site 2 storage system.

Success

Use Case 3 — Recover Oracle Database After Quorum Site Failure

Recover from a quorum disk failure while Oracle database instances are running at the surviving site.

Success

Use Case 4 — Recover Oracle Database After Storage Replication Link Failure

Recover from storage replication link failure between site 1 and site 2 storage systems.

Success

Use Case 5 — Recover Oracle Database After Path Failure Between Servers and Local Storage System

Recover from path failure between servers and local storage.

Success

Use Case 6 — Recover Oracle Database after All Fibre Channel links Fail

Recover from a failure all of the Fibre Channel link connections between site 1 and site 2.

Success

Use Case 7 — Demonstrate Planned Power Off and Power On at Site 1

Demonstrate how to perform a planned outage and restart with the site 1 storage system.

Success

 

In conclusion, using Hitachi Storage Virtualization Operating System with global-active device provides an infrastructure with continuous availability that does the following:

  • Protect your database with global-active device from unplanned outages at data centers to keep database available.
  • Use global-active device with host-based applications to fail over between a primary site and secondary site Hitachi Virtual Storage Platform Gx00 with no disruption. Hitachi Dynamic Link Manager provides host multi-pathing with deep storage integration.
  • There is no adverse effect on recovery procedures and data protection for distances between sites that are 20 km to 100 km apart.

You can leverage the benefits of synchronous data replication beyond traditional disaster recovery protection to include workload balancing across sites and coordinated site-wide maintenance with no downtime.

 

Sincere thanks to  Yoshihito Katayama, Tsuyoshi Inoue, ITPD Team, Steven Burns, Eduardo Freitas for their vital contribution and making this paper possible.

 

Please Click Here to get best practice guide to Protect Database Oracle 12c with Global-Active Device on Hitachi Virtual Storage Platform G Series

Please Click Here to get recorded video for hands on done for executing scenario where we  "Recover Oracle Database After Storage Replication Link Failure."

Outcomes