Skip to main content

Who is this article for?
Find your product plan in the Code42 console on the Account menu.

Incydr Professional and Enterprise
Incydr Basic and Advanced
Other product plans

Incydr Professional and Enterprise, no.

Incydr Basic and Advanced, no.

CrashPlan Cloud, no.

Other product plans, yes.

CrashPlan for Small Business, no.

This article applies to on-premises authority servers.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Monitored private authorities

Who is this article for?
Find your product plan in the Code42 console on the Account menu.

Incydr Professional and Enterprise
Incydr Basic and Advanced
Other product plans

Incydr Professional and Enterprise, no.

Incydr Basic and Advanced, no.

CrashPlan Cloud, no.

Other product plans, yes.

CrashPlan for Small Business, no.

This article applies to on-premises authority servers.

Other available versions:

Cloud

Overview

A Code42 monitored private authority is Code42 authority server software running on hardware or a virtual server provided and owned by the customer, but monitored and managed by Code42. This arrangement provides you, the customer, with maximum security and minimum responsibility. This guide describes the requirements for the system or virtual server that you need to provide to Code42.

Before you begin

Before studying details of what to provide for a monitored private authority, it helps to understand the context. For a monitored private authority:

  • You own and maintain the hardware and virtual environment, or cloud instance, where the Code42 authority server runs.
  • Code42 owns and maintains the operating system, authority server software, and related applications.
  • You manage and administer your organizations, users, and devices via the authority server's Code42 console.

What you provide

  • Hardware and virtual environment, or cloud instance, running a standard Ubuntu 16.04 operating system.
  • IP addresses, domain names, and other network details.
  • Code42's access to the environment.

What Code42 does

  • Tests and verifies the hardware and virtual environment, or cloud instance.
  • Intalls a CloudOS operating system.
  • Installs Code42 monitoring and management tools.
  • Installs and configures Code42 authority server software.
  • Monitors performance and reliability of your Code42 environment.

What Code42 monitors

Code42 monitors your authority server regarding details like the following, and resolves any issues that arise:

  • Code42 server service status
  • Code42 server version and update availability
  • Out of memory alerts
  • Low disk space alerts
  • Out of disk space alerts
  • Database health
  • Web Code42 console response

System requirements

In order for Code42 to create a monitored private authority server, you need to provide the hardware and virtual environment, or a cloud instance, that meets the following specifications:

  • Ubuntu 16.04 operating system
    • 64-bit
    • SysVinit package
  • 64-bit Intel processor
  • 8-core, E5 CPU
  • ECC RAM sufficient to serve the expected number of user devices:
    • 16 GB for up to 10,000 devices
    • 32 GB for 10,000 to 50,000 devices
    • 64 GB for 50,000 or more devices
  • Ethernet connections at least 1 Gbps
  • 200 GB SSD storage for operating system and Code42 software
    • RAID1, RAID10, or RAID6
    • performance optimized
  • Storage on separate media for backing up the Code42 database
    • 500 GB for up to 10,000 devices
    • 1 TB for 10,000 to 50,000 devices
    • 2 TB for 50,000 or more devices

Network information

In order for Code42 to create a monitored private authority server, you need to provide the following network information for the hardware and virtual environment, or cloud instance:

  • Hostname (for example, myhost.example.com)
  • Host (for example, myhost)
  • IP Address for ETH0 (for example, 192.0.2.10)
  • Netmask for ETH0 (for example, 255.255.255.0)
  • Gateway Address (for example, 192.0.2.1)
  • DNS Server(s) (for example, 192.0.2.100)
  • DNS Search domain(s) (for example, example.com)
  • NTP Network Time Server (for example, time.example.com)
  • Email Server (for example, mail.example.com)
  • Region/Timezone (for example, “America/Chicago” or “Asia/Singapore”)

For more information

For details about creating a monitored private authority server, contact either:

For details about troubleshooting an authority server:

  • Was this article helpful?