Configuring GDR

After you install the KSYS filesets, you can use the ksysmgr command to interact with the KSYS daemon to manage the entire environment for disaster recovery.

Review the GDR concepts to understand the associated entities for the GDR solution.

Before you configure the KSYS settings, you must complete the following tasks:

• Include the /opt/IBM/ksys path to the root directory so that you need not specify this path every time you run the ksysmgr command. To include this path, run the following command in the KSYS node:

  export PATH=$PATH:/opt/IBM/ksys

  Or, you can append this command to the .profiles file in the root directory.
• Verify that the KSYS node does not have an existing KSYS configuration by running the following command:

  lsrpdomain

  The output must indicate that no domain exists.
• Verify that the IBM.VMR resource class exists by running this command:

  lsrsrc | grep VMR

  Or,

  lssrc -a | grep VMR

  The output must display various IBM.VMR resource classes. If the lsrsrc command does not display any IBM.VMR resource classes, check the existing classes by running the following command:

  grep -i vmr /usr/sbin/rsct/cfg/ct_class_ids

  The output must display the IBM.VMR resource class.
  Note: You cannot configure the KSYS resources if the IBM.VMR resource class does not exist.
• If you are using AIX® LPARs as virtual machines in the active site, set the ghostdev parameter in the AIX kernel. Thereby, after a disaster recovery movement to the backup site, all the ghost devices associated with the recovered LPARs are removed from the backup site during the AIX boot process. To set the ghostdev parameter, complete the following steps:
  1. Log in to the source virtual machine as a root user.
  2. Modify the AIX kernel by running the following command:

     # chdev -l sys0 -a ghostdev=yes

  3. Run the following commands:

     # savebase
     # bosboot -ad /dev/ipldevice

     Note: These commands must be run on the source virtual machines. Since all the data is replicated to the backup site, these changes are also propagated from the active site to the backup site.