Storage Foundation for Oracle® RAC 7.3.1 Administrator's Guide - Linux
- Section I. SF Oracle RAC concepts and administration
- Overview of Storage Foundation for Oracle RAC
- About Storage Foundation for Oracle RAC
- Component products and processes of SF Oracle RAC
- About Virtual Business Services
- Administering SF Oracle RAC and its components
- Administering SF Oracle RAC
- Starting or stopping SF Oracle RAC on each node
- Administering VCS
- Administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- Administering the CP server
- Administering CFS
- Administering CVM
- Changing the CVM master manually
- Administering Flexible Storage Sharing
- Backing up and restoring disk group configuration data
- Administering SF Oracle RAC global clusters
- Administering SF Oracle RAC
- Overview of Storage Foundation for Oracle RAC
- Section II. Performance and troubleshooting
- Troubleshooting SF Oracle RAC
- About troubleshooting SF Oracle RAC
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the SF Oracle RAC cluster nodes
- Issues during online migration of coordination points
- Troubleshooting Cluster Volume Manager in SF Oracle RAC clusters
- Troubleshooting CFS
- Troubleshooting interconnects
- Troubleshooting Oracle
- Troubleshooting ODM in SF Oracle RAC clusters
- Prevention and recovery strategies
- Tunable parameters
- Troubleshooting SF Oracle RAC
- Section III. Reference
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 back up FSS disk group configuration data on all cluster nodes that have connectivity to at least one disk in the disk group, type the following command:
# /etc/vx/bin/vxconfigbackup -T diskgroup
To restore the configuration data for an FSS disk group
- Identify the master node:
# vxclustadm nidmap
- 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.
- 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
- 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.
- Restore the configuration data on the primary node:
# vxconfigrestore diskgroup
- Verify the configuration data:
# vxprint -g diskgroup
- If the configuration data is correct, commit the configuration:
# vxconfigrestore -c diskgroup
To abort or decommit configuration restoration for an FSS disk group
- Identify the master node:
# vxclustadm nidmap
- Abort or decommit the configuration data on the master node:
# vxconfigrestore -d diskgroup
- 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.3.1 Troubleshooting Guide.
See the vxconfigbackup(1M) manual page.
See the vxconfigrestore(1M) manual page.