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.

Set up a PRO Server Slave

Overview

CrashPlan PRO's Multi-Server feature lets you easily manage your backup growth needs by simply adding PRO Servers to your enterprise. Multi-Server support provides the flexibility to set up both local and remote server backup destinations with centralized management.

Before You Begin

You should be familiar with the material in this article:

How It Works

Install PRO Server on the machine you wish to slave, using the same master license key as the master server, 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 hostname and port field, enter your Master PRO Server's hostname and port.
  4. In the Master GUID field, enter the GUID for the Master PRO Server.
  5. Click Save.

If the server was slaved successfully you will want to log into the master and add the slave as a destination for users.

Considerations

  • New clients will be able view and choose either the master or slave, or both as backup destinations.
  • Existing clients are not granted permission to back up to the slave PRO Server by default. To allow existing users to back up to the slave, follow these steps:
    1. Choose Settings > Edit Default Destinations.
    2. Click the Apply Destination Changes to Existing Users check box.
  • Each server acts as an independent backup destination and backup archives do not replicate across servers. Full capabilities are here.
  • If the master goes down, backups to the slave will continue, but no new computers can start an initial backup up to the slave until the master returns.
  • All users with the ADMIN, MANAGER, or SYSADMIN role on the master will be copied to each slave when it synchronizes with the master.
  • If you are a consultant storing backup data for businesses, the master/slave configuration ties your servers together rather tightly. A slave can authorize computers without the master, but the user data is read only. If you (the consultant managing the master server) were hit by a bus or you decide to retire early, your customers would not be able to add additional computers or manage user data and settings without your (master) server. If they decide to start over with their own master they will lose their archives and the history in them.

Related Articles

recipe/enterprise_growth.txt · Last modified: 2010/04/01 17:59 by jcarlson