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.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2005 Forums
 High Availability (2005)
 error 5184 when adding sqllogs in separate disk
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Hitesh Shah
Yak Posting Veteran

India
80 Posts

Posted - 04/05/2008 :  14:11:20  Show Profile  Visit Hitesh Shah's Homepage  Send Hitesh Shah a Yahoo! Message  Reply with Quote
I am trying to create logs in a separate disk in the cluster. I get error 5184 indicating some dependency error . Here is the dependency layout in SQL server group.

f:\ --> Mount point
f:\appdata --> data for SQL and user database data files --> F:f:\appothers--> other datafiles --> f:G:\--> mount point
g:\sqllogs --> user data base logfiles --> g:
Does this mean I have to make f:\appdata dependent on g:\sqllogs also. If yes will the error go .

Does changes in cluster resource need server restart .

sodeep
Flowing Fount of Yak Knowledge

USA
7174 Posts

Posted - 04/05/2008 :  14:49:22  Show Profile  Reply with Quote
Did you create dependency for Log files properly?
Go to Top of Page

sodeep
Flowing Fount of Yak Knowledge

USA
7174 Posts

Posted - 04/05/2008 :  14:50:40  Show Profile  Reply with Quote
Here it is:

http://technet.microsoft.com/en-us/library/ms177447.aspx
Go to Top of Page

rmiao
Flowing Fount of Yak Knowledge

USA
7266 Posts

Posted - 04/05/2008 :  21:42:07  Show Profile  Reply with Quote
Have to add g:\ as dependency resource to sql resource, need stop sql resource to do that.
Go to Top of Page

Hitesh Shah
Yak Posting Veteran

India
80 Posts

Posted - 04/07/2008 :  03:09:47  Show Profile  Visit Hitesh Shah's Homepage  Send Hitesh Shah a Yahoo! Message  Reply with Quote
Did work successfully by adding g:\ as dependency resource to sql resource. Thanks all for the help.
Go to Top of Page

Hitesh Shah
Yak Posting Veteran

India
80 Posts

Posted - 04/08/2008 :  14:02:24  Show Profile  Visit Hitesh Shah's Homepage  Send Hitesh Shah a Yahoo! Message  Reply with Quote
The error 5184 is solved . But I have one question out of curiosity .

I have g:\ and g:\sqllogs (mounted on g:\) separate disks configured. g:\sqllogs is dependent on g:\ .

For adding disk dependency for SQL server resource , what should I add resource dependency g:\ or g:\sqllogs . I have added g:\ and it works . But I feel it should be dependent on g:\sqllogs (which is in turn already dependent on g:\) . Please tell me the actual settings at ur end .

If u wnat me change the dependency , if i bring the resource offline , change the dependency and bring it online, is there anything else also required to be done (like rebooting ..) .
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
38200 Posts

Posted - 04/08/2008 :  15:39:32  Show Profile  Visit tkizer's Homepage  Reply with Quote
We use mount points as well. You just need to add G: as a dependency.

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

Hitesh Shah
Yak Posting Veteran

India
80 Posts

Posted - 04/25/2008 :  04:24:13  Show Profile  Visit Hitesh Shah's Homepage  Send Hitesh Shah a Yahoo! Message  Reply with Quote
quote:
Originally posted by tkizer

We use mount points as well. You just need to add G: as a dependency.

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



Tara ,

I check http://support.microsoft.com/kb/819546/ which contains following info .


The SQL Server 2005 resource depends on the SQL network name resource and the physical disk resources that hold its data. When mount points are being used together with the physical disks, each mount point must appear as a cluster resource. Additionally, each mount point must also be added as a SQL Server dependency. If only the root physical disks dependency is added and the mount points are not added, database corruption will occur on failover. Database corruption may also occur when SQL Server is restarted without failing over.


Is this true . Have u faced any db corruption for actual failover. Is there any potential problem / pitfall for following this advice .

Edited by - Hitesh Shah on 04/25/2008 04:25:27
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
38200 Posts

Posted - 04/25/2008 :  13:08:28  Show Profile  Visit tkizer's Homepage  Reply with Quote
We've had this 4-node cluster with 11 SQL instances in production for about 2 years now. Each instance is using 3-4 mount points. We've failed over to other nodes dozens and dozens of times. We've never had any database corruption whatsoever. We check DBCC CHECKDB every night.

Perhaps it makes a difference which software package you are using for the mount points. I'm not sure though. We are using Veritas Volume Manager on a Hitachi SAN.

I will be checking with my team though if they know anything about this.

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

Hitesh Shah
Yak Posting Veteran

India
80 Posts

Posted - 04/25/2008 :  23:54:48  Show Profile  Visit Hitesh Shah's Homepage  Send Hitesh Shah a Yahoo! Message  Reply with Quote
That's fine . If u get any info from ur tip , please let me know.

In the meanwhile I believe there is noharm in adding all mount points . In fact in that there is no need for root hard disk dependency (as the mount points already depend on the same and SQL resource depends on mount) . Any comments / experience are welcome.
Go to Top of Page

Hitesh Shah
Yak Posting Veteran

India
80 Posts

Posted - 04/28/2008 :  00:52:15  Show Profile  Visit Hitesh Shah's Homepage  Send Hitesh Shah a Yahoo! Message  Reply with Quote
On adding mount points to SQL resource all my errors in the error logs on resource failover (OS error 21 writing log files ) vanished. I thought these errors were due to disk signature difference , old controller firmware etc . And worked in those directions . I didnt new that the solution lied in this small step .

Nevertheless , at the end of the day I learnt lot .
Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2019 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.05 seconds. Powered By: Snitz Forums 2000