Backing up and restoring Flexible Storage Sharing disk group configuration data

The disk group configuration backup and restoration feature also lets you back up and restore configuration data for Flexible Storage Sharing (FSS) disk groups. The vxconfigbackupd daemon automatically records any configuration changes that occur on all cluster nodes. When restoring FSS disk group configuration data, you must first restore the configuration data on the secondary (slave) nodes in the cluster, which creates remote disks by exporting any locally connected disks. After restoring the configuration data on the secondary nodes, you must restore the configuration data on the primary (master) node that will import the disk group.

To back up FSS disk group configuration data

To restore the configuration data for an FSS disk group

  1. Identify the master node:
    # vxclustadm nidmap
  2. Check if the primary node has connectivity to at least one disk in the disk group. The disk can be a direct attached storage (DAS) disk, partially shared disk, or fully shared disks.
  3. If the primary node does not have connectivity to any disk in the disk group, switch the primary node to a node that has connectivity to at least one DAS or partially shared disk, using the following command:
    # vxclustadm setmaster node_name
  4. Restore the configuration data on all the secondary nodes:
    # vxconfigrestore diskgroup

    Note:

    You must restore the configuration data on all secondary nodes that have connectivity to at least one disk in the disk group.

  5. Restore the configuration data on the primary node:
    # vxconfigrestore diskgroup
  6. Verify the configuration data:
    # vxprint -g diskgroup
  7. If the configuration data is correct, commit the configuration:
    # vxconfigrestore -c diskgroup

To abort or decommit configuration restoration for an FSS disk group

  1. Identify the master node:
    # vxclustadm nidmap
  2. Abort or decommit the configuration data on the master node:
    # vxconfigrestore -d diskgroup
  3. Abort or decommit the configuration data on all secondary nodes.
    # vxconfigrestore -d diskgroup

    Note:

    You must abort or decommit the configuration data on all secondary nodes that have connectivity to at least one disk in the disk group, and all secondary nodes from which you triggered the precommit.

See the Veritas InfoScale 7.0 Troubleshooting Guide.

See the vxconfigbackup(1M) manual page.

See the vxconfigrestore(1M) manual page.