It sounds like the instance is down. Check whether the instance is in fact running via configuration manager, if not check the latest error log to see why it is...

which means if you can get hold of backups easily and quickly going back say 3 days, run checkdb every 3 days.

when the restore job runs successfully files that are older than your retention period will be deleted.

If the restore is successful older files will by definition already have ben restored...

its the restore job that deletes the files no longer required.

OS error 112 = not enough space on drive, so yes this is a space error

is the query slow? you say you drop the index and key lookup goes, what is it replaced by, a table or clustered index scan? Is the query faster or...

to reinforce that you definitely shouldn't have other log backup jobs...

you can restart from a differential if no further full backup of the primary has been done since the one used to initialise logshipping, i.e. the primary and the secondary...

when logshipping the only backups of the log must be done via the logshipping jobs.

You will have to remove the 10 min log backups outside of logshipping and change the...

thanks for posting back.

use the rolling upgrade method:

http://support.microsoft.com/kb/958734

you can restore log backups to a copy_only full backup, I just tried it. You should confirm it for yourself by trying it.

As Michael says, normal full backups do not...

the share where the logs are backed up to has to be a cluster resource so it fails over when the sql instance does, that way its visible on either...

the maximum number of databases per instance is 32767, therefore the maximum DBID = 32767, I would say thats the reason this number was chosen for the resource database,...

is that restarting SQL, or restarting the server?

I would take this up with the SAN people, and as jared says, make sure you are not looking at mapped drives rather...