This issue can occur if the standby cell is not able to replicate the database from the primary.
!!! GRACEFULLY SHUTDOWN ALL CELLS AND TAKE SNAPSHOTS PRIOR TO MAKING ANY DATABASE CHANGES !!!
!!! IF YOU DO NOT FEEL COMFORTABLE PERFORMING THESE STEPS PLEASE CONTACT BROADCOM SUPPORT FOR ASSISTANCE !!!
Clone the database from the Primary Cell to the Standby Cell.
1. Remove the Standby from the Repmgr Cluster.
2. Delete the Postgres Database from the Failed Standby Cell.
3. Copy the Primary Cell Database to the Failed Standby Cell.
# sudo -i -u postgres repmgr -h <primary_database_ip> -U repmgr -d repmgr -f /opt/vmware/vpostgres/current/etc/repmgr.conf standby clone
4. Start Postgres Service.
# systemctl start vpostgres.service
5. Register the Standby Cell with the Repmgr Cluster.
# sudo -i -u postgres repmgr -h <primary_database_ip> -U repmgr -d repmgr -f /opt/vmware/vpostgres/current/etc/repmgr.conf standby register --force
6. Verify the Standby Cell is registered to the Repmgr Cluster Successfully and you no longer see the error message or replication lag with the Standby Cell.
# sudo -i -u postgres repmgr cluster show
# sudo -i -u postgres repmgr node status
7. Start the vCD Services.
# service vmware-vcd start