Well you do have during installation.
You could easyly determine the actual size of the db and set the new db 10 times higher - jsut to be shure.
a daily cron job could check size of the sparse/actual size to determine if its nessesary to adjust the db setting.
that way the max size limit would be adjusted dynamically
seriisously dont you understand that a 80gig sparsefile has a major impact. only because the limit was set in 8.0 wont help - noone will check every single value of the settings for bad changes - even if they do they wont expect having a file there that size.
the minimum requirements of 90gig without data have to be documentated - in red big letters. its not trivial its a big deal.
btw a quick and dirty fix - really reserving that amount of space
and no you do not need to run db_recover prior rsync if you do a cold backup.
you backup the hole zimbra installation anyway.
heres a little note how we really backup (i hope most do that this way)
so what we do (i dont do it with rsync but our backup software but dont make much difference in the way todo it)
we backup hot - jsut to get most daty into the backup set - (always incremental of course)
then shutdown zimbra - backup everything - because of the incremental backup all we need to backup are recent changes and the database files
time for a hole shutdown backup 90 seconds atm - no need to run anything in advance - the backup is the exact mirror of the server with a shutdown zimbra
you can even restore such a backup easy on a different testing server, all its needed is one entry in /etc/hosts, prior installation of the same zimbra version just to get apt and some minor syschanges on to it -delete the new installation restore the cold backup - its running
(of course firewalling the smtp ports or it will send some mails hanging in the queues during backup time)
What 90GB requirement? The 80GB sparse file is not actually allocated against the disk. I routinely install ZCS8 on a server with a 48GB hard drive with the 80GB maxsize setting with no issue. What is allocated against the disk is the actual size of the DB. And before you try correcting me with regards as to what is or is not required for LDAP and a cold backup in ZCS7 or less, you may want to spend some time doing some research. I've been using OpenLDAP for over a decade. I've been a member of the project team almost as long. It just may be that I have a deeper understanding of how OpenLDAP works than you do.
In any case, I've no further comments on this. You've been advised of what to do to resolve your issue. What you do with that information is up to you.
8.0.3 are ready for download!
Originally Posted by quanah
Is the ldap problem fixed in 8.0.3 version ?
Can anyone explain why there is a difference in file size depending on backup method?
Backup done with "zmslapcat"
-rw-r----- 1 zimbra zimbra 266K 2013-03-29 22:35 ldap.bak
Backup done with "mdb_copy"
-rw-r--r-- 1 root root 1,1M 2013-03-29 22:10 data.mdb
Size of directory as per "du"
du -sh /opt/zimbra/data/ldap/mdb/db/
zmslapcat will create an LDIF backup of the LDAP database (a text file)
mdb_copy creates a backup in mdb format (a binary file) - just omits all the "holes" in the sparse file (hence the matching size of the data.mdb file created by mdb_copy and the /opt/zimbra/data/ldap/mdb/db/ directory)
Originally Posted by Smakodak
Thank you, Quannah!
Thanks Quannah for all the information you provided in this thread - I learned something new about LDAP and Zimbra :)
I admire your patience and greatly appreciate your helpful approach. All too often highly experienced developers come across as "ignorant" of comments/wishes by us mere users. Not you! You listened, explained and even created some useful tools and improved Zimbra based on the input.
Thank you! It's always an adventure deploying new technologies. ;)
Thanks for responding:)
Originally Posted by winepress
I complete this steps, but /opt/zimbra/data/ldap/mdb.prev/db/data.mdb size = 85899345920
Is mdb.prev backup folder? Can I delete it?
Quick question Quanah. I've used cp to backup my server since ZCS5 and now with ZCS7. I shut the server down first then cp -rp the zimbra directory. I have restored successfully from these backups. Your statement that it remains unacceptable for ZCS7 and prior due to BDB has me confused. Since my method appears to work why are you saying it is unacceptable? Restoring in the opposite direction from the copied zimbra directory appears to work. Could you elaborate on unacceptable?