Leverages the same replication technology as Subversion MultiSite.
► Delivers transaction-aware continuous hot backup of the primary server to one or more backup servers over a LAN or WAN.
► Meets a recovery point objective (RPO) of zero.
• Everything up to the moment of failure is captured and recovered automatically without administrator intervention.
► Meets a recovery time objective (RTO) of zero.
• Users fail over to backup servers automatically and transparently without anyinterruption in service.
► Ensures zero loss of data and no lost development time.
• Eliminates the risk of human error during disaster recovery.
► Significantly more cost effective than disk mirroring solutions that won’t work over aWAN.
Architecture
► Replicators used by WANdisco’s Subversion MultiSite are used to:
• Ensure continuous hot backup of the primary server to one or morebackup servers.
• Provide self-healing capabilities to automate the recovery process when the primary server comes back online.
► The failover agent automatically redirects clients to backup server(s) in the event of networkor server failures.
Demo
Network Architecture
Reduces network traffic and bandwidth usage and costs
► All reads are local and generate no WAN traffic.
► Streaming on Persistent connection between servers.
• Connection pooling used for multiplexing.
• TCP 3-Way Handshake Eliminated.
► Uses WANdisco’s own protocol over the WAN.
• Eliminates normal SVN chattiness over the WAN
• WAN roundtrip times are significantly reduced
► Overcomes WAN performance issues with HTTP WebDAV Protocol.
• Entire commit with multiple files can be sent over one connection, rather than opening and closing connections for each file.
► Server Versions Supported
• Subversion server versions 1.3 and above are supported.
► Backend Support:
• FSFS and Berkeley DB are supported.
► Supported Clients
• Subversion command line, SmartSVN, RapidSVN, TortoiseSVN, Subclipse, and any HTTP client that works with Subversion.
► System Requirements
• WANdisco for Subversion will run in any J2SE 1.5 or above compliant Java runtime environment. A minimum of 64 MB of RAM and 450MHz CPU is recommended for the server
System Requirements
► Meets a recovery point objective (RPO) of zero. Everything up to the moment of failure is captured and recovered.
► Meets a recovery time objective (RTO) of zero. User access is restored immediately after a server failure or network outage.
► Requires no retraining. Developers and administrators use the Subversion clients and tools they’re familiar with.
► Backup servers can be on the same local area network (LAN) as the primary server, or located remotely over a wide area network (WAN).
► Minimizes network traffic and bandwidth costs over a WAN.
► Can be implemented standalone, or in conjunction with WANdisco’s Subversion MultiSite solution.
Summary