mmsdrrestore command
Restores the latest GPFS™ system files on the specified nodes.
Synopsis
mmsdrrestore [-p NodeName] [-F mmsdrfsFile] [-R remoteFileCopyCommand]
[-a | -N {Node[,Node...] | NodeFile | NodeClass}]
Availability
Available on all IBM Spectrum Scale™ editions.
Description
The mmsdrrestore command is intended for use by experienced system administrators.
Use the mmsdrrestore command to restore the latest GPFS system files on the specified nodes. If no nodes are specified, the command restores the configuration information only on the node on which is it run. If the local GPFS configuration file is missing, the file that is specified with the -F option from the node that is specified with the -p option is used instead. This command works best when used with the mmsdrbackup user exit. See mmsdrbackup user exit.
Parameters
- -p NodeName
- Specifies the node from which to obtain a valid GPFS configuration file. The node must be either the primary configuration server or a node that has a valid backup copy of the mmsdrfs file. If not specified, the local node is used.
- -F mmsdrfsFile
- Specifies the path name of the GPFS configuration file for the mmsdrrestore command to use. This configuration file might be the current one on the primary server, or it might be a configuration file that is obtained from the mmsdrbackup user exit. If not specified, /var/mmfs/gen/mmsdrfs is used.
-
If the configuration file is a Cluster Configuration Repository (CCR) backup file, then you must also specify the -a option. All the nodes in the cluster are restored. However, if a configuration of the cluster is still available, you can restore the configuration of an individual node by running mmsdrrestore -p.
- -R remoteFileCopyCommand
- Specifies the fully qualified path name for the remote file copy program to be used for obtaining the GPFS configuration file. The default is /usr/bin/rcp.
- -a
- Restores the GPFS configuration files on all nodes in the cluster.
- -N {Node[,Node...] | NodeFile | NodeClass}
- Restores the GPFS configuration
files on a set of nodes.
For general information on how to specify node names, see Specifying nodes as input to GPFS commands.
This command does not support a NodeClass of mount.
Exit status
- 0
- Successful completion.
- nonzero
- A failure occurred.
Security
You must have root authority to run the mmsdrrestore command.
The node on which the command is issued must be able to run remote shell commands on any other node in the cluster without the use of a password and without producing any extraneous messages.For more information, see Requirements for administering a GPFS file system.
Examples
- To restore the latest GPFS system
files on the local node using the GPFS configuration
file /var/mmfs/gen/mmsdrfs from the node
that is named primaryServer, issue the following
command:
mmsdrrestore -p primaryServer
The system displays output similar to the following example:Tue Jul 3 18:19:53 CDT 2012: mmsdrrestore: Processing node k164n04.kgn.ibm.com mmsdrrestore: Node k164n04.kgn.ibm.com successfully restored.
- To restore the GPFS system
files on all nodes in the cluster using GPFS configuration
file /GPFSconfigFiles/mmsdrfs.120605 on
the node that is named GPFSarchive, issue
the following command from the node named localNode:
mmsdrrestore -p GPFSarchive -F /GPFSconfigFiles/mmsdrfs.120605 -a
The system displays output similar to the following example:Tue Jul 3 18:29:28 CDT 2012: mmsdrrestore: Processing node k164n04.kgn.ibm.com Tue Jul 3 18:29:30 CDT 2012: mmsdrrestore: Processing node k164n05.kgn.ibm.com Tue Jul 3 18:29:31 CDT 2012: mmsdrrestore: Processing node k164n06.kgn.ibm.com mmsdrrestore: Command successfully completed
- The following command restores the GPFS system
files from the information in a Cluster Configuration Repository (CCR) backup
file. When you restore from a CCR backup file, you must specify the -a option.
All the nodes in the cluster are restored:
The command displays output similar to the following example:mmsdrrestore -F /GPFSbackupFiles/CCRBackup.2015.10.14.10.01.25.tar.gz -a
Restoring CCR backup CCR backup has been restored