- Code42 CrashPlan (previously CrashPlan PROe)
This tutorial explains how to add storage to your private Code42 environment by adding a new storage server to an existing destination and by adding a store point to a storage server.
For directions on how to add the Code42 cloud as a back up destination, see this article.
See the Destinations reference for more information on storage and data balancing .
Add a Storage server
Before you begin
Add a destination
The steps below assume you are adding a storage server to an existing destination. To add a new destination:
Sign in to the administration console on your master server
- Go to Storage > Destinations.
- Select Add a new destination.
- Enter a name for for the destination to be displayed to users and throughout the administration console.
- Choose Create.
All servers within a destination must be on the same LAN or at the same data center.
Verify firewall rules
Servers listen for communication from other servers on ports 4283, 4286, and 4288. Before adding any servers to your environment, verify that there are bidirectional firewall rules allowing this communication between servers. All servers must be able to communicate with the master server and vice versa. Servers within a destination must also be able to communicate with each other over ports 4283, 4286, and 4288. Learn more about destinations.
Verify current Master server version
When adding a storage server, make sure to use the same version of the Code42 server software as your master server. To verify the version of your master server and download the correct installer version:
On the server you'd like to use as a storage server:
- Install the Code42 server software.
- From the administration console sign in screen:
- Enter the required information to create the administrator account.
- Enter your existing Master License Key.
This is the same Master License Key as is used on the master server.
- Choose Create Account to sign in to the administration console.
- Go to Settings > Server.
- Enter a Primary and Secondary network address and save.
- From the action menu, select Make Storage Server.
Don't see make storage server?
Make Storage Server only appears on clean installs of the enterprise server.
- Copy the connection string that is presented.
From the administration console on your master server:
- Sign in to the administration console on your master server.
- Go to Storage > Destinations.
- Choose the name of the destination where you'd like the new storage server to be added.
- From the action menu, select Add Server.
- Paste the connection string from the storage server into the Connection String field and save.
Storage server offline
After saving the connection string, the master server confirms the changes have been saved and the storage server will go offline. After 5 to 10 minutes, the storage server comes back online and is accessible from the master server administration console.
Once the server has been added to your environment, add one or more store points.
Add a store point
- Go to Storage > Servers.
- Click the name of the server where you'd like to add the new store point.
- From the action menu, select Add Store Point.
- Enter a descriptive name for the new store point.
- Enter the path to the new store point. This must be a directory that currently exists on the file system and that the host Code42 server has permission to write to.
- (Optional) Enter notes about this store point. These notes are for administrators and might be things like the hardware manufacturer's support info, information about the underlying system, or anything else you think might be useful.
- Click Create.
Once you click Create, a directory is created immediately underneath the path you specified in Step 5. For example, if you'd like the store point to reside under the /repository directory, then a directory is created called /repository/CrashPlanArchive_mSERVERIDxSPID. For example:
This directory is only created at the time of store point creation.
- (Optional) After the store point is created, you can enable data balancing to spread out archives equally between store points.