Can anyone suggest what would be causing this, and how to fix it?
Here is the background:
- SEP Sesam (Edition: Standard, Version: 3.6.4.27, Brand: 20100428131703) and Scalix (11.4.5) are running on a linux (Centos 5.3) server, with backups saved to an eSATA removeable hard disk (the same problem occurs with a USB connection).
Every night, SEP Sesam runs a scheduled backup of non-Scalix files on two servers, plus a full Scalix snapshot backup and individual Scalix mailbox backups. The file server and Scalix snapshot backups continue to work; the Scalix mailbox backups on the same Scalix installation fail.
The mailbox backup task is set up in SEP Sesam as backup type "Scalix" with source in the format "mail:host=mailservername.domain.com.au:instance=mailservername:mn=mailservername", save options set as "-a max_exports=2" and encryption disabled.
If I backup the Scalix mailboxes using sxmboxexp/gzip and a script outside SEP Sesam, the backup completes properly (mailbox sizes up to 2.7GB). Similarly, when I ran a single mailbox backup with source in the format "mail:host=mailservername.domain.com.au:mn=mailservername:instance=mailservername, Firstname Lastname", the backup completed properly." But a full, scheduled backup in SEP Sesam of all mailboxes fails consistently.
The main SEP Sesam log shows that the backup starts correctly, but ends, for example, as follows (names changed):
2010-09-09 23:56:00: sbc-3250: Info: Transferred: 19 MB. Throughput: 222.66 MB/h
2010-09-09 23:56:05: sbc-1007: Error: XBSA Call failed with message: System detected error, operation aborted. Data sending failed. (32) Broken pipe
2010-09-09 23:56:10: sbc-1007: Error: XBSA Call failed with message: System detected error, operation aborted. Data sending failed. (32) Broken pipe
2010-09-09 23:56:10: sbc-3109: Info: Item processed with failure: [/var/opt/sesam/var/work/_sbc_scx_/SC20100909230012/mailservername/Firstname1 Lastname1::firstlastname1@domainname.com.au::Firstname1 Lastname1]
2010-09-09 23:56:10: sbc-3006: Info: Saveset size: 19469636 bytes. Throughput: 19.995121 MB/Hour.
2010-09-09 23:56:10: sbc-3005: Info: Closing saveset.
2010-09-09 23:56:10: sbc-1010: Error: XBSA Call BSAEndData (closing saveset) failed: System detected error, operation aborted. TRANSIENT or PERMANENT NEGATIVE reply: 553 STOR Failed. 553 STOR Failed. Connection timed out (0)
2010-09-09 23:56:10: sbc-3052: Info: Items processed correctly: [4]. Not processed or incorrectly processed items: [0].
2010-09-09 23:56:10: sbc-3053: Info: Operation failed!
2010-09-09 23:56:10: sbc-3001: Info: Exiting.
2010-09-09 23:56:10: scx-3500: Info: SBC exited with [2]
2010-09-10 00:34:26: scx-3500: Info: Return 0
(<class exceptions.IOError at 0xb7eee44c>, <exceptions.IOError instance at 0xb7c7d56c>, <traceback object at 0xb7c8b66c>)
2010-09-10 00:34:26: scx-3200: Info: Mailbox Firstname2 Lastname2::firstlastname2@domainname.com.au::Firstname2 Lastname2 successfully exported
2010-09-10 00:34:26: scx-1500: Error: Unknown exception occurred [exceptions.IOError]
2010-09-10 00:34:26: scx-1007: Error: Operation failed
Traceback (most recent call last):
File "/usr/local/cx_Freeze/initscripts/Console.py", line 27, in ?
File "../sbc_scx.py", line 734, in ?
File "../sbc_scx.py", line 713, in Arguments
File "../sbc_scx.py", line 321, in scalix_mb_backup
IOError: [Errno 32] Broken pipe
2010-09-10 00:50:49: scx-3500: Info: Return 0
We do not remember changing anything to cause the backups to stop working, and can't work out how to fix the problem.