Procedure for backup

This topic describes the procedure for backing up the cluster configuration on the primary site.

Before you begin, ensure the following:
  • No data migration is in progress or initiated. Starting SOBAR backup during any migration operation might eventually lead to data loss.
  • The prerequisites are met and the preparation steps for the recovery site are performed. For more information, see Prerequisites for the primary site.

Perform the following steps:

  1. File system configuration backup:
    1. Back up the cluster configuration of every file system on the primary site that you want to recover: /usr/lpp/mmfs/bin/mmbackupconfig <file_system_name> -o <cluster_backup_config_file>. For example, 
      mmbackupconfig gpfs_tctbill1 -o powerleBillionBack_gpfs_tctbill1_02232018
      
mmbackupconfig: Processing file system gpfs_tctbill1 ...
mmbackupconfig: Command successfully completed
      For example, to list the backup files, issue this command.
      ls -l /root/powerleBillionBack_gpfs_tctbill*
      
-rw-r--r--. 1 root root 19345 Feb 23 11:24 /root/powerleBillionBack_gpfs_tctbill1_02232018
-rw-r--r--. 1 root root 19395 Feb 23 11:25 /root/powerleBillionBack_gpfs_tctbill3_02232018
    2. Securely transfer the backup files to a safe location (they will be used later in the restore process on the recovery site).
  2. File system metadata backup (Back up the cloud data and automatically export it to the shared container).
    1. From a node in your cloud services node class on your primary site, run the mcstore_sobar_backup.sh script under the /opt/ibm/MCStore/scripts folder.
      Note: Make sure the <global-filesystem-directory> you choose is mounted, accessible from all nodes in the cluster, and has enough space to accommodate the backup.
      The following is an example and a sample output: 
      
[root@primary-site-tct-node scripts]/opt/ibm/MCStore/scripts/ mcstore_sobar_backup.sh 
gpfs_tctbill1c powerleSOBAR1 TCTNodeClassPowerLE /ibm/gpfs_tctbill1
Creating backup for File System : gpfs_tctbill1
TOTAL_USED_INODE_SPACE 1261342920704
...
mmimgbackup: [I] Image backup of /dev/gpfs_tctbill1 begins at Wed Mar 14 17:03:05 EDT 2018.
...
mmimgbackup: [I] Image backup of /dev/gpfs_tctbill1 ends at Wed Mar 14 22:37:55 EDT 2018.
...
Exporting SOBAR backup: 9277128909880390775_gpfs_tctbill1_03-14-18-17-03-01.tar to cloud 
and Data Container is : powerleSOBAR1
...
Completed backup procedure for File System : gpfs_tctbill1 use 
9277128909880390775_gpfs_tctbill1_03-14-18-17-03-01.tar for restore operation
    2. Repeat the mcstore_sobar_backup.sh command for each file system you are backing up, using the same sharing_container_pair_set_name and the same global-filesystem-directory and the tct_node-class-names where appropriate.
  3. cloud services configuration backup
    1. Issue this command: mmcloudgateway service backupConfig --backup-file <backup_file>. For example, 
      
[root@primary-site-tct-node ~] mmcloudgateway service backupConfig --backup-file 
/temp/TCT_backupConfig

mmcloudgateway: Starting backup

Backup Config Files:
[mmcloudgateway.conf  -  Retrieved]
[_tctkeystore.jceks   -  Retrieved]
[_tctnodeclasspowerle.settings  -  Retrieved]
[*.p12 files -  Not Found]

mmcloudgateway: Creating the backup tar file...
mmcloudgateway: Backup tar file complete.
The file is '/temp/TCT_backupConfig_20180306_123302.tar'.
mmcloudgateway: The backup file should be archived in a safe and secure location
as it may include authentication credentials.
mmcloudgateway: Command completed.
      The backup file is located here: /temp/TCT_backupConfig_20180306_123302.tar. For more information, see Backing up the cloud services configuration.
    2. Securely transfer this backup file to a safe location (It will be used later in the restore process on the recovery site).