Re: HOW to setup printer in Majority Node Set



Thanks to everyone! We have the big picture now!
Have a Great Day!!!
--
Best Regards
Fred


"Rodney R. Fournier [MVP]" wrote:

You still need shared Printer disks with MNS and it sounds like you are
missing those :)

Cheers,

Rodney R. Fournier

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner


"FreddiG" <FreddiG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F2E34A0D-9AC6-4056-9D4C-C919FB67B122@xxxxxxxxxxxxxxxx
Hello Elden,
Thanks for the timely reply. After I posted this I found the same doument.
Unfortunately, when I got to step 8(f) in the document :
8. To add a Physical Disk resource to the group (this step can be skipped
if
a Disk Resource already exists):
a. Right-click the new spooler resource group (for example,
Spooler-Group1),
point to New, and then click Resource.
b. In the Name box, type a name for the resource (for example, type
Spooler
Disk Resource).
c. In the Resource type list, click Physical Disk, and then click Next.
d. Make sure that the Possible owners list contains the cluster nodes that
you want as possible owners of this resource, and then click Next.
e. On the Dependencies page, click Next (the physical disk resource does
not
have any resource dependencies).
f. In the Disk list, click the physical hard disk that you want to use for
this resource.
g. Click Finish, and then after the resource is successfully created,
click
OK.

At step 8(f) there is no physical disk in the drop down box. I am a bit
confused. I have configured the MNS NODE1, NODE2, NODE3 without any shared
disk. On each node there are file shares that are identical. The data on
each
NODE is local. THe data is on the LOCAL G Drive. The DISK, when I install
W2K3 Advanced Server, was partioned into a C Drive (W2K3 system) and a G
Drive (Files/Data). There are no external storage devices available for
each
NODE. Only the defined LOCAL Drives.
The data does not change. Hence no need for a 3rd party replication
software.

There is no shared disk defined to the MNS NODE1, NODE2, NODE3. This is
where I am confused of how to define a shared disk in a majority node
cluster. Could you please point out what I am doing wrong? If I get past
the
point of being able to see my LOCAL C Drive ot LOCAL G Drive I would be
home
free. But I don't see any drives in the drop down list.
Your help is SO GREATLY APPRECIATED! Thank you again for your post!!! Look
forward to your reply!!

--
Best Regards
Fred


""Elden Christensen [MSFT]"" wrote:

Hi Fred,

Setting your quorum model to MNS just resolves the core services needs
for
a shared disk, it does not address application needs.
Print Clusters require a shared disk, here's a whitepaper I've ground out
that will walk you through getting it all setup.
http://www.microsoft.com/WindowsServer2003/techinfo/overview/availableprinte
r.mspx

Thanks!!
Elden Christensen
Program Manager
Windows Failover Cluster Group
Microsoft Enterprise Server Products


Of course, this posting wouldn't be complete without a nice, juicy
disclaimer from our lawyers: This posting is provided "AS IS" with no
warranties, and confers no rights. You assume all risk for your use. ©
2006
Microsoft Corporation. All rights reserved.
http://www.microsoft.com/info/cpyright.htmHi Fred,






.



Relevant Pages

  • Re: Correcting corrupt $MFT on shared clustered disk.
    ... against a cluster disk. ... handles against the disk. ... After digging into it I figured out I didn't need the extended maintenance mode and figured out the rest of the article. ... If I assign drives for different areas, I figure we'll eventually end up with the same problem we had before: some areas running out of space and others with space to spare. ...
    (microsoft.public.windows.server.clustering)
  • Re: Correcting a corrupted $MFT on a shared clustered disk
    ... Also, the problem I'm having is on the smaller basic disk, the GPT one is ... When I do run chkdsk, are there any special issues with the cluster? ... The three drives are a 500MB for the quorum, ...
    (microsoft.public.windows.server.general)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... > 4) assume the Old disk drive is O: and the New disk Drive is N: ... > 4) Create a new Disk Resource for the new disk and have that in the SQL ... Server Cluster running SQL 2000. ... >>drives popped right back in place with their original drive letters back. ...
    (microsoft.public.windows.server.clustering)
  • Phisical disk resource
    ... I'm setting up a 2 node cluster under 2003 ent. ... is working but I am not able to bring the shared disk ... INFO FmpPropagateResourceState: resource a94c4968- ... INFO Physical Disk: ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... Isin't the W2K3 Cluster Server Recovery tool designed to ... > 4) assume the Old disk drive is O: and the New disk Drive is N: ... > 4) Create a new Disk Resource for the new disk and have that in the SQL ... >>just fine but not the data drives, basically on step 14 my old drives ...
    (microsoft.public.windows.server.clustering)

Loading