Print Server fail over issue clawless 11.07.2007 19:04:03 Hello, We have an active/active print server cluster. When it fails over there is an odd issue. Node 1 has "alpha" print spooler and node 2 has "beta" print spooler. When all is normal, you bring up \\alpha you see the printer on alpha, same with beta, however, when alpha fails over and you use \\alpha you see printers from alpha and beta intermixed and many printers from alpha are missing. Also while failed over if you go to \\beta, you see the same list. The same thing occurs when beta fails over. You get the same list on both alpha and beta however many beta printers are missing. ideas?

Re: Print Server fail over issue "Russ Kaufmann [MVP]" <russ[ at ]clusterhelp.com> 11.07.2007 22:04:05 "clawless" <clawless[ at ]discussions.microsoft.com> wrote in message news:384EA9B5-3D6A-4CB5-8B45-134AB39FA8B1[ at ]microsoft.com... [Quoted Text] > Hello, > > We have an active/active print server cluster. When it fails over there is > an odd issue. > > Node 1 has "alpha" print spooler and node 2 has "beta" print spooler. > When > all is normal, you bring up \\alpha you see the printer on alpha, same > with > beta, however, when alpha fails over and you use \\alpha you see printers > from alpha and beta intermixed and many printers from alpha are missing. > Also while failed over if you go to \\beta, you see the same list. The > same > thing occurs when beta fails over. You get the same list on both alpha > and > beta however many beta printers are missing. That is expected behavior. It is possible, in Windows Server 2008, to use scoping to stop it from appearing this way. Printers should not be missing unless they were not properly created in the cluster. -- Russ Kaufmann MVP - Windows Server - Clustering ClusterHelp.com, a Microsoft Certified Gold Partner Web http://www.clusterhelp.com Blog http://msmvps.com/clusterhelp The next ClusterHelp classes are: July 10-13 in Denver July 16-19 in New York Sep 3 - 6 in Copenhagen

Re: Print Server fail over issue "Chuck [MSFT]" <ctimon[ at ]online.microsoft.com> 12.07.2007 00:49:45 Give us a feel for how many printers alpha and beta are each supporting separately? Then tell us what the value is for your Quorum Log size. -- Chuck Timon, Jr. Microsoft Corporation Windows Server 2008 Readiness Team This posting is provided 'AS IS" with no warranties, and confers no rights. "clawless" <clawless[ at ]discussions.microsoft.com> wrote in message news:384EA9B5-3D6A-4CB5-8B45-134AB39FA8B1[ at ]microsoft.com... [Quoted Text] > Hello, > > We have an active/active print server cluster. When it fails over there is > an odd issue. > > Node 1 has "alpha" print spooler and node 2 has "beta" print spooler. > When > all is normal, you bring up \\alpha you see the printer on alpha, same > with > beta, however, when alpha fails over and you use \\alpha you see printers > from alpha and beta intermixed and many printers from alpha are missing. > Also while failed over if you go to \\beta, you see the same list. The > same > thing occurs when beta fails over. You get the same list on both alpha > and > beta however many beta printers are missing. > > ideas? > >

Re: Print Server fail over issue clawless 12.07.2007 13:16:04 Thank you for the replies. Alpha currently has 83 printers and beta has 67. The quorum log is currently is 32KB. It is set to the default max of 4MB. Based on this question I found this article: http://support.microsoft.com/kb/257897. I am guessing I should increase this as the clusdb file is just over 6 MB.... - Clawless "Chuck [MSFT]" wrote: [Quoted Text] > Give us a feel for how many printers alpha and beta are each supporting > separately? Then tell us what the value is for your Quorum Log size. > > -- > Chuck Timon, Jr. > Microsoft Corporation > Windows Server 2008 Readiness Team > This posting is provided 'AS IS" with no warranties, and confers no rights. > "clawless" <clawless[ at ]discussions.microsoft.com> wrote in message > news:384EA9B5-3D6A-4CB5-8B45-134AB39FA8B1[ at ]microsoft.com... > > Hello, > > > > We have an active/active print server cluster. When it fails over there is > > an odd issue. > > > > Node 1 has "alpha" print spooler and node 2 has "beta" print spooler. > > When > > all is normal, you bring up \\alpha you see the printer on alpha, same > > with > > beta, however, when alpha fails over and you use \\alpha you see printers > > from alpha and beta intermixed and many printers from alpha are missing. > > Also while failed over if you go to \\beta, you see the same list. The > > same > > thing occurs when beta fails over. You get the same list on both alpha > > and > > beta however many beta printers are missing. > > > > ideas? > > > > >

