Prerequisites for the primary site

This topic describes the preparations that must be done at the primary site.

Detailed preparation steps or prerequisites are as follows:
  1. Disable cloud services maintenance operations on the appropriate node class being restored on the recovery site. For more information, see Configuring the maintenance windows.
  2. Disable all cloud services migration policies by using the --transparent-recalls {DISABLE} option in the mmcloudgateway containerPairSet create command. For more information, see Binding your file system or fileset to the Cloud service by creating a container pair set.
  3. Perform the required configuration steps:
    1. Create a cloud storage account. For more information, see Managing a cloud storage account.
    2. Define a cloud storage access point (CSAP). For more information, see Defining cloud storage access points (CSAP).
    3. Create a cloud service for cloud data sharing by using the mmcloudgateway cloudService create command, where you must specify --cloud-service-type as Sharing. For more information, see Creating cloud services.
  4. Allocate space in object storage for the backup:
    • Create a shared container pair Set with a sharing cloud service and with encryption disabled (and etag enabled if a data integrity check on the SOBAR backup tar file is required). This container will be used to share the backup data between the primary site and the recovery site.
  5. Calculate the maximum amount of space that will be used by the global filesystem directory (for mcstore_sobar_backup.sh script):
    1. On the primary cluster, use the mmdf command for each file system to determine the number of total inodes (look for Inode Information at the bottom).
      For example, 
      mmdf gpfs_tctbill1 | grep Inode
      Inode Information
Total number of used inodes in all Inode spaces:          307942342
Total number of free inodes in all Inode spaces:             748602
Total number of allocated inodes in all Inode spaces:     308690944
Total of Maximum number of inodes in all Inode spaces:    410512384
    2. Add up all the used inodes for all the file systems you are backing up and multiply by 4096 to determine necessary space requirements (307942342*4096=1.26TB).
      Note: This will automatically provide a buffer since the actual file will be compressed (tar) and the final size will depend on the compression ratio).
  6. Allocate space in associated file system for backup: This is a global file system directory that is allocated to handle the temporary space requirements of the SOBAR backup.