If you lost your data and don t have a plan, its too late to for DR! When Disaster strikes, will you have HA protection?

Size: px

Start display at page:

Download "If you lost your data and don t have a plan, its too late to for DR! When Disaster strikes, will you have HA protection?"

Stewart Richards
5 years ago
Views:

2 If you lost your data and don t have a plan, its too late to for DR! When Disaster strikes, will you have HA protection?

3 Little about me Definitions History IBM I Disaster Recovery High Availability Disaster Recovery products How they Work Comparison Summary High Availability products How they Work Comparison Summary Things to consider Q & A

5 My name is Robert Seal My first job in IT was Programmer on a 4341 Worked on System 34 and loved the screen design aid Managed several IT departments Designed and created applications from Spare Parts inventory to Model Option Order entry/order processing Designed and created what became itera HA Responsible for remote journaling being used by itera Left to start my own company, isam Blue, llc Channel Managers for a French HA company Created isb-ha Know and used most HA products and many DR products

6 Disaster Recovery products Performs a point in time save of your data Most perform snapshots Data can be stored many different types of media, including the cloud No Real time data replication Disaster Recovery Plus Some are really DR products Some are really HA products Vendors make a lot of claims High Availability products Provide real time data replication, keeping a target server in-sync with the Production server. In the event of a failure of your Production server you can route you users to the Target sever No Point in time / snapshot saves

8 Regulatory Requirements - Unpredictable need for fast access - Lifecycle management Regulatory Archive Have to keep Archive Storage Asset Archive Want to keep Asset Requirements - Openness for flexible access - Valuation management - Longevity Mostly structured, human-generated Mostly un-structured, machine-generated Litigation Support & ediscovery Content or Records Management Database Archiving Digital Media Reference Data Technical Computing Business Analytics Media Production Medical Imaging Seismic Other Media Distribution Surveillance Telemetry Digital Preservation Experiments 8

System 3 1969-1985 Single User Single-platter Disk roughly

card each fixed disc could have a removable cartridge disk

1975-1977 Single user 5, 9, or 13 MB Disk Storage Did not

10 System Single User Single-platter Disk roughly the size of a large pizza; initially each platter held 2.5 MB Max 2.5 to 10 MG data storage Disaster Recover 96 column punched card each fixed disc could have a removable cartridge disk attached High Availability was just a wild dream System Single user 5, 9, or 13 MB Disk Storage Did not replace System 3 Disaster Recover Introduced the an eight-inch Floppy High Availability lots of talk, but no action

11 System Multi-user, Multi-tasking included System 3 and System 32 Processors MB of storage Disaster Recover leaped forward "magazines" - boxes of 8-inch floppies Tape Drive High Availability First Applications created Driven by System to to 1.4 GB System 36 and System 34 were both being sold Disaster Recovery Quarter-inch cartridge Tape drive High Availability was not available

12 1979 System 38 Disaster Recovery Save to Disk then to tape became popular Autoloader Tape drives became available High Availability leaped forward Journaling was added to the OS Journal entries were read on production system, sent to target, and applied. OMS/ODS, Mimix, and DataMirror started either on 34 or Application System/400 or AS/400 replaces system 34 and 36 Disaster Recovery also moved forward More Tape save options High Availability Additional object journaled

13 System/400 Disaster Recovery More Tape save options High Availability First attempt at Remote Journaling Failed Traders HA eserver iseries. Disaster Recovery People started to talk about Disk to disk options (Remote) High Availability Remote Journaling was moved to the Machine level All HA Vendors except Traders moved or added remote journaling IFS was journaled itera HA, Maxava, and Power HA Remote Journaling was the biggest change to HA since Journaling. Remote Journaling offered Fastest communications Improved data integrity Lower Production CPU usage OS handled communications Easier for users itera-ha Changed HA Easier for customer No Journaling experience Easier Startup More Automation

14 2006, IBM System i. Disaster Recovery also moved forward Transfer Saved data to offsite storage High Availability IBM improved journaling, fewer errors Apply Journal entry command improved Bug Busters Vision, itera, and Mimix were all purchased by a private equity firm IBM Purchased Data Mirror IBM began pushing Power HA 2008 power systems Disaster Recovery also moved forward Transfer Saved data to offsite storage now called Cloud DR Disaster Recovery Plus is born Using Journal receivers Saving ever few hours High Availability IBM improved journaling, fewer errors Apply Journal entry command improved Sheilds isb-ha Rocket buys DataMirror IBM Continue to improve Power HA End to end integration Improved small to large IBM i Improved Switch New Products Simplified Installation One step commination setup One step Link setup Trainable Notification system Where is HA going Continued to improve automation Journaling Improvements More Cloud options Improvement to security

16 Tape Applications Running on production server Devices Emulating Tape Devices Home Grown

17 Dedicated System Save Quite your system Perform the save to tape Non-Dedicated System Save Save using Save While active Watch out for add member issues

Emulates Tape Device issues Save Command IBM i writes to tape drive that is really the appliance After Save, tape image is sent to cloud Application running

18 Emulates Tape Device issues Save Command IBM i writes to tape drive that is really the appliance After Save, tape image is sent to cloud Application running on IBM i Makes a list of objects to save Save the object to file Some Send Delta changes others the complete save file to the appliance Appliance send to cloud

19 IBM has made this a lot better option by developing the Virtual Tape. Perform standard save command to virtual tape FTP Tape image to cloud You can also use save to save file

20 Tape Option Appliance Options Application Tape Emulation Home Made Replication Method Blocks of Data No Yes No No Tape Image Yes No Yes Yes Save Check Point All Obj By object All Obj Option Object size reduction Compression Yes Yes Yes Yes Delta Processing No Yes No No De-Dup? No Option Yes Other items Runs Application on Prod. No Yes No Yes Use standard Yes No Yes Yes IBM Save Cmd SAVSYS Yes No Yes Option Use current save Yes No Yes Option process How is data stored As a tape image Yes No Yes Yes Stored in blocks with index file(s) No Yes No No

21 Tape Summary option lower cost Cloud Application Space saving Cloud Tape Emulation Save System and Checkpoints Home Grow You love what you make Vendors Tape Hardware vendors Cloud Application Evault LaserVault Cloud Tape Emulation IBM Tributary

22 Some products called High Availability are Disaster Recovery Nightly backup, change receivers, and save receivers every few hours Vendors call it High Availability They do not keep the backup in-sync real time Some products called Disaster Recovery are High Availability Apply on target in near real time with manual failover Vendors call it Disaster Recovery They do not perform Snapshot or point in time save. They do have a place, my only concern is that you classify them correctly.

23 Need simple solution Tape Backup Have the time and resources Build your own Checkpoints and SAVSYS Emulate Tape solutions Cloud Backups Applications running on IBM i Shorter RPO Disaster Plus The one you choose!

25 Hardware Replication Logical or Software based Replication (apply journal entries) Harvest on Production Use Remote Journaling and Harvest on Target Let s see how each method works

Some System Objects must reside on system ASP System ASP is replicated by Logical Replication Main Site Prod DS5000 PowerHA for i (automation & management) HA/DR Site DS5000

26 Some System Objects must reside on system ASP System ASP is replicated by Logical Replication Main Site Prod DS5000 PowerHA for i (automation & management) HA/DR Site DS5000 HA/DR Requires SAN SAN storage is defined in blocks IASP Prod Global Mirroring IASP Prod IBM i sees SAN as IASP IBM i sends update to SAN SAN sends changed blocks to target SAN

27 Your Program Application Program 1 3 Journal 2 Table Receiver 13 2

28 Application Program 1 Sync A sync Table 2 Receiver 1 Receiver 1

29 Your Program Application Program Application Handles Apply System Handles Apply Table Receive/Apply Process Table Receiver 1 Receiver 1

30 Your Program Receive/ Apply Process Application Program Receive/ Send Process Table Table Receiver 1

31 Replication Method Hardware Logical Hardware Logical Special Requirements Blocks of Data Yes No SAN Yes Optional Journaling / Save object Limited Yes IASP Yes Optional Save and hold No PD Ability to use No Yes target Select / Omit No Yes Re-Sync restart Yes Optional Objects Replicated All PD Audits No Yes One step setup No PD Switch Backups Configurable No PD Automatic Snapshot Process Yes No Flexible No PD Backup From Target Yes Yes How many steps? PD Communications Test Switch Opt.? PD Automatic Setup No PD Monitoring Remote Journaling Optional PD Required PD Replication HA Independent Yes PD Trainable PD Notification system Bandwidth requirements High RJ low NRJ Lower

32 Summary Hardware Replicate Everything Lot of bandwidth Like idea of Block Replication Willing to buy SAN Using IASP is not a problem Logical Ability to choose what to replicate Lower Bandwidth Requirements More Testing Options Use the backup for reports Logical W/O Remote Journaling Bandwidth constraints Vendors Hardware IBM EMC Logical W/O Remote Journaling Vision Traders (only option) Bug Buster isb-ha Logical using Remote Journaling Maxava Shields Vision Bug Buster isb-ha

33 IASP not a problem, lots of bandwidth Hardware Replication Want more control of what you replicate Logical Replication Simplest communications Logical Replication Hardware replication Bandwidth and issue Logical without Remote Journaling The one you choose

36 Recovery Point Objective RPO Recovery Time Objective RTC Service Level Agreement - SLA Total Cost of ownership TCO Operating Cost

38 What are your customers Expectations? Auto industry charges 1 million an hour if line stops because of lack of parts SLA with Big Box Stores Does your customer have a choice of vendors? Will they walk? Do you have a paper Trail? Web Reduced paper to increase efficiency How are you going to find out what needs to be entered? Are you Regulated?

39 Types of outages to be addressed Unplanned (for example, a hardware failure) Planned (for example, a software upgrade) Backups (for example, create copy of disk for on-line save to tape) Disasters (for example, site loss, power grid outage, etc). Communications Bandwidth requirements Reliability Pointing users to Target system

Robert Seal can be contacted: 801.368.9400 Robert.seal@isamblue.

40 Robert Seal can be contacted: This presentation is copyrighted by isam Blue, llc 1188 w 2000 n, Mapleton, UT Isamblue.buz

New IBM i Technologies and Wine Make Backup and Recovery Better. Debbie Saugen Director, Business Continuity Services

New IBM i Technologies and Wine Make Backup and Recovery Better Debbie Saugen Director, Business Continuity Services debbie.saugen@helpsystems.com About the Speaker Debbie Saugen is recognized worldwide