NSI

Software, Inc.
www.nsisoftware.com
Double-Take

4.4
Product Overview
Brad Rodgers
NSI Software, Inc.
Warning: No part of this document may be reproduced or transmitted in any
form or by any means, electronic, or mechanical, for any reason, without the
express written permission of NSI Software. The information in this document is
subject to change without notice. Companies, names and data used in
examples herein are hypothetical and/or fictitious unless otherwise stated.
Note: Product names mentioned herein may be trademarks and/or registered
trademarks of their respective companies.
Agenda
Introduction to NSI Software
.

The Technology behind Replication
Double-Take Business Solutions
Real World Examples
Q & A
The worlds most relied upon vendor
for continuous data protection and
application availability solutions.
The #1 host-based replication software for Windows
60,000 licenses - protecting half of the F500 all the way to the SME
Proven protection for critical applications like Exchange & SQL
Technology available from Dell, HP, IBM, SunGard & resellers.
NSI Software About Us
Leading Provider of Data Replication and High Availability Software and Services

Founded in 1991
Over 240 employees in three offices Hoboken NJ, Southboro MA,
and Indianapolis IN.
Award-winning products Double-Take

and GeoCluster

Over 26 patented technologies
Comprehensive Professional Services Offerings
Prestigious Microsoft Certifications
Certified for Windows Standard, Enterprise and Datacenter
Server on Windows 2000 and 2003
Gold Certified Partner
NSI Software Milestones

$7 Million Strategic Investment
17 Consecutive quarters of XX% growth


50,000
th
license sold
$15 Million Strategic Investment

IBM, HP and Dell standardize on DT for Win. Storage
NSI enters NAS market

Microsoft Gold Partner
Microsoft Server, Adv/Enterprise and Datacenter certified

Launched Double-Take 4.x and GeoCluster
Established Indiana Research Facility

$37 Million Strategic Investment
Awarded US Patent 5,974,563

Released second generation Double-Take, 92% common
code, Windows NT, UNIX and NetWare

Awarded US Patent 5,819,020 protecting 20+ technologies
related to real-time backup
Launched Double-Take

Founded / Launched Balance Suite
Award Winning Solutions
Real-time data protection
Automatic server failover
Application Availability & Disaster Recovery
Windows NT4, 2000, WPNAS and 2003
(Server, Enterprise / Advanced Server, and DataCenter)





Provides redundancy of MSCS storage
Allows MSCS cluster to be separated over IP
Based on Double-Take replication engine
Windows NT 4, 2000, WPNAS and 2003
(Enterprise / Advanced Server / DataCenter)

Double-Take Solutions Overview
High Availability
(Target) Server
Off-Site
Disaster Recovery
(DR) Server
Optional Centralized
Tape Backup
Server
Consolidation
Data Migration
Snapshot
Production (Source)
Servers
Direct offsite connection
or two-stage connection
through local HA server
C
Y
Z
X
Q
Q
Q
EXCH03 (10.1.1.64)
Running Exchange Services
on Drive-X
SQL02 (10.1.1.65)
Running SQL Services
on Drive-Y
WWW (10.1.1.66)
Running WWW + FTP Services
on Drive-Z
CLUSTER01 (10.1.1.63)
Arbitration Path \\FS1\Quorum
Arbitration Path \\FS2\Quorum
Arbitration Path \\FS3\Quorum
LEFTY
10.1.1.61
EXCH03
10.1.1.64
WWW
10.1.1.66
RIGHTY
10.1.1.62
SQL02
10.1.1.65
MSCS with GeoCluster
Y
Z
X
C
So, here is your Windows Network
Active Directory
DNS and WINS
Database Web
File Sharing
& DocMgmt
eMail
NSI

Software, Inc.
www.nsisoftware.com


How Replication
ensures data integrity
Applications
Application Layer
Exchange services
Databases engine
File sharing
Web applications
Server Model
Applications
Windows Operating System
Windows NT4
Windows 2000
Windows-Powered NAS
Windows 2003
Including Storage Server
Server Model
Operating
System
Applications
Operating
System
File System or Cache
An area of memory for disk transactions to be
stored before being written to disk
Server Model
File System
Disk/Hardware layer
Including disk drivers, disk controller
and the actual hard drives
Server Model
Applications
Operating
System
Hardware
Layer
File System
Applications
Operating
System
Hardware
Layer
File System
Applications
Operating
System
Hardware
Layer
File System
Replication
Server Model with Replication Path
NSI

Software, Inc.
www.nsisoftware.com


