![Workload Optimization Karl Oman, Sr. Solutions Architect Double-Take Software (Canada) [email_address] www.doubletake.com](https://image.slidesharecdn.com/vmwareusersgroup-canada-koedit-22feb2010-revx1-101020145934-phpapp02/85/doubletake-software-1-320.jpg)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Double-Take Software
Similar to Double-Take Software (20)
More from 1CloudRoad.com
More from 1CloudRoad.com (18)
Recently uploaded
Recently uploaded (20)
Double-Take Software
- 1. Workload Optimization Karl Oman, Sr. Solutions Architect Double-Take Software (Canada) [email_address] www.doubletake.com
- 4. Enterprise Customers
- 8. Virtualized Target Servers Failover Monitoring Replication Lower the TCO of your Disaster Recovery solution by implementing Virtualized target servers and Double-Take
- 9. Complete Virtualization Failover Monitoring Replication Lower the TCO of your entire infrastructure by implementing Virtual machines and Double-Take for all of your servers
- 10. How Real-Time Replication Works Operating System Hardware Layer File System Any IP Network Applications Operating System Double-Take Filter Hardware Layer File System Applications Initial Mirror of Data WAN Optimized Three Levels of Data Compression and Bandwidth Limiting Capabilities
- 13. Virtualized Target Servers Failover Monitoring Replication Lower the TCO of your Disaster Recovery solution by implementing Virtualized target servers and Double-Take
- 14. Virtual Recovery Assistant FS-System.vmdk FS-Data.vmdk EX-System.vmdk EX-Data.vmdk DB-System.vmdk DB-Data.vmdk C: System.vmdk DT-VRA FS-System FS-Data File Server Exchange Database C: E: EX-System.vmdk EX-Data.vmdk DB-System.vmdk DB-Data.vmdk C: System.vmdk DT-VRA FS-System.vmdk FS-Data.vmdk File Server C: E: EX-System EX-Data C: E: DB-System DB-Data C: E:
- 15. RPO and RTO time Time t=0. Point of failure 24 hrs days RPO RTO seconds $ minutes Recovery Time Objective Recovery Point Objective NSI reduces the cost of both RPO and RTO significantly.
- 16. Host Level Protection: ESX & vSphere: Intermittent w3-system.vmdk w3-data.vmdk WWW ex-system.vmdk ex-data.vmdk EX fs1-system.vmdk fs1-data.vmdk FS1 w3-system.vmdk w3-data.vmdk DRW ex-system.vmdk ex-data.vmdk EX2 fs1-system.vmdk fs1-data.vmdk FS2
- 17. ESX Host Level Protection: How it Works www.doubletake.com Committing (remove_snapshot) Source VM Files Replica VM Files Administrative Client *-delta.vmdk *.vmsd *-delta.vmdk *.vmsd Replicating (SCP) *-delta.vmdk *.vmsd *.vmdk *-flat.vmdk *.vmx Synchronizing (SCP) Source ESX Server Datastore (Source) Target ESX Server Datastore (Target) SSH SSH Web Services *.vmdk *-flat.vmdk *.vmx Monitoring (Time/Size)
- 21. Backup and Recovery www.doubletake.com Replication Recovery Recovery Protect Multiple Production Servers With One Backup Repository Recover Back to the Original Server, to New Hardware, or to a Virtual Machine Recovery Repository Server
- 24. Backup Console
- 25. Select Image for Recovery
- 26. How Backup Virtual Recovery Works DB-System.vmdk DB-Data.vmdk C: System.vmdk DT-VRA System.vmdk Backup VRA Source2 Image Source3 Image LiveWire Repository Server C: Source Image Source Data.vmdk Source System.vmdk Source Data.vmdk Source System.vmdk VMWare VMDKs are automatically provisioned by Backup Recover Server Image With Backup Virtual Recovery VMDKs are detached and started as a separate VM VMWare ESX
- 30. Double-Take Move www.doubletake.com Double-Take replicates the workload in real-time while users remain online and working Once a full copy of the workload has been replicated, users can be migrated to the new server within minutes Old Server Target Server Double-Take Move Console
- 32. Double-Take Migrations Physical to Physical Physical to Virtual Virtual to Physical Virtual to Virtual Storage to Storage
- 33. Site to Site Migration Migrate workloads efficiently between sites over any distance Migrate from multiple sites for datacenter consolidation
- 35. How Migration Works (x2x) C: Volume Operating System and Applications Data Volumes User and Application Data Staging Area Replication Step 3: Target Server is Rebooted Step 1: System State Real-Time Replication Step 2: System State is Applied Old Server Target Server
- 36. Physical to Virtual Migration FS-System.vmdk FS-Data.vmdk EX-System.vmdk EX-Data.vmdk DB-System.vmdk DB-Data.vmdk C: System.vmdk DT-VRA FS-System FS-Data Exchange Database C: E: EX-System.vmdk EX-Data.vmdk DB-System.vmdk DB-Data.vmdk C: System.vmdk DT-VRA FS-System.vmdk FS-Data.vmdk File Server C: E: EX-System EX-Data C: E: DB-System DB-Data C: E: File Server Double-Take automatically provisions VMDKs for each workload volume When a full workload is replicated, migration can be completed in minutes
- 40. Q&A For More Information http://www.doubletake.com www.doubletake.com
Editor's Notes
- SPLA 12-15K average sale 30-45 Average Close time 250 software services Champion/Terramake
- 10/20/10 Page With traditional backup, protection is generally a disruptive daily event that has to be scheduled and managed. When there is a problem with the backup, it can fail, schedules can overlap and you are left to clean up a whole mess and try to reschedule or give up and have an even greater exposure to data loss until the next scheduled backup. The backup window has been a real nightmare for administrators, and the shift to global trade and 7 X 24 hour operation has made this impossible in some circumstances. The open file managers and specialized backup APIs have helped (when they work) by making it possible to keep files semi-open during backup. However, in reality, they do a “rolling close” and slow down operations considerably, requiring that backups still be scheduled for times where system activity is very low. Snapshots can help reduce the gaps in protection associated with backup to a point. Snapshots typically rely on proprietary hardware deployments, so cannot be used universally in a mixed environment. There are practical (often vendor imposed) limitations on the number of snapshots that can be maintained, and on how active the system can be. Integration with backup and applications is complex, and may require professional services or experienced consultants to implement and update. Replication maintains an at or near real time image of the primary dataset. While this can be helpful in the case of physical interruption, it does nothing to protect against logical corruption, nor does it provide a time dimension. Corruption or accidental deletion on the primary dataset is instantaneously replicated to the secondary – corruption time 2 phenomenon. Third mirror splits and BCVs (Business Continuance Volumes – an EMC term) may be used to “freeze” points in time. However, these are costly and complex, both in terms of disk usage and operational management. Generally, customized scripting and vendor verification are required, and this still does not eliminate the gaps in coverage between splits. TimeData continuously captures all changes that are made to the data on the server, including changes to the meta data (permissions, attributes). This is an automatic process that occurs in real time. There is no scheduling involved, and no need to pre-select times to snapshot data. Everything is captured, and no intervention is required. TimeData offers the best Recovery Point Objective available, eliminating the protection gaps inherent with backup, snapshot and replication. No pre-selection or psychic awareness required Meaningful events, such as database checkpoints, transactions, file save events, are captured and marked Data is captured exactly as it is written to the primary file system – (no secondary processing or reconstruction of blocks to file) This is not a series of granular snapshots or points in time – ALL changes are captured as and when they occur Changes are ordered and applied in the sequence in which they occur, thereby maintaining congruence at all times
- SPLA 12-15K average sale 30-45 Average Close time 250 software services Champion/Terramake