Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 High Availability (2005)
 drives not showing up in enterpise manager

Author  Topic 

bandersnatcher
Starting Member

3 Posts

Posted - 2007-07-24 : 08:30:49
Hello
I am having a bit of a fun time at the moment I am currently trying to set up a clustered sql environment and have hit a snag at the moment. The physical set up is all done on good dell kit that has been checked out by a dell engineer who is happy with the set up, I set up the hardware as a clustered environment and then installed sql server 2000 ent and sp4 afterwards. The virtual server itself can see all of the drives through my computer but within the enterprise manager it will only see the drive that the data base is on even though you can force it by typing in the full destination to create a manual backup on one of the drives it cannot see. Anyone got an idea what this is about.
thank you in advance

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-07-24 : 12:54:50
Are the drives setup in Cluster Administrator and the SQL Server service is dependent upon those drives?

Tara Kizer
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-07-24 : 13:56:52
And they should be in same group with sql resources.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-07-24 : 14:02:00
Well that's what I said. You can't have a dependency exist outside of the cluster resource.

Tara Kizer
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

bandersnatcher
Starting Member

3 Posts

Posted - 2007-07-25 : 04:31:13
Does this mean that the directory will not be visable unless it is made dependant on the sql service ? (Sorry I can't take the server offline to check at the moment or I would just try it )
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-07-25 : 11:09:16
Yes.
Go to Top of Page

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2007-07-25 : 12:08:36
this is normal.

we use UNC paths for backups to get around these types of issues.



-ec
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-07-25 : 15:31:24
Not normal if you want to put db files on it.
Go to Top of Page

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2007-07-25 : 15:49:40
quote:
Originally posted by rmiao

Not normal if you want to put db files on it.



this is normal for cluster install. read the first post, the OP is not trying to put datafiles on these drives.


-ec

Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-07-25 : 15:56:59
Installation only adds one disk as sql dependency resource to put on system dbs, have to add other disks manually if don't want to put all users dbs on same disk with system dbs.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-07-25 : 16:21:04
rmiao, you are missing ec's point.

Tara Kizer
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-07-25 : 16:40:59
Got it.
Go to Top of Page

seethem
Starting Member

46 Posts

Posted - 2007-08-22 : 17:03:18
quote:
Originally posted by eyechart

this is normal.

we use UNC paths for backups to get around these types of issues.



-ec


How do you do this?
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-08-22 : 17:41:00
UNC path:
BACKUP DATABASE DbName
TO DISK = '\\SomeRemoteServer\SomeShare\SomeBackupFile.BAK'




Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

seethem
Starting Member

46 Posts

Posted - 2007-08-22 : 20:44:53
quote:
Originally posted by tkizer

UNC path:
BACKUP DATABASE DbName
TO DISK = '\\SomeRemoteServer\SomeShare\SomeBackupFile.BAK'




Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/


Hi Tara,

Thanks for the response, here is going a step further....

Suppose I wanted to have all of my databases off of a 2-node cluster backup to a shared file-system. Additionally, I want this file-system to be highly available.
Do I then create a new resource group with an I.P. address and have that new resource group highly available and then add the shared disk to this new resource group and then use the UNC paths to do backups.


Thanks... Regards,
seethem
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-08-22 : 20:52:29
Wouldn't the shared file system be configured as a new drive and that drive be added as a dependency to the SQL Server cluster group?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

seethem
Starting Member

46 Posts

Posted - 2007-08-22 : 21:18:15
quote:
Originally posted by tkizer

Wouldn't the shared file system be configured as a new drive and that drive be added as a dependency to the SQL Server cluster group?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/


Hi Tara,

I don't think I would want to do that. I have several instances on both nodes. The truth is that my nodes are in an active/active configuration.

I want to have one large LUN for the backups...
That is why I want it in a highly available start.


Thanks and regards,
seethem

Regards,
seethem
Go to Top of Page

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2007-08-22 : 21:40:10
you wouldn't have to give this new drive a distinct name or IP address. You could simply add this drive to one of your current SQL cluster groups. You would then setup a share in the cluster admin tool on this new shared drive. accessing it would be simple, just UNC to the SQL virtual host name + sharename.



-ec
Go to Top of Page

seethem
Starting Member

46 Posts

Posted - 2007-08-23 : 14:26:40
quote:
Originally posted by eyechart

you wouldn't have to give this new drive a distinct name or IP address. You could simply add this drive to one of your current SQL cluster groups. You would then setup a share in the cluster admin tool on this new shared drive. accessing it would be simple, just UNC to the SQL virtual host name + sharename.



-ec

Isn't it cleaner to do it the way I suggested? I don't know. You all are the gurus.
Go to Top of Page
   

- Advertisement -