Prepare your installation.
Verify first access.

1. Prepare the server and capacity

Verify the operating system and x86_64 architecture supported by your delivery package. The Full Master package documentation lists a starting minimum of 4 vCPU, 16 GB RAM and 20 GB free application space, excluding repository capacity. Size the deployment for workloads and concurrent jobs. Prepare a separate persistent repository mount that survives reboots.

• Finalize hostname and FQDN before installation.
• DNS and NTP must work; required APT/DNF dependencies must be available.

cat /etc/os-release
uname -m
hostnamectl
timedatectl status
df -h

2. Verify the package and manifest

Obtain the Full Master archive for your operating system and its delivery manifest through an authorized EraBackup channel. Follow the delivery signature or checksum verification procedure. Do not start installation if SHA-256 values differ from the manifest. The example assumes SHA256SUMS is in the package directory.

sha256sum -c SHA256SUMS

3. Open the terminal installer

Extract the verified archive, enter its directory and run install-tui with sudo. Replace the example archive and directory names with the exact delivered names. This procedure is for a clean server; do not run initial installation over an existing EraBackup database.

tar -xzf <FULL_MASTER_ARCHIVE>.tar.gz
cd <EXTRACTED_FULL_MASTER_DIRECTORY>
sudo ./install-tui

4. Enter Master and repository details

Select the integrations to install. Enter Master FQDN/IP, repository path and repository ID, followed by administrator details. The repository path must refer to the mounted storage. Set the initial administrator password through the hidden prompt, not command-line arguments. Correct any operating system, disk or server identity mismatch in the final summary.

5. Complete installation and check services

After reviewing the summary, start installation and keep the terminal open. The Full Master installer signals successful completion with INSTALL_OK. Then inspect the healthcheck and failed service list. Record failures and resolve their cause before rerunning the installer.

sudo /opt/erabackup/bin/erabackup-master-healthcheck
sudo systemctl --failed
sudo systemctl list-timers 'era-*' --no-pager

6. Verify TLS trust and first sign-in

Use your enterprise PKI certificate or the internal CA chain generated during installation. Certificate SANs must match the FQDN used for access. If using an internal CA, deploy its certificate to client trust stores through an approved process. Open the application over HTTPS and sign in with the delivered administrator account. Resolve CA, name or time issues rather than bypass certificate warnings.

curl --cacert /etc/erabackup/tls/ca.crt https://<ERABACKUP_FQDN>/

7. Complete licensing and the first source connection

Check license status and resource limits in the licensing screen. Add the platform connection with its API account and required permissions, then verify the inventory belongs to the intended environment. Complete OpenStack/Safir node deployment through Deploy Agent, or VMware proxy/VDDK and OpenShift components through their respective delivery procedures. Master access alone does not prove data-path readiness.