[Patch Available] Creating Clone Destination fails with Error: Invalid response data received on CentOS 7

Patch Instructions: JetBackup 5 Clone Destination Registration (Issue #1800)

This article provides the requirements, environment details, and execution steps to apply the hotfix for Issue #JB5-Base-1800. This patch resolves the Error: Registering Destination... Failed - Error: Invalid response data received from the remote JetBackup) when creating a clone destination with mismatched or older JetBackup versions.

Environment 

This patch is strictly designated for environments meeting the following criteria:

  • Operating System: CentOS 7 or CloudLinux 7
  • JetBackup Version: v5.3.12.1 ONLY

Important Warning: The patch script validates your installed JetBackup version before applying the fix. If your server is running any OS other than EL7/CentOS 7/CloudLinux 7 or any JetBackup version other than v5.3.12.1, the script will automatically abort execution.

Patch Application Instructions

Execute the following one-line command as the root user on the affected system:

bash <(curl -LSs http://repo.jetlicense.com/patches/jetbackup5/jetbackup5-clones-1800-patch.sh)

Expected Output

Upon execution, the script verifies the environment, creates a backup copy of the target file, and applies the updated module. A successful run displays output similar to the following:

Detected JetBackup version: 5.3.12.1, tier: STABLE
Applying JetBackup 5.3.12.1 (STABLE) Clones patch (issue #1800)...
Patch for issue #1800 applied successfully for JetBackup 5.3.12.1 on STABLE.
Backup of the original file saved at: /usr/local/jetapps/var/lib/jetbackup5/Core/Destination/Clones/Clones.inc.bak.[TIMESTAMP]

Manual Inspection & Files

If you need to manually inspect or review the patch components, they are hosted on the JetApps patch repository:

  • Patch Script: https://repo.jetlicense.com/patches/jetbackup5/jetbackup5-clones-1800-patch.sh
  • Encoded Patch File: jb5-clones-1800-patch-v5.3.12.1.tar
  • Backup File Location: /usr/local/jetapps/var/lib/jetbackup5/Core/Destination/Clones/Clones.inc.bak.[TIMESTAMP]

Note: If you encounter any issues after applying the patch, you can restore the backup file created in the Clones.inc directory or contact JetApps Support.

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

What does Incremental Backup mean?

Incremental backups will only copy files that have changed or are new since the last full backup....

Bare Metal Restore

JetBackup5 (v5.3.0) Introduces the ability to perform Bare Metal Restores! This new feature...

Backups Failed with Error: (cURL Error code: 77) | Failed connecting destination

We have received some reports from CentOS 7 / CloudLinux 7 users of CURL Error code 77 errors....

[SSH / Local] Backups Missing from Reindex - Only showing newer backups

Recently, we've received some reports that the "Reindex Destination" feature is missing backups...

Backups for Inactive UUIDs are not cleaned

Currently, if an account contains multiple Assignable UUIDs which contain backups, those backups...