32.2. Affichage de l'état des grappes de récupération

Procédure

1. Authentifiez tous les nœuds qui seront utilisés pour les deux clusters.

   [root@z1 ~]# pcs host auth z1.example.com z2.example.com z3.example.com z4.example.com -u hacluster -p password
   z1.example.com: Authorized
   z2.example.com: Authorized
   z3.example.com: Authorized
   z4.example.com: Authorized

2. Créez le cluster qui sera utilisé comme cluster primaire et démarrez les services de cluster pour le cluster.

   [root@z1 ~]# pcs cluster setup PrimarySite z1.example.com z2.example.com --start
   {...}
   Cluster has been successfully set up.
   Starting cluster on hosts: 'z1.example.com', 'z2.example.com'...

3. Créez le cluster qui sera utilisé comme cluster de reprise après sinistre et démarrez les services de cluster pour le cluster.

   [root@z1 ~]# pcs cluster setup DRSite z3.example.com z4.example.com --start
   {...}
   Cluster has been successfully set up.
   Starting cluster on hosts: 'z3.example.com', 'z4.example.com'...

4. À partir d'un nœud du cluster primaire, configurez le second cluster en tant que site de récupération. Le site de reprise est défini par le nom de l'un de ses nœuds.

   [root@z1 ~]# pcs dr set-recovery-site z3.example.com
   Sending 'disaster-recovery config' to 'z3.example.com', 'z4.example.com'
   z3.example.com: successful distribution of the file 'disaster-recovery config'
   z4.example.com: successful distribution of the file 'disaster-recovery config'
   Sending 'disaster-recovery config' to 'z1.example.com', 'z2.example.com'
   z1.example.com: successful distribution of the file 'disaster-recovery config'
   z2.example.com: successful distribution of the file 'disaster-recovery config'

5. Vérifier la configuration de la reprise après sinistre.

   [root@z1 ~]# pcs dr config
   Local site:
     Role: Primary
   Remote site:
     Role: Recovery
     Nodes:
       z1.example.com
       z2.example.com

6. Vérifiez l'état du cluster primaire et du cluster de reprise après sinistre à partir d'un nœud du cluster primaire.

   [root@z1 ~]# pcs dr status
   --- Local cluster - Primary site ---
   Cluster name: PrimarySite
   
   WARNINGS:
   No stonith devices and stonith-enabled is not false
   
   Cluster Summary:
     * Stack: corosync
     * Current DC: z2.example.com (version 2.0.3-2.el8-2c9cea563e) - partition with quorum
     * Last updated: Mon Dec  9 04:10:31 2019
     * Last change:  Mon Dec  9 04:06:10 2019 by hacluster via crmd on z2.example.com
     * 2 nodes configured
     * 0 resource instances configured
   
   Node List:
     * Online: [ z1.example.com z2.example.com ]
   
   Full List of Resources:
     * No resources
   
   Daemon Status:
     corosync: active/disabled
     pacemaker: active/disabled
     pcsd: active/enabled
   
   
   --- Remote cluster - Recovery site ---
   Cluster name: DRSite
   
   WARNINGS:
   No stonith devices and stonith-enabled is not false
   
   Cluster Summary:
     * Stack: corosync
     * Current DC: z4.example.com (version 2.0.3-2.el8-2c9cea563e) - partition with quorum
     * Last updated: Mon Dec  9 04:10:34 2019
     * Last change:  Mon Dec  9 04:09:55 2019 by hacluster via crmd on z4.example.com
     * 2 nodes configured
     * 0 resource instances configured
   
   Node List:
     * Online: [ z3.example.com z4.example.com ]
   
   Full List of Resources:
     * No resources
   
   Daemon Status:
     corosync: active/disabled
     pacemaker: active/disabled
     pcsd: active/enabled