We are seeing intermittent errors with backups (we are testing using a Buffalo NAS device).
The two types of errors affecting perhaps 10% of the accounts in a system wide backup are "bad file descriptor" and "unable to remove /opt/zimbra/backup/tmp/..." (though there is nothing in ~/backup/tmp).
Accounts in the Admin UI displaying this errors are not restorable. Other accounts restore fine.
Not sure where to start debugging, so I thought I'd post here!
Our setup is that we have Buffalo NAS device on the same subnet exposing a Samba share. We mount the share on the Zimbra box and then create a symlink to the mount point from /opt/zimbra/backup, after mv-ing the existing /opt/zimbra/backup somewhere else.
I looked through previous posts here with "bad file descriptor" content, and didn't see anything that applied directly.
I grepped zimbra.log for "btpool" and nothing looked out of sorts there either.
We have fsck'd the Buffalo device and still get the same problem.
We did find this article:
Java Bad File Descriptor Close Bug
but I wouldn't know where to begin looking at Zimbra's code, nor even if the backups are being done via Java somehow.
The network connection between the two devices is about three feet, with known good Cat6 cables and an HP switch whose log is showing no errors.
Other servers using the NAS have no such problems. No other servers are accessing the NAS device during the Zimbra backup period.
Any ideas would be appreciated; NAS storage is much cheaper than DASD and makes off-site replication easier as well.