by PJacob » Thu Nov 13, 2008 2:54 pm
Hello,
I have setup:
1. V/M Win2k8 enterprise ( named PS1, print server 1 )
2. V/M Win2k8 enterprise ( named PS2, print server 2 )
3. V/M Win2k8 standard ( named PSQ, print server quorum )
I also followed the wonderfull instructions from the site to create the
iScsi Q:\ quorum disk, and the the R:\ generic drive.
I then created a cluster called PSC "print server cluster"...
at this point everything is looking great...
my goal is to create a "clustered" print server...
I then go into the "Failover Cluster Management" MMC,
and add "print server" in the "Services and Applications" that I want
to make as "high availability"...
I then proceed and create something called "PMS" (print management system) this is where all my printers will be installed on.
is this clear so far? it appears that all information on the printers I create
on "PMS" use the R:\ (generic) drive to store the printer information,
so that if the cluster needs to fail-over it can do so...
I guess that my point is that if the server running the starwind iScsi software goes down what happens? I currently have this up and running and when I simulated a crash on the server running starwind iScsi "PSQ",
the cluster "PSC" ran fine, but the service I need high availablity did not run "PMS" the printing services for MS.
I hope all this makes sense... in a physical world the quorum disk and the shared storage on a sans would be redundant with multiple storage processors and multiple san switches... can starwind somehow be configured to be more high-availabilty? in case the server running starwind iScsi crashes?
p.s. I do really like your product it runs very well, I can tell you guys are a hardworking bunch that is dedicated to making a quaility product.