Thank you

I figured it out

It was the Server name was incorrect.  The MSTDC setup on the Cluster was wrong after correcting that email starting working.

Thanks again for all the responses.

Tom

Thanks

I got the records cleared now.

yes I added it as a dependency

Was able to restore the databases from my .bak files.

Guys

I figured it out

I am now able to restore user databases.

We can mark this as resolved.

Thanks for all the help

I do have the drive added to the cluster  it is assigned to the Role

The...

Why is it that no one knows how to restore the databases

Why do we back up the database if we can not restore them

All the...

Steve,

The storage was destroyed I do not know how or  why the drive filled up and caused some sort of corruption

I have only backup files and...

Update Guys I finally got SQL Agent to Start it was a permissions issue on the drive to the path to the log folder

Now my only issue is restore...

Thanks for responding.

I have reviewed all my code on the site do not see any additional code that would do this.

It is in the database I...

Ok guys

port 2433 is not listening
unable to telnet to that port
port 1433 is listening and I can telnet to port 1433 no problem

Hi

First that ip address is just made up it is not my actual ip address

I turned off the Windows Firewall and the same results Not sure...

Frederico

I figured it out

Start Failover Cluster Manger
Select Roles
Then chose the Role in which you need to add the LUN to
In the bottom...

This can be marked as resolved.

Figured out how to add the new LUN to the cluster

Need to go to the Other Resources section after you...

I have three sql instances on this same cluster server and all are using Networked iSCSI LUNS all work but one drive that is why I created a new LUN.

SQL 2014 Enterprise  Clustered on Windows 2012 R2 Servers which are both VM's (VMWARE)  The LUN's are via my NAS device using iSCSI