---
name: Backup-ts-offline-agent-linux
title: Why does my Linux Backup Agent appear offline?
description: The Linux® backup agent might appear offline in the portal for multiple reasons. Follow the steps to rule out issues with firewall port settings, registration, and the `buagent` process on the server.
last-updated: 2026-06-08
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/Backup?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why does my Linux Backup Agent appear offline?
{: #troubleshoot-LinuxAgent}
{: troubleshoot}
{: support}

The Linux® backup agent might appear offline in the portal for multiple reasons. Follow the steps to rule out issues with firewall port settings, registration, and the `buagent` process on the server.
{: shortdesc}

Linux® agent shows as offline in Portal.
{: tsSymptoms}

## Possible firewall issue
{: #ts-LinuxAgentFW}

Currently, at minimum, your servers must allow access to the **`10.200.86.0/24`** and **`10.2.118.0/24`** subnets for TCP ports **8086**, **8087**. If the port settings are incorrect, traffic is blocked, and the agent cannot communicate with the Cloud Backup Portal.
{: tsCauses}

Check firewall ports - 8086 & 8087. For more information, see [Configuring firewall ports for IBM Cloud Backup for Classic](https://cloud.ibm.com/docs/Backup?topic=Backup-portinfo&format=markdown).
{: tsResolve}

## BUAgent service isn't running
{: #ts-LinuxAgentbua}

When the `BUAgent` process is no longer active on the server, the Linux® Agent appears offline in the Cloud Backup Portal.
{: tsCauses}

Make sure that the BUAgent is running by issuing the following command on the Linux® system.
{: tsResolve}

```sh
/etc/init.d/vvagent status
```
{: pre}

The output shows whether the BUAgent is running.

```sh
VVAgent is running (PID: )
BUAgent is running (PID: )
```

* If the BUAgent is not running, start it with the following command.

   ```sh
   /etc/init.d/vvagent start
   ```
   {: pre}

* If the BUAgent appears to be running, restart the service with the following command.

   ```sh
   /etc/init.d/vvagent restart
   ```
   {: pre}

## The agent needs to be reregistered to the Cloud Backup portal
{: #reregistagentinportal}

If it still shows that the Agent is offline after a refresh of the Portal page, then the Agent needs to be registered again.
{: tsCauses}

Registering an Agent to the Portal retains all existing jobs, schedules, and configurations as-is. Go to the Agent installation directory, then run the register command.
{: tsResolve}

```sh
cd opt/BUAgent
./register
```
{: pre}

Answer the following prompts.
* What is the web-based Agent Console address? `cloudbackupregister.service.softlayer.com` or `cloudbackupregister.service.usgov.softlayer.com`
* What is the web-based Agent Console connection port [8086]? Press Enter, 8086 is the correct port.
* What is the web-based Agent Console username? The answer is the same username that is used to log in to Portal.
* What is the web-based Agent Console password? The answer is the same password that is used to log in to Portal.

For more information about viewing or changing the backup password, see [Managing the username and password for the Cloud Backup service](https://cloud.ibm.com/docs/Backup?topic=Backup-changePassword&format=markdown).
{: tip}

If the previous steps don't work, pull up and review the most recent BUAgent-X.XLOG.

1. Go to `opt/BUAgent`.

   ```sh
   cd /opt/BUAgent
   ```
   {: pre}

2.  List the contents and sort them by date.

    ```sh
    ls -lrth
    ```
    {: pre}

3. Find the name of the most recent `BUAgent-x.XLOG` and open it with `/opt/BUAgent/xlogcat`. It can't be opened with `cat` or `vim`.

   ```sh
   ./xlogcat BUAgent-1.XLOG
   ```
   {: pre}

4. Review the log and determine the issue.

If your service plan covers it, you can get help by creating a [support case](https://cloud.ibm.com/unifiedsupport/supportcenter){: external}.