I installed box A (OES2SP1) and configured an
iPrint service on it (created driver store and
print manager). The start of rcnovell-ipsmd and
rcnovell-idsd is ok.
Now I installed box B (OES2SP1).
Is it possible to use the iPrint service of box A
on server B?
If I want to start idsd, I receive the
following error message on box B:
"Starting Novell iPrint DriverStore: ... service not
configured"
Now my question:
can I use the iPrint service of box A on box B and
what must I keep in mind for manual failover if
box A crashes (without! NCS)?
Best regards,
Bernhard
thanks for the tip, but our 2 boxes are located
in 2 SANs (different locations).
Therefore I think, hartbeat can't be a solution for us.
But the approach with rsync to keep the driver
store synced is worth the trouble to test.
Thx
Bernhard
brunold schrieb:
> Bernhard,
>
> take a look at this communities article:
>
> 'Building an iPrint Cluster Using Heartbeat and OES Linux | Novell User
> Communities'
> (http://www.novell.com/communities/node/1850/building-iprint-cluster-using-heartbeat-and-oes-linux)
>
> We run iprint on a heartbeat cluster where we use drbd to synchronize
> the iprint manager database between the two nodes. Heartbeat controls
> idsd, ipsmd, the drbd mirror as well as a virtual ip where the clients
> print to.
>
> Rainer
>
>
I've done on box B:
- copied iPrint files and folders from box A to box B:
# scp -r <user>@<ip_address_of_box_a>:/etc/opt/novell/iprint/*
/etc/opt/novell/iprint
# scp -r <user>@<ip_address_of_box_a>:/var/opt/novell/iprint/*
/var/opt/novell/iprint
# cd /etc/opt/novell/iprint/conf
# rm ipsmd.conf
# ln -l PrintManager.Context.ipsmd.conf ipsmd.conf
- then changed the DNS entry for the iPrint server.
The DNS entry for the iPrint server points now to box B.
- start services:
# rcnovell-idsd start => ok
# rcnovell-ipsmd start => ok
Next topic will be not to use "scp" for manual copy but
"rsync" for automatical synchronization.
Bernhard
brunold schrieb:
> Bernhard,
>
> I thought also about checking the config in that article regarding a
> virtual ip address where the idsd is listening on and the configuration
> of the idsd and ipsmd. That is what you need to take care that when you
> want to start the idsd on a different node, you need wto work with a
> virtual ip address.
>
> Rainer
>
>