Can you update cluster configuration without stopping application

[Adam Noble]

Hi,

We have a slight issue. One of our servers within a cluster had to be re-built with ignite. The problem is it cam back with different device paths to the EMC disks. This causes me an issue as the cluster configuration file points to a lock disk for this server which does not exist. I therefore need to ammend the configuration to reflect the new path. I am assuming I will have to stop the cluster to do this and therefore the package running my application. Is this correct. This is service-guard by the way.

Cheers

[melvyn burnard · Accepted solution]

If the path to your lock disc has changed, you will have to halt the cluster, make the relevant change in the ascii file, and then reapply the configuration.

[Helpdesk USE-HP]

If your application has down time then it is best to change your SG config but if your application is like some of the ones that I have and you don't have any down time. Then, you might try running the attached procedure. It requires a couple of reboots to the server that you rebuilt but you can change the instance numbers of the disks to sync up the names of the disks between the two servers. This makes it nice any easy when you are doing other maintenance on your cluster. It will also make it so that you can have your old instance names and won't have to bring down your cluster.

Good luck,
Rob
attachment deleted due to contravention of ITRC guidelines