of centralized application delivery and data stores enable mobile work-styles and users love the ease of use and ubiquitous availability of applications and data. But Are you sure you have the ability to recover from a catastrophic disaster that seems to happen too often ? Have you taken a look at how you protect your data? Most likely you have configured a disaster recovery strategy that includes replicating a snapshot of your data to your backup data center as shown in the image below.
In some cases, you might even reply to a data center service providers that provides backup as a service. It is important that you take a close look at your RPO and RTO targets you review your disaster recovery strategy. The following image shows a point in time when a failure occurs in the storage system. Recovery Point Objective is the point in time you have the opportunity to return to. This leads to how often you need to replicate. For example, if you have a replication schedule that is night, your RPO is probably close to 24 hours. Recovery Time Objective is the amount of time it takes for the storage system to fully recover from such a failure and is generally a function of how the storage system is designed.
If you're like the typical company, you are probably taking nightly backups. As the criticality of data increases every day, can you really afford to lose the value of an entire data day when strikes disaster? Probably not! You may have to tighten your RPO budgets and plan your replication to run in the background much more frequently - for example, every 30 minutes or more. But are you really able to start and finish this replication in the short window available? This is usually dependent on your WAN capacity and quality. Even if you have quite a WAN pipe, problems such as loss and latency can significantly reduce the use. Let's take a look at why this is the case.
The picture above shows how the TCP flow and ramps up to standard how it behaves when there is packet loss. TCP has a maximum size of the window to keep out unrecognized packets outstanding and must wait an acknowledgment before sending more packets. When the round is high latency, which limits the use of the WAN. When there are losses, the behavior is far worse as TCP reduces the size of the window and ramps it up much more slowly. When you have a combination of these, use the WAN goes down significantly.
Some storage systems allow you to adjust the size of the TCP window, but they still do not address the behavior of the congestion. You also have the possibility to improve the efficiency of replication by compressing the transferred data blocks, but you end up exhausting the CPU and you much rather use it for file service.
Instead, a better approach is to use external WAN optimization appliances that handle the TCP flow control and compression. Citrix CloudBridge brings a comprehensive set of WAN optimization technologies such as TCP optimization, high performance compression, acceleration and QoS support specific protocol to deal specifically with these deployments. According to WAN conditions and the compressibility of the data, typical improvements range from 5 to 10 times the reduction in replication time. With QoS, all traffic through the connection can be classified based on the type of application, priority and shaped so that it is possible to maintain the SLA across applications.
Citrix CloudBridge that the first platform was used to accelerate XenApp and XenDesktop deployments now Sharefile accelerate deployments. With the addition of storage replication to the list of optimizations, the platform can now provide a complete acceleration of these deployments through the center of the branch and data. The following image shows the deployment model associated with the optimization of service delivery and storage replication using the same equipment.
To better understand this compelling architecture and CloudBridge solution, please visit: http: // www. citrix.com/cloudbridge . You can also come and meet our product experts and hear more details about the solution to our Synergy breakout session:
http://www.citrixsynergy.com/losangeles/sessions- labs / .html breakout-sessions? track = Networking & session = SYN303
0 Komentar