Stay organized with collectionsSave and categorize content based on your preferences.
This page describes how to install Backup and DR agent on a Linux host and
perform other operations such as how to regenerate a secret key, check the
Backup and DR agent status, and restart the Backup and DR agent.
How it works
The Backup and DR agent for Linux runs as a daemon process under username root.
It listens on TCP port 5106 for communication from the backup/recovery appliance.
The agent writes to a log file in the installation directory/var/act/log/UDSAgent.logand posts significant events to the/var/log/messagesrepository.
After installing the agent, you need to initialize trusted communications
between the backup/recovery appliance and the Backup and DR agent.
This only needs to be done once.
The secret key needs to be added within two hours of being generated.
If the secret key expires, you need togenerate a new key.
Sometimes you may need to regenerate a secret key. For example, if a host
remains offline for an extended period, its certificate status may change to
"Uninitialized". If this occurs, you mustgenerate a new keyto
re-establish a valid certificate and resume normal operation.
Install the agent on a Linux host
Use the following instructions to install the agent on a Linux host:
To install the agent, choose one of the following:
For Linux 32-bit installation, run the following command.
rpm -ivh connector-Linux_x86-version.rpm
For Linux 64-bit installation, run the following command.
rpm -ivh connector-Linux-version.rpm
For Linux Ubuntu installation, run the following command.
dpkg -i connector-linux_ubuntu_amd64-version.deb
The agent always installs at/opt/act. When the installation is
complete, a secret key displays.
Save the secret key in a notepad or in a text editor, you need to add this
in Backup and DR agent section, seeAdd Linux host.
Regenerate the secret key
The secret key that is generated in theInstall the agent on a Linux hostsection is
valid only for two hours. You need to add it to the management console within
this timeframe or generate a new one.
Use the following instructions to generate a new key and add it to the management
console.
On the Linux host, sign in as a root user and run either of the commands in
the directory:
To reset the secret key after confirmation the action, run the following
command:
/opt/act/bin/udsagent secret --reset
To reset the secret immediately without confirmation, run the following
command:
/opt/act/bin/udsagent secret --reset --restart
Save the secret key in a notepad or in editor. This secret key is valid for
two hours.
Add a secret key
If you want to update the secret key or didn't add the secret key
the first time, you can add in theLinux hostusing the following instructions.
In the management console, selectManageand then selectHosts.
Right-click the Linux host and chooseEdit.
Go toBackup and DR agent Settingssection and find theSecretfield.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eThis guide covers installing the Backup and DR agent on a Linux host, which runs as a daemon process under root and communicates via TCP port 5106.\u003c/p\u003e\n"],["\u003cp\u003eAfter installation, a secret key is generated for secure communication, which must be added to the management console within two hours or regenerated.\u003c/p\u003e\n"],["\u003cp\u003eThe status of the Backup and DR agent can be checked using either \u003ccode\u003eservice udsagent status\u003c/code\u003e for non-systemd systems or \u003ccode\u003esystemctl status udsagent\u003c/code\u003e for systemd systems.\u003c/p\u003e\n"],["\u003cp\u003eYou can restart the agent using \u003ccode\u003e/etc/init.d/udsagent restart\u003c/code\u003e for non-systemd hosts or \u003ccode\u003esystemctl restart udsagent\u003c/code\u003e for systemd hosts.\u003c/p\u003e\n"],["\u003cp\u003eThe agent can also be uninstalled, either using \u003ccode\u003eyum remove\u003c/code\u003e or \u003ccode\u003erpm -e\u003c/code\u003e for CentOS/RHEL/SLES, or \u003ccode\u003edpkg --remove\u003c/code\u003e for Ubuntu, after stopping the agent service.\u003c/p\u003e\n"]]],[],null,["# Install the Backup and DR agent on a Linux host\n\nThis page describes how to install Backup and DR agent on a Linux host and\nperform other operations such as how to regenerate a secret key, check the\nBackup and DR agent status, and restart the Backup and DR agent.\n\nHow it works\n------------\n\nThe Backup and DR agent for Linux runs as a daemon process under username root.\nIt listens on TCP port 5106 for communication from the backup/recovery appliance.\nThe agent writes to a log file in the installation directory\n`/var/act/log/UDSAgent.log` and posts significant events to the\n`/var/log/messages` repository.\n\nAfter installing the agent, you need to initialize trusted communications\nbetween the backup/recovery appliance and the Backup and DR agent.\nThis only needs to be done once.\nThe secret key needs to be added within two hours of being generated.\nIf the secret key expires, you need to [generate a new key](#regenerate).\n\nSometimes you may need to regenerate a secret key. For example, if a host\nremains offline for an extended period, its certificate status may change to\n\"Uninitialized\". If this occurs, you must [generate a new key](#regenerate) to\nre-establish a valid certificate and resume normal operation.\n\nInstall the agent on a Linux host\n---------------------------------\n\n| **Note:** You must have at least 1 GB of free space in the /opt directory for UDSAgent to install or upgrade on Linux hosts.\n\nUse the following instructions to install the agent on a Linux host:\n\n1. Download the agent installer file, see\n [Obtain the right Backup and DR agent for your host](/backup-disaster-recovery/docs/concepts/about-connector#right-connector).\n\n2. Upload the installer file to your Linux server.\n\n3. To install the agent, choose one of the following:\n\n - For Linux 32-bit installation, run the following command.\n\n rpm -ivh connector-Linux_x86-\u003cvar translate=\"no\"\u003eversion\u003c/var\u003e.rpm\n\n - For Linux 64-bit installation, run the following command.\n\n rpm -ivh connector-Linux-\u003cvar translate=\"no\"\u003eversion\u003c/var\u003e.rpm\n\n - For Linux Ubuntu installation, run the following command.\n\n dpkg -i connector-linux_ubuntu_amd64-\u003cvar translate=\"no\"\u003eversion\u003c/var\u003e.deb\n\n The agent always installs at `/opt/act`. When the installation is\n complete, a secret key displays.\n4. Save the secret key in a notepad or in a text editor, you need to add this\n in Backup and DR agent section, see\n [Add Linux host](/backup-disaster-recovery/docs/configuration/add-linux-hosts).\n\n### Regenerate the secret key\n\nThe secret key that is generated in the\n[Install the agent on a Linux host](#agent-linux) section is\nvalid only for two hours. You need to add it to the management console within\nthis timeframe or generate a new one.\n\nUse the following instructions to generate a new key and add it to the management\nconsole.\n\n1. On the Linux host, sign in as a root user and run either of the commands in\n the directory:\n\n - To reset the secret key after confirmation the action, run the following\n command:\n\n /opt/act/bin/udsagent secret --reset\n\n - To reset the secret immediately without confirmation, run the following\n command:\n\n /opt/act/bin/udsagent secret --reset --restart\n\n2. Save the secret key in a notepad or in editor. This secret key is valid for\n two hours.\n\n### Add a secret key\n\nIf you want to update the secret key or didn't add the secret key\nthe first time, you can add in the [Linux host](/backup-disaster-recovery/docs/configuration/add-linux-hosts)\nusing the following instructions.\n\n1. In the management console, select **Manage** and then select **Hosts**.\n\n2. Right-click the Linux host and choose **Edit**.\n\n3. Go to **Backup and DR agent Settings** section and find the\n **Secret** field.\n\n4. Paste the secret key that you saved earlier in the **Secret** field\n and click **Save** . Ensure the **Certificate** status changes to **Valid** .\n If you get a partial success message, use the instructions to\n [Validate backup/recovery appliance to Backup and DR agent connectivity](/backup-disaster-recovery/docs/concepts/appliance-network-settings#validate).\n\n### Check Backup and DR agent status\n\nAfter the agent is installed, you can verify its status on the Linux hosts using\nthe following commands.\n\n- On non-system targets (RHEL before 7.0 and SUSE Linux before 12.0),\n run the following command.\n\n service udsagent status\n\n The output looks similar to the following for the line `udsagent daemon is running`: \n\n service udsagent status\n udsagent daemon is running\n\n- On `systemd` targets (RHEL 7.0+, SUSE Linux 12.0+, and Ubuntu 16.0+), run the following\n command:\n\n systemctl status udsagent\n\n The output looks similar to the following: \n\n ```postgres\n [root@postgres ~]# systemctl status udsagent\n ● udsagent.service - Google Cloud Backup and DR service\n Loaded: loaded (/usr/lib/systemd/system/udsagent.service; enabled; vendor preset: disabled)\n Active: active (running) since Wed 2022-11-09 22:13:45 UTC; 17min age\n Process: 1056 ExecStart=/act/initscripts/udsagent.init start (code=exited, status=0/SUCCESS)\n Main PID: 1128 (udsagent)\n CGroup: /system.slice/udsagent.service\n ├─1128 /opt/act/bin/udsagent start\n └─1132 /opt/act/bin/udsagent start\n\n Nov 09 22:13:44 postgres systemd[1]: Starting Google Cloud Backup and DR Service...\n Nov 09 22:13:45 postgres udsagent.init[1056]: Starting /opt/act/bin/udsagent as a daemon. It may take a few minutes for the service to start completely.\n Nov 09 22:13:45 postgres udsagent.init[1056]: Starting /opt/act/bin/udsagent as a daemon. It may take a few minutes for the service to start completely.\n\n### Restart the Backup and DR agent on a Linux host\n\nTo restart the Backup and DR agent on a Linux host, execute the following\ncommand on the host.\n\n- For **Non-systemd (RHEL before 7.0 and SUSE Linux before 12.0)** hosts,\n run the following command:\n\n /etc/init.d/udsagent restart\n\n- For **Systemd (RHEL 7.0+, SUSE Linux 12.0+, and Ubuntu 16.0+)** hosts,\n run the following command:\n\n systemctl restart udsagent\n\n### Uninstall the Backup and DR agent from a Linux host using the command line\n\nUse the following instructions to uninstall the Backup and DR agent from a\nLinux host: \n\n### CentOS/RHEL/SLES\n\n1. Sign in as a root user and stop the Backup and DR agent by running the\n following command:\n\n systemctl stop udsagent\n\n For older Linux versions you may need to use the following command: \n\n /etc/init.d/udsagent stop\n\n2. Check the installed Linux Backup and DR agent\n RPM name with the following command:\n\n yum list installed | grep udsagent\n\n You can also use the following command to check the RPM name: \n\n rpm -qa udsagent\n\n The output looks similar to the following: \n\n udsagent-11.0.1-8756.x86_64\n\n3. Uninstall the package using the name you obtained from the query.\n For example:\n\n yum remove udsagent-11.0.1-8756.x86_64\n\n You can also use the following command to uninstall the package: \n\n rpm -e udsagent-11.0.1-8756.x86_64\n\n### Ubuntu\n\n1. Sign in as a root user and stop the Backup and DR agent by running the\n following command:\n\n systemctl stop udsagent\n\n2. Uninstall the agent using the following command:\n\n dpkg --remove udsagent\n\nWhat's next\n-----------\n\n- To install Backup and DR agent on a Linux host, see [Install the Backup and DR agent on a Linux host](/backup-disaster-recovery/docs/configuration/linux-agent)\n\n- To install Backup and DR agent on a Windows host, see [Backup and DR agent on Windows hosts](/backup-disaster-recovery/docs/configuration/windows-agent)\n\n- To configure iSCSI connectivity on a Linux host, see [iSCSI connectivity on a Linux host](/backup-disaster-recovery/docs/configuration/add-linux-hosts#iSCSI)\n\n- To configure NFS connectivity on a Linux host, see [NFS connectivity on a Linux host](/backup-disaster-recovery/docs/configuration/add-linux-hosts#NFS)\n\n- To upgrade Backup and DR agent, see [Maintain Backup and DR agents on hosts](/backup-disaster-recovery/docs/configuration/manage-agent)"]]
