How to resume a GlusterFS geo-replication session

Resuming a paused GlusterFS geo-replication session restarts asynchronous replication so a secondary cluster can catch up after maintenance, upgrades, or a planned pause. Keeping the session running reduces the recovery point gap and keeps the secondary volume current for disaster recovery.

Geo-replication runs gsyncd workers on the primary cluster to track changes on the primary volume and synchronize them to the secondary volume over SSH. Pausing a session stops worker activity without removing session configuration, so resuming continues synchronization from the last known checkpoint.

Resuming can trigger a burst of disk and network I/O while pending changes are transferred, so monitor the session until it stabilizes and plan around peak workload periods. A session in a fully stopped state requires start rather than resume, and a force resume is reserved for coordinated snapshot restores performed on both the primary and secondary volumes.

1. Resume the geo-replication session on the primary cluster.

   $ sudo gluster volume geo-replication gvol-primary geoaccount@snode1.example.com::gvol-secondary resume
   geo-replication: resume: success

   The secondary spec format is user@host::volume.

2. Resume the session with force for coordinated snapshot restores performed on both volumes.

   $ sudo gluster volume geo-replication gvol-primary geoaccount@snode1.example.com::gvol-secondary resume force
   geo-replication: resume: success

   Force resume is intended only after a coordinated snapshot restore on both the primary and secondary volumes.

3. Confirm the session reports Active with a healthy crawl status.

   $ sudo gluster volume geo-replication gvol-primary geoaccount@snode1.example.com::gvol-secondary status
   MASTER NODE           STATUS   CRAWL STATUS  LAST SYNCED
   pnode1.example.com    Active   OK           2025-12-25 10:15:01
   ##### snipped #####

   Column names and row count vary by GlusterFS release and brick count.