backupacct — Command Reference
Create an Eenos hosting-account backup with selectable archive format and component exclusions.
Create an Eenos hosting-account backup with selectable archive format and component exclusions.
Requirements
Run as root on the Eenos server. An existing hosting account, destination storage with enough space and inodes, and the database/backup utilities required for the included services. Coordinate application writes for a consistent backup.
Usage
The following example uses the operation described below; replace example identities and paths before use:
/usr/local/eenos/scripts/backupacct exampleuser --workdir /backup --logArguments and options
| Argument / option | Usage and meaning |
|---|---|
user | Positional argument. Eenos user name to backup |
--workdir | Value: WORKDIR. The directory to put the package |
--compressed | Flag. Compress backup into gzipped tar file (tar.gz) |
--archived | Flag. Archive backup into tar file (.tar) |
--nocompress | Flag. Neither compressed nor archived backup |
--skiphomedir | Flag. Exclude home directory backup |
--skipmysql | Flag. Exclude MySQL database backups |
--skippgsql | Flag. Exclude PgSQL database backups |
--skipmongodb | Flag. Skip Mongodb database backups |
--skipmailman | Flag. Exclude Mailman3 mailing list backups |
--skipemail | Flag. Exclude email accounts |
--skipbwdata | Flag. Exclude bandwidth usage |
--skipdiskusage | Flag. Exclude disk usage |
--skippublichtml | Flag. Exclude public_html folder |
--log | Flag. Enable unique backup log |
-h, --help displays this parser's help. Selectors in the same mutually exclusive group cannot be combined. The installed version remains authoritative for available options.
Operational effects
Reads account content and creates backup data. Compression is enabled by default when no format flag is selected. Choose only one of --compressed, --archived and --nocompress. Skipped components are absent from the backup.
Verify the result
Inspect /var/log/backup/backupacct.log or the unique log reported with --log, check the generated backup and test a restore independently.
Check operation output and the relevant service/application state. Several legacy wrappers exit successfully after logging a handler failure, so a zero shell exit status alone is not proof of completion.