Who is this article for?
CrashPlan for Enterprise, yes.
Code42 for Enterprise, yes.
CrashPlan for Small Business, no.
This article applies to on-premises authority servers.
The Code42 managed appliance and Managed Private Cloud (MPC) are fully-managed systems that require minimal maintenance. This guide is intended to assist you in unboxing, installing, configuring, and maintaining your M1 or S2 managed appliance or Managed Private Cloud.
Set up your Managed Private Cloud
When you receive your managed appliance, open the boxes and verify the contents of the shipment. Each managed appliance shipment contains the following:
- Managed appliance
- Rack mount rail kit
- Power cords (4)
- Hard drives
Hard drives are pre-mounted in hot swap carriers and installed within the managed appliance.
- Cable management arm kit
- Product information guide
Prepare these physical requirements for your Managed Private Cloud:
- Dual 110-240V power sources (standard power cables are included)
The managed appliance requires a maximum of 750W.
- 1-2 U rack space per managed appliance
Reserve additional space under the managed appliance if you plan to expand.
- 2 Ethernet connections
- Monitor and keyboard for initial setup
Step 1: Install the rack mount
- Unbox and inspect the rack mount rail kit.
- Rack the chassis using the instructions included in the kit.
Due to the physical size and weight of the managed appliance, we recommend that two people work together to place your managed appliance in your server rack.
Step 2: Install the hardware
- Plug in keyboard (USB) and monitor (VGA) for initial setup.
- Plug in Ethernet cable to the iDRAC port.
- Plug in Ethernet cable to the eth3 port.
- Plug in power cords to each power supply.
- Power on the managed appliance.
Verify power supply and drive status
Check the power supply indicator lights to verify that each drive is working properly. Each drive carrier in the managed appliance has two LEDs: an activity LED (green) and a status LED (bicolor, green/amber). The activity LED flashes whenever the drive is accessed. The status LED reveals the status of each individual drive.
For more information on LED status, refer to our LED Indicator Guide.
Configure your Managed Private Cloud
Gather network information
Gather the following network configuration information before you begin installation:
|IP address for ETH0||192.0.2.10|
|Subnet mask for ETH0||255.255.255.0|
|IPMI IP address||192.0.2.11|
|IPMI subnet mask||255.255.255.0|
|DNS search domain(s)||example.com|
- The Intelligent Platform Management Interface (IPMI) is a set of computer interface specifications that allow remote management and monitoring of a system's hardware and operating system.
- iDRAC is the IPMI interface used by your M1 and S2 managed appliance.
- To decrease risk of intrusion, this interface should be configured on its own out-of-band network. If you have questions, contact our Customer Champions for support.
Configure your firewall
Prepare the following firewall rules on your network before the managed appliance installation. We have divided these firewall rules between your managed appliance, Monitoring, and Cloud Storage rules.
Code42 server network ports
The following tables list the default Code42 server ports.
- Open port 4287 for inbound requests from Code42 apps.
- Open port 4285 for inbound requests from browsers and from Code42 apps version 6.5 and later.
- Open 4280 only in the rare case where your server does not use TLS security.
You can use port forwarding, also called port mapping, to avoid port conflicts and port restrictions within your Code42 environment and on other networks.
Your authority server
|Your storage servers||Backup traffic from internal and external endpoints|
||Your authority server and storage servers||
Inbound IP addresses
For best results, we recommend that you allow inbound requests to your Code42 authority server from all the Code42 cloud storage IP addresses.
- Open ports 25, 53, 123, and 443 to let your Code42 servers send requests to mail, DNS, NTP (Network Time Protocol) servers, and the Code42 license server.
- Open an LDAP or RADIUS port only if you use one of those services.
- Open port 5432 only for a server that uses a PostgreSQL database.
- Open 5432 if PostgreSQL resides at an IP address other than the server's address,
- Or open 5432 if PostgreSQL and your server share the same address, but your firewall otherwise blocks connections to localhost.
For specific Code42 IP addresses, contact our Customer Champions for support.
|25||TCP||Your Code42 server||Mail Server(s)||SMTP services|
|53||UDP||Your Code42 server||DNS Server(s)||DNS services|
|123||UDP||Your Code42 server||NTP Server(s)||NTP services|
|443||TCP||Your Code42 server||
Code42 product license/subscription service
|TCP||Your Code42 server||
Managed appliance and monitored authority upgrade files
|TCP||Your authority server||LDAP or Active Directory Server(s)||Integration with LDAP or Active Directory services|
|UDP||Your Code42 server||RADIUS Server(s)||RADIUS services|
|5432||TCP||Your Code42 server||PostgreSQL||Database service|
Multi-server deployment ports
If you use multiple Code42 servers, most likely one authority server and one or more storage servers, then in the firewall that protects each server:
- Open 4283 only in the rare cases where your servers do not use TLS security.
- Open port 4287 and 4288, both inbound and outbound, for server-to-server communications using TLS security.
- (Version 7.0 and earlier) Open port 4286, both inbound and outbound, also for server-to-server communications.
Your Code42 server
|Your Code42 server||Data balancing between Code42 servers|
(Version 7.0 and earlier)
Your Code42 server
|Your Code42 server||Statistics traffic between Code42 servers|
In order to allow Code42 to monitor your managed appliance, you need to configure your network to allow communication from Code42.
Only apply firewall rules for monitoring if you use Code42's managed appliance monitoring.
For specific IPs, contact our Customer Champions for support.
|TCP||Your Code42 server||
Code42 Monitoring Address
|Remote monitoring (Zabbix)|
Code42 Remote Access IP
|Your Code42 server||Remote SSH access from Code42 offices|
Code42 Remote Access IP
|Your Code42 server||Remote console access from Code42 offices|
Code42 Remote Access IP
|Your authority server's IPMI Interface||Remote IPMI access from Code42 offices|
|623||TCP||Your authority server's IPMI Interface||
Code42 Remote Access IP
|Remote IPMI access from Code42 offices|
Cloud storage ports
Configure your managed appliance
When you power-on the managed appliance and the operating system loads, the main command-line interface (CLI) console opens. Type
set and press Tab twice to display all available
set commands. Use the following
set commands for initial system setup.
Set the time zone
set-tz to set the local time zone for your managed appliance
If the clock on your managed appliance is incorrect, use
ntpdate to retrieve the correct time from the configured NTP server.
Configure iDRAC (IPMI)
The iDRAC (IPMI) Remote Management console enables remote web administration of the managed appliance. The iDRAC IPMI uses a dedicated network device and has its own network configuration. Use
set-ipmi to configure the iDRAC for your managed appliance.
|How should the IPMI get its address?||dhcp|
|IP for IPMI interface||192.0.2.11|
|Subnet mask for IPMI interface||255.255.255.0|
|Gateway for IPMI interface||192.0.2.1|
|Should the IPMI interface be restarted after networking changes?||yes|
Configure the primary network interface
The primary network interface contains the hostname, IP address and other network settings that the managed appliance will use to communicate across your network. Use
set-net to configure the primary network interface for your managed appliance.
|Enter the desired hostname (or leave blank)||server1.example.com|
|Please enter an NTP server hostname/IP||ntp.crashplanpro.com|
|Please enter DNS server(s) separated with commas||192.0.2.100, 192.0.2.101|
|Enter the domain name (or leave blank)||example.com|
|Please enter IPv4 address for eth0||192.0.2.10|
|Please enter IPv4 subnet mask for eth0||255.255.255.0|
|Please enter the WAN gateway address for eth0||192.0.2.1|
|Would you like to continue with these settings?||
Once the primary network interface has been configured, run the
restart-networking command to apply the settings.
Test iDRAC (IPMI) settings
show-all at the command prompt to view all current network settings. You can also view only the IPMI settings with
Open a browser and navigate to the IPMI IP address. If properly configured, you should see the following screen:
Maintain your managed appliance
Monitor for issues
Code42 highly recommends using our managed appliance monitoring, which allows Code42 to configure your managed appliance for maximum performance and reliability. Code42 proactively monitors for potential issues in order to prevent them, and quickly assist you in resolving any problems that may arise.
Code42 monitors these status elements and problem indicators, as well as others:
- Code42 server service status
- Code42 server version and update availability
- Power supply failures
- Drive failures
- Out of memory alerts
- Low disk space alerts
- Out of disk space alerts
- RAID array health
- Database health
- Web Code42 console responsiveness
For more information on Code42's managed appliance monitoring service, contact our Customer Champions for support.
Review managed appliance logs
You can view the managed appliance logs through the Code42 console from Server > Settings > System logs: View.
From the server log view, a drop-down menu lets you choose the log file you wish to view.
|com.backup42.app.log.X (0 is the newest log)||Primary repository of events, errors, and data. Check this log first for any exceptions.|
|request-[date].log||Lists all of the web requests made to the internal web server.|
|history.log.X (0 is the newest log)||Lists system alerts and general events that have occurred on the server.|
Contact support at Code42
Command line reference
Press TAB twice to display all available commands.
|apt-retrieve-credentials||Retrieve credentials and set up via code42.cfg|
|apt-submit-credentials ||Generate a unique password and upload credentials|
|clear||Clear the command screen*|
|date||Display the current date and time*|
|df||Display available disk space on the filesystem*|
|factory-defaults||Completely removes the contents of the code42.cfg|
|firewall on||Enable iptables firewall rules set within /etc/iptables/rules.v4|
|firewall off||Disable iptables firewall rules set within /etc/iptables/rules.v4|
|free||Display total free and used physical and swap memory, and buffers used by the kernel*|
|history||Display the recent commands executed*|
|hostname||Display the system's hostname*|
|iostat||Displays the current CPU load average and disk I/O utilization, providing a great way to monitor your disk I/O usage*|
|ipmi-factory-defaults||Reset IPMI settings to factory defaults|
|ipmi-password||Set an IPMI password|
|ipmi-reload||Re-issues IP/DHCP/networking configuration commands from the code42.cfg to the IPMI|
|ipmi-reset||Reboots the IPMI interface|
|Configure the IPMI network settings|
|last-known-good||Reverts to a previously set known good configuration|
|lsicmd||Display drive status|
|netstat||Print information about the Linux networking subsystem*|
|ntpdate||Set the local date and time by polling the Network Time Protocol (NTP) given as the server arguments to determine the correct time*|
|ping||Use to check that there is a network communication to another computer*|
|poweroff||Shut down the appliance*|
|ps||Give a snapshot of the current processes*|
|reboot||Reboot the system*|
|restart-networking||Restarts networking, applying network changes|
|set-ipmi||Configure the IPMI network settings|
|set-monitoring||Configure the server to contact for monitoring|
|set-net||Run the network configuration wizard|
|set-tz||Run the time zone configuration wizard|
|show-all||Display all configuration settings|
|show-ipmi||Display all IPMI devices|
|show-net||Display network configuration settings|
|show-raid||Display virtual drive info|
|show-serial||Display the serial number of the managed appliance|
|show-version||Display appliance, CLI, and Pepper version numbers|
|silencealarm||Silence any audible alarms, such as a failed drive alarm|
|tcpdump||Analyzes TCP/IP and other packets transmitted or received by a network*|
|top||Display the top CPU processes*|
|traceroute||Print the route that packets take to the network host*|
|uptime||Display how long the system has been running*|
|w||Displays the users currently logged in, and lists their running processes*|
* - indicates this command is a native Linux command. For full information on Linux commands, please view the command's man page. Note that man pages are not installed on the managed appliance operating system.