Volsave in a 5.1a cluster

From: Robert Mulley (robert.mulley@travelcorporation.com.au)
Date: Wed Jan 29 2003 - 18:09:03 EST


Hello all,

I've just upgraded a two GS320 member cluster from v5.1 to v5.1A PK3.
Upgrade went suprisingly well and I've experienced no problems except for
one thing. We daily via cron execute a volsave command to save all the LSM
configuration on the machine. The command gets executed on both nodes of the
cluster. Under 5.1 volsave command saves to a directory such as
/usr/var/lsm/db/LSM.20030129182500.hostname. However the behaviour seems
different under 5.1A and it save it under
/usr/var/lsm/db/LSM.20030129182500.clusteralias. Which means that each node
in the cluster is trying to write to the same directory. I've checked the
man page but I can't see a way I can specify to use hostname rather than
cluster alias. Has anyone else experienced this or know how to resolve the
problem.

Regards,

Robert Mulley
System Administrator
The Travel Corporation Pty Ltd
Travel House
35 Grafton Street
Woollahra NSW 2025
(02) 9028 5585



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:05 EDT