test

Sun Cluster System Administration Guide for Solaris OS

ProcedureHow to Provoke a Switchover

  1. Access nodeA and nodeC as superuser or assume a role that provides solaris.cluster.admin RBAC authorization.

  2. Change the primary cluster to logging mode.

    • For Sun StorEdge Availability Suite software:


      nodeA# /usr/opt/SUNWesm/sbin/sndradm -n -l lhost-reprg-prim \
/dev/vx/rdsk/devgrp/vol01 \
/dev/vx/rdsk/devgrp/vol04 lhost-reprg-sec \
/dev/vx/rdsk/devgrp/vol01 \
/dev/vx/rdsk/devgrp/vol04 ip sync

    • For Sun StorageTek Availability Suite software:


      nodeA# /usr/sbin/sndradm -n -l lhost-reprg-prim \
/dev/vx/rdsk/devgrp/vol01 \
/dev/vx/rdsk/devgrp/vol04 lhost-reprg-sec \
/dev/vx/rdsk/devgrp/vol01 \
/dev/vx/rdsk/devgrp/vol04 ip sync

    When the data volume on the disk is written to, the bitmap volume on the same device group is updated. No replication occurs.

  3. Confirm that the primary cluster and the secondary cluster are in logging mode, with autosynchronization off.

    1. On nodeA, confirm the mode and setting:

      • For Sun StorEdge Availability Suite software:


        nodeA# /usr/opt/SUNWesm/sbin/sndradm -P

      • For Sun StorageTek Availability Suite software:


        nodeA# /usr/sbin/sndradm -P

      The output should resemble the following:


      /dev/vx/rdsk/devgrp/vol01 ->
lhost-reprg-sec:/dev/vx/rdsk/devgrp/vol01
autosync:off, max q writes:4194304,max q fbas:16384,mode:sync,ctag:
devgrp, state: logging

    2. On nodeC, confirm the mode and setting:

      • For Sun StorEdge Availability Suite software:


        nodeC# /usr/opt/SUNWesm/sbin/sndradm -P

      • For Sun StorageTek Availability Suite software:


        nodeC# /usr/sbin/sndradm -P

      The output should resemble the following:


      /dev/vx/rdsk/devgrp/vol01 <-
lhost-reprg-prim:/dev/vx/rdsk/devgrp/vol01
autosync:off, max q writes:4194304,max q fbas:16384,mode:sync,ctag:
devgrp, state: logging

    For nodeA and nodeC, the state should be logging, and the active state of autosynchronization should be off.

  4. Confirm that the secondary cluster is ready to take over from the primary cluster.


    nodeC# fsck -y /dev/vx/rdsk/devgrp/vol01

  5. Switch over to the secondary cluster.


    nodeC# clresourcegroup switch -n nodeC nfs-rg
Next Steps

Go to How to Update the DNS Entry.