How does it
REALLY work?
How Replication really works
from an EXCHANGE perspective
1) Client sends message
1) Client sends message
2) Mail client sends to
Exchange server
How Replication really works
from an EXCHANGE perspective
INFO-STORE UPDATE
db=Private_Mailbox
Recipient=Sam Jones
MSG=TO/CC/Options
Message-Body
3) Server updates LOG
and DATA
IMMEDIATE (to DISK) for LOG:
dB / Recipient /
Message=To/Cc/Opt/XxXxXx
TO DATA-STORE in MEMORY
dB / Recipient /
Message=To/Cc/Opt/XxXxXx
1) Client sends message
2) Mail client sends to
Exchange server
How Replication really works
from an EXCHANGE perspective
INFO-STORE UPDATE
db=Private_Mailbox
Recipient=Sam Jones
MSG=TO/CC/Options
Message-Body
(DATA PAGES eventually paged to disk)
How Replication really works
from an OPERATING SYSTEM perspective
3) Server updates LOG
and DATA
1) Client sends message
2) Mail client sends to
Exchange server
IMMEDIATE (to DISK) for LOG:
dB / Recipient /
Message=To/Cc/Opt/XxXxXx
TO DATA-STORE in MEMORY
dB / Recipient /
Message=To/Cc/Opt/XxXxXx
4) Server OS generates
TWO FILE WRITES

one to LOG.CHK
one to PRIV.EDB
File Operation #487
Path = d:\EXCHSRVR\MDBDATA\
File = PRIV.EDB
Operation = [W]rite
Start = 92324 bytes
Length = 42 bytes
Data = To/Cc/Opt/XxXxXx
4) Server OS generates
TWO FILE WRITES

one to LOG.CHK
one to PRIV.EDB
(DATA PAGES eventually paged to disk)
IMMEDIATE (to DISK) for LOG:
dB / Recipient /
Message=To/Cc/Opt/XxXxXx
TO DATA-STORE in MEMORY
dB / Recipient /
Message=To/Cc/Opt/XxXxXx
How Replication really works
from an OPERATING SYSTEM perspective
File Operation #326
Path = d:\EXCHSRVR\MDBDATA\LOGS
File = LOGx.CHK
Operation = [W]rite
Start = 1720 bytes
Length = 42 bytes
Data = To/Cc/Opt/XxXxXx
Applications
Operating
System
Hardware
Layer
File System
File Operation #326
Path = d:\EXCHSRVR\MDBDATA\LOGS
File = LOGx.CHK
Operation = [W]rite
Start = 1720 bytes
Length = 42 bytes
Data = To/Cc/Opt/XxXxXx
How Replication really works
from an OPERATING SYSTEM perspective
File Op
#326
Path
File
Op
Start
Length
DATA
DBLHOOK (driver) asks:
1) Is the Source connected to a Target ?
YES
2) Is it a Write or Read or ???
WRITE=YES
3) Is the file or directory supposed to
be replicated? YES In the Rep Set
How Replication really works
from an DOUBLE-TAKE perspective
Applications
Operating
System
Hardware
Layer
File System
File Operation #326
Path = d:\EXCHSRVR\MDBDATA\LOGS
File = LOGx.CHK
Operation = [W]rite
Start = 1720 bytes
Length = 42 bytes
Data = To/Cc/Opt/XxXxXx
Applications
Operating
System
Hardware
Layer
File System
File
#326
Path
File
Op
Start
Length
DATA
File
#327
Path
File
Op
Start
Length
DATA
File Op
#487
Path
File
Op
Start
Length
DATA
File
#328
Path
File
Op
Start
Length
DATA
. . .
326
327
328
487
How Replication really works
from an DOUBLE-TAKE perspective
Applications
Operating
System
Hardware
Layer
File System
Applications
Operating
System
Hardware
Layer
File System
326
327
328
487
.
.
326
327
328
.
.
.
.
.
.
.
.
.
.


File Op
#487
Path
File
Op
Start
Length
DATA
How Replication really works
from an DOUBLE-TAKE perspective
Applications
Operating
System
Hardware
Layer
File System
File Operation #326
Path = d:\EXCHSRVR\MDBDATA\LOGS
File = LOGx.CHK
Operation = [W]rite
Start = 1720 bytes
Length = 42 bytes
Data = To/Cc/Opt/XxXxXx
Its the same data
in the same order
T:\FS1-D\EXCHSRVR\LOGS\
With one optional exception
326
327
328
.
.
.
.
.
.
.
.
.
.


