Agree with Grant re. the need to actually restore from a database backup to ensure it's recoverable.

RESTORE VERIFYONLY is fairly useless (with regards to data integrity in the backup set)...

A backup of a database does not need create a temporary file anywhere. SQL Server writes the backup data directly to disk, even if it was to a network...

Try the suggestions in this article and its sub-articles. Provides some tests you could run.

Thanks.

When you restore a database from a backup set, the size of the data files and transaction log files will be identical to that of the database at the time...

We take full backup of the db's daily and all of a sudden we start seeing this error for last 3 days for one particular db. Nothing has changed and...

Are you backing up to an existing file? That's probably the case, and the existing file contains a backup set that was split across 2 files. If you...

Using the PASSWORD option in SQL Server backups only require that you be able to supply the same password during restore operations. It does not encrypt the data in...

With regards to the errors in the event log, it appears that the Litespeed backup process terminated the backup operation. I would suggest looking for any logs that Litespeed...

sql_lock (11/2/2010)

---

You could try simulating what your 3rd party product with the MS VDI simulator

http://blogs.msdn.com/b/sqlserverfaq/archive/2010/10/27/sql-server-backup-simulator.aspx?

The credit has to go to @andrew Kelly for his blog post last week..

http://sqlblog.com/blogs/andrew_kelly/archive/2010/10/28/sql-server-backup-simulator.aspx

NOTE: Read the...

It looks like the Litespeed backup process aborted the backup.

As mentioned by Pradeep, look in the SQL Server error logs to check if there are more informative error messages in...

For example, from FULL BAKCUP A to FULL BACKUP B, we have a log chain. If you issue a FULL backup C without COPY_ONLY between A and B, then, you...

Have you manually check if you are able to read/write to the network share, perhaps using Windows Explorer, when logged on as the same account as that used by your...

For large tables, SQL...

Here's something I wrote some time back on improving backup speed: Speeding up backups

Hope this helps some.

Have you tried creating the same user account, with the same passwords, on both machines, and use that account as the SQL Server Agent service startup account?