Hi,
Through my employer I purchased the Xceed ActiveX suite to use the Backup v1.1 control. It seemed ideal for my purposes.
I created a backup program for my application, tested it with a few gigabytes of data, and satisfied that it worked I released it for customer use.
Now a customer has called complaining that they cannot restore their 6Gb backup. I checked and was staggered to find that Xceed Backup creates corrupted backups when the ZIP file goes over 4Gb in size.
There appears to be no archive volume splitting option, and Xceed's control does not automatically move to a new file when the 4Gb per ZIP file limit is reached. I checked the documentation and there is no mention of this limitation. Surely Xceed knew about it? Why have a proper backup control that cannot backup more than 4Gb of compressed data?
What's worse is that the control will happily create a 5, 10, 15+Gb ZIP with no complaints at all. Only if the archive is tested after backup does the error become apparent, with all files after the 4Gb mark being unrecoverable.
I'll now have to quickly write a new backup program and distribute it ASAP. I hope I've missed something in Xceed's Backup and there is a simple solution to my problem. Otherwise, I would like to see the rationale behind a backup component that can store less than one DVD's worth of data.
