October 5, 2009 at 11:45 pm
Hi,
We have Active/Passive cluster setup for SQL Server 2005. Windows admin configured the 2 node windows 2003 x64 cluster and then we have created a sqlgroup and created 2 resources of type 'Physical disk' in that group. Also created a backup group and created a resource of type 'Physical disk' in the backup group. And installed SQL Server 2005 with the provided Virtual IPAddress .
After that in SQLGroup in Cluster Administrator:
1. Go to SQLServer resource->properties->dependencies->modify-> here added E,F, G as dependencies. Network name is already there as a dependency. Please see the attachment.
In backup group, in Cluster administrator:
1. Selected the Physical Disk on Right hand side & verified the dependencies, there is none. Also if I click modify on dependencies, nothing is there to add as dependency.
I'm not clear on what to add & not to add as dependencies. please see the attachment and advise me what to change on my configuration.
Could you suggest me good document an these dependencies items
thanks
October 7, 2009 at 10:44 am
please advice...
October 7, 2009 at 11:29 am
You should download this whitepaper and read it.
it's got a lot of pictures which will help you greatly.
It shows you step by step on how to install and configure the cluster.
October 7, 2009 at 11:48 am
I'd start by searching the MSDN and Technet sites for Cluster Configuration.
October 7, 2009 at 12:57 pm
In addition to the reading, can you answer the following:
1. Does it work on the current node?
2. Does it continue to work when you failover to the other node?
If the answers to the above are yes, then you have a good cluster.
Repeat 1 and 2 for backups and restores, TLog backups, replication, log shipping, etc. Add or remove features as per your setup.
If the answers are all still yes, it's a job well done.
Not too sure about the backup resource though ...
October 7, 2009 at 1:03 pm
The Network Name needs to be dependent on the IP Address.
SQL Server needs to be dependent on the Network Name and any physical disks where its database files are to be stored (it won't let you create a database on a disk that isn't a dependent).
That's about it. There will be no need for a disk to be dependent on anything.
We use a file share for backups (no different to using a physical disk, except it is remote), this is not a dependent. But, we have it in the same group as SQL instance. I don't see why you would want a separate group for a disk assigned to backups, assuming you are using native SQL backup.
hth.
October 7, 2009 at 1:36 pm
I don't see why you would want a separate group for a disk assigned to backups, assuming you are using native SQL backup.
hth.
Actually, we ran out of the Drive letters i.e we already used all the Drive letters from C to Z. So we do not have Drive letters to keep a separate back drive in each sqlgroup!!! that's why we are using a common backup drive (which is in Backup group) for all sql instances..
thanks
October 7, 2009 at 1:49 pm
You might want to do some research on Mount Points. Those can be used in place of drive letters.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply