Releases: lucascbeyeler/zmbackup
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:
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 [email protected]
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 [email protected]
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 [email protected]
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 [email protected].
Release 1.2.0 BETA 5 is now LIVE
This new release fix the following bugs from BETA 4:
- Zmbackup -i wasn't working correctly with SQLITE3 because the logic behind it wasn't migrate to relational database;
- Migration is broken when check the size of the files;
- Wrong time for Alias Backup inside zmbackup.cron.
And the following features are created for this new release:
- install.sh now can delete the backup storage if you want after the uninstall;
- install.sh now show a help if you use -h or --help;
- SessionAction.sh now contains all the functions related to zmbackup -l;
- Zmbackup -r restore LDAP and Mailbox if the user don't send any other parameter;
- Zmbackup -m now migrate from TXT to SQLITE and from SQLITE to TXT;
- Including the start date and conclusion date from a backup per account;
ATENTION: This is the last release of Zmbackup 1.2.0 with the BETA tag. From this moment on we are going to only fix any bug until we consider the entire branch stable for use.
Any problem, please, create an issue and/or send an e-mail for [email protected].
Release 1.1.9 is now LIVE
This version patch is only to remove the full + incremental restore, because a lot of peoples are having issues during the execution of the restore activity. This function is already deprecated in 1.2.0 and we have no plans on bringing back.
The Full Restore now works like any other kind of restore - only restore the session and nothing more.
Any problem, please, create an issue and/or send an e-mail for [email protected].