How Replication really works
from an DOUBLE-TAKE perspective
Applications
Operating
System
Hardware
Layer
File System
Applications
Operating
System
Hardware
Layer
File System
Production Cache Not Lost


Writes Only - not Reads


Data selectable at a File or
Directory Level


Transaction-based Replication
How Replication really works
from an DOUBLE-TAKE perspective
Hardware Independent
Application Independent
Applications
Operating
System
Hardware
Layer
File System
Improves ROI by
extending life of server
No Hidden Costs
(no agents or options)
Solution Points
NSI

Software, Inc.
www.nsisoftware.com
Double-Take

Business Solutions
High Availability
For the purposes of this presentation,

High Availability is defined as a method by which user
data and/or applications are protected and continue to be
available to the user community in order to allow the user
community to remain productive.

This level of survivability assumes and requires that the
remainder of the computing environment is functional
meaning that the users workstations continue to have power and
connectivity to the server resources and the network topology has not
been significantly altered

Production (source) Servers
FS1
DB
FS2
FS3
WWW
FS4
FS5
F/P
Redundant Server
(target)
FSDT
10.9.9.1
10.9.9.3
10.9.9.5
10.9.9.4
10.9.9.2
10.9.9.252
FS1 10.9.9.1
dB System Services started
FS3 10.9.9.3
WWW System Services started
FS5 10.9.9.5
High Availability
Disaster Recovery
For the purposes of this presentation,

Disaster Recovery is defined as a method by which
network information is protected and continues to be
available in the event that the computing environment is
critically impacted.

This level of survivability makes no assumptions and/or
requirements for other surviving components.
Disaster Recovery
Off-Site Storage
Disaster Recovery
FS1
FS2
FS3
FS4
FS5
Backup & Restore
For the purposes of this presentation,

There is no such thing as Backup

The idea of backing up
or writing data to tape/optical is simply the
PREPARATION FOR RESTORE


it is also that series of tasks that make auditors happy.
Open Files on all servers
high CPU on backup server
high network % during backup
I/O results in system-crash

Backup & Recovery
Why not backup at 3PM ?
FS1

FS2

FS3

FS4

FS5
Tape Backup
Open Files on all servers
high CPU on backup server
high network % during backup
I/O results in system-crash
Every office backing up itself
(managed by non-I/S personnel)

Off-Site Courier Services
Backup & Recovery
Why not backup at 3PM ?
FS1
Dallas
FS2
New York
FS3
Chicago
FS4
Seattle
FS5
Los Angeles
Tape Backup
Tape Backup
Off-Site Storage
no Open Files - without agents
no CPU issues
no network bandwidth limits
no stability concerns
truly Centralized Backup
Enhanced Backup
FS1

FS2

FS3

FS4

FS5
Gartner Group
Strategic Planning Assumption
75 percent of large enterprises will combine data replication and
tape technology for rapid application recovery (0.7 probability).

Bottom Line : Organizations that are running 24x7 operations and
are confronting shrinking backup windows, or that foresee an
inability to meet service-level agreements, should plan and
budget for deploying data replication technologies.


Gartner : Designing to Restore From Disk: Backup Futures
Backup with In-Band Processing
1) Production Server checkpoints
databases
Production
Database
(Source)

Backup with In-Band Processing
2) Flag inserted into DT queue
1) Production Server checkpoints
databases
Backup with In-Band Processing
3) When Target receives Flag
operation as completed on Target

so Script executes
2) Flag inserted into DT queue
1) Production Server checkpoints
databases
Backup with In-Band Processing
SNAPSHOT
Backup
so Script executes
In-Band Command Processing
is only available in
REMOTE SITE
running
Windows 2003
as of Monday 8AM VSS Snapshot
as of Monday Noon VSS Snapshot
as of Tuesday 8AM VSS Snapshot
as of Tuesday Noon VSS Snapshot
as of Wednesday 8AM VSS Snapshot
DATA CENTER
running
Windows 2003
Double-Take
Replication
as of August 1 VSS Snapshot
as of August 8 VSS Snapshot
as of August 15 VSS Snapshot
as of August 22 VSS Snapshot
as of August 29 VSS Snapshot
Combining Replication
and VSS Snapshots
MSCS Cluster
Nodes
Group 2
Physical Disk S:
Network Name
IP Address
File Share
Replication Set(s)
Replication from
Node 1
Group 1
Physical Disk T:
Network Name
IP Address
File Share
Replication Set(s)
Cluster Disaster Recovery
Double-Take
Replication from
Node 2
Cluster Disaster Recovery
MSCS Cluster
Nodes
Double-Take
Replication from
Node 2
Group 2
Physical Disk S:
Network Name
IP Address
File Share
Replication Set(s)
Replication from
Node 1
Group 1
Physical Disk T:
Network Name
IP Address
File Share
Replication Set(s)
Migration Projects
Current Server

