When you create a new element, it is mastered by the replica
in which you create it. You can change the mastership of the element
using the chmaster command.
About this task
You can perform the following element
operations only at the element's master replica:
- Changing identities or permissions on the element (for replicas
that preserve identities and permissions).
- Changing permissions on the element (for replicas that preserve
permissions).
- Locking the element with the obsolete option.
- Removing the element.
Procedure
- At the master replica, enter a chmaster command:
MINUTEMAN% multitool chmaster bangalore tests.txt@@
Changed mastership of file element "tests.txt@@" to "bangalore"
- At the old master replica, export and send an update packet
to the new master replica:
MINUTEMAN% multitool syncreplica –export –fship bangalore@/vobs/dev
Generating synchronization packet
/opt/devops/clearcase/shipping/ms_ship/outgoing/sync_boston_hub_0
7-Dec-02.18.15.57_5978_1
- shipping order file is
/opt/devops/clearcase/shipping/ms_ship/outgoing/sh_o_sync_boston_
hub_07-Dec-02.18.15.57_5978_1
Attempting to forward/deliver generated packets...
-- Forwarded/delivered packet
/opt/devops/clearcase/shipping/ms_ship/outgoing/sync_boston_hub_0
7-Dec-02.18.15.57_5978_1
- At the new master replica, import the packet:
RAMOHALLI> multitool syncreplica –import –receive
Applied sync. packet C:\Program
Files\DevOps\ClearCase\var\shipping\ms_ship\incoming\sync_boston_
hub_07-Dec-02.18.15.57_5978_1 to VOB \\ramohalli\vobs\dev.vbs
- At the new master replica, verify that mastership has been
received:
RAMOHALLI> multitool describe –fmt "%n\t%[master]p\n" tests.txt@@
tests.txt@@ bangalore@\dev