This site hosts the documentation for CrashPlan PROe version 3.8.2010.
Looking for documentation on PROe version 3, released in April of 2012? Please visit our current documentation.

Setting Up a Master / Slave Configuration with Multiple PRO Servers

Overview

Backing up to multiple destinations means your machines are backed up to two or more locations, which provides the highest level of availability and protection. A common configuration is to have onsite backup for fast, convenient restores and offsite backup for disaster recovery. Each server acts as an independent backup destination and backup archives do not replicate across servers. Full capabilities are here.

Multi-server support provides the flexibility to set up both local and remote server backup destinations, when you want central, enterprise level control and management of your backup archives, policies and users.

Before You Begin

  • Make sure your firewall is configured to allow bi-directional traffic for both master and slave servers on port TCP 4282.
  • Make sure both PRO Servers have Network Addresses configured. The Primary Address must be accessible to each PRO Server.
  • You should be familiar with:

How It Works - the Basics

Adding a slave as a destination involves:

  • Installing PRO Server on the machine you want to slave.
  • Identifying the slave as a destination for a group of users (at the server or organization level)
  • Setting the destination options for the slave, including deciding to make the slave destinations available to existing users or to new users only.

How It Works - the Details

Creating a Slave PRO Server

Using the same master license key as the master server, install PRO Server on the machine you wish to slave. Then follow these steps to attach the slave to your master PRO Server.

Make sure your Slave PRO Server is a clean install and no one has backed up to it yet.

  1. Log into your slave PRO Server.
  2. Choose Settings > Edit Master Server.
  3. In the Master Host and Port fields, enter your Master PRO Server's hostname and port, 4282.
  4. In the Master GUID field, enter the GUID for the Master PRO Server.
  5. Click Save.

With slaving complete, the slave is now available as a backup destination for new users. Follow the next steps to enable the slave destination for existing users.

Enabling the Slave as a Destination for Existing Users

Use these instructions to enable a new destination for existing users.

WARNING: The Edit Default Destinations page allows you to make significant system changes that can affect users' ability to restore their backup, including removing all of the backup archives. Be sure to review the summary of other options for a complete understanding of the options.

Specifying Destinations at the Server Level

  1. Log in to the master server admin console.
  2. Click Settings > Edit Default Destinations on the navigation menu.
    This page displays the destinations available for organizations belonging to this server, including the slave you added in the previous section.
    default destinations
  3. (optional) Click Apply all changes to existing users if you want to make this destination (and all other changes you make on this page) to all existing computers on this server.
  4. Click Save.

Specifying Destinations at the Organizational Level

If any of organizations do not get their Default Destinations from the server level, you need to edit the organization's Default User Settings to make the slave available as a destination.

  1. Log in to the admin console.
  2. Navigate to the organization to which you want to add a slave as a destination.
  3. Click Default User Settings on the navigation menu.
  4. In the Add new destination by guid box, enter the GUID of the master.
  5. Click Apply all changes to existing users to make this destination and to make all other changes on this page available to all existing computers in this org or any of its child orgs that inherit backup destination settings.
  6. After you click Save all computers entering this org will be granted permission to back up to both destinations in the list.
    If you re-enable Inherit Backup Destinations, and apply that change to all users, a list of the destinations that will be removed appears in the admin console.

The Effects of Applying Changes to Existing Users

If you choose to apply these settings to existing users, subsequently clicking the Remove or Stop Backups options result in removing the backup archives for existing users. This table identifies the effect of applying these options to existing users on their backup archives.

Option Effect Deletes Backup Archives
Auto Start Indicates whether or not the clients granted this destination will automatically start backing up immediately No
Apply to Existing Indicates whether or not changes should apply to all computers in this org (and possibly child orgs) -
Stop Backups Stop backups running to this destination without canceling permission to use the destination (the client could restart) Yes
Remove Removes the destination from the list Yes

Related Articles

recipe/back_up_to_multiple_pro_server.txt · Last modified: 2010/08/30 10:24 (external edit)