4

Data loss, server failures, and configuration issues can occur unexpectedly. A reliable disaster recovery strategy ensures that your backups remain accessible and your accounts can be restored with minimal downtime. In this guide, we’ll explain different JetBackup disaster recovery scenarios, including recovery without JBConfig, restoring data after losing access to the original server, JetBackup version compatibility, and how to re-enable Disaster Recovery mode.

Understanding JetBackup Disaster Recovery

JetBackup 5 includes a Disaster Recovery feature designed to restore both account backups and JetBackup configurations. When JBConfig backups are enabled, JetBackup automatically creates encrypted backups of its internal databases, including MongoDB and JetIndexd, allowing a complete recovery of backup jobs, destinations, schedules, and settings.

However, recovery options differ depending on the information available during a disaster.

Scenario 1: How to Perform Disaster Recovery Without JBConfig or the Master Encryption Key

Why This Happens

JetBackup only backs up its internal databases when the JBConfig feature is enabled on backup destinations. If JBConfig was never configured or the Master Encryption Key is unavailable, JetBackup cannot restore its internal configuration database.

Although configuration recovery is not possible, account backups can still be restored manually.

Important Limitations

When recovering without the Master Encryption Key:

• JetBackup configurations cannot be restored.
• Backup jobs, destinations, schedules, and settings will be lost.
• Existing backup chains cannot continue.
• New backups must be generated from scratch.
• Recovery is limited to read-only destinations.

Manual Recovery Steps

Step 1: Prepare the New Server

• Install the operating system.
• Install a supported control panel.
• Install JetBackup 5.

Step 2: Access the Disaster Recovery Page

After installation:

• Open the JetBackup Dashboard.
• Navigate to the Disaster Recovery page.
• Select New Installation.

Step 3: Prevent Orphan Backup Removal

Navigate to:

General Settings → Days to Keep Orphan Backups

Set the value to:

0

This prevents JetBackup from automatically deleting orphaned backup files.

Step 4: Create a Read-Only Destination

Create a new backup destination and:

• Point the backup path to the location containing your existing backups.
• Enable Read-Only Mode.

Step 5: Allow Reindexing

JetBackup will automatically:

• Scan the backup location.
• Reindex existing snapshots.
• Detect available account backups.

Step 6: Restore Orphan Accounts

Navigate to:

JetBackup → Restore & Download

Select:

Account Type → Orphan Accounts

Choose the accounts you want to restore and start the restoration process.

Scenario 2: Can I Perform Disaster Recovery If I Lost Access to the Old Server?

Yes, Recovery Is Possible

If the original server is unavailable but you still have access to the backup destination and the Master Encryption Key, you can perform a full disaster recovery.

This method restores:

• JetBackup configurations
• Backup destinations
• Backup jobs
• Schedules
• Account backups

Recovery Steps

Step 1: Install JetBackup

Install JetBackup on the replacement server.

Step 2: Open JetBackup

Navigate to:

WHM → Plugins → JetBackup

Step 3: Start Disaster Recovery

Select:

Recover From Disaster

Step 4: Add Backup Destination

Enter the same destination details that were used on the previous server.

Step 5: Restore JBConfig Backup

JetBackup will detect available JBConfig backups.

Enter your:

Master Encryption Key

Step 6: Begin Recovery

If the key is valid, JetBackup will:

• Create the destination.
• Reindex backup data.
• Recover MongoDB and JetIndexd databases.

Depending on database size and snapshot count, this process may take some time.

Step 7: Restore Accounts

After the configuration recovery completes, JetBackup will display the account restoration window.

Choose the required accounts and begin the restore process.

Important: Do not refresh or close the browser while the JBConfig restoration is in progress.

Scenario 3: JetBackup Version Compatibility Questions

Can JetBackup 4 Backups Be Used in JetBackup 5.3.x?

No.

JetBackup 4 backups are not compatible with JetBackup 5.

Because JetBackup 4 has reached End of Life (EOL), backups created in JetBackup 4 cannot be restored directly in JetBackup 5.

Key Point

• JetBackup 4 backups → Not supported in JetBackup 5
• Migration requires creating new backups in JetBackup 5

Can JetBackup 4 and JetBackup 5.3.x Run on the Same Server?

Direct installation of JetBackup 4 and JetBackup 5.3.x together is not supported.

However, administrators running JetBackup 4.1.3-3 can temporarily install JetBackup 5.2.11 alongside JetBackup 4 during migration.

This allows:

• Continued use of JetBackup 4
• Creation of new backups in JetBackup 5
• Smooth transition to the latest JetBackup version

Install JetBackup 5.2.11

# Install JetBackup v5.2.11
yum install jetbackup5-cpanel-5.2.11 jetmongod-4.4.0.1 --disablerepo=* --enablerepo=jetapps,jetapps-stable

After installation:

1. Configure backup jobs in JetBackup 5.
2. Generate fresh backups.
3. Upgrade JetBackup 5 to the latest supported version.

Operating System Support Notice

Before upgrading, verify your server meets the latest system requirements.

The following operating systems have reached End of Life:

• CentOS 7
• CloudLinux 7
• Debian 10
• Ubuntu 18.04

Support for these operating systems is limited to JetBackup version 5.3.12.

For the best experience and security, use the latest JetBackup 5 release on a supported operating system.

Scenario 4: I Selected “New Installation” Instead of Disaster Recovery. Can I Restore the Recovery Option?

Yes

If you accidentally selected New Installation, you can re-enable Disaster Recovery mode by renaming the Disaster Recovery flag file.

File Location

/usr/local/jetapps/etc/jetbackup/dr.flag

Command

mv /usr/local/jetapps/etc/jetbackup/dr.flag /usr/local/jetapps/etc/jetbackup/dr.flag_bk2

Final Step

Refresh the JetBackup interface.

The Disaster Recovery option will become available again, allowing you to proceed with the recovery process.

Conclusion

JetBackup Disaster Recovery provides multiple recovery options depending on the information available after a server failure. Whether you’ve lost access to the original server, misplaced the Master Encryption Key, or need to recover orphaned backups, JetBackup offers methods to restore critical account data. Enabling JBConfig backups, securely storing the Master Encryption Key, and keeping JetBackup updated are essential best practices for ensuring a successful recovery when disaster strikes.

Need Help Recovering Your JetBackup Environment?

Whether you’ve lost access to your server, misplaced your Master Encryption Key, or need assistance with JetBackup migration and disaster recovery, the SupportPRO team is here to help. Contact SupportPRO today for fast and reliable JetBackup support.