Backing up and restoring protocols and CES configuration information

The backup and restore capabilities of the mmcesdr command can be used when there is no secondary cluster and the user still wants to protect protocol and export services configuration information. The independent fileset used to store protocol and export services configuration information can be backed up using IBM Spectrum Protect software and then restored if it ever needs to be restored to the cluster.

Note: The following steps only describe how to back up and restore the protocols and CES configuration information. The actual data contained in protocol exports would need to be backed up and restored separately.

On the primary cluster, use the following command to back up the configuration information:

mmcesdr primary backup

The system displays output similar to the following:

Performing step 1/2, configuration fileset creation/verification.
Successfully completed step 1/2, configuration fileset creation/verification.
Performing step 2/2, protocol and export services configuration backup.
Successfully completed step 2/2, protocol and export services configuration backup.

For backup, you can use IBM Spectrum Protect (formerly known as Tivoli® Storage Manager) or some other tool. For example, you can use mmbackup as follows:

mmbackup configuration_fileset_link_point --scope inodepace -t full

On the primary cluster, restore data from the off cluster storage into the configuration fileset. If mmbackup was used to back up the configuration fileset, the IBM Spectrum Protect command to restore is similar to the following:
```
dsmc restore -subdir=yes "configuration_fileset_link_point /*"
```
On the primary cluster, use the following command to restore the configuration information:
```
mmcesdr primary restore
```
The system displays output similar to the following:
```
Restoring cluster and enabled protocol configurations/exports.
Successfully completed restoring cluster and enabled protocol configurations/exports.
```
In some cases, running the mmcesdr primary restore command might display the following error message:
Saved configuration file does not exist.. In this case, do the following:
- If this cluster is part of a Protocols DR relationship, place a copy of the DR configuration file at a specified location and run the mmcesdr primary restore command again using the --input-file-path option.
- If this cluster is not part of a Protocols DR relationship, run this command again with the --file-config --restore option to force restoring the file configuration information. The system displays output similar to the following:
```
# mmcesdr primary restore --file-config --restore
Restoring cluster and enabled protocol configurations/exports.
Successfully completed restoring cluster and enabled protocol configurations/exports.

================================================================================
=  If all steps completed successfully, remove and then re-create file
=  authentication on the Primary cluster.
=  Once this is complete, Protocol Cluster Configuration Restore will be complete.
================================================================================
```
On the primary cluster, remove the file authentication and then add it again:

Note: If you want to perform a restore as part of a failback (either to an old primary cluster or a new primary cluster) and want to re-create the file configuration/exports, use one of the following commands:
mmcesdr primary restore
or
mmcesdr primary restore --file-config --recreate.