Re: Clustering concepts...

From: Rick Collins (rcollins_at_NOSPAMmed.unc.edu)
Date: 09/11/04

  • Next message: gotdough: "SQL Cluster recovery from node failure" 
    Date: Sat, 11 Sep 2004 17:30:30 -0400

    > Clustering involves a single data store on a 'shared' storage system (SCSI
    > Array, SAN, etc. NOT NAS).

    Actually, you can cluster to a shared resource on a NAS. We have a NetApp
    880 Filer and have been running SQL clusters quite nicely using Snapdrive
    over Gig fiber for a couple of years using the procedures outlined at this
    NetApp link:
    http://www.netapp.com/tech_library/3248.html#2.

    "Geoff N. Hiten" <SRDBA@Careerbuilder.com> wrote in message
    news:u%23O18vplEHA.3712@TK2MSFTNGP15.phx.gbl...
    > Active/Active and Active/Passive are obsolete concepts from SQL 7.0 when
    > each SQL instance had a primary owner host node and a partner owner node.
    > Under SQL 2000, all nodes are interchangable in a cluster. Some people
    > mistakenly use teh terms to refer to single and multiple instance SQL
    > clustering.
    >
    > Clustering involves a single data store on a 'shared' storage system (SCSI
    > Array, SAN, etc. NOT NAS). Shared is not exactly correct since the
    > cluster
    > software arbitrates ownership so that only one host node owns the
    > resource(s) at a time. Therefore, you have to have a working MSCS cluster
    > in order to create a SQL cluster.
    >
    > Replication is not a good technique for creating a warm standby server.
    > Replication has VERY limited ability to handle schema changes without a
    > total resynch. It also does not replicate stored procedures or views.
    >
    >
    > --
    > Geoff N. Hiten
    > Microsoft SQL Server MVP
    > Senior Database Administrator
    > Careerbuilder.com
    >
    > I support the Professional Association for SQL Server
    > www.sqlpass.org
    >
    > "Karl Albrecht" <karlman@pacbell.net> wrote in message
    > news:O8QGJUplEHA.2340@TK2MSFTNGP11.phx.gbl...
    >> We have just setup two servers running a copy of SQL 2000 on Windows 2000
    >> server. Each of these servers is running vendor software that interrracts
    >> with the databases. One server is primary and one is backup. Clients only
    >> interract with the vendor process on the servers and not the SQL
    >> directly.
    >>
    >>
    >> Some general questions on SQL 2000 high availability options...
    >>
    >> Does Active/Passive and Active/Active refer to clustering options that
    >> require that the servers be clustered on the OS level? Is this the only
    >> option that keeps the databases syncronized in real time?
    >>
    >> Is replication a good method if the failover will be done manually?
    >>
    >>
    >> Thanks!
    >>
    >> Karl Albrecht
    >>
    >>
    >
    >

  • Next message: gotdough: "SQL Cluster recovery from node failure"

    Relevant Pages

    • Re: N+1 Configuration
      ... Jasper Smith (SQL Server MVP) ... But looking in the cluster admin tool, ... mounting all other drives under that drive ...
      (microsoft.public.sqlserver.clustering)
    • Re: Clustering Question
      ... I have worked with Windows 2003 Small Business Server, Exchange Server 2003 and 2000 SQL server but not in a clustered environment. ... Do you want to cluster SQL? ... > you cannot install Cluster on a Small Business Edition, ...
      (microsoft.public.windows.server.clustering)
    • Re: Clustering Question
      ... The SQL Cluster would need to be ... SQL will need to Enterprise as well. ... So if I understand you correctly one computer will need Windows Server ...
      (microsoft.public.windows.server.clustering)
    • Re: Issues creating a new failover cluster on the same server
      ... G:\Microsoft SQL Server\MSSQL.1 ... CHNSQL04 Cluster Group ... Drives: H and F ... Group, the MS DTC Group, and each of the SQL Server Instance Groups running ...
      (microsoft.public.sqlserver.clustering)
    • Re: Connecting to cluster instance from .NET
      ... I have tried using the SQL 2000 CD and i have ... Virtual IP addresses for the cluster resource groups. ... SQL Server will listen on only those IP addresses ... This is odd because the 172.16 network is a Class B ...
      (microsoft.public.sqlserver.clustering)
    Loading