Quote:
Originally Posted by eatickets My apologies, I mis-spoke: are there any solutions aside from a network-mounted backup? (i.e. an FTP solution or a Zimbra plugin that will let us save the backups off-server without forcing us to keep the backup server space connected regularly) The solution must be integrated with Zimbra in such a way that if the backup drive space is not connected, Zimbra will still function regularly and not create a new full backup just because it can't find the full backup it just moved to the remote storage space. My client doesn't want NFS or external physical drive options. |
You can rsync your backups to another location. That should fill the bill.
Another possibility would be a network backup solution. We use Retrospect because we already owned it and it is hard-link-aware, which is useful when you do backups using --noZip. See also
Ajcody-Backup-Restore-Issues - Zimbra :: Wiki
Basically you would still do your backup to the local drive, but you could set your deletion horizon to a shorter period--as short as one day if you don't care about hardlinking across full backups using --noZip. If you do this, though, you want to make damn sure that your rsync (or whatever) is copying each backup before it gets deleted. Probably the way to do this would be to take the backup deletion out of the zimbra crontab and instead call zmbackup -del as part of clean-up after shipping the backups to the remote storage.
If you want to absolutely minimize the local space used by backups over any time period, then you'll need a script that only calls zmbackup when the remote storage is available. Then, if you want, you could backup directly to the remote storage. Or you could create the backup locally and then immediately rsync (etc.) it, then delete it. (zmbackup -del 0d may or may not work; if not, you can probably get away with
rm -R /opt/zimbra/backup/sessions/* . But don't hold me to that.)