Configuring backup profiles

Edit online

You can use the SMIT interface or the clmgr add backup_profile command to configure backup profiles.

To configure backup profiles in PowerHA® SystemMirror® Version 7.2.3, or later, complete the following steps:
  1. From the command line, enter smit sysmirror.
  2. From the SMIT interface, select Cluster Applications and Resources > Cloud Backup Configuration > Backup Profiles , and press Enter.
  3. Complete the following fields, and then press Enter.
    Backup Profile
    Specify the name of the backup profile. You can select any of the configured resource groups or the rootvg profile as the backup profile name. If you want to back up all resource groups in a cluster, select ALL.
    Enable Backup
    Select this option to enable or disable the backup profile. You can also use this option to temporarily postpone the backup operation. The default value is Yes.
    Backup Method
    Select this option to specify the backup solution. Select Cloud to use IBM Cloud™™ or AWS. Select Remote Storage to use SVC storage based replication. The default value is Cloud. The following fields are displayed if you select the backup method as Cloud:
    Bucket Name
    Specify the name of an existing cloud storage bucket to upload the files into the cloud storage device.
    Target Location
    Specify a directory or file system that must be used to temporarily store backup files. A backup file is created in the specified location with data from the selected volume groups, and then the backup file is uploaded to the bucket in the cloud storage that you want to use. The last version of the backup file that was uploaded to the cloud storage is available in the target location. You must have adequate free space to store backup files of all volume groups that are specified in the selected backup profile.
    Cloud Service
    Specify IBM or AWS as the cloud service provider. The default value is IBM.
    Compression
    Specify the compression option for the backup data. Select Enable to automatically compress all backup data. Select Disable if you do not want to compress data. The default value is Disable. The compression option is not supported for file sizes that are larger than 10 GB.
    Note: The gzip program is used for data compression.
    Backup Frequency
    Specify the number of days for which you want PowerHA SystemMirror to collect the data for backup. Acceptable values for this field are in the range 0 - 999. For example, if you specify the value as 7, the data is backed up once a week. If you specify the value as 0, the data is backed up only once.
    Backup Schedule
    Specify the time when you want the backup process to start. Acceptable values for this field are in the range 00:00 - 23:59. The default value is 00:42.
    Incremental Backup Frequency
    Specify the frequency, in hours, when you want PowerHA SystemMirror to collect the incremental backup data. The value for this field cannot be higher than the value specified in the Backup frequency field. Acceptable values for this field are in the range 0 - 999. You can use the Incremental Backup Frequency option along with the Backup Frequency option.
    Encryption Algorithm
    Specify Yes and select the encryption type as KMS or AES to encrypt the backup data. Specify Disable if you do not want to encrypt the backup data. The default value is Disabled. If the selected cloud service is IBM, only AES can be used as the encryption algorithm.
    Volume Group(s)
    Select the volume groups that apply to the backup profile. If you have selected a resource group as the back up profile name, the volume groups that you specify must be a part of the selected resource group. If you want to back up all volume groups for a selected resource group, select ALL.
    Replicated Resources
    This field is available only if you are using IBM® SAN Volume Controller (SVC) or IBM System Storage DS8000 (DS8K) storage devices.
    For SVC storage
    • If the value of the Backup Method field is Cloud, you must specify a FlashCopy® consistency group. The specified FlashCopy consistency group must contain FlashCopy mappings between the source disks and the target disks that are created in the storage system. The source disks and the target disks must be of the same size. The source disks and the target disks must be mapped to all nodes in a specific resource group before starting the FlashCopy operation. The FlashCopy consistency group must not be part of any resource group in the cluster.
    • If the value of the Backup Method field is Remote Storage, you must specify a SVC Peer-to-Peer Remote Copy (PPRC) consistency group. The specified consistency group must contain relationships between the source disks and the target disks that are created in the storage system. The target disk is not required to be mapped to any cluster nodes. The SVC PPRC consistency group must not be part of any resource group in the cluster.
    For DS8K storage
    Create a mapping file anywhere in the node with all the target and source disks listed down there. There are two columns in the mapping file, first column contains source disks Volume ID’s list, and second column consists of target disks Volume ID’s list. You must specify this mapping file name in the Replicated Resources option.
    Storage Name
    Select the storage system names that contain the replicated resources that are defined in the backup profile. If you are using IBM SVC storage device for a remote copy operation, you can use only the SVC PPRC primary console. If you are using IBM PowerHA SystemMirror Enterprise Edition configuration, you must define the storage devices separately for the backup operation.
    Notify Method
    Specify a custom method (script) to be called if the backup operation fails. You must specify the full path name to the notify method. The script that you specify must exist on all cluster nodes and you must be able to run the script. When the notify method is called, the script receives two parameters as input strings: backup profile name and the reason for failure. The reason for failure is similar to the following example: 
    Flash copy operation failed for Backup profile demo_backup. Check clutils.log for more details.
    .
  4. Verify and synchronize the changes across the cluster.