Self-Hosted Online Server

About Online Server Deployments

Zmanda Pro servers deployed in environments with public internet access can reach the Zmanda Pro Licensing server for activation, automatic license count updates, and automatic license renewal.

Backup data is never sent to or from Zmanda servers.

Supported Operating Systems

  • RHEL 8 and above (including RHEL-based distros)

  • Debian 12 (Bookworm) and above (including Debian-based distros)

Prerequisites for On-Prem Zmanda Pro Server

Dependencies

Network Configuration

  1. DNS A Records For the Zmanda Pro server’s FQDNs (Fully Qualified Domain Names), create DNS A records in your organization’s DNS manager. Example: If your server is configured to listen on backup.zmanda.com, create the following DNS records:

    • <ZMANDAPRO_SERVER_IP> backup.zmanda.com

    • <ZMANDAPRO_SERVER_IP> root-backup.zmanda.com

    Purpose:

    • backup.zmanda.com: Access the dashboard and manage backups.

    • root-backup.zmanda.com: Internal use for patching and upgrades.

    If you don't have an internal DNS server, modify the /etc/hosts file on client devices to map these FQDNs to the Zmanda Pro server's IP.

  2. Additional Requirements

    • An intermediate CA certificate that is trusted by all client devices.

    • Generate an HTTPS certificate for the configured domain (e.g., backup.zmanda.com) and add root-backup.zmanda.com as a Subject Alternative Name (SAN).

  3. Required Ports

    • 443: HTTPS traffic to the Zmanda Pro server.

    • (Optional) 9001: HTTPS traffic to the StorageManager service.

    Note: Client devices must be able to reach the Zmanda Pro server.

The Zmanda Pro Server Setup Package

  1. Download the zmandasetup.zip package to your Linux system

  2. Unzip the setup package:

    unzip zmandasetup.zip

This will unpack all the configuration files required to run the Zmanda Pro server. Included files are shown below:

Zmanda Pro Server Setup Package

Package Contents

  • setup.sh: The Zmanda Pro server installer

  • setup.conf: Default configurations to run setup.sh

  • certs: Directory containing:

    • Self-signed CA certificate

    • HTTPS certificate

    • Respective keys

    • Note: It's highly recommended to use your own set of CA & HTTPS certificates

  • Dockerfile & docker-compose.yml: Docker service files for building and running the Zmanda Pro Server

  • docker-image: Contains required docker images for on-premises deployment

    • zmandapro-server-.tar will be patched for subsequent upgrades

    • Images are loaded locally, requiring no outbound requests

  • scripts: Automation scripts for client device installation

  • server.cfg: Custom Configurations for your Zmanda Pro Server

  • storagemanager.zip (OPTIONAL): The Zmanda Pro storage manager service and its dependencies

License Activator Information

What is a License Activator? Running the setup.sh script prepares your environment to start the Zmanda Pro server. However, to administer backups and perform other operations, you will need a License Activator.

Important Notes:

  • The License Activator can only activate one instance of a Zmanda Pro Server container.

  • For disaster recovery (DR) or replica server setups, please contact the Zmanda Sales Team for additional instances.

Running the License Activator The License Activator requires an unlock key, which is provided by Zmanda.

Last updated

Was this helpful?