HP NA Architectures for Failover and Disaster Recovery Based on NA 9.21 Feb 2013

Transcription

1 HP NA Architectures for Failover and Disaster Recovery Based on NA 9.21 Feb 2013

2 Brought to you by Vivit Network Automation Special Interest Group (SIG) Leaders: Wendy Wheeler & Chris Powers

3 Today s Host Wendy Wheeler Network Automation SIG Champion Content Manager/Operations Manager HP

4 Housekeeping This LIVE session is being recorded The recording will be available on BrightTALK immediately after this session Q&A: Please type questions in the Questions Box below the presentation screen Additional information available for you behind the Attachment button and later on the Vivit website

5 Today s Presenter 12 years in Network Management Business Unit of HP with experience in several networking domains Swamy Mandavilli NA Functional Architect HP Worked on NNMi and NNMi ispis Has several HP patents granted, many of which are in Network Management domain

6 Agenda 1. High Availability 2. Disaster Recovery 1. Overview 2. High-level Steps 3. Q&A

7 High Availability NA s solution: Horizontal Scalability architecture Two or more NA cores connected to one Database All NA cores and DB within a location (e.g., same data center) Task scheduling alternatives Core Binding Distributed Round Robin (recommended, if it can be used) Network -2 Network -1 Network -3 Core-2 Automatic Failover Automatic Failback with Distributed Round Robin New HS Guide has full details For Database HA Solutions such as Oracle RAC can be used Core-1 DB Core-3

8 Overview of Disaster Recovery Why DR solution Needed? Unplanned data center wide disasters such as Earthquake Planned outages of data center such as: Procedures Hurricane warning Data center shutdown due to maintenance work Full details in: Disaster Recovery Configuration Guide Latest version: 9.20 patch1 Use new version of HS guide (modified for DR) Latest version: 9.21 NA version 9.21 has both: HS with automatic failover capability Disaster Recovery capability

9 Disaster Recovery Architecture DR environment in a remote location (different data center typically) One-way database replication All NA cores configured as HS NA cores File Synch (for non-db global-data) NA cores in DR location are in INACTIVE status

10 NA Core Active/Inactive Status Active Status: Fully functional NA Core Inactive Status: Does not run tasks Users should not log in Does not communicate with other NA Cores Does not participate in failover Users can connect to CLI only for setting NA Core status Can be running or shutdown NA Server can be powered down (optional) *** Status of an NA Core can be changed to Active/Inactive using CLI: NA> set core status

11 Setup Steps (highlights) Start with NA deployment running in Primary location Typically multiple NA cores in HS Or, it can be standalone NA Create DB in DR location Export data from Primary DB and import into DR DB Configure one-way replication: Primary DR DB Install and configure NA environment in DR location Point all NA cores to the DB in primary location Follow steps similar to regular HS Inactivate NA Cores in DR location Using CLI commands: NA> set core status Configure File Synch Optional: power down NA Core servers in DR location

12 Database Replication Any replication technology can be used Oracle Golden Gate (Oracle, Microsoft SQL Server) Oracle Data Guard Microsoft SQL Server Replication *** We tested primarily with Golden Gate on Oracle

13 File Synch Synch of NA data that is not in the DB Driver Packs, OS Images, required RCX options In HS, these are replicated from Active NA Core to other Active NA Cores Two high-level approaches 1. Copy files directly to NA Cores in DR location 2. Use Intermediate server Needed if NA Core servers in DR location are powered down Copy from one of the NA cores in primary location to an Intermediate server At switchover time: copy from Intermediate server to ALL the NA cores in DR location Use any file replication technology Set up script for periodic check/update We tested with rsync

14 Switchover Steps (Highlights) File Synch: copy files from Intermediate server to NA cores in DR location Point NA cores in DR location pointing to DB in DR location Stop replication Activate NA cores in DR location Inactivate NA cores in Primary location Reconfigure Integrations (if any) Start NA cores in DR location

15 Switchback Options 1. Go back to the original configuration 2. Recreate primary location same or different physical location 3. Make the current DR location as new primary and set up another DR location

16 Switchback Steps (Highlights) with option 1: Go back to original config Export/Import data from DR location DB to primary DB While that is the typical approach, alternative approach with reversereplication may be used for shorter duration and planned outages In that case, at switchover time, setup for reverse-replication Start one-way replication Activate NA Cores in primary location Point the NA Cores in DR location to primary DB Inactivate NA Cores in DR location Re-configure integrations (if any) Start NA cores in primary location

17 Other Topics in This Context Non-Production Licenses needed for NA cores in DR location i.e., similar to HS If Satellites are used: DR-location also needs to include at least one Core-Gateway And, redundant Tunnels need to be created with higher cost Total number of NA cores (including Inactive): Maximum 9 Ongoing monitoring of healthy DB replication expected (error checking etc.) *** Use steps in the Disaster Recovery Configuration Guide. This presentation is not meant to include complete set of steps.

18 Q & A

19