LogoLogo
EBR DocsHelp
Zmanda Pro
Zmanda Pro
  • Welcome to the Zmanda Pro Documentation
  • Overview and Concepts​
  • Best Practices
  • Start Here
    • Initial Security Setup
    • Step 1: Adding a User
    • Step 2: Client Download and Installation
    • Step 3: Client Login
    • Step 4: Adding a New Storage Vault
    • Step 5: Adding a New Protected Item
    • Step 6: Initiating a Backup
    • Step 7: Checking Backup Job Status
    • Step 8: Restore Data
  • Guide
    • Zmanda Pro Server Deployment (On-prem)
      • Zmanda Pro Self-Hosted Deployment
        • Self-Hosted Online Server
        • Self-Hosted Online Server Setup
        • Self-Hosted Offline Server
        • Self-Hosted Offline Server Setup
        • Storage Manager Service
        • Storage Manager Service Setup
        • Zmanda Pro Client Setup
        • Disaster Recovery Plan: Self-Hosted Server
        • Disaster Recovery Plan: Self-Hosted Server Recovery Workflow
        • Admin Password Reset
        • Custom Certificates Upload
    • Zmanda Pro Usage
    • Zmanda Pro Client Installation
      • Zmanda Pro user configuration
      • Storage configuration
    • Restarting at boot ​(Linux)
    • Protected Items
      • Files and Folders
      • MySQL
        • Xtrabackup
          • Configuration
          • Backup
          • Restore
          • Recover
        • MyDumper
          • Configuration
          • Backup
          • Restore
          • Recover
        • MySQLDump
          • Configuration
          • Backup
          • Restore
          • Recover
        • LVM
          • Configuration
          • Backup
          • Restore
          • Recover
        • Managing Data Directory Permissions with SELinux and AppArmor
        • Compatibility Matrix
      • MariaDB
        • MariaBackup
          • Configuration
          • Backup
          • Restore
          • Recover
        • MyDumper
          • Configuration
          • Backup
          • Restore
          • Recover
        • MariaDBDump
          • Configuration
          • Backup
          • Restore
          • Recover
        • LVM
          • Configuration
          • Backup
          • Restore
          • Recover
        • Managing Data Directory Permissions with SELinux and AppArmor
        • Compatibility Matrix
      • Microsoft Office 365
      • Postgres
      • Program Output
      • Microsoft Hyper-V
      • Microsoft SQL Server
      • MongoDB
      • Windows Server System State
      • Application-Aware Writer
      • Disk Image
      • VMware vSphere
        • Configuration
        • Backup
        • Restore
        • Troubleshooting
      • MariaDB
        • Backup & Restore MariaDB with a staging path
        • Backup & Restore MariaDB without a staging path using Streaming
      • Oracle RMAN
        • Configuration
        • Backup
        • Restore
        • Perform a Full Database Backup with Oracle RMAN
        • Perform a database backup using a Custom Oracle RMAN Script
        • Restore an Oracle RMAN backup using Backup Manager
        • Recover an Oracle database after restoring from Zmanda Pro Backup Manager
        • Troubleshooting Oracle RMAN backups with Backup Manager
    • Configure SSO
    • Configure & Apply Policies
    • Configure Email Reporting
    • Backup Manager
      • Login
    • Automation Tools
      • Bulk Operations with ZPAT
        • Bulk addition of policies
        • Bulk onboarding of devices
        • Bulk deletion of users
        • Bulk Rename of Devices
        • Bulk Restore
        • Bulk addition of protected items
        • Bulk administration of client devices with Ansible
      • Disaster Recovery Plan: Zmanda Pro Clients
    • Encryption & Key Management
    • Zmanda Pro Job Statuses
    • Disk Image Walkthrough
      • Create & Use Recovery Media
    • Common Problems & Solutions
    • Troubleshooting
    • VMware to Hyper-V Migration
      • Configuration
      • Backup
      • Restore to Hyper-V
Powered by GitBook
LogoLogo

Quick Links

  • Amanda Community Wiki
  • Amanda Community Downloads
  • Share Feedback

About

  • About Us
  • Customer Testimonials

Terms

  • Terms of Use
  • Privacy Policy

Contact Info

  • Denver, CO, USA
  • 888-496-2632 (US)
  • 408-732-3208 (INT)

