Re: Restoring one clusternode.

Failover does not occur for disks just the computer itself. You have a
shared disk resource(s) which 1 node in the cluster owns. Should that node
fail then another will take over ownership of the disk resources. It sounds
like you require fault tolerant hardware. I siggest to re-read all the links
so you better understand clustering and what it provides.

And log file placement is usually decided by performance resons.
--
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria

"Johnny Lundgren" <JohnnyLundgren@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:1B59D480-E4F9-40F1-8609-CD7CC07DC331@xxxxxxxxxxxxxxxx
> Thanks Nik,
> Got it now and your doc solved the recovering SQL on one node-question.
> Although, I cannot find anything about recommendations on where to place
> the
> transaction logs.
> Should I place the logs on different shared drives than the clustered SQL
> db:s ?
> If so, what will be the impact if a failover occurs on either of the
> shared
> disks ?
>
> I would like to have documents describing this particular scenario.
> All I can find in the docs so far is that the logs should reside on
> mirrored
> drives preferrably.
>
> Regards
> Johnny Lundgren
>
> "Nik Marshall-Blank" wrote:
>
>> They are the blue hyperlinks in the word document I attached (last page).
>>
>> --
>> Nik Marshall-Blank MCSD/MCDBA
>> Linz, Austria
>>
>> "Johnny Lundgren" <JohnnyLundgren@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message news:D4C201FF-5E36-42B0-9FF2-C319E11CC07A@xxxxxxxxxxxxxxxx
>> > Hello Nick,
>> >
>> > I think you forgot to post the links..?
>> >
>> > Regards
>> > Johnny Lundgren
>> >
>> > "Nik Marshall-Blank" wrote:
>> >
>> >> These are my notes with links at the end.
>> >>
>> >> --
>> >> Nik Marshall-Blank MCSD/MCDBA
>> >> Linz, Austria
>> >>
>> >> "Johnny Lundgren" <JohnnyLundgren@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> >> message news:C8CEA952-209A-41BF-8C85-F4473964CE62@xxxxxxxxxxxxxxxx
>> >> > Hello,
>> >> >
>> >> > I one clusternode fails. What is the procedure to reinstall the SQL
>> >> > software
>> >> > INCLUDING SQL servicepacks? Preferrably without disturbing the
>> >> > remaining
>> >> > node. Documents anyone ?
>> >> > Also, SQL-logs, where could or should they reside ? On the same
>> >> > shared
>> >> > disk
>> >> > as the db:s or on another one? Or maybe on a local disk ?
>> >> >
>> >> > Regards
>> >> >
>> >> > Johnny Lundgren
>> >>
>> >>
>> >>
>>
>>
>>


.

Relevant Pages

  • Re: Configure failover in seconds
    ... When a failover starts, it starts. ... "pause" because of your san disks who need to failover. ... add this script as a resource to your cluster ... Is this done in CLuster Administrator? ...
    (microsoft.public.windows.server.clustering)
  • Re: Truly High Available?
    ... an MNS cluster is the perfect solution for you. ... would have at least 1 node on each site with mirrored SAN disks. ... It will be a true Failover Cluster in the sense of MSCS, ...
    (microsoft.public.sqlserver.clustering)
  • Re: Restoring one clusternode.
    ... I am very well acquainted with the MS Cluster Services but I am no expert on ... the logs will default reside on the same ... Directing the logfiles on local disks and separate from the O.S.? ... >> Should I place the logs on different shared drives than the clustered SQL ...
    (microsoft.public.sqlserver.clustering)
  • Re: Random Event 1135
    ... If you go to a command line and issue a "cluster log /g" command, ... you can check the Failover ... Cluster Operational logs for messages regarding network ...
    (microsoft.public.windows.server.clustering)
  • Re: Cluster Failover history
    ... I would recommend looking into the functionality of the Cluster logs and the ... but W2K and up has cluster logging enabled by ... can anyone help me find a good resource on how to trace Cluster failover ...
    (microsoft.public.windows.server.clustering)