11-29-2010 10:39 AM
I keep running into an error when I try to backup with attachments on the server where the ACT database resides.
I get variations of:
Errors: Failed to log into the database. An IO exception occurred while reading from or writing to the zip file.
Zip file: C:\WINDOWS\TEMP\tmp2223.tmp
the tmp file is different, and I have cleared out that folder, with the same results.
This error happens whether I manually or automatically backup.
This error does NOT happen on a nother computer, or when I don't backup attachemtns.
My attachments folder is huge. Is there anyway to divide them?
12-01-2010 01:30 PM
12-01-2010 02:00 PM
10 01:30 PM
12-02-2010 05:02 AM
12-10-2010 01:57 PM
Basically 3 options:
1. Clear additional space on your C: drive
2. Run the backup from a workstation (not a fan of this option because it requires the data to cross a network - but as long as you test restoring your backups frequently (to a new db name) to ensure integrity of the zip files, it is a viable option)
3. Continue backup without attachments through ACT! and use alternate/manual process to backup/copy the 'database files' folder. The 'database files' folder is not locked by SQL and can be copied by any backup program.
01-26-2011 04:26 PM
It is concerning that Sage provide an automated backup utility but do not provide for any facility to email administrators that backup has failed ( or completed). As a consequence it is easy to setup a backup schedule and believe it is functioning.
The problem with insufficient disk space is only one reason for a backup failing to run.
I know that 3rd party poducts are available to monitor and signal on a failure to backup but that does not remove the necessity for Sage to urgently address this short coming in their own product.
It isn't that complex for Sage to sort this out - come on Sage this is an important data security issue - let's see it happen please.