Zimbra 10.1.16 Released - Please Post Your Patch/Upgrade Results Here

[adrian.gibanel.btactic]

So... you have a VPS installed with Zimbra NE 10.1.15 with Backup v1, the traditional NE backup that you have setup ages ago.

After upgrading your Zimbra NE 10.1.15 installation (with scheduled and enabled Backup v1) to Zimbra NE 10.1.16...
Does backup change from Backup v1 to Backup v2?

After reading the Transitioning Scheduler Configuration in the Admin Guide which it's hinted at the 10.1.16 release notes:

Scheduler transition steps for adopting the V2 Backup Engine are documented in Transitioning Scheduler Configuration for Backup Engine v2.

I concluded that the Backup v1 was kept as-is and that you had to do extra steps for enabling v2.

The problem that I have right now is that the 10.1.16 release notes wiki page has been updated to add this explanation:

After upgrading to 10.1.16, the Backup feature will default to V2. If you prefer to continue using V1 (legacy backup), set zimbraBackupDeduplication to nodedupe and restart the mailstore service immediately after completing the upgrade.

which implies to me the opposite, that you won't be working with Backup v1 if you upgrade from 10.1.15 to 10.1.16.

I think something along the lines of:

Since 10.1.16, the Backup feature will default to V2 in new installations. If you prefer to continue using V1 (legacy backup), set zimbraBackupDeduplication to nodedupe and restart the mailstore service immediately after completing the upgrade.

would avoid some mis-understanding.

Can anyone from Synacor clarify (and update the wiki page if applies) ?

Thank you!

[andrey.ivanov]

For me the documentation is quite clear - V2 backup is on by default and it works if there are no "legacy" switches in "zmschedulebackup -q" (legacy are "--zip" and similar). If there are legacy switches - it continues as V1. Once you eliminate legacy switches in scheduler - next backup cycle uses V2.

It is a classic deduplication problem - if the data is zipped you cannot deduplicate it.

[L. Mark Stone]

Upgrade our multi-server hosting farm last night; mix of Rocky 8, 9 and Ubuntu 20 servers with no problem.

Users report no issues (so far).

Two things I noticed:

First, we are seeing interesting cookie errors in ~/log/zmmailboxd.out:

Code: Select all

Feb 06, 2026 3:26:51 PM org.apache.http.client.protocol.ResponseProcessCookies processCookies
WARNING: Invalid cookie header: "Set-Cookie: ClientId=; expires=Thu, 01 Jan 1970 00:00:00 GMT; path=/". Invalid 'expires' attribute: Thu, 01 Jan 1970 00:00:00 GMT
Feb 06, 2026 3:26:51 PM org.apache.http.client.protocol.ResponseProcessCookies processCookies
WARNING: Invalid cookie header: "Set-Cookie: ClientId=704DA6D175CA4587A6621135358C4A72; expires=Sat, 06 Feb 2027 15:26:51 GMT; path=/; secure; samesite=none". Invalid 'expires' attribute: Sat, 06 Feb 2027 15:26:51 GMT

Second, We have two identical Proxy/MTA servers; identical except that one has LDS and ZURT installed and the other does not. The one with LDS and ZURT did not get fully updated. Running like dnf clean metadata && dnf check-update still showed no newer packages to install. I've opened a Support Case and will report back.

Hope that helps,
Mark

[oetiker]

I did upgrade on Ubuntu 22.04 System
Zimbra 10.1.16_GA_4863 (build 20260203175501)

No issue so far except the PDF preview is still not available on the web client. Is there a setting to activate that?

[ghen]

Mark,

There were no actual changes for proxy, MTA and LDS components, only a zimbra-*-patch version bump and a zmfixperms update for Ubuntu 24 support (on all components).

[L. Mark Stone]

We have two identical Proxy/MTA servers; identical except that one has LDS and ZURT installed and the other does not. The one with LDS and ZURT did not get fully updated. Running like dnf clean metadata && dnf check-update still showed no newer packages to install. I've opened a Support Case and will report back.

This turned out to be a repo issue on the impacted server. The file /etc/yum.repos.d/zimbra.repo was missing several entries. I've asked Support if they have seen this before. Added the missing entries and completed the upgrade no problem.

Hope that helps,
Mark

[thomas.klaube]

Hi all,

after updating to 10.1.16 zmbackup seems broken:

Code: Select all

[zimbra@server]$ /opt/zimbra/bin/zmbackup -f -a all                                  
Error occurred: Cannot invoke "String.equals(Object)" because the return value of "com.zimbra.cs.account.Server.getAttr(String)" is null

No matter how I try to reconfigure the backup schedule, this error persists (--zip, --zipStore, --noZIp, --zstd, --csd, --csds, standard or autogrouped backup, everything yields the same error message). I even tried removing the old backups or to only backup one account -> no luck....

Any hints?

Regards
Thomas

[adrian.gibanel.btactic]

Hi all,

after updating to 10.1.16 zmbackup seems broken:

Code: Select all

[zimbra@server]$ /opt/zimbra/bin/zmbackup -f -a all                                  
Error occurred: Cannot invoke "String.equals(Object)" because the return value of "com.zimbra.cs.account.Server.getAttr(String)" is null

I wonder if your problem is somehow related to ZBUG-4620: Fix login issue by resolving domain on backend using serverName commit. Probably not.

If it's related the solution would be that the server is properly resolvable from itself.

---

In any case I would for-loop the backup manually one account at a time. (You know using an account after -a instead of all. It might be that some of your accounts don't have a proper server assigned to them and that's what cause the error.

Maybe the old backup system just skipped them and the new one someone takes them into account when it shouldn't.

Update: I see you already tried to backup only one account.

---

Also... Have you checked /opt/zimbra/log/mailbox.log when that happens to see if there's more detailed debug information there of the error?

[adrian.gibanel.btactic]

Hi all,

after updating to 10.1.16 zmbackup seems broken:

Code: Select all

[zimbra@server]$ /opt/zimbra/bin/zmbackup -f -a all                                  
Error occurred: Cannot invoke "String.equals(Object)" because the return value of "com.zimbra.cs.account.Server.getAttr(String)" is null

For the record when upgrading from ZCS NE 10.1.15 to ZCS NE 10.1.16 this didn't happen to us. The backup with the v1 configuration was done properly.

[thomas.klaube]

Hi Adrian,

If it's related the solution would be that the server is properly resolvable from itself.

Also... Have you checked /opt/zimbra/log/mailbox.log when that happens to see if there's more detailed debug information there of the error?

The server is perfectly resolvable from itself. However, it is a dual stacked VM. So there are ipv4 + ipv6 addresses configured on the network interface but Zimbra is configured to run on ipv4 only (zimbraIPMode: ipv4). Maybe this is some kind of an issue?!? After updating to 10.1.16 zimbra adminUI started complaining about missing [::1] ipv6 loopback entries in the postfix mynetworks section which it never did before (the server is running zimbra for >10 years).

There are no debug information in mailbox.log _at all_. Not even a hint that zmbackup was invoked...

Thanx and regards
Thomas