Windows NT4

Single CPU

Local disk
NEW Server

Windows 2000/2003

Multiple CPUs

SAN or WPNAS
Monday
set up new server

Tuesday
mirroring / replication

Thursday/Friday
Move users as needed

Weekend
Whatever you want
any time that you need multiple
copies of your active data
Y2K / Migration / Testing
Tear-Off / Snapshot
Production
Server or
Cluster
Remote Site
Data Distribution
R
R
R
IP Load Balancing
HW/SW
Balanced IP
10.0.0.1
Balanced Web Server Farm
SAN Replication
S:\
SAN
T:\
IP
NSI

Software, Inc.
www.nsisoftware.com
Double-Take

Customer Solution Scenarios
Scenario 1 : H/A, D/R and B/U
Off-Site Storage
SITE 1 = BEFORE
Tape Backup
FS1
dB
FS2
eMail
FS3
file
FS4
file
FS5
file
Scenario 1 : H/A, D/R and B/U
SITE 1 = AFTER
FS1
dB
FS2
eMail
FS3
file
FS4
file
FS5
file
Scenario 1 : H/A, D/R and B/U
SITE 1 = AFTER
App Server failover to servers
File Server failover to NAS
D/R and Backup at NAS
Scenario 1 : H/A, D/R and B/U
TOTAL SOLUTION
32 DoubleTakes
3 NAS devices
1 tape solution
Scenario 2 : Widely Distributed Environment
100 remote locations
Three target data centers
Each Source Site as at
least 4 servers* (x 33)
= approximately 132 sources per target data center
Data General
Scenario 2 : Widely Distributed Environment
Each Data Center
with 10 Target servers*
Scenario 2 : Widely Distributed Environment
33 Sites x 4 servers each = 132 servers

to one target Data Center
with 10 target servers





Approximately 13 sources per target*
Data General Data General Data General Data General Data General Data General
Scenario 2 : Widely Distributed Environment
www.NSIsoftware.com
Supplemental Reference slides when discussing regulatory
issues (or stats)
High Availability - Statistics
59% of Fortune 5000 companies experience a minimum of 1.6
hours of downtime per week.
This includes Software Crashes, Required System Reboots, and Normal Maintenance.
-Dunn & Bradstreet


In one 2000 study, ONE out of FOUR organizations had a
significant disruption in their computer systems.
- Arcus Data Security
33% = less than four hours
18% = five to eight hours
20% = nine to 24 hours
24% = more than 24 hours

The cost of lost productivity can be calculated using the
average salary+benefits figure of $36 / hour / person
(not including lost revenue opportunities or damage to corporate credibility)
- IDC
40% of all companies that experience a major disaster will
go out of business if they cannot gain access to their data
within 24 hours.
-Gartner

Organizations that lost Records in a Fire:
44% never reopened for business.
30% of the rest didnt stay in business for 3 years.
- Assoc. of Records Managers and Admin.

The Government Accounting Office (GAO) continues to purchase
products or obtain services in the disaster recovery arena.
Because of regulations and the state of security today, spending in
information technology (IT) will grow rapidly with CO-OP
probably the fastest growth of any other area of federal
government
The 2002 IT budget was $2.7 billion, almost double from 2001.
In 2003, the estimate of $4.2 billion for IT represents another 50 percent increase.
The 2004 budget was $4.7 billion.
Disaster Recovery - Statistics
Healthcare & HIPAA
Security Section

142.308 Security standard.
(a) Administrative procedures to guard data integrity, confidentiality, and availability

(3) A contingency plan, a routinely updated plan for responding to a system emergency, that includes
performing backups, preparing critical facilities that can be used to facilitate continuity of operations in the
event of an emergency, and recovering from a disaster. The plan must include all of the following
implementation features:

(i) An applications and data criticality analysis (an entitys formal assessment of the
sensitivity, vulnerabilities, and security of its programs and information it receives,
manipulates, stores, and/or transmits).

(ii) Data backup plan (a documented and routinely updated plan to create and maintain, for a
specific period of time, retrievable exact copies of information).

