So, I've been following this thread closely as we have recently been thinking about creating some sort of better redundancy for our main print server.
Right now, I have printmig set up to export daily--we could do the import and re-point people to another server in a pinch. We don't need to be 24/7, but would like to eliminate the whole re-pointing step if something were to happen. We have various printer models, including HP, Dell, Brother, and Canon amongst others, with drivers ranging from PCL5, PCL6, PS, and HP's Universal (newest printers only). I had been thinking about whether we should look at building a print cluster--sounds like many folks have had issues with this? I would probably rebuild from scratch (or migrate using MS's new "upgrade" method, but there are a lot of drivers to reinstall) on WS08 clustering. I've not actually done any Windows clustering before (besides NLB) so there is a learning curve here. We are also in the throes of a virtualization project. We are more than likely going Hyper-V on a new Dell Equallogic SAN array. So, another option that comes to mind is once we virtualize, keep a backup of the virtual machine handy that we could just spin up on another host and array should the first one fail. I understand that this would not be any sort of "live" migration--we're okay with that. If we did the clustering, it would still be virtualized. Given these options, does anyone have any preferences, and why? -Bonnie ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
