Creating A Cluster Printer Spooler; Advanced Cluster Administration Procedures; Failing Over And Failing Back - HP StorageWorks P4000 G2 User Manual

Creating a cluster printer spooler

Printer spoolers should be created in a separate group dedicated to this purpose for ease of
management. For each printer spooler, a physical resource is required to instantiate the print spooler
resource. In some cases, dedicated physical resources are not available and hence sharing of the
physical resource among other members of the group is acceptable, remembering that all members
of a group are managed as a unit. Hence, the group will failover and failback as a group.
To create a printer spooler:
1. Create a dedicated group (if desired).
2. Create a physical resource (disk) (if required, see note).
3. Create an IP address resource for the Virtual Server to be created (if required, see note).
4. Create a Virtual Server Resource (Network Name) (if required, see note).
NOTE:
If the printer spool resource is added to an existing group with a physical resource, IP
address, and virtual server resource, steps 1-4 are not required.
5. Create a Print Spool resource.
6. To add a printer to the virtual server:
a. Double-click the printers and faxes icon.
b. Right-click the new screen, and then click add printer. A wizard starts.
c. Click create a new port, and then click Next.
d. Enter the IP address of the network printer.
e. Update the Port Name if desired, click Next, and then click Finish.
f. Select the appropriate driver, and then click Next.
g. If presented with a dialog to replace the driver present, click keep the driver, and then click
Next.
h. Name the printer, and then click Next.
i. Provide a share name for the printer for network access, and then click Next.
j. Provide location information and comments, and then click Next.
k. Click Yes to print a test page, click Next, and then click Finish.
l. A dialog box appears regarding the test page. Select the appropriate answer.
The Printer Spool is now a clustered resource.

Advanced cluster administration procedures

Failing over and failing back

As previously mentioned, when a node goes offline, all resources dependent on that node are
automatically failed over to another node. Processing continues, but in a reduced manner, because
all operations must be processed on the remaining node(s). In clusters containing more than two
nodes, additional fail over rules can be applied. For instance, groups can be configured to fail over
different nodes to balance the additional work load imposed by the failed node. Nodes can be
48 Cluster administration