'Never Finished' error in JetBackup 5

'Never Finished' error in JetBackup 5

The "Never Finished" error in JetBackup happens when a backup job doesn’t complete properly, leaving the process stuck in a "never finished" state. This issue can pop up for a bunch of reasons, like JetBackup services acting up, cache problems, or misconfigurations. Below, we’ll walk you through how to spot and fix this problem.

What Does the Problem Look Like?

  • The backup job doesn’t finish and shows a "Never Finished" status in JetBackup logs.
  • The backup process seems to hang and never completes, even though backups for other users or accounts work just fine.
  • The logs don’t show any specific errors, but the backup just won’t finish.

What Usually Causes This?

  1. JetBackup Services Acting Up: Sometimes, JetBackup services can get stuck or unstable because of cached data or internal glitches.
  2. Misconfigured Settings: If your backup settings aren’t set up right, it can cause the process to fail or get stuck.
  3. Sync Issues: In some cases, the backup might fail to sync with the destination server, stopping the process from completing.

How to Fix It: Restart JetBackup Services

One of the easiest and most effective ways to fix the "Never Finished" error is to restart JetBackup services. Here’s how to do it:

  1. Log into your server via SSH using your admin credentials.
  2. Restart JetBackup services by running these commands:

# service jetmongod restart
# service jetbackup5d restart

These commands will restart JetBackup and MongoDB services, which can clear out any cached data or unstable states causing the issue.

  1. Check the backup status: After restarting the services, manually start the backup job and see if it completes successfully.

Extra Tips to Avoid This Issue

  • Check your disk space: Make sure the destination server has enough space to store your backups.
  • Double-check your backup settings: Ensure your backup configurations are optimized to avoid sync problems.
  • Keep JetBackup updated: If the issue keeps happening, consider updating JetBackup to the latest version. Updates often include bug fixes and performance improvements.

    • Related Articles

    • JetBackup 5: How to fix the Integrity Check error using CLI/SSH

      When JetBackup performs its automated integrity verification processes, they may sometimes complete partially due to network interruptions, timeouts, or communication issues with the remote storage destination. If you receive notifications indicating ...

    • How to Block IPs and Ranges in Imunify360: CLI & GUI Master Guide

      Imunify360 is the ultimate defense for web servers. While its automated firewall is excellent, manual intervention is sometimes necessary to stop botnets or targeted attacks. In this guide, you will learn how to manage blocks precisely using commands ...

    • How to delete iDrive e2 files using AWS CLI on Mac

      When you need to delete large amounts of files from an iDrive e2 bucket, doing it through the web interface can take hours or even days. The most efficient solution is to use AWS CLI from your Mac terminal, as it processes multiple files in parallel ...

    • Basic SSH commands

      FILE MANAGEMENT Copy file cp -a archivo.zip archivocopia.zip Create a 404.html file touch /home/usuario/public_html/404.html Compress directory zip -r archivo.zip /home/usuario/public_html/directorio Extract file unzip archivo.zip View contents of a ...

    • How to install and configure Nginx as a reverse proxy in cPanel/WHM 🚀

      What is Nginx and why use it with cPanel? Nginx is a high-performance web server that can function as a reverse proxy in front of Apache on cPanel servers. This configuration allows Nginx to handle static files (images, CSS, JavaScript) while Apache ...