So I've looked at the admin guide, and perused the forums, and this information seems to be lacking...
How do I get backups to tape so that when my entire office melts down life will still go on?
Currently I send /opt/zimbra/backup to tape. Is this what I need? Anything else?
please provide more info on what Zimbra version you are using OSS or Network..
if you have OSS version follow the following link and backup the DATA either on network or on your TAPE.
Open Source Edition Backup Procedure - Zimbra :: Wiki
Network edition, 175 users, about 600 gigs of data, 1 server...
Short version: Good, all you really need to do is backup the contents of /opt/zimbra/backup
Originally Posted by Nutz
But now that we know your NE Don't forget to update your profile
NE restore methods are on this page, your probably interested in the bottom sections: /docs/ne/latest/administration_guide/10_Backup_Restore.13.1.html
I also always store the installer for the version that I'm on with it my backups as well.
You should always have a full, as incremental without are kind of useless.
Simply, move/copy/rsync the backups to your tape drive.
Alternatively you could change your backup path to go directly to tape:
You can change the backup target for one backup by using zmbackup -t
CLI - zmbackup Network Edition Only - Zimbra :: Wiki
Set it more permanently through the admin console gui > global settings> backup tab
As of 4.5.6 you can easily set:
OR zmprov mcf zimbraBackupTarget /location
(check current with zmprov gacf | grep zimbraBackupTarget)
* Do be aware of the now fixed Bug 21753 - ldap backup not kept with rest of backup
Which is why most still create a symlink /opt/zimbra/backup> /mnt/backup symlink anyways even after changing the default backup target. Plus, this was the old method anyway.
Of course you need to be able to write to that location in the first place http://www.zimbra.com/forums/../imag...lies/smile.gif Bug 13198 - Proper error message should show when backup target directory does not have proper rights to take backup
And that's all I can think of that needs extrapolating on - of course keep asking if you need it :)
So I've had some problems with this:
1) Backing up via Galaxy Express takes 24 + hours, an 1.7 TB of tape (for a 380 gig /opt/zimbra/backup/ directory)
2) Tried just tar-ing up the backup directory using (on gig-e):
/bin/tar -cf - /opt/zimbra/backup | ssh firstname.lastname@example.org dd of=~/mailbackups/`date "+%Y-%m-%d"`_backups.tar
tar went quickly at first, then slowed way down and has been running for 2 days now, slowly growing at less than 1 meg a min. I assume due to all the small files? Or maybe the backup directory is regularly written to? Redo logs?
3) Currently trying this:
/sbin/dump -0uan -f - /opt | ssh email@example.com dd of=~/mailbackups/`date "+%Y-%m-%d"`.dump
(almost 1% done after an hour)
scp /opt/zimbra/backups root@host:~/mailbackups
Any other ideas would be very helpful...