Re: Print Server fail over issue "Ryan Sokolowski [MVP]" <ryan[ at ]clustering101.com> 12.07.2007 17:14:53 Good call...you should increase this to around 12228 KB or more if you wish / expect more printers in the future. -- Ryan Sokolowski MVP - Windows Server - Clustering MCSE, CCNA, CCDA, BCFP This posting is provided "AS IS" with no warranties, and confers no rights. "clawless" <clawless[ at ]discussions.microsoft.com> wrote in message news:B6757905-9C89-4B07-9C67-B8180022FC67[ at ]microsoft.com... [Quoted Text] > Thank you for the replies. > > Alpha currently has 83 printers and beta has 67. The quorum log is > currently is 32KB. It is set to the default max of 4MB. Based on this > question I found this article: http://support.microsoft.com/kb/257897. I > am > guessing I should increase this as the clusdb file is just over 6 MB.... > > - Clawless > > > > "Chuck [MSFT]" wrote: > >> Give us a feel for how many printers alpha and beta are each supporting >> separately? Then tell us what the value is for your Quorum Log size. >> >> -- >> Chuck Timon, Jr. >> Microsoft Corporation >> Windows Server 2008 Readiness Team >> This posting is provided 'AS IS" with no warranties, and confers no >> rights. >> "clawless" <clawless[ at ]discussions.microsoft.com> wrote in message >> news:384EA9B5-3D6A-4CB5-8B45-134AB39FA8B1[ at ]microsoft.com... >> > Hello, >> > >> > We have an active/active print server cluster. When it fails over there >> > is >> > an odd issue. >> > >> > Node 1 has "alpha" print spooler and node 2 has "beta" print spooler. >> > When >> > all is normal, you bring up \\alpha you see the printer on alpha, same >> > with >> > beta, however, when alpha fails over and you use \\alpha you see >> > printers >> > from alpha and beta intermixed and many printers from alpha are >> > missing. >> > Also while failed over if you go to \\beta, you see the same list. The >> > same >> > thing occurs when beta fails over. You get the same list on both alpha >> > and >> > beta however many beta printers are missing. >> > >> > ideas? >> > >> > >>

Re: Print Server fail over issue clawless 12.07.2007 17:32:03 Will do. I also found out that a few of our tech are not following the SOP for creating printers. Several of the "missing" printers are there but are just not printing, need to create the TCP/IP port on both servers.... Thanks!!! - Clawless "Ryan Sokolowski [MVP]" wrote: [Quoted Text] > Good call...you should increase this to around 12228 KB or more if you wish > / expect more printers in the future. > > -- > Ryan Sokolowski > MVP - Windows Server - Clustering > MCSE, CCNA, CCDA, BCFP > > > This posting is provided "AS IS" with no warranties, and confers no rights. > "clawless" <clawless[ at ]discussions.microsoft.com> wrote in message > news:B6757905-9C89-4B07-9C67-B8180022FC67[ at ]microsoft.com... > > Thank you for the replies. > > > > Alpha currently has 83 printers and beta has 67. The quorum log is > > currently is 32KB. It is set to the default max of 4MB. Based on this > > question I found this article: http://support.microsoft.com/kb/257897. I > > am > > guessing I should increase this as the clusdb file is just over 6 MB.... > > > > - Clawless > > > > > > > > "Chuck [MSFT]" wrote: > > > >> Give us a feel for how many printers alpha and beta are each supporting > >> separately? Then tell us what the value is for your Quorum Log size. > >> > >> -- > >> Chuck Timon, Jr. > >> Microsoft Corporation > >> Windows Server 2008 Readiness Team > >> This posting is provided 'AS IS" with no warranties, and confers no > >> rights. > >> "clawless" <clawless[ at ]discussions.microsoft.com> wrote in message > >> news:384EA9B5-3D6A-4CB5-8B45-134AB39FA8B1[ at ]microsoft.com... > >> > Hello, > >> > > >> > We have an active/active print server cluster. When it fails over there > >> > is > >> > an odd issue. > >> > > >> > Node 1 has "alpha" print spooler and node 2 has "beta" print spooler. > >> > When > >> > all is normal, you bring up \\alpha you see the printer on alpha, same > >> > with > >> > beta, however, when alpha fails over and you use \\alpha you see > >> > printers > >> > from alpha and beta intermixed and many printers from alpha are > >> > missing. > >> > Also while failed over if you go to \\beta, you see the same list. The > >> > same > >> > thing occurs when beta fails over. You get the same list on both alpha > >> > and > >> > beta however many beta printers are missing. > >> > > >> > ideas? > >> > > >> > > >> > > >

