Upgrade To 6.0.9 - Backups Crontab Borked

[LMStone]

We just upgraded our hosting farm from 6.0.8+P3 to 6.0.9 and noticed that the crontabs for running backups were borked by the upgrade.

Originally we had:

zimbra@viognier:~> crontab -l | grep backup
0 1 * * 6 /opt/zimbra/bin/zmbackup -f --noZip --includeHsmBlobs -a all 
0 1 * * 0-5 /opt/zimbra/bin/zmbackup -i --noZip --includeHsmBlobs
0 0 * * * /opt/zimbra/bin/zmbackup -del 12d
zimbra@viognier:~>

But after the backup we only had:

zimbra@viognier:~> crontab -l | grep backup
0 0 * * * /opt/zimbra/bin/zmbackup -del 12d
zimbra@viognier:~>

Anyone else see this before I file a bug report?

Other than that (and the known log rotate issue), no problems we see so far.

Hope that helps,
Mark

[phoenix]

There's no change in the crontab for my single server after the upgrade:

0 1 * * 6 /opt/zimbra/bin/zmbackup -f   -a all 
0 1 * * 0-5 /opt/zimbra/bin/zmbackup -i  
0 0 * * * /opt/zimbra/bin/zmbackup -del 1m

[Saturdays]

Yeah, there is no change in my crontab too.... after the upgrade....

[Klug]

Same changes on all my crontabs, all my customers' crontabs and friends' crontab 8)
We're all using "--noZip", that's why...

The install scripts make a copy of the backup part of the crontab (normal) in order to recreate the crontab the way it was after the upgrade.

The problem: while the scripts make a "stupid" copy (using crontab -l), they use the ZCS tool to create the crontab (zmschedulebackup iirc).

This tool is not able to handle "--noZip" on its command line.

So the two full and incremental lines get "deleted" because the tool is not able to deal with the additional parameter.

I did not open (nor look for) a bug, because I'm used to modify the crontab after each upgrade (in order to add "--noZip").

[ewilen]

Yes, easiest thing after install is to do zmschedulebackup -D to set up the default within crontab. Then use crontab -e to edit and restore your custom configurations.

--includeHsmBlobs is probably also going to mess up the crontab on upgrade, as you might guess.

[potlgd]

I had a similar problem when I upgraded from 5.0.15 to 6.0.8. Here is the bug report if you want to vote for it.

Bug 50584 - zmsetup upgrade does not properly handle zmbackup zipStore option

Chris

[LMStone]

Originally Posted by ewilen

Yes, easiest thing after install is to do zmschedulebackup -D to set up the default within crontab. Then use crontab -e to edit and restore your custom configurations.

--includeHsmBlobs is probably also going to mess up the crontab on upgrade, as you might guess.

With this upgrade we started to do a crontab -l and direct the output to a backup file before the upgrade, and then do the same after the upgrade to a different file, and lastly run a diff across the two files to see what Zimbra has changed.

It's not just the backup schedule changing as part of the upgrade that we like to check!

All the best,
Mark