Restoring the object storage

You need to meet the following prerequisites before beginning the recovery procedure:

Restore the GPFS cluster with the same node names that were used during the backup procedure
Restore your OpenStack Keystone server and make sure that it is operational.
Install Swift software on any IBM Storage Scale object nodes.
Install the IBM Storage Protect backup-archive client software on the IBM Storage Scale object nodes that were clients previously.
Note: IBM Storage Scale object nodes and IBM Storage Protect client nodes need to be available when the object storage configuration and contents are being restored.

After you perform the prerequisite procedures, you can begin the recovery procedure.

Note: The sample file system that is used throughout this procedure is called smallfs. Replace this value with your file system name wherever necessary.

Retrieve the base file system configuration information.

Use the following command to generate a configuration file that contains the details of the former file system:
```
mmrestoreconfig smallfs -i /tmp/smallfs.bkpcfg.out925 -F 
smallfsQueryResultFile
```
Re-create the NSDs when they are missing.
Using the output file that is generated in the previous step as a guide, the administrator might need to re-create NSD devices for use with the restored file system. In the output file, the NSD configuration section contains the NSD information:
```
######## NSD configuration ##################
## Disk descriptor format for the mmcrnsd command.
## Please edit the disk and desired name fields to match
## your current hardware settings.
##
## The user then can uncomment the descriptor lines and
## use this file as input to the -F option.
#
# %nsd:
#   device=DiskName
#   nsd=nsd8
#   usage=dataAndMetadata
#   failureGroup=-1
#   pool=system
#
```
If changes are needed, edit the file in a text editor and follow the included instructions to use it as input for the mmcrnsd command and run the following command:
```
mmcrnsd -F StanzaFile
```

Re-create the base file system.

The administrator needs to re-create the initial file system. The output query file created in step 1 can be used as a guide. The following example shows the section of this file that is needed when re-creating the file system:

######### File system configuration #############
## The user can use the predefined options/option values
## when recreating the file system.  The option values
## represent values from the backed up file system.
#
# mmcrfs FS_NAME NSD_DISKS -j cluster -k posix -Q yes -L 4194304 --disable-fastea
  -T /smallfs -A no --inode-limit 278016#

Restore the essential file system configuration.
The essential file system configuration can be restored to the file system that was created in the previous step by running the mmrestoreconfig command:
```
mmrestoreconfig smallfs -i /tmp/smallfs.bkpcfg.out925 
```
Run the following command to mount the object file system on all of the nodes:
mmmount <file system device> -a

For example, mount the file system with the following command:
mmmount smallfs -a
Restore the configuration of the IBM Storage Protect client nodes by copying the saved configuration files from their saved location to each IBM Storage Protect client node.
1. The IBM Storage Protect client config files dsm.opt and dsm.sys needs to be restored to /opt/tivoli/tsm/client/ba/bin/.
2. If the IBM Storage Protect client password file, TSM.PWD, is saved during the backup procedure, it needs to be restored to /etc/adsm/.
3. Run the following command to verify that each IBM Storage Protect client node can communicate with the IBM Storage Protect server without prompting for a password: dsmc q sess
Restore the object storage data from the IBM Storage Protect server.
1. Run the dsmc restore command as shown to start a no-query restore on an IBM Storage Protect client node.
  dsmc restore <GPFS Object path> -subdir=yes -disablenqr=no \ -servername=<tsm server> -errorlogname=<error log path>.
  
  You can use the following example:
  dsmc restore /smallfs/ -disablenqr=no \ -servername=tsm1 -errorlogname=/tmp/object_restore.log
2. When the restore jobs are completed, check the error logs. If any errors are found, correct them so that the restore operations finish successfully.