Windows 2003 Print Clusters - Part Three: Troubleshooting Missing Print Queues

re: Windows 2003 Print Clusters - Part Three: Troubleshooting Missing Print Queues

Robert A. — Tue, 07 Aug 2007 18:07:08 GMT

I'm trying to synthesize some of this information into more generalized cluster info:

Based on the description in this series about how the ClusDB works, it sounds like each node in a cluster hosts it's own stand-alone JET-engine clusDB, but all nodes SHARE a logfile. Upon failover, the new owner replays the logfile, committing all uncommited transactions to its own local copy of the DB.

However, this wouldn't work if the Quorum group were on a different node than the (for example) Exchange group, because the node wouldn't be able to write the creation of a new resource, such as a POP3 service, to the Quorum log, since it only owns the Exchange group, and not the Quorum group (andit's associated disk).

So how exactly are these changes committed across all members of a multi-node cluster? Is there RPC traffic sent to the Quorum Network Name (I don't have a test cluster to take down the quorum and try to create a resource while sniffing the private and public nets)? How are those changes commited to non-active nodes, or offline nodes?

Thanks in advance.

re: Windows 2003 Print Clusters - Part Three: Troubleshooting Missing Print Queues

Sumesh — Thu, 13 Sep 2007 14:42:26 GMT

You are right, it becomes the duty of the node owning the quorum resource to update the quorum logs

re: Windows 2003 Print Clusters - Part Three: Troubleshooting Missing Print Queues

Shawn Yong — Thu, 17 Jan 2008 04:00:56 GMT

anyone done activite/active clustered print server before?

i'm not able to create 2 print$ share folder on the 2 group. duplicate share name was the messsage. i'm looking solution that will enable me to point the drivers to print1$ and print2$. Not sure will there be other better options then above. Thanks.