Have you tried backing up to another drive?

Are you appending to an existing backup file?  Try backing up to a new file.

Your backups on the existing file appear to have been created using a BLOCKSIZE of 65536...

I would suggest ensuring that the backup file was first valid, as that error indicates that the header may be damaged.  Try restoring that backup on a similar SQL Express instance.

Red-Gate's SQL Backup (http://www.red-gate.com/sql/sql_backup.htm) ?

Is it like so then?

During a full backup, all new entries into the transaction log file are not written to the data file until the full backup completes.  Which implies...

SQL Backup has been cluster-aware since the initial release of version 3.0.  Other usability features include

• multiple trx log restores from a single command e.g. RESTORE LOG mydb FROM FILE =...

For a recent view of SQL Server backup compression software, see

• http://www.sqlservercentral.com/columnists/wbrown/fourofakindbackupsoftwareshootout.asp
• http://www.sqlservercentral.com/columnists/wbrown/fourofakindbackupsoftwareshootoutpart2.asp

MiniSQLBackup licensing costs are as follows:

• single named server license - USD 99/-
• two named servers license - USD 179/-
• ten named servers license - USD 795/-

and includes free updates for one year...

It appears that MiniSQLBackup (MSB) is spending a lot more time on the compression phase compared to writing the backups out to disk.  The I/O counters are extremely low in...

MiniSQLBackup does not offer an 'interface' for log shipping, but does implement a log shipping functionality that we hope makes the task easier.  Basically, you can throw a bunch of log...

Backups are I/O intensive.  Perhaps some other process was tying up the disks where the database and backups reside e.g. virus scanning apps performing a scheduled scan, another process moving some...

You might start here:

Four of a Kind - Backup Software Shootout

Four of a Kind - Backup Software Shootout Part 2

If you are using the full/bulk-logged recovery models, you might need to perform more frequent transaction log backups to keep the size of the trx log to a manageable level. ...

SQL Server does not have to be in single user mode to perform backups.  However, there are certain functions that might block a backup, such as CHECKALLOC, bulk copy & SELECT...

All changes to the database are first written to the trx log before written to the data files (which may occur later).  A trx is deemed to be committed only...