zar 2.0.8
Overview
Zeroincombenze® Archive Replica
ZAR stand for Zeroincombenze® Archive Replica. It is a tool kit to backup, restore, replicate files and/or database.
ZAR manages easily backup for Odoo database, keeps last nth copies and purges oldest copies.
Features
backup and restore odoo database
backup and restore based on rules by configuration file
restore database with automatic actions disabled
multiple copies of database by configuration file
automatic purging of oldest copies
configuration based on host name: it works on duplicate host image too
backup on same host or on remote host
Usage
zar should be execute by postgres user
Execute zar_upd to install and configure. Configuration file is zar.conf Execute zar_bck to do backup or restore, based on host role Execute zar_rest to do restore
To execute in cron, use zar_bck -k
There are avaiable two postgresql facilities:
pg_db_active
pg_db_reassign owner
pg_db_active show and kill postgres session. It can kill oldest session out of pool.
pg_db_reassign_owner can reassign owner to database. It reassign the ownership of all objects.
Getting started
Prerequisites
Zeroincombenze(R) tools requires:
Linux Centos 7/8 or Debian 9/10/11 or Ubuntu 16/18/20/22/24
python 2.7+, some tools require python 3.7+, best python 3.9+
bash 5.0+
Installation
For stable version:
pip install zar
For current version:
cd $HOME git@github.com:zeroincombenze/tools.git cd $HOME/tools ./install_tools.sh
Upgrade
Stable version via Python Package
pip install --upgrade zar
Current version via Git
cd ./tools ./install_tools.sh -pUT source $HOME/devel/activate_tools
ChangeLog History
2.0.8 (2025-04-27)
[FIX] Compress tar w/o filestore
[IMP] python 3.11 is certificated programming language
2.0.7 (2024-12-30)
[IMP] pg_db_active with port for postgresql multi-version
2.0.6 (2024-08-21)
[IMP] pg_db_active with port for postgresql multi-version
2.0.5 (2024-05-22)
[FIX] zar_upd
2.0.4 (2023-09-08)
[IMP] Backup filestore
[FIX] Remote copy to /dev/null
2.0.3 (2023-09-06)
[FIX] DB name with hyphen (-)
2.0.2 (2023-05-14)
[IMP] reassing_owner accept db_port
2.0.1 (2023-02-25)
[IMP] Remote bckdir different from local
2.0.0 (2022-10-20)
[IMP] Stable version
Credits
Copyright
SHS-AV s.r.l. <https://www.shs-av.com/>
Contributors
Metadata
Release files for zar 2.0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zar-2.0.8.tar.gz | 57.3 kB | Without provenance | Details for zar-2.0.8.tar.gz |
Release files / zar-2.0.8.tar.gz
| Download URL | zar-2.0.8.tar.gz |
|---|---|
| Size | 57.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d1d30574128120175ddfa9485c51f862310c90e13abf5be3fe514662a4852e8
|
|
BLAKE2b-256 checksum How to use checksums |
c40238044c825e1136346c8bf40a65e548b0fa731e0a8118c601ddb0348bbcd3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.13
|
Security for zar 2.0.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.