• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1229
  • Last Modified:

Printer Server disaster recover on VMware

I am planning to create print server on VMware. We need to have a disaster recover plan. What is the best practice for this? Should we use clustering? How will the failover work? Thanks
0
dongocdung
Asked:
dongocdung
6 Solutions
 
jhyieslaCommented:
It depends on your tolerance for having a printer server down.

Although printing is important in our environment, we would not cease to exist if we could not print for a short period of time.   From my standpoint, which obviously is different than yours, clustering seems like overkill.  

For myself, I would do a couple of things.  First, I would create the print server and then make a clone of it that could be stored off site or on another server. As long as the underlying hardware is solid, that should get you back up in short order.  I would also use the MS printmig3 program to make a copy of all of the printers and their settings. This would allow you on a new server to quickly reestablish all of your printers. If you have more than one VM and are using vMotion, that is another thing that should help protect you server.  

The bigger picture is that you should have an overall DR plan that would take into account all of your servers, whether physical or virtual.

The MS print migrator program can be found at http://www.microsoft.com/downloads/details.aspx?FamilyID=D6915F13-EDE4-4708-83C1-0091EEADE293&displaylang=en
0
 
65tdCommented:
Agree with the points above.  MSCS adds additional complexity, maybe better utilize two stand alone prt servers.

We use a virtual print server in ESX 3.5 DRA/HA cluster, living on a SAN (single point of failure, no replication of SAN).
Use VCB to back the server up and figure recovery time would be short.
0
 
MrMintanetCommented:
Being it is a print server, just backup the virtual machine's configuration and virtual disk after you have finished configuring the server.  Then, if the virtual print server crashes, just use your backup by simply dragging and dropping the backup information to the appropriate location that VMWare is pointing to.  This is not hard.
0
Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

 
MrMintanetCommented:
As for "failover".  Being it is a print server and not an exchange server, I would suggest to simply create 2 separate print servers.  Then have the users able to use either print server from their predefined printer list.
0
 
markzzCommented:
I largely agree with the above but not entirely.
Create 2 Print servers is fine, forget clustering it's over kill for such a simple process.
Microsoft have a printer migration wizard which if I recall can be used via the command line.
This tools could be used to script the export of the printers, configuration and drivers on your Prod Print Server and of course the import of this on the DR Print server. In the event of DR you would have to add a registry entry on the DR Print server which gives it a second host name (google adding a second host name Windows 2003) and you would have to edit DNS  and point the prod servers host record at the DR Print Server.
It may not be hot failover but it's pretty quick.
Of course there is no replacement for backups so VCB the Prod Print Server regularly.
0
 
MrMintanetCommented:
If you want a ridiculously simple solution, schedule a an event to occur from control panel.

Schedule a script to ping the print server

IF ping fails

Execute startup of other VMware Print Server

How to script this:
http://www.petri.co.il/virtual_script_startup_shutdown_vmware_servers.htm

IF ping sucessful

End Script

Good Luck
0
 
markzzCommented:
This is an interesting idea MrMintanet and one I can see could be very useful indead, but bringing up a print server that doesn't have the necessary printers configured would be futile.
I guess a hot clone could be done of the print server to another name but then you have the issue of what IP will it need in the DR siite.
To avoid these complications you could even script the export and import of printer configurations, DNS changes and registry import
Print migrator http://www.microsoft.com/windowsserver2003/techinfo/overview/printmigrator3.1.mspx
The registry changes can be made with the reg.exe command
DNS edit the DNS via the CLI util DNSCMD.exe http://www.windowsreference.com/dns/dnscmdexe-dns-server-command-line-utility-for-windows-dns/
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now