270 likes | 458 Views
Leading Edge Solutions, Proven Technologies. Anne-Elisabeth Caillot Pre-Sales & Business Development Anneelisabeth.caillot@visionsolution.com +33(0)1 47 77 15 11 +33(0)6 70 93 71 15. Core Protection Products. Hardware-Independent failover. Full-Server or Data-Only protection.
E N D
Leading Edge Solutions, Proven Technologies Anne-Elisabeth Caillot Pre-Sales & Business Development Anneelisabeth.caillot@visionsolution.com +33(0)1 47 77 15 11+33(0)6 70 93 71 15
Hardware-Independent failover Full-Server or Data-Only protection Reporting and Alerting Windows and Linux
What do I want to protect? Site Hypervisor Data Server Service
www.doubletake.com How Double-Take Replication Works • Host level filter driver replication • Simplified management • Auto discovery, guest level policies, & guest protection schema • One click failover and failover management • Unlimited number of VMs
How Double-Take Replication Works S.T.A.R : Sequential Transfer Asynchronous Replication Applications Applications Any IP Network Operating System Operating System Double-Take Filter Double-Take Filter • Advantages : • Real Time Asynchronous Replication, • Bandwidth optimization, • Intelligent compression, • Byte level replication, • VSS snapshot integration • Data consistency with sequential data transmission, File System File System Hardware Layer Hardware Layer
Hyper-V’s File-Based Data • *.VHD – Files that hold all the data for a particular volume associated with a virtual machine. • *.AVHD - When you take a snapshot of a virtual machine, its .VHD files are “frozen” and subsequent disk writes within the VM are instead stored in a .AVHD file. • *.XML - Hyper-V stores a virtual machine’s configuration information in an industry-standard XML file. • *.BIN and *.VSV - When you pause or take a snapshot of a running virtual machine, Hyper-V stores the contents of the virtual machine’s RAM in a .BIN file and information about the current state of the running virtual machine in a .VSV file.
Mirroring (1/2) • FullMirror • Copies all of the directories and files in the replication set to the target machine. If a mirror has already been completed, another full mirror will overwrite the data on the target. DifferenceMirror Compares all files in the replication set on the source and their current state on the target machine. The comparison is based on the date, time, and size of the file (DTS-Check). Changes can be transmitted on file or block level. NEW: Use of the NTFS Change Journal The difference mirror after a reboot of the source server only checks the changed files since Double-Take services stoped. This dramatically shortens the mirror times after a (planned) reboot!
Queueing • Memory • 32-1024 MB (128 MB default) • HDD • Size depents on infrastructure (LAN/WAN, data volume, etc)
Double Take Monitoring Lan/Wan Source Target • Failover Server Name and IP address • Failover DNS Records • IP ICMP or Heartbeat Monitoring on Host • Detect Failure in Seconds or Minutes • Failover Alert integrated in SCVMM through ProTip integration
Double-Take : Failover & Failback DNS-Failover IP-Failover • Advantages : • Faster Failover • No DNS rights necessary • Disadvantages : • Not possible between different subnets • Advantages : • Online Restore / low Downtime • No subnet limits • Disadvantages : • DNS Rights required
VHD VHD VHD VHD VHD VHD Hyper-V Host Hyper-V Host Host-Level Protection for Hyper-V
VHD VHD VHD VHD VHD VHD Hyper-V Host Hyper-V Host Double-Take for Hyper-V VHD Physical Server Hyper-V VRA
Virtual Recovery Assistant DT-VRA C: DT-VRA FS-System C: System.vhd C: System.vhd E: FS-Data FS-System.vhd File Server C: FS-System.vhd EX-System.vhd E: FS-Data.vhd EX-Data.vhd FS-Data.vhd C: EX-System File Server EX-System.vhd DB-System.vhd E: EX-Data EX-Data.vhd DB-Data.vhd Exchange DB-System.vhd C: DB-System DB-Data.vhd E: DB-Data Database
Automatically provisioned VM Hyper-V Environment • No need to install VMs on the target • Offline VMs on target • No OS/Application licensing on the target
Hyper-V (non-CSV) Cluster & DT Availability Cluster-to-Cluster Cluster-to-Stand-alone
DT Availability for Hyper-V Cluster (non-CSV) & Live Migration over Geographical Distances: Replicate and failover Hyper-V virtual machines in real time over geographic distances quickly and easily
GeoCluster Feature Extend MSCS clusters across any distance Real-time, byte-level replication Eliminate single point of disk failure Support up to 8 node clusters Traditional Cluster Replication
How GeoCluster Works At failover, the new active node resumes with current, replicated data Only the active node accesses its disks Data is replicated to all passive nodes Replication Replication GeoCluster nodes use separate disks, kept synchronized by real-time replication
Hyper-V and Geocluster Double Take and Microsoft clusters Best of two worlds… • Double-Take provides continuous replication • Disaster recovery • Low network and server impact • Works over WAN • MSCS provides application “failover” • Key apps are HA aware using Cluster API • Standard API for 3rd party development • Application Level Monitoring and Failover
DT Availability for Hyper-V Cluster And what works with CSV technology ?? Double-Take Availability can protect Hyper-V with Cluster Shared Volume !! SAN Disk VHD VHD VHD
DT Availability to protect CSV cluster Replication Failover Monitoring With CSV cluster technology, DT Availability is installed within each VMs and enables : - real-time replication for the full VM - manual or automatic failover
Demonstration: Please wait for the demo environment to fully load.