Running Trial Version, Complete Backup was Successful.

 When I run Verify Image on it, status is given as Failed, but neither backup log file nor image verify log file have any errors.  The backup log file states "Process finished successfully," though I don't see either a "success" or "failed" item in the image verify log.  It ends with "sbrest" "image created at (data/time)."

All items are regular info icons except the Trial period which has 20 days left.  I have run Chkdsk on the device, reformatted it (Quick Format), ran Defrag, no errors reported and with no change in results.  I am backing up a drive with <120GB to an eSata external with 397GB free space after the backup was completed.  I've restarted for a fresh start with no change in results. 

Here is the detail log for the verify. I did goof; I used a wide window and didn't see the slider, so the log file does contain errors I didn't see before.  Since only the first error really counts, it appears that something didn't get written properly (#500).  (Isn't there a Compare facility to run just after the backup?)

Also, to answer your question, the "failed" was only for the verify; the backup reported "Completed."  I will also append the backup log file.

First, here is the verify log file: 

09-Jun-2008 20:53:33    service    100    service (build 42) started job.
09-Jun-2008 20:53:33    service    300    trial period has 17 days left
09-Jun-2008 20:53:33    service    104    3.2.0.2 7BE4-AF97 FCB0-6618
09-Jun-2008 20:53:33    sptask    110    Worker thread has started
09-Jun-2008 20:53:33    sptask    111    sbrun -mdn ( sbfile -r F:\C_VOL-b001.spf : sbcrypt : sbrest  )
09-Jun-2008 20:53:33    (loader)    112    corelogic version: 1.0.0.210
09-Jun-2008 20:53:33    sbfile    101    successfully opened file F:\C_VOL-b001.spf
09-Jun-2008 20:53:33    sbcrypt    109    filter started
09-Jun-2008 20:53:34    sbcrypt    107    image compression mode: 5
09-Jun-2008 20:53:34    sbcrypt    107    image encryption mode: 0
09-Jun-2008 20:53:34    sbrest    109    image created at 06-Jun-2008 17:02:01 GMT-5:00
09-Jun-2008 20:53:34    sbrest    109    imaged volume had 625137664 sectors, 512 bytes each
09-Jun-2008 20:53:34    sbrest    109    image GUID {1DD786D3-9942-474D-A932-9A3CF20A38C0}
09-Jun-2008 20:53:34    sbrest    109    image has no comment
09-Jun-2008 20:53:34    sbrest    109    original disk C/H/S = 38913/255/63 partition #1
09-Jun-2008 20:53:34    sbrest    109    image created on:
09-Jun-2008 20:53:34    sbrest    109     - OS version 6.00 build 6001 Service Pack 1
09-Jun-2008 20:53:34    sbrest    109     - machine JJSTEWART-PC (0.0.0.0) MAC 04:4B:80:80:80:03
09-Jun-2008 20:53:34    sbrest    109     - corelogic version 1.0.0.210
09-Jun-2008 20:53:34    sbrest    107    partition type for a target: 7
09-Jun-2008 20:54:03    sbcrypt    500    Chunk failed due to malformed data
09-Jun-2008 20:54:03    sbrest    500    Unexpected end of the image file
09-Jun-2008 20:54:03    sbcrypt    109    fini done
09-Jun-2008 20:54:03    sbrest    109    fini done
09-Jun-2008 20:54:03    sbfile    109    fini done
09-Jun-2008 20:54:03    (loader)    504    Final error (-109 The pipe has been ended.)
09-Jun-2008 20:54:03    sptask    516    sbrun.exe started successfully but failed to complete the task
09-Jun-2008 20:54:03    service    104    retry task
 

The status showed "failed."

Here is the log file for the backup:

