What is the effect of /usr/es/sbin/cluster/utilities/clfileprop -m <collections>

I have a 2-node cluster that I've been failing back and forth. The problem is that changes I make to my startup script on the receiving node keeps getting overwritten by the source node - even though the version on the source node is the once most recently updated. As part of the fallover procedure, the application stop script on the source node includes the following:

/usr/es/sbin/cluster/utilities/clfileprop -m collection1 collection2... collectionn

My understanding is that the propagation process is supposed to push the newest version to all nodes in the cluster. So, when I run the clfileprop command, shouldn't it recognize that the version of the file on the standby node is newer and update all nodes with that version?
babyb00merAsked:
Who is Participating?
 
woolmilkporcConnect With a Mentor Commented:
Hi,

when running clfileprop manually the node from which this command is issued becomes the "propagation" node,
and the files of this node will be propagated to all other nodes, regardless of their age.

The same is true if the option to "propagate filecollections whenever cluster verification and synchronization is executed" is set.
The node from which verification is run is the propagation node.

The behaviour you desire can only be achieved when setting the option to "propagate the file collection automatically
after a change to one of the files in the collection."
HACMP checks the file collection status on each node (every 10 minutes by default) and propagates any changes.
This way any node which has a newer version of a file becomes the propagation node and consequently pushes this file
to the other nodes.

wmp
0
All Courses

From novice to tech pro — start learning today.