Refer to the Quick Start Guide for basic installation steps.
Customize Zelta's behavior by setting environment variables in zelta.env. For example:
AWK="/usr/bin/gawk"ZELTA_SNAP_NAME="date +%Y-%m-%d_%H-%M-%S"For detailed SSH setup instructions, refer to /conf/ssh.
Guide to setting up non-root replication with zfs allow, referencing /conf/zfs-allow.
Example setups for users "space" and "twin" using separate Zelta versions and configurations:
$HOME/bin to the PATH and utilizing local user directories for .env and .conf.In this example:
BACKUP_ROOT: hottub/Backups sets the default location where backups are stored. We enable 2 auto-retry attempts and 3 threads, which will replicate all 3 sites simultaneously.dallas, megacity, scranton) organize hosts into groups for multithreading (or just help organize the configuration).server01.itech, server01.metacortex) identify source machines.BACKUP_ROOT: hottub/Backups
RETRY: 2
THREADS: 3
# Site names are for organization and multithreading
dallas:
# Each target hostname is indented
server01.initech:
# The final dataset element will be replicated to BACKUP_ROOT
- pool01/system_logs # Replicates to "hottub/Backups/system_logs"
- pool01/user_data
server02.initech:
# Choose a destination with this syntax (ssh "user@host:" is allowed)
- pool02/web_assets: hottub/web_assets
megacity:
server01.metacortex:
- sink01/agent_files
- sink01/neo_backups: hottub/Neo
scranton:
server01.dndrmfln:
- tank01/accounting_db
- tank01/marketing: design@mkthost3:pool03/material_archives
server02.dndrmfln:
- tank01/sales_reports
- tank01/hr_records
Community and Support:
Professional Collaboration:
Engage with Zelta designers and integrators at Bell Tower.