Ik have a strange error, at least strange for me.
I have been running the zimbra open source edition for over 2 years now. With it i have been using "yet another zimbra backup script"
These both have been running fine, not trouble what so ever.
2 weeks ago i upgraded zimbra to the latest version and now the backup script is giving me errors.
I am a medium experienced linux user and as far as i can see i a running out of space. But that can't be, i have plenty of space where the backup and temp files are written.
Doing a fast cold sync...
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: write failed on "/tmp/fakebackup/data/ldap/mdb/db/data.mdb": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7]
rsync: connection unexpectedly closed (1208 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7]
rsync threw an error!
This should not happen at this stage... exiting!
The thing that also worries me is that after the error the zimbra services aren't started again and leaves me over night with a non functioning mail server.
I have to start the services manually in the morning.
I have disabled the cron lines for the auto backup for a week now but can't seem to solve this problem.
Even have downloaded a new copy of the backup script and started over but the same result.
Does anyone have encountered something like this before, or can kick me in the right direction.
My server specs:
Server = Virtual box running Ubuntu 10.04.4 LTS
Disk space = Usage of /: 15.8% of 36.60G
Any help is appreciated.