Achieving high availability on the

1
DRMS - Disaster Recovery
Replicate Your Stratus Data
2
DRMS Disaster Recovery Mirroring System

• Real-time data mirroring
• High throughput
• Hands-free operations
• Easy configuration
• No application changes
• Minimal overhead
• Different Platforms

3
DRMS Data Flow
Databases
Production Server
Hot-Backup Server
TCP/IP
TCP/IP
DRMS Primary Servers
DRMS Backup Servers
UNIX
SQL XML Comma Del.
Critical I/O
Critical I/O
User Applicationsw/ DRMS
DRMS Servers
Database
4
DRMS Replicates

• All file types
• fixed
• sequential
• relative
• stream
• 1-way server queue
• message queue
• VOS internal commands
• Batch
• Command-line
• Macros
• Supports dynamic file wild-cards

5
DRMS is scalable

• Replicate data in any direction
• Many-to-one operation (A-to-C, B-to-C)
• Dual-mode operation (A-to-B, B-to-A)
• Supports all VOS platform (PA7100,
  PA8000,V-Series)
• Supports all VOS release
• The result a Load-Balancing solution

6
DRMS is simple

• No additional hardware or software
• No application changes (not even bind files !)
• Use existing communications
• One table (standard TIN) to configure
• Practically no learning curve

7
Configuration drms_files.tin

• /record_type include
• process_name
• source_path s1d02gtProductiongtdataba
  segt
• destination_dir s2d04gtProductiongtdataba
  se

8
Hands-off operations

• Designed for 24x7 hands-off operation from boot
  to shutdown
• No ongoing maintenance required
• Line failure recovery
• Line switching - alternate routing
• Allows configuration changes without interruption
  (bouncing the software)

9
Performance

• Designed to preserve Primary application
  performance and integrity
• Operation is pushed to remote system
  immediately
• Execution occurs on target system
• Reported 5 overhead at full Continuum capacity
  (_at_25 TPS)

10
Online Monitors Reports

• Online monitor
• Total transactions
• Transaction processing rate
• Queuing activities and statistics
• Reports
• Daily statistics
• By-file/by-I/O type statistics
• Error reporting and handling
• Debugging traces

11
DRMS Implementation

• Identify critical data files for replication
• Identify critical program modules
• Configure drms_files.tin
• Bind programs with drms_routines.obj
• Start DRMS on secondary module
• Start DRMS on primary module
• Monitor operations using built-in tools
• Fine-tune for throughput

12
DRMS Data Extractor
Critical I/O
Critical I/O (raw data)
Configuration File Selection Criteria File
Layouts Index Definitions Templates Field
Selection
Formatted Output SQL XML Comma-DelimitedUser-Defi
ned

• Templates allow fine tuning of SQL and XML
  formats
• User-defined/modifiable data formats
• User may control selection of specific fields

13
DRMS Data Extractor - SQL
Stratus/VOS Raw Data Buffer John Smith
133 Second Ave. New York 10128
From VOS swrite operations Insert into
clients-file values (John,Smith,133 Second
Ave.,New York,10128)
From VOS sdelete operations Delete from
clients-file where first_nameJohn and
last_namesmith
From VOS srewrite operations update
clients-file set address133 Second
Ave.,cityNew York,zip10128) where
first_nameJohn and last_namesmith
14
DB2/SQL Implementation

• Identify VOS files you wish to replicate
• Determine whether you need the entire VOS file
  structure or only selected fields will suffice
• Create your databases/tables ahead of time
• Assign a TCP/IP address and port for the VOS DRMS
  Server and test connectivity
• Complete DRMS configuration
• Rebind your VOS applications and start the system
  without any further changes

15
DB2/SQL Design Notes

• DRMS is designed to perform all data-parsing,
  data-conversion, data-extraction and
  output-formatting on the Stratus/VOS platform
• Any fine-tuning of SQL statements, if any, are
  done on Stratus/VOS
• The receiving platform is responsible only for
  communicating with the Stratus/VOS over standard
  TCP/IP networks and for applying the SQL
  instructions to the pre-defined databases/tables.
• All tables must be defined on the target system
  ahead of time
• Future releases may allow run-time, dynamic
  creation of new tables and indexes

16
DRMS Users

• ICA Handlarnas
• Food retailer in Sweden, since 97
• 2,300 stores, 7.7 billion (ON2)
• The Bank of New York (ON/2)
• The Bank of New York
• Tosco Marketing
• Oil company in San Francisco, since 99
• 15 billion, avg. 650,000 transactions/day (ON2)

17
Customer Testimonials

• DRMS has been stable and has worked reliably
  since we first installed it in August 97
• DRMS implementation took about 2 weeks
• DRMS is very easy to set up and configure
• During peak time (25 transactions/per second)
  we've measured an overhead of no more than 5
• DRMS reliability and SoftMark's extraordinary
  responsiveness has made the implementation of our
  Disaster-Recovery plans an easy, pleasant and
  trouble-free experience
• We rate Application Resources and SoftMark as
  our best vendors in terms of problem/issue
  turnaround
• We are extremely pleased with the performance
  and reliability of DRMS as well as the level of
  support from Application Resources and SoftMark

18
SoftMark solutions are exclusivelydistributed
worldwide by
Contact Mr. Eran Mertens E-mail
em_at_stratusoft.com Telephone [phone] ARI
http//www.stratusoft.com/ SoftMark
http//www.softmark.com/