Results 1 to 7 of 7

Thread: Upgrade To 6.0.9 - Backups Crontab Borked

  1. #1
    LMStone's Avatar
    LMStone is offline Moderator
    Join Date
    Sep 2006
    Location
    477 Congress Street | Portland, ME 04101
    Posts
    1,367
    Rep Power
    10

    Default Upgrade To 6.0.9 - Backups Crontab Borked

    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:
    Code:
    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:
    Code:
    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

  2. #2
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,491
    Rep Power
    56

    Default

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

    Code:
    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
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    Saturdays is offline Advanced Member
    Join Date
    Jun 2010
    Posts
    198
    Rep Power
    5

    Default

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

  4. #4
    Klug's Avatar
    Klug is offline Moderator
    Join Date
    Mar 2006
    Location
    Beaucaire, France
    Posts
    2,316
    Rep Power
    13

    Default

    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").

  5. #5
    ewilen's Avatar
    ewilen is offline Moderator
    Join Date
    Jun 2008
    Location
    Berkeley, CA
    Posts
    1,474
    Rep Power
    9

    Default

    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.

  6. #6
    potlgd is offline Junior Member
    Join Date
    Dec 2010
    Posts
    5
    Rep Power
    4

    Default

    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

  7. #7
    LMStone's Avatar
    LMStone is offline Moderator
    Join Date
    Sep 2006
    Location
    477 Congress Street | Portland, ME 04101
    Posts
    1,367
    Rep Power
    10

    Default

    Quote Originally Posted by ewilen View Post
    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

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 3
    Last Post: 02-18-2011, 03:49 PM
  2. ZCS Upgrade to 6.0.9 and ZCO Change
    By derek.rose in forum Zimbra Connector for Outlook
    Replies: 11
    Last Post: 12-03-2010, 12:40 PM
  3. Successful upgrade from 6.0.8 to 6.0.9 on Centos 5 64bit
    By matnor in forum Zimbra Success Stories
    Replies: 7
    Last Post: 12-01-2010, 03:23 AM
  4. Upgrade Zimbra Open Source from 6.0.7.1 to 6.0.9
    By antonello74 in forum Administrators
    Replies: 5
    Last Post: 11-23-2010, 04:44 AM
  5. upgrade 3.01>4.0.2@userlimit= backups "unknown document: BackupRequest"
    By martin@coherentlogix.com in forum Installation
    Replies: 6
    Last Post: 10-04-2006, 08:41 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •