Theoretically, the two backups can start at precisely same time. But your two servers may not be precisely synchronized. You may have to use the STOPAT clause in your restore.

Do you have many scripts running on your cluster? Do these scripts create many objects, such as table variables and ..., ? If so, are they destoyed after usage?

10-15% CPU...

You need to join your one table with another in your WHERE clause.

It happened to me before. How did you move your DTS to the new server?

You may try different approach to move.

1. Save As from the old server;

2. Save as a...

Here are my cents.

When using database maintenance plan, you can find there is a check box for verification after backup. You can use it to check integrity.

You can add a...

Here are my two cents.

1. Did you reboot your machine?

2. Does the registry for SQL 2005 still exists?

Run

sp_configure

you can see "remote access"

Turn it on (set the value to 1 to enable the remote access).

Generally speaking,

CPU usage

Free disk space

Failed jobs

...

You may turn on other counters when such an isssue comes up.

In my memory, SQL 2000 backup a database first and then delete old one if the backup is successful by default.

You can remove the old backup files using xp_cmdshell command...

Did you really include the two percentage signs?

Couple suggestions.

1. Make your transactions as short as possible.

2. Include NO_LOCK clause in your SELECT statement (or change your isolation level in the SELECT statement).

Here is an alternative.

Create your new database on your target server, then, migrate your data using DTS.

Hopefully, it will be helpful.

Did you read the following discussions? Hopefully, it will be helpful.

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=69430

For the shared locks, you may modify your queries with no_lock or the isolation level.

It is related to registry.

Here is one link. Hopefully, it is helpful.

http://www.jsifaq.com/SF/Tips/Tip.aspx?id=9175