CloudLink: Resolve Sync Off Between Cluster Nodes After Restoring from Backup

Summary: Customer could still log on to the web portal of both CloudLink cluster nodes, but each node reported the other as sync‑off. The environment runs CloudLink 6.5 P01 with integrated ScaleIO 2.0.1.2 on encrypted disks in CentOS 7.3 (Operating System). ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Observed Issues

  • Web portal login succeeds on both CloudLink cluster nodes, but each node reports the other node as “sync off”.
  • Disk space checks on both nodes show no usage issues.
  • GUI inspections reveal no obvious errors, although the CloudLink cluster lacks a certificate.
  • Rebooting one cluster node does not clear the “sync off” status for the other node.
  • Rebooting the second node also leaves the “sync off” condition unchanged.

Cause

Inconsistent Cluster State After Separate Restores

The cloudlink cluster became unsynchronised because the two cloudlink virtual machines were restored from backup at different times. This asynchronous restoration introduced divergent configuration data and metadata between the nodes.

  • Each node loaded a different snapshot of the cluster database, causing mismatched node identifiers.
  • Cluster certificates were not regenerated or shared, leaving the cluster without a valid shared certificate.
  • The inconsistency prevented the nodes from establishing a synchronized state, resulting in each node reporting the other as “sync off”.

Resolution

Recover CloudLink Cluster Synchronization

Action Plan

  • Restore one CloudLink node from a known‑good backup.
  • Remove any remaining cluster members from the restored node’s configuration.
  • Deploy a fresh CloudLink instance from the OVA package.
  • Join the newly deployed CloudLink to the existing cluster.

Step‑by‑Step Procedure

  1. Restore a CloudLink node

    Use the backup that was taken before the corruption occurred. 

  2. Delete other cluster members from the restored node

    Access the restored node’s web portal and navigate to Cluster → Members . Remove each listed member. 

  3. Deploy a new CloudLink from the OVA

    Download the latest CloudLink OVA that matches version 6.5 P01 with ScaleIO 2.0.1.2. 

  4. Join the new CloudLink to the cluster

    From the new node’s web portal, select Cluster → Join Existing Cluster and provide the IP address and credentials of the restored node. 

Verification

  • Log in to the web portal of each cluster node.
  • Confirm that the Cluster → Status page shows both nodes as Sync On .
  • Check that a valid cluster certificate is present under Security → Certificates .
  • Run a quick health check to ensure no errors are reported.
Caution: Restoring a node from backup while other nodes remain active can create data inconsistency. Perform the restore on a single node only, then rebuild the remaining members as described.
Note: Verify that sufficient disk space is available on the host before deploying the new OVA. Insufficient space may cause deployment failures.
Warning: If you are unfamiliar with OVA deployment or CLI commands, contact Dell Support before proceeding to avoid unintended service disruption.

Affected Products

CloudLink

Products

CloudLink
Article Properties
Article Number: 000034993
Article Type: Solution
Last Modified: 02 كانون الثاني 2026
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.