Beruflich Dokumente
Kultur Dokumente
Ver s i o n 4 . 0 S P 0 1
D o u b l e - Ta k e Av a i l a b i l i t y I n t e g r a t i o n G u i d e
July, 2012
Double-Take Availability Version 4.0 SP01 Integration Guide
Copyright Vision Solutions , Inc. 20032012
All rights reserved.
The information in this document is subject to change without notice and is furnished under a license agreement. This
document is proprietary to Vision Solutions, Inc., and may be used only as authorized in our license agreement. No portion of
this manual may be copied or otherwise reproduced without the express written consent of Vision Solutions, Inc.
Vision Solutions provides no expressed or implied warranty with this manual.
The following are trademarks or registered trademarks of their respective organizations or companies:
Vision Solutions is a registered trademark and ORION Solutions, Integrator, Director, Data Manager, Vision Suite,
ECS/400, OMS/400, ODS/400, SAM/400, Double-Take GeoCluster, Double-Take RecoverNow, Double-Take SHARE,
RecoverNow and iTERA HA are trademarks of Vision Solutions, Inc.
DB2, IBM, i5/OS, iSeries, System i, System i5, Informix, AIX 5L, System p, System x, and System z, and WebSphere
International Business Machines Corporation.
HP-UXHewlett-Packard Company.
TeradataTeradata Corporation.
IntelIntel Corporation.
LinuxLinus Torvalds.
OracleOracle Corporation.
SybaseSybase, Inc.
All other brands and product names are trademarks or registered trademarks of their respective owners.
If you need assistance, please contact Vision Solutions SCP Certified CustomerCare team at:
CustomerCare
Vision Solutions, Inc.
Telephone: 1.800.337.8214 or 1.949.724.5465
Email: support@visionsolutions.com
Web Site: www.visionsolutions.com/Support/Contact-CustomerCare.aspx
Contents
Chapter 2Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Setting RecoverNow Applications to Manual Failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Network Bandwidth and CPU Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
iii
Contents
iv
Overview of Double-Take
Availability
Introduction
A combination of High Availability Clustering and Data Replication
ensures an effective and efficient disaster recovery solution. Double-Take
GeoCluster (hereafter referred to as GeoCluster), is the clustering
component that automates the detection and recovery of applications and
their dependent resources from various system and human failures.
Double-Take RecoverNow (hereafter referred to as RecoverNow), is the
replication component that provides Continuous Data Protection (CDP)
and a high level of data protection from both disasters and data
corruption. The two components, GeoCluster and RecoverNow, working
together, comprise the Double-Take Availability solution.
GeoCluster and RecoverNow provide efficient disaster recovery:
Chapter 1: Overview
Supported Configurations
Vision Solutions supports two RecoverNow configurations:
Chapter 1: Overview
Chapter 1: Overview
Chapter 1: Overview
NOTE
Chapter 1: Overview
12. Edit the stanza that is similar to the example stanza shown below in the
/tmp/C<Failover Context ID>.cfg file replacing the contents of the
ObjectAttributeValue field with the output from the rthostid
command.
SCCuAttr:
ObjectName = "backup"
ConfigObjectSerial = 4
ObjectType = "SCRT/info/host"
ObjectAttributeName = "HostId"
ObjectAttributeValue = "5FBBC3EF"
ObjectAttributeType = "ulong"
SerialNumber = 4006
ObjectNlsIndex = 0
SC_reserved = 0
ContextID = 11
Chapter 1: Overview
Chapter 1: Overview
Chapter 1: Overview
Unplanned Failover
Planned Failover
NOTE
Unplanned Failover
In this scenario, the Production server is unavailable due to a disaster. For
example, an entire site is lost due to a disaster such as a flood or hurricane.
Use the following procedures to restore data from the Recovery Server to
the Production Server. For complete details on these procedures refer to
Chapter 13, Double-Take RecoverNow Disaster Recovery Operations in
the Double-Take RecoverNow User Guide.
1. On the Recovery Server, create a Snapshot and validate the data
integrity:
scrt_ra -C <Context ID> -D <time>
or
scrt_ra -C <Context ID> -t <LFCID>
Once you create a snapshot of the replica, you can analyze the integrity
of the data. If analysis indicates data corruption, remove the snapshot
and use a virtual restore to locate and validate an optimal restore point.
2. On the Recovery Server, backup the data. This provides additional data
protection by keeping complete copies of the data on archive media
such as tape. Refer to Chapter 12, Working with Archived Data, in
the Double-Take RecoverNow User Guide
3. On the Recovery Server, execute Failover. Do one of the following:
Failover Restore: Roll back to the actual data replica.
scrt_ra -C <Primary Context ID> -F [-t | -D | -S]
Chapter 1: Overview
Planned Failover
In this scenario, the administrator has a scheduled maintenance period and
switches operations that run on the Production Server to the designated
Recovery Server.
The data can be restored to the Production Server from the Recovery Server
using the following procedure:
1. On the Recovery Server stop the application.
2. On the Recovery Server failover to the Recovery Server:
rtdr -C <Primary Context ID> failover
10
Chapter 1: Overview
4. On the Recovery Server start the LCA (scr_lca) and synchronize the
data to the Production Server.
rtdr -fC <failover context> resync
11
Chapter 1: Overview
12
There are two production nodes with a shared disk between them
Chapter 1: Overview
Failover Scenarios
Several failure scenarios are supported, these topics describe the most
significant failure, that of the Production Server. Vision Solutions highly
recommends, for a Production to Recovery configuration, that the
application whose data is being replicated by RecoverNow be configured in
GeoCluster does not automatically failover on failure. This is because, once
a failover is complete, the ability to use RecoverNows data roll-back
(CDP) recovery feature is lost. Switching from Primary mode to Failover
mode on the Recovery Server wipes clean its undo and redo logs.
Once you are notified of the failure, you should determine the cause of
failure and decide whether it is necessary to use the RecoverNow CDP
(roll-back) feature, or to proceed and manually initiate the failover
sequence. If you perform any roll-back, you can use GeoCluster to clear the
failure state, and resume normal operations. The latter (manual failover) is
done by switching the Application from the Production Server to the
Recovery Server via the GeoCluster Web Interface.
Upon failover, the mode for the Recovery Server changes from Primary to
Failover, thereby making accessible to the application (which had also
failed over from the Production to the Recovery Server) the replicated data,
by activating the logical volumes and filesystems associated with that
Context.
On recovery of the failed Production Server, in keeping with the GeoCluster
policy to not automatically fall back, the Production Server is also switched
to Failover mode, and replication is activated. Although the terminology
used by RecoverNow is that the Failover Context is in use, this is not a
degraded state; normal operations can occur indefinitely.
Once the Production servers data has been synchronized with the Recovery
server, the user can manually switch the Application from the Recovery
Server back to the Production Server. In this way, the user can initiate the
recovery sequence, which causes the mode of the Recovery Server to
change from Failover to Primary, thereby re-assuming the role of recovery,
while the Production Server changes to its Primary mode and re-initiates
replication.
For each Primary and Failover Context pair GeoCluster manages, the
GeoCluster Web Interface provides:
Direction of replication
13
Chapter 1: Overview
14
Planning
Storage
In RecoverNow, data to be replicated is kept in non-shared storage. Each
GeoCluster node has its own storage relegated to replication. That means
that the Production Server and the Recovery Server each have their own
storage.
An application runs on the Production server. When an application runs
on the Production server, it accesses only the primary data store. When an
application runs on the Recovery Server, it accesses the failover data
store.
Disk Space
If you are using RecoverNow in tandem with GeoCluster, the 64-bit
kernal version of RecoverNow uses approximately 24 MB in directory
/usr/scrt.
However, over time, information will be added to the following files:
/usr/scrt/log
/usr/scrt/archive
/usr/scrt/run
/usr/scrt/config
Settings
Specify the following settings:
Configuration 1For a Highly Available Production Server
configuration the AUTO ON: Volume Group parameter must be set to
"no" for the RecoverNow shared Volume Groups. The value can be
15
Chapter 2: Overview
16
Chapter 2: Overview
17
Chapter 2: Overview
18
Setup
This section is intended for customers who want to install and configure
RecoverNow and GeoCluster.
19
Chapter 3: Overview
If you are using another HA tool, you must write your own script to
make it highly available
Application A: LV 1-10
Application B: LV 11-20
Application C: LV 21-30
These logical volumes are part of a Volume Group that is active on only one
node. If an application fails over, all of the LVs must go with it so that a
logical volume is not active on more than one node at a time.
To set up this scenario, define your LVs and Volume Group in a
RecoverNow context using RecoverNow. Any context which uses
20
Chapter 3: Overview
21
Chapter 3: Overview
22
Chapter 3: Overview
23
Chapter 3: Overview
24
Documentation Set
Title
Description
25
Chapter A: Overview
26