(iii) A disaster recovery plan (the part of an overall contingency plan that contains a process
enabling an enterprise to restore any loss of data in the event of fire, vandalism, natural
disaster, or system failure).

(iv) Emergency mode operation plan (the part of an overall contingency plan that contains a
process enabling an enterprise to continue to operate in the event of fire, vandalism,
natural disaster, or system failure).

(v) Testing and revision procedures (the documented process of periodic testing of written
contingency plans to discover weaknesses and the subsequent process of revising the
documentation, if necessary).
SEC and NYSE
Securities Exchange Act Rule 17a-3 is the principal rule which sets forth the books and records
required to be made by all broker-dealers.

In addition, Rule 17a-4 establishes the time periods and the manner in which such books and
records must be preserved and made accessible.

These rules and NYSE rules relating to record maintenance, such as Rule 440 (Books and
Records), apply to all members and member organizations - including those acting solely as
Floor brokers and that do not conduct business with public customers.

Rule 446 requires a published Business Continuity Plan.

Members and member organizations have a continuing responsibility to make and preserve records,
which are sufficient to satisfy the requirements of the above rules and to substantiate reports
made to the Exchange.
----------------
NYSE Rule 440 and the Securities Exchange Act Rule 17a-4 apply to the electronic logs maintained
in lieu of paper order tickets and reports of execution, which relate to the members business. In
addition, members and member organizations must ensure that all communications whether
electronic or otherwise, including but not limited to e-mails, instant messages, and similar
communication devices that relate to the firms business as such must be maintained and
retained in compliance with NYSE Rule 440 and SEA Rules 17a-3 and 17a-4.
SEC / Federal Reserve / Treasury
Interagency Paper on Strengthening US Financial System
TECHNOLOGY RECOMMENDATIONS

The business continuity planning process should take into consideration improvements in technology
and business processes supporting back-up arrangements and the need to ensure greater
resilience in the event of a wide-scale disruption.

Core clearing and settlement organizations that use synchronous back-up facilities or whose back-up sites
depend primarily on the same labor pool as the primary site should address the risk that a wide-scale disruption
could impact either or both of the sites and their labor pool. Such organizations should establish even more
distant back-up arrangements that can recover and resume critical operations within the business day on
which the disruption occurs.


By the end of 2004, plans should provide for back-up facilities that are well outside of the current
synchronous range that can meet within-the-business-day recovery targets.


There is general consensus that the end-of-business-day recovery objective is achievable for firms that play significant
roles in critical markets, although many state that this is possible only if firms are able to utilize synchronous data
storage technologies, which can limit the extent of geographic separation between primary and back-up sites. A
number of commenters note that a recovery time objective of four hours is unrealistic unless core clearing and
settlement organizations and the telecommunications infrastructure are operating. Some commenters suggest
that recovery and resumption time objectives should vary by type of market. Other commenters note that further
guidance on the definitions of an "event" and "end-of-business day" is needed to help ensure meaningful
recovery and resumption time objectives.
5015.2-STD for Federal Agencies
(and Contractors)
C2.2.9. System Management Requirements. The following functions are typically provided by the operating system or
by a database management system. These functions are also considered requirements to ensure the integrity
and protection of organizational records. They shall be implemented as part of the overall records management
system even though they may be performed externally to an RMA.

C2.2.9.1. Backup of Stored Records. The RMA system shall provide the capability to automatically create backup
or redundant copies of the records and their metadata (see references (z), (ag) and (am)).

C2.2.9.2. Storage of Backup Copies. The method used to back up RMA database files shall provide copies of the
records and their metadata that can be stored off-line and at separate location(s) to safeguard against
loss due to system failure, operator error, natural disaster, or willful destruction (see 36 CFR 1234.30,
reference (at)).

C2.2.9.3. Recovery/Rollback Capability. Following any system failure, the backup and recovery procedures provided
by the system shall:

C2.2.9.3.1. Ensure data integrity by providing the capability to compile updates (records, metadata, and any other information
required to access the records) to RMAs.

C2.2.9.3.2. Ensure these updates are reflected in RMA files, and ensuring that any partial updates to RMA files are separately
identified. Also, any user whose updates are incompletely recovered, shall, upon next use of the application, be notified that a
recovery has been attempted. RMAs shall also provide the option to continue processing using all in-progress data not reflected in
RMA files (see references (z) and (am)).

C2.2.9.4. Rebuild Capability. The system shall provide the capability to rebuild from any backup copy, using the
backup copy and all subsequent system audit trails (see reference (z)).