it says what it looks like, backup has completed for the last three nights.

Are you purging backup history older than 3 days?

I'm aware of the process being used on standard clusters

http://sqlblog.com/blogs/linchi_shea/archive/2009/10/04/pause-the-passive-node-to-apply-sql2005-service-pack-or-hotfix.aspx

of course another option might be to remove or evict the new node from the cluster and re-do it correctly.....:-)

If it goes wrong...

pausing the node was how I last applied a patch to a multi site cluster, see here

Its a workaround for when a SQL 2005 patch fails to apply to all...

by shut down the passive node I believe jeffrey means pause the node via cluster manager

This is the process for moving system databases at SQL2005

tempdb is the easiest and safest to move, personally I avoid moving the other system databases unless I really have to.

no need to apologise for incorrect assumptions, I just felt you weren't taking the information on-board.

I said...

hit the books.

A full backup DOES NOT truncate the transaction log, therefore you can restore a log through a full backup.

i.e.

full backup 1

log backup 1

log backup 2

full backup 2

log backup...

why post and ignore the answers?

copy_only...

use the 'from device' radio button and navigate to the location of your backup to select the backup you want to restore.

Note just in case - you only need to...

Reinstall.

But why is the E drive dying? You would actually be better off moving your system databases from the C to the E in terms of best practice configuration.

sorry just reread your post, if the E drive is going completely not to be replaced, its a reinstall

could you move all the contents of the current E drive to the new drive, then re-label the new drive as the E? SQL would need to be stopped.

Otherwise its...

please when giving extra info that has been requested do it by adding another post rather than editing your original post. People only get notified you have replied when you...