06-Jun-2008 17:01:25    service    100    service (build 42) started job manually as full
06-Jun-2008 17:01:25    service    300    trial period has 20 days left
06-Jun-2008 17:01:25    service    104    3.2.0.2 7BE4-AF97 FCB0-6618
06-Jun-2008 17:01:25    service    100    backup volume C:\ (NTFS)
06-Jun-2008 17:01:25    service    102    creating snapshot for  \\?\Volume{793f2d7d-4499-11dc-9f57-806e6f6e6963}
06-Jun-2008 17:01:25    service    199    try snapshot by  VSS API by STC provider
06-Jun-2008 17:01:25    service    199    all possible methods:  VSS API by default provider VSNAP API directly VSS API by STC provider and no other alternate methods
06-Jun-2008 17:01:58    service    150    retrieving snapshot name.
06-Jun-2008 17:02:00    service    103    snapshot was created by  VSS API by STC provider. It took 35 seconds
06-Jun-2008 17:02:00    service    104    ready to do full image
06-Jun-2008 17:02:00    sptask    110    Worker thread has started
06-Jun-2008 17:02:00    sptask    111    sbrun -mdn ( sbvol -fs \\?\STC_SnapShot_Volume_21_0 \\?\Volume{793f2d7d-4499-11dc-9f57-806e6f6e6963} : sbcrypt -50 : sbfile -wd F:\C_VOL-b001.spf )
06-Jun-2008 17:02:01    (loader)    112    corelogic version: 1.0.0.210
06-Jun-2008 17:02:01    sbvol    109    free space exclusion on
06-Jun-2008 17:02:01    sbvol    101    successfully opened volume \\?\Volume{793f2d7d-4499-11dc-9f57-806e6f6e6963}
06-Jun-2008 17:02:01    sbvol    107    FAT system area sectors: 0
06-Jun-2008 17:02:01    sbvol    112    file \\?\STC_SnapShot_Volume_21_0\pagefile.sys excluded OK
06-Jun-2008 17:02:01    sbcrypt    109    filter started
06-Jun-2008 17:02:01    sbfile    101    successfully opened file F:\C_VOL-b001.spf
06-Jun-2008 17:02:01    sbvol    107    disk MBR sectors: 1
06-Jun-2008 17:02:01    sbvol    107    first track sectors: 63
06-Jun-2008 17:02:01    sbvol    109    disk CHS 38913/255/63 partition 1
06-Jun-2008 17:02:01    sbcrypt    107    compression mode: 5
06-Jun-2008 17:02:01    sbcrypt    107    encryption mode: 0
06-Jun-2008 17:04:35    sbfile    109    probing the target media for > 4GB files support
06-Jun-2008 17:40:42    sbvol    109    last volume read done
06-Jun-2008 17:40:42    sbcrypt    109    tail started
06-Jun-2008 17:40:42    sbcrypt    109    fini done
06-Jun-2008 17:40:42    sbfile    200    OK F:\C_VOL-b001.spf
06-Jun-2008 17:40:42    sbfile    109    fini done
06-Jun-2008 17:40:42    sbvol    109    fini done
06-Jun-2008 17:40:42    sptask    114    Process finished successfully
06-Jun-2008 17:40:47    service    105    snapshots were destroyed
 

"Chunk failed due to malformed data" usually means the image file is corrupt.  The backup log looks perfectly normal, so I think you started out with a good backup, which was later corrupted by something.  You should check your System event log for disk-related errors or warnings (ones that come from disk, ftdisk, ntfs, dmio, or your storage controller driver), as they can indicate a hardware problem.  Hardware problems are the most common reason for corrupt images.

But speaking of your storage controller, we have occasionally seen strange problems when using eSATA drives for a destination device.  You should still check your System log, but you could also try copying the backup to another drive, such an an internal disk or an external USB disk, and see if it will verify from that location.  This will let us know if the file is actually corrupt, or only reporting that is is due to an eSATA problem.  If it still fails, it's possible that all backups created to the eSATA device are being corrupted due to an eSATA problem.  Try backing up to a different drive attached to the same system and see if that backup will verify. 

 I finally got a good backup and a good verify.

 Your suspicion about eSATA devices led me to try changing the drive over to a FireWire400 interface, which it is capable of doing.  (My ASUS mobo doesn't have a FireWire800.)  Something I did initially produced two partitions on that one drive, the second was a small 2GB piece.  Needless to say, I reformatted the drive.  The size was larger now, so obviously the smaller second chunk before reformatting couldn't be seen. I copied a backup I made to a USB disk, which verified successfully, onto the reformatted drive and it verified there.  Next, I did a backup to the reformatted drive, which was successful.  Then I verified it, which was successful, status "Completed."

 Next, I'm going to go back to eSATA and backup/verify.  Since I discovered the 2GB piece and then reformatted, it might work now. 

 Remember, my "real" problem was that I ran backup successfully, but the verify failed.  (At first, I didn't scroll down to see the errors.)  I suspect that the original format terminated abruptly though it was essentially completed, thus the completed/failed confusion.

 So now, thanks to your advice, I will proceed to buy your product.  I am convinced that not only is it good, but that the support you give is second to none.

I will advise when I try the eSATA again to see if it is successful because of the reformatting.