khawkins wrote: ↑Tue Mar 14, 2023 9:30 pm
BradC wrote: ↑Thu Mar 09, 2023 9:11 am
The Zextras tools (or the -ng extensions) enabled the commonly promoted "side by side" migration. I've spent a few hours having a look at v10 today and it appears it's back to the old clunky zimbra backup, which is not real time and only good for DR if you make frequent local copies of the redo logs. So that's a significant regression on the -ng backup along with making migrations more difficult.
Other than that it appears mostly much of a muchness and it'll be interesting to watch how it evolves. Hopefully competition from Zextras has lit a bit of fire under the Zimbra team.
Thanks for pointing this out, I'm so disappointed to hear this. Ngbackup was the one solidly good thing (to me) that came from upgrading to 8.8.15...
There are some intentional differences in the backup and restore in Zimbra Daffodil. The release of Daffodil allows the Zimbra Product and Development team to address a number of issues that NG modules prevented us from doing. We are committed to providing industry-leading features which will give us the flexibility to adapt to current and future industry changes.
In making the decision to go a different direction, discussions occurred with customers to obtain how they are using backup and their positive and negative experiences. This decision doesn’t mean we believe that NG real-time backup isn't a working solution but we feel that a better solution can be created which will be more adaptable, flexible, and resolves a number of issues that NG can not address. Here are some common issues reported by customers and from Support data:
- NG requires a full mailbox restore for all mailbox corruption. The most common issue is corruption within the MySQL databases or OS where the Store was not affected. The majority of customers who experienced this type of issue requested the ability to restore at the component level. Daffodil backup brings back flexibility with what type of data you want to restore including blob-less restore.
- The ability to scale backup is another issue that is reported and seen within our Support data. More accounts and data on the mailbox server increases the likelihood to have NG backup performance issues. Because NG is an add-on, it competes for the same resources as mailboxd and MySQL, where NG real-time backup can negatively affect user experience.
- From our support data and customer experiences, we are seeing a correlation between an increase in the age of a real-time backup to unknown issues during restoration. These issues can prevent a full restore which requires an alternative restore method and data loss.
Time to restore
- If a disaster occurs, NG backup is able to restore when accounts are live, but many restores take significant time, Restore can affect the performance of the server, and end users still notice and complain about missing data and user experience.
We continue to review how the Zimbra backup feature is used and how we can further develop this feature. Taking a new perspective on the Zimbra backup functionality, we are able to address a number of issues and improvements in the overall Backup and Recovery experience. In the coming months, we will be releasing enhancements to the backup and other features which will address the footprint of the backup, speed of restoration, backup message management, cluster to cluster migration. We will continue to keep everyone informed as new functionality becomes available.
We always want to hear from the community about how you use Zimbra, what issues you have, and your needs.