Re: Print Server fail over issue "Chuck [MSFT]" <ctimon[ at ]online.microsoft.com> 12.07.2007 17:33:37 Yes you should. -- Chuck Timon, Jr. Microsoft Corporation Windows Server 2008 Readiness Team This posting is provided 'AS IS" with no warranties, and confers no rights. "clawless" <clawless[ at ]discussions.microsoft.com> wrote in message news:B6757905-9C89-4B07-9C67-B8180022FC67[ at ]microsoft.com... [Quoted Text] > Thank you for the replies. > > Alpha currently has 83 printers and beta has 67. The quorum log is > currently is 32KB. It is set to the default max of 4MB. Based on this > question I found this article: http://support.microsoft.com/kb/257897. I > am > guessing I should increase this as the clusdb file is just over 6 MB.... > > - Clawless > > > > "Chuck [MSFT]" wrote: > >> Give us a feel for how many printers alpha and beta are each supporting >> separately? Then tell us what the value is for your Quorum Log size. >> >> -- >> Chuck Timon, Jr. >> Microsoft Corporation >> Windows Server 2008 Readiness Team >> This posting is provided 'AS IS" with no warranties, and confers no >> rights. >> "clawless" <clawless[ at ]discussions.microsoft.com> wrote in message >> news:384EA9B5-3D6A-4CB5-8B45-134AB39FA8B1[ at ]microsoft.com... >> > Hello, >> > >> > We have an active/active print server cluster. When it fails over there >> > is >> > an odd issue. >> > >> > Node 1 has "alpha" print spooler and node 2 has "beta" print spooler. >> > When >> > all is normal, you bring up \\alpha you see the printer on alpha, same >> > with >> > beta, however, when alpha fails over and you use \\alpha you see >> > printers >> > from alpha and beta intermixed and many printers from alpha are >> > missing. >> > Also while failed over if you go to \\beta, you see the same list. The >> > same >> > thing occurs when beta fails over. You get the same list on both alpha >> > and >> > beta however many beta printers are missing. >> > >> > ideas? >> > >> > >>

Re: Print Server fail over issue "Chuck [MSFT]" <ctimon[ at ]online.microsoft.com> 12.07.2007 19:05:21 Yeah, need to create the printers in the context of the Virtual Server and not the local node. The big clue that something is wrong is if you go to <Start>, <Settings> and then <Printers and Faxes> on the local cluster node, and if you see printers defined there that you know are clustered printers, then there is a config problem. -- Chuck Timon, Jr. Microsoft Corporation Windows Server 2008 Readiness Team This posting is provided 'AS IS" with no warranties, and confers no rights. "clawless" <clawless[ at ]discussions.microsoft.com> wrote in message news:F25BB2D7-F17D-4215-90EC-FC9102B4868A[ at ]microsoft.com... [Quoted Text] > Will do. > > I also found out that a few of our tech are not following the SOP for > creating printers. Several of the "missing" printers are there but are > just > not printing, need to create the TCP/IP port on both servers.... > > Thanks!!! > > > - Clawless > > "Ryan Sokolowski [MVP]" wrote: > >> Good call...you should increase this to around 12228 KB or more if you >> wish >> / expect more printers in the future. >> >> -- >> Ryan Sokolowski >> MVP - Windows Server - Clustering >> MCSE, CCNA, CCDA, BCFP >> >> >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> "clawless" <clawless[ at ]discussions.microsoft.com> wrote in message >> news:B6757905-9C89-4B07-9C67-B8180022FC67[ at ]microsoft.com... >> > Thank you for the replies. >> > >> > Alpha currently has 83 printers and beta has 67. The quorum log is >> > currently is 32KB. It is set to the default max of 4MB. Based on >> > this >> > question I found this article: http://support.microsoft.com/kb/257897. >> > I >> > am >> > guessing I should increase this as the clusdb file is just over 6 >> > MB.... >> > >> > - Clawless >> > >> > >> > >> > "Chuck [MSFT]" wrote: >> > >> >> Give us a feel for how many printers alpha and beta are each >> >> supporting >> >> separately? Then tell us what the value is for your Quorum Log size. >> >> >> >> -- >> >> Chuck Timon, Jr. >> >> Microsoft Corporation >> >> Windows Server 2008 Readiness Team >> >> This posting is provided 'AS IS" with no warranties, and confers no >> >> rights. >> >> "clawless" <clawless[ at ]discussions.microsoft.com> wrote in message >> >> news:384EA9B5-3D6A-4CB5-8B45-134AB39FA8B1[ at ]microsoft.com... >> >> > Hello, >> >> > >> >> > We have an active/active print server cluster. When it fails over >> >> > there >> >> > is >> >> > an odd issue. >> >> > >> >> > Node 1 has "alpha" print spooler and node 2 has "beta" print >> >> > spooler. >> >> > When >> >> > all is normal, you bring up \\alpha you see the printer on alpha, >> >> > same >> >> > with >> >> > beta, however, when alpha fails over and you use \\alpha you see >> >> > printers >> >> > from alpha and beta intermixed and many printers from alpha are >> >> > missing. >> >> > Also while failed over if you go to \\beta, you see the same list. >> >> > The >> >> > same >> >> > thing occurs when beta fails over. You get the same list on both >> >> > alpha >> >> > and >> >> > beta however many beta printers are missing. >> >> > >> >> > ideas? >> >> > >> >> > >> >> >> >> >>