Inaccessibility of the CES shared root path

The CES shared root path is rarely changed, except for scenarios where there is no other option, such as disk failure, which makes the CES shared root path inaccessible.

Description

When the CES shared root path changes, the S3 configuration data is not restored automatically to a new CES shared root path. Before you enable the S3 service, the restore the backed up S3 configuration data to the new CES shared root path.

Important: When you are restoring the data from the backup. Check the content before you restore the data.

Workaround

The steps to restore the S3 configuration to a new CES shared root path are as follows:

1. List and verify that the backed up tar.bz2 file of S3 configuration is present in the CCR.

    mmccr list

   A sample output is as follows:

   version name 
   --------- -------------------- 
    1 ccr.nodes 
    1 ccr.disks 
    1 mmLockFileDB 
    1 genKeyData 
    1 genKeyDataNew 
    16 mmsdrfs 
    1 mmsysmon.json 
    33 cesiplist 
    211 _s3-config-backup.tar.bz2 

2. Download the tar.bz2 backup file of the S3 configuration.

    mmccr fget _s3-config-backup.tar.bz2 /tmp/_s3-config-backup.tar.bz2 

   A sample output is as follows:

   fget:211 

3. Verify the content of the tar.bz2 backup file of the S3 configuration.

   # tar -xvf /tmp/_s3-config-backup.tar.bz2 -C /tmp/backup/

   A sample output is as follows:

   ./ 
   ./config.json 
   ./accounts/ 
   ./accounts/demo-account.json 
   ./buckets/ 
   ./buckets/demo-bucket.json 
   ./system.json 
   ./access_keys/ 
   ./access_keys/Pei0Og7tlMD4mFfq5qi5.symlink 

4. Ensure that the /tmp/backup/ directory structure is present.

   # tree /tmp/backup/ 

   A sample output is as follows:

   /tmp/backup/ 
    ├── access_keys 
    ├── accounts 
    ├── buckets 
    ├── config.json 
    └── system.json 

5. If config.json and system.json are present, proceed with restoration of the S3 configuration from the tar.bz2 backup file.

    mms3 config restore /tmp/_s3-config-backup.tar.bz2

   A sample output is as follows:

   The S3 configuration directory at path /mnt/cesSharedRoot/ces/s3-config is not empty. Restore operation will overwrite the existing S3 configuration and restart the S3 service on all CES nodes. Do you want to proceed ? [y|n]:y 
   Started Restoring s3-config configuration data 
   Restore of IBM Storage Scale S3 configuration successfully done. 
   INFO[2024-03-11T18:57:57+01:00] S3 Configuration successfully changed. S3 service restarted on the CES node: ces-12.openstacklocal. 
   INFO[2024-03-11T18:57:58+01:00] S3 Configuration successfully changed. S3 service restarted on the CES node: ces-13.openstacklocal. 
   INFO[2024-03-11T18:57:59+01:00] S3 Configuration successfully changed. S3 service restarted on the CES node: ces-14.openstacklocal.