Code42 platform hardware and software requirements
Who is this article for?
Incydr, no.
CrashPlan for Enterprise, yes.
Code42 for Enterprise, yes.
CrashPlan for Small Business, no.
Overview
This article outlines the hardware and software requirements for components of your Code42 environment.
Code42 server requirements
Authority server summary
Customers not using the Code42 cloud have these Code42 server options, in brief:
Component | Small Code42 environment Up to 10,000 devices |
Medium Code42 environment 10,000 to 50,000 devices |
Large Code42 environment 50,000 or more devices |
---|---|---|---|
Operating system |
|
|
|
Authority servers |
|
|
|
Database |
|
|
|
While the Code42 server can run on a variety of operating systems and hardware configurations, Code42 provides support for only the configurations described below.
To avoid security risks, keep your operating system updated.
Contact us with questions about requirements for your Code42 environment. Review Key considerations when planning your Code42 environment for more information.
Authority server requirements
Component | Small Code42 environment Up to 10,000 devices |
Medium Code42 environment 10,000 to 50,000 devices |
Large Code42 environment 50,000 or more devices |
---|---|---|---|
Code42 platform | Latest version | Latest version | Latest version We recommend load-sharing among multiple authority servers. Contact us for information. |
Operating system |
Linux
Windows
|
Linux
|
Linux
|
Additional software |
Java
Version 7.x bundles OpenJDK 11 with the application.
For version 6.x, the Code42 installer downloads the JRE:
|
Java
Version 7.x bundles OpenJDK 11 with the application.
For version 6.x, the Code42 installer downloads the JRE:
PostgreSQL
|
Java
Version 7.x bundles OpenJDK 11 with the application.
For version 6.x, the Code42 installer downloads the JRE:
PostgreSQL
|
CPU type | 64-bit Intel processor, 8-core, E5 | 64-bit Intel processor, 8-core, E5 | 64-bit Intel processor, 8-core, E5 |
Memory |
16 GB ECC RAM |
32 GB ECC RAM |
64 GB ECC RAM |
Networking |
One or more Ethernet connections of 1 or 10 Gbps each |
One or more Ethernet connections of 1 or 10 Gbps each |
One or more Ethernet connections of 1 or 10 Gbps each |
Storage for OS and Code42 server Software |
200 GB SSD for operating system and Code42 server software
|
200 GB SSD for operating system and Code42 server software
|
200 GB SSD for operating system and Code42 server software
|
Storage for database backups | At least 500 GB for backups of the Code42 server database (stored on separate media) | At least 1 TB for backups of the Code42 server database (stored on separate media) | 2 TB for backups of the Code42 server database (stored on separate media) |
Storage server requirements
Component | Requirement |
---|---|
Code42 platform | Latest version |
Operating system |
One of the following operating systems:
|
Additional software |
Version 7.x bundles OpenJDK 11 with the application.
For version 6.x, the Code42 installer downloads the JRE:
|
CPU type |
64-bit Intel processor, 8-core, E5 |
Memory |
32 or 64 GB ECC RAM |
Networking |
One or more Ethernet connections of 1 or 10 Gbps each |
Storage for software and operating system |
200 GB SSD for operating system and Code42 server software
|
Storage for archives |
|
Code42 console requirements
End user application requirements
The system specifications listed below are the minimum requirements needed to successfully install the Code42 app.
Code42 app version 6.0 and later
Code42 app version 5.1.2 and later
Code42 app version 4.5.2 and later
Previously supported operating system versions
For previously supported operating system versions, see our article on operating system support.
Network ports
Code42 server ports
The following tables list the default Code42 server ports.
Inbound ports
In firewalls:
- 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.
Port(s) | Protocol | Source | Destination | Description |
---|---|---|---|---|
4287 (TLS) |
TCP |
|
Your authority server |
|
Your storage servers | Backup traffic from internal and external endpoints | |||
4280 (HTTP) 4285 (HTTPS) |
TCP |
|
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.
Outbound ports
In firewalls:
- 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.
Port(s) | Protocol | Source | Destination | Description |
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 | update1.code42.com |
Managed appliance and monitored authority upgrade files |
|
389 (LDAP) 636 (LDAPS) |
TCP | Your authority server | LDAP or Active Directory Server(s) | Integration with LDAP or Active Directory services |
1812 1813 |
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.
Port(s) | Protocol | Source | Destination | Description |
4283 4287 (TLS) 4288 (TLS) |
TCP |
Your Code42 server |
Your Code42 server | Data balancing between Code42 servers |
4286 (Version 7.0 and earlier) |
TCP |
Your Code42 server |
Your Code42 server | Statistics traffic between Code42 servers |
Code42 app ports
You must have port 443 or 4287 open for use by Code42 apps.
In firewalls that protect your devices and the LANs where they reside:
- Open 4287 for outbound messages to your authority server.
- If you use Code42 cloud storage, open port 443 for outbound messages to storage server.
- Open port 4244 if your firewall blocks connections from localhost to localhost to enable the Code42 app and the Code42 service to run on the same device. If the default port 4244 is in use when the Code42 app installs, the app uses some other available port. See the app.log file.
- To enable the optional web restore function, open port 4285 for outbound messages from browsers to storage servers, on-premises or in the Code42 cloud.
Port(s) | Protocol | Source | Destination | Description |
---|---|---|---|---|
4287 |
TCP | LANs |
|
Default ports for communication from the device to Code42 server(s) in on-premises environments |
443 | TCP | LANs | Code42 cloud storage | Communication from the device to storage in the Code42 cloud |
4244 | TCP | Localhost | Localhost | Default port for Code42 app connection to the Code42 service |
4285 | TCP | Browsers in LANs | Your storage server | For the optional web restore function |
Code42 cloud storage IP addresses