What edition of sql 2005 installed?

You might have installed either workgroup or express edition. Check the following...

SQL Server 2005 Features Comparison

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

I believe it is active/active which is more than one instance.. if you have only one instance it is active/passive...

But read the thread from sql gurus...

http://groups.google.com/group/microsoft.public.sqlserver.clustering/browse_thread/thread/cf80bb93e0cdc8bd/38efb4d25e7837c8?lnk=st&q=check+sql+server+active%2Factive+or+active%2Fpassive&rnum=1&hl=en#38efb4d25e7837c8

Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1

http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad125641/ReadmeSQL2005.htm

If cleanup task won't work you can use the procedure...

declare @dt datetime

set @dt = getdate()-2

EXECUTE master.dbo.xp_delete_file 0,N'\\sql2k5\SQLBackup\,N'.bak', @dt

Did you change the datatype in a proc or table?

It could be Data Type Precedence issue.

http://msdn2.microsoft.com/en-us/library/ms190309.aspx

It could be blocing issue too...

Do you have any blocking information for that period...

Means you guys are not interested for point in time recovery... then it advisable to change the recovery model to SIMPLE.

Good to know it is working

Try also sp_spaceused procedure after DBCC UPDATEUSAGE...

I beleiv it is sql BUG...

You can make use of the following scripts...

http://www.databasejournal.com/scripts/article.php/1450801

http://vyaskn.tripod.com/sp_show_biggest_tables.htm

Can you please post your sql server version..Run the following and post it..

Select @@version

1. I have seen the cases where restore verifyonly varified even when backup was not usable.

2. You ran retore verify on production using the copy on production.

3. Try the restore...

I mean to say " I never did this" where as I typed "like" extra word which changed meaning entirely...

I never did this so I don't have any opinion on...

Yes, as long as sql can see that server with write access..

I do this all the time...

Backup database dbname to disk = '\\servername\c$\dbname.bak' with init, stats=10

Blocking is nothing to do with your restore db as different name pointed all reports to the new db...

You need to figure it out what blocking what? For that you...