Setting Up The PROe Private Cloud
Who is this article for?
Incydr, no.
CrashPlan for Enterprise, no.
Code42 for Enterprise, yes.
CrashPlan for Small Business, yes.
This article applies to on-premises authority server version 3.
Overview
This article describes how to install your Code42 environment as a private cloud deployment of CrashPlan PROe, in which your data is stored on your own servers. For details on other CrashPlan PROe deployment options, see CrashPlan PROe Architectures.
After completing the tutorial, you will have:
- Installed the enterprise server
- Configured your enterprise server as a master server and backup destination
- Started backing up one device running the CrashPlan app to the master server
Before you begin
- Review the system and network requirements to verify that your systems meet the system requirements
- Open required ports on the server that will be your master server
Step 1: Set up your master Enterprise server
Download & install CrashPlan PROe
- Download the latest 3.x version of the CrashPlan PROe installer for your operating system.
Each enterprise server installer includes CrashPlan app installers for Windows, OS X, Linux, and Solaris. - Launch the installer.
- Windows: Double-click the MSI file.
- OS X:
- Mount the DMG.
- Double-click the PKG file.
- Linux:
- Unpack the tgz archive.
- Navigate to the location of the unpacked files with
cd. - Execute the install.sh BASH script from the directory in which it resides.
User privileges Example command Installation as root sudo ./install.sh
Installation as a user ./install.sh
- Solaris:
- Move the tar.gz archive into /var/spool/pkg
- Unpack the tar.gz archive
- Install CrashPlan PROe package with
pkgadd. If there are multiple packages in the default spool directory, then specify the folder name of the package to be added. For example:pkgadd CrashPlanPROServer
- Follow the prompts to complete the installation.
When installation is complete, the installer starts the enterprise server service and launches the PROe Monitor. The PROe Monitor displays licensing information and contains a link to access the Code42 console, which is your browser-based management console.
Activate your Enterprise server
- Open the Code42 console in a web browser. You can:
- (Windows) Open PROServer from your Start Menu
- (OS X) Open PROServer in your Applications folder
- Point a web browser to your server's hostname or IP address on port 4280.
- Example 1: http://master-server.example.com:4280/console
- Example 2: http://192.0.2.100:4280/console
- Enter information for your Code42 environment administrator account.
- This creates a local administrator account within your Code42 environment. The local administrator has full administrative permissions.
- It is not necessary to use the same information entered when requesting a MLK. Your user accounts are internal only, limited in scope to your Code42 environment.
- System alerts are sent to the email address associated with this administrator account.
- The administrator account cannot be used for backing up devices.
- Enter your Master License Key (MLK). If you do not have an MLK, contact sales.
- Navigate to Settings > Server.
- Complete the fields for Primary Network Address and Secondary Network Address of your enterprise server, according to your environment. The enterprise server communicates by default on TCP port 4282.
- Example 1: master-server.example.com:4282
- Example 2: 192.0.2.100:4282
- Do not add "http://" to the primary and secondary network addresses.
- You can specify a DNS name or an IP address for the primary and secondary network addresses.
- We recommend using an IP address, not a DNS name, for the Secondary Network Address in order to avoid unexpected behavior in the event of DNS issues.
Primary and secondary network addresses
The Primary Network Address and Secondary Network Address fields must be completed and correct in order for devices to connect to your enterprise server.
The Primary Network Address and Secondary Network Address fields must be completed and correct in order for devices to connect to your enterprise server.
Step 2: Back up your device using the CrashPlan app
Install the CrashPlan app
- In the Code42 console's Welcome to CrashPlan PROe window, click the icon of your device's operating system to begin the installer download.
- Launch the installer.
- Windows: Double-click the MSI file.
- OS X:
- Mount the DMG.
- Double-click Install CrashPlanPROe.
- Linux:
- Unpack the tgz archive.
- Navigate to the location of the unpacked files with
cd. - Execute the install.sh Bash script from the directory in which it resides. For example:
./install.sh
- Solaris:
- Move the tar.gz archive into /var/spool/pkg
- Unpack the tar.gz archive
- Install CrashPlan app package with
pkgadd. If there are multiple packages in the default spool directory, then specify the folder name of the package to be added. For example:pkgadd CrashPlanPROServer
- Follow the prompts to complete the installation.
Create your backup user account
Once install is complete, the CrashPlan app launches. You must create an account for backing up this device.
- On the New Account screen, enter the information required to create the backup account.
- Username: Must be in the form of an email address.
- Registration Key: The 16 character alpha-numeric string included on your MLK email.
- PROe Server Address: The IP address or hostname and port number of your master server. The enterprise server listens for client communication on TCP 4282.
- Click Submit to create your backup account.
Start backup
From the Backup screen, click Start Backup to begin backing up the user home directory to your enterprise server.
Next steps
After successfully installing the Code42 environment, you can now do the following:
- Configure server settings such as adding a primary network address or configuring an external mail server for sending alerts and reports
- Back up your database dumps to facilitate recovering from a master server failure
- Create an organization in which you can place users who have similar backup requirements
- Set device defaults to enforce backup policies for new devices, as well push settings to existing devices
- Add a store point to increase your available storage
- Add a destination for high availability and redundancy