Hi
Thanks for writing such an amazing suite of programs, I can't even begin to tell you how much the migration modules have reduced the immense stress of migrating our system from ZCS6 to ZCS8
We're running Zimbra virtualized in a Centos 6.4 VirtualBox system, that's going great.
I have a 147GB SAS drive containing the VM for Zimbra, a 70GB SAS drive for the Host OS / other VMs, and a larger 640GB SATA drive for bulk secondary storage and for later backup to tape
I'm trying to use the shared folder guest addition facility to store the zextras backup onto the SATA drive and failing 
Making sure the zimbra user is added to the vboxsf group I've tried both pointing the backup path box to both /media/sf_backup and making a sym link from /opt/zimba/backup to the sf_backup folder
The problem is whenever I click on the "Initialize NOW!" button I get the following message
"Unable to create backup directory: /opt/zimbra/backup/zextras/"
[root@mail zimbra]# ls -l backup
lrwxrwxrwx 1 root root 30 May 8 13:26 backup -> /media/sf_backup/zimbra-backup
[zimbra@mail media]$ ls -l /media/
drwxrwx--- 1 root vboxsf 4096 May 8 11:58 sf_backup
[root@dmz mnt]# ls -l backup/
drwxrwsrwx 3 root vboxusers 4096 May 8 15:52 zimbra-backup
[zimbra@mail media]$ groups
zimbra adm tty postfix vboxsf
So there's no reason that zimbra cannot write to that folder
In-fact if I su to zimbra and then mkdir zextras in /media/sf_backup/zimbra-backup it works fine
[zimbra@mail zimbra-backup]$ pwd
/media/sf_backup/zimbra-backup
[zimbra@mail zimbra-backup]$ mkdir zextras
[zimbra@mail zimbra-backup]$ ls -l
drwxrwx--- 1 root vboxsf 4096 May 8 16:52 zextras
I then re-run the "Initialize NOW!" button and get the same error
If I don't try such tactics and do the initialize step on the host disk it works and starts writing out, but not in the right area
Can anyone shed some light on what I'm doing wrong here?