Release 1.2.8 is now LIVE

Zmbackup:

• Log file was always empty; introduced zmlog() wrapper that writes to both syslog and $LOGFILE directly (issue #195);
• zmlog and LOGFILE were not exported to parallel subshells, causing 'command not found' errors during backup runs;
• SSL_ENABLE default was never assigned in constant(), causing HTTP to be used silently even when SSL was configured (issue #198);
• restore_main_ldap "nothing to restore" check used wrong test operator, making the skip branch unreachable (issue #199);
• mailbox_restore checked wrong variable for "No such file or directory" detection (issue #200);
• validate_config logged wrong variable name in the final missing-field error message (issue #201);
• clean_empty was swallowing its exit code and logging an empty error string (issue #202);
• Missing mbox and signature session types in list_sessions_txt (issue #203) and importsessionSQL (issue #204);
• sendmail failure was logged at info level instead of warn in notify_begin and notify_finish (issue #205);
• export readonly VAR was not enforcing readonly on variables in create_temp, sessionvars and constant (issue #206);
• Unquoted $PID variable in checkpid could cause word-splitting on paths with spaces (issue #207);
• HTTP 204 No Content response from zmmailbox was incorrectly treated as a backup error (issue #215);
• Exit code from delete_one was not being captured, masking failures in delete operations (issue #212);
• -m flag renamed to -mg for --migrate to resolve ambiguity with -m/--mail (issue #213);
• Session removal from sessions.txt made atomic using mv instead of cat-based rewrite (issue #208);
• Comprehensive unit test suite added to safeguard future changes;

Installer:

• sqlite3 added as a required dependency;
• CentOS support removed; Rocky Linux support added;
• zmbackup.cron now sets MAILTO="" to suppress unwanted crontab email notifications;

Any problem, please, create an issue.

Release 1.2.7 is now LIVE

Zmbackup:

• Failures on the script should not be hidden anymore;
• Empty zmbackup files are now treated as failed backup;
• Fixed or removed any fault sed;
• Fault LDAP string will cause the script to fail instead of attempt to rollback;
  • This bug could cause the destruction of the LDAP;
• Running as sudo would not load correctly all the .bashrc variables for the zimbra user;

Installer:

• Install script supports IPv6;

Any problem, please, create an issue.

Release 1.2.6 is now LIVE

Zmbackup:

• Dropped cURL and wget in favor of the Zimbra CLI - if your backup server is located on a different one than Zimbra mailbox this version will fail to you.

Any problem, please, create an issue.

Release 1.2.5 is now LIVE

Installer:

• New option - zmbackup can now configure the port where your Zimbra admin is running;
• Some code cleaning pointed by Pycharm;

Zmbackup:

• Dropped httpie in favor of cURL to solve the 2GB limitation issue;
• Rename black list to blocked list;
• Solved logger issue "Argument list too long" - you should now see the log correctly
• Some code cleaning pointed by Pycharm;
• Solved the problem with e-mail report not sending;

Any problem, please, create an issue.

Release 1.2.4 is now LIVE

This release is just based on the last commits - please check them for more details

Release 1.2.3 is now LIVE

This new release fix the following bugs from Release 1.2.2:

Installer:

• Install script picking the wrong hostname;
• The e-mail used by zmbackup to send reports wasn't being included in the config file during install;
• Removing some garbage characters from the IP that are broking the install script;
• Making the script create the entire structure used by the backup;
• Install.sh doesn't remove the dependencies anymore - temporary fix!

Zmbackup:

• Zmbackup not running with SQLITE3;
• The old backups aren't being removed - actually was only the most recent ones;
• Simplified the logic behind the LDAP Backup;
• Fixed the TXT to SQLITE migration;
• Fixed size reporting for individual backups;
• Zmbackup now locks the backup again for one per day - disabled by config;
• Fixed the LDAP Backup for TXT file;
• Now the --migrate create the SQLITE file, if doesn't exist;
• Fixed the permissions inside the WORKDIR for CIFS and NFS;

Thanks for @cavassin, @ananiasfilho and Thiago Castro for all the fix proposed inside the project!

Any problem, please, create an issue.

Release 1.2.1 is now LIVE

This new release fix the following bugs from Release 1.2.0:

• Issue #73 - Zmbackup -d crash if SQLITE3 options is enabled
• Issue #74 - Mail report stopped working

And the following features are created for this new release:

• Issue #59 - New Feature: Enable/Disable mail notification
• Issue #69 - New feature: backingup only active accounts
• Issue #70 - Better config file error handle
• Issue #71 - New error codes

WARNING: Please, include the options BACKUP_INACTIVE_ACCOUNTS and ENABLE_EMAIL_NOTIFY inside the zmbackup.conf if you want to use the new features. See the zmbackup.conf for more details about what they do.

Any problem, please, create an issue and/or send an e-mail for zmbackup@protonmail.com

Release 1.2.0 is now LIVE

After a long time, Zmbackup 1.2.0 is now release as stable. Compared the release RC2, this version fix the following bugs:

• Issue #63 - Zmbackup now create the username from the first domain that the command zmprov gad shows;
• Issue #67 - Zmbackup restore now works with SQLITE3
• Issue #66 - Install.sh now install httpie in CentOS 6
• Issue #68 - Install.sh now install wget and the storage is removed during uninstall process if you want;

Any problem, please, create an issue and/or send an e-mail for zmbackup@protonmail.com

Release 1.2.0 Release Candidate 2 is now LIVE

This new release fix the following bugs from Release Candidate:

• Better handling of stale PID files - by @crebelein;
• ISSUE #54 - Error: Command (--no-notice) starts with '-'. Is this a wrong option?;

And the following features are created for this new release:

• Including parallel's repository for CentOS 6;
• Fix the installer crashing if you have two or more entries for the domain in /etc/hosts

Any problem, please, create an issue and/or send an e-mail for zmbackup@protonmail.com

Release 1.2.0 Release Candidate is now LIVE

Zmbackup Release Candidate is finally here! This is the first release that can be considered a complete product, but still not stable enough to be used in production. Bellow there is a list of all the bugs fixed after the BETA 5:

• Zmbackup is deleting lock file if you run a second time - should keep until the first time is running;
• Zmbackup -r is not working if you don't inform the restore type;
• install.sh don't remove the zmbackup.cron if --remove is used;
• The message "preserve backup storage" is jumping a line;
• Asked by @saschadd: include all the backup routines inside zmbackup.cron;
• Incremental backup should be doing a full backup instead when there is no full backup;
• Migration should only run if the user change the option inside zmbackup.conf;
• Fix database lock when run a full backup;
• Incremental is not running Full backup at first;
• Mailbox don't count correctly how much accounts are backed up when try to send the e-mail;
• Reported by Germán I. Paul: Zmbackup does not execute the backup routine inside CentOS;
• Migrate should run only if Zmbackup is not running;
• Zmbackup wasn't removing all the files after a routine;
• Migration process is broke;
• Zmbackup computing wrong size in SQLITE3.

Any problem, please, create an issue and/or send an e-mail for zmbackup@protonmail.com.