2025 © Zmanda, A BETSOL Company

On this page
  • What is ZPAT (Zmanda Pro Automation Tool)?
  • Pre-Requisites
  • Getting Started
  • ZPAT configurations
  • Global flags

Was this helpful?

Export as PDF
  1. Guide

Automation Tools

PreviousLoginNextBulk Operations with ZPAT

Last updated 2 months ago

Was this helpful?

What is ZPAT (Zmanda Pro Automation Tool)?

ZPAT is an add-on tool for Zmanda Pro that helps automate crucial bulk operations on your Zmanda Pro Server.

Some of these bulk operations include:

  • Registering 1000s of Zmanda Pro agents at once, including creating unique backup users for each system

  • Assigning backup user policies

  • Renaming Zmanda Pro Client devices in the Zmanda Pro console

  • Adding Protected Items

  • Triggering backups and restores

  • Triggering reindexes for Storage Vaults

  • Triggering deletion of Zmanda Pro users

Pre-Requisites

  1. A running instance of the Zmanda Pro Server (can be online or offline)

    1. Admin credentials to the server are required to run ZPAT

  2. A Linux system to act as the administration host machine. It must satisfy these to run ZPAT

    1. The administration host should have connectivity with the Zmanda Pro Server

NOTE:

  • The administrator host should also be capable of resolving the domain on which the Zmanda Pro server is listening and also trust the certificates presented by the Zmanda Pro server

    • This can be done in two ways:

      • Make an A record entry in your organization’s DNS server for the FQDN (if you’ve setup a self-hosted instance you would’ve already performed this) and use your own HTTPS certificates signed by your organization’s trusted CA. If you’re using [OR]

Getting Started

ZPAT configurations

The Zmanda Pro automation tool uses CSV files to configure bulk operations.

CSV files don't naturally support comments. However, in ZPAT configuration files, you can include comments by starting a line with ‘##’ characters.

The following configuration files are available:

  1. defaults.conf

  2. onboard-devices.csv & onboard-devices-overrides.csv

  3. reindex.csv

  4. restore-for-devices.csv

  5. add-pi.csv

  6. add-policies.csv

  7. rename-devices.csv

  8. delete-users.csv

ZPAT offers an Ansible automation toolkit to remotely manage Zmanda Pro Clients' bulk installation uninstallation, and certificate updates. Alternatively, you can use your own remote management tools to administer your client devices.

The ZPAT Package

Contents

Item

Description

1

README.md

A detailed usage documentation on ZPAT and it’s available options

2

zpat binary

The Zmanda Pro Automation tool

3

config/*.csv

4

config/defaults.conf

Default parameters which are specified in each run of ZPAT server= : The Zmanda Pro Server URL on which the operations will be performed. Administrator login credentials for this server are required

storage= : The Default Storage Option used. The default value will be “<storage>”

Global flags

These flags are available for all ZPAT commands.

Flag

Description

1

--server OR -s

string

Specify the Zmanda Pro Server URL corresponding to the ZPAT operation to be run. NOTE: You will be prompted for the server URL on the first run of ZPAT and must enter the complete FQDN with a leading https://. For subsequent ZPAT operations, the server URL will be saved in the /opt/zmandapro/automations/config/defaults.conf file. Using the flag overrides whatever is present in the defaults.conf file.

2

--config OR -c

string

Specify the absolute path to a CSV configuration file for a specific ZPAT operation. Without using the flag, the base bath defaults to /opt/zmandapro/automations/config. ZPAT will look for the configurations within this directory. Using the flag will override the default value.

ZPAT doesn’t require elevated privileges (root on Linux or Administrator on Windows). However, using for Zmanda Pro devices will require appropriate privileges on the administration host. For a self-hosted Zmanda Pro deployment, the administrator host must be in the same network as the Zmanda Pro server.

Make an entry for your Zmanda Pro server’s FQDN in the /etc/hosts file of your administration host and install the ca.crt from your if you’re using the default self-signed certificates. Check out How to install certificates on Linux here.

Reach out to a to get started with your Zmanda Pro Self-hosted deployment automation with ZPAT

The bulk operations are configured in their respective CSV files. More information on each of the CSV is available in the respective

System Requirements
Ansible or other remote management tools
Zmanda Pro Setup package
Zmanda Sales Representative
bulk operations documentation