Who is this article for?
CrashPlan for Small Business, yes.
Code42 for Enterprise, yes.
Link: Product plans and features.
This article applies to version 4.
Multi-destination support with high availability for plans is a feature of SharePlan that ensures plan files and events are available on all participating destinations, regardless of varying network topology, connectivity issues, or usage patterns. Destinations with high availability support enabled can retrieve plan data from each other instead of a client device.
- Redundancy is increased by using multiple destinations, because data is still available despite a power failure, server failure, or disk array failure in one of the destinations
- Reliability is enhanced, because devices can still sync even if one of the destinations becomes unavailable
- Resilience is greater, because more than one path to the data means that your devices will be less affected by network congestion, power failures, and other problems that could affect sync activity
- Bandwidth is conserved, because your LAN won't be overburdened with duplicate uploads of data to multiple destinations
Before you begin
Review the Destinations Overview to ensure you have a complete understanding of the storage hierarchy and how destinations work in the Code42 environment.
Multi-destination support with high availability for plans increases the redundancy, reliability, and resilience of your Code42 environment, because the data within plans and on endpoint devices only needs to be uploaded once, to one of your destinations, before becoming available on all destinations. This is especially useful if circumstances prevent devices from communicating directly with each other or with all destinations.
The diagram below summarizes multi-destination support with high availability for plans. In the environment below, all SharePlan devices are in an organization that is offered both Destination A and Destination B.
For this example, assume the following conditions apply:
- SharePlan Device 1 is unable to connect to Destination B due to network topology, firewall settings or temporary network outage
- SharePlan Device 1 is unable to communicate directly with SharePlan Device 2
- Files from SharePlan Device 1 are uploaded to a server at Destination A
- Plan data is automatically synced directly from the server at Destination A to a server at Destination B
- Even if there is no network connection available between SharePlan Device 1 and Destination B, the plan files and events will be synced to Destination B
- When SharePlan Device 2 requests data from the plan, it can download the needed files from either Destination A or Destination B, depending on which destination responds first.