Virtual Disk size is inaccurate
Posted: Thu Jul 14, 2016 7:23 pm
I have Zimbra installed in a virtual machine in XenServer 6.5.0. It is working great for one of my smaller companies that has about 20 users. However, within XenCenter I keep an eye on my .VHD files for each of my virtual machines to make sure the sizes stay healthy, but then I noticed something very strange today. I have a live Zimbra server, and a test server. I have been testing some backup and restore solutions for the databases, and today I copied over the entire /opt/zimbra directory from the test mail server to a backup drive I had mounted to it. I was very confused when the backup ended up taking much longer than I expected, and when it finished my backup of that directory, it ended up being 105 GB. This is very strange because the .VHD file associated to that machine is only 40 GB! it didn't take me long to find the culprit, and it was the main LDAP database file "zimbra\data\ldap\mdb\db" which was an even 80 GB! I barely have over 20 GB in mail in that test server, and I actually know how to completely restore a user's mail and databases without even using that main LDAP database, but my boss insisted I copy over the whole directory. My live mail server of course has the same 80 GB "data.mdb" file in the same location, and of course it doesn't reflect in the size of the virtual hard disk associated with it.
So, can anyone explain to me why that LDAP database file is 80 GB, and how come my virtual disk doesn't count the size of that file when reporting its own size? I have researched it and come up with no information.
So, can anyone explain to me why that LDAP database file is 80 GB, and how come my virtual disk doesn't count the size of that file when reporting its own size? I have researched it and come up with no information.