All discovered servers will be listed on this page. Their page contains a tabular format consisting of seven (7) columns prefix with database and file icons, indicating its type of server when it was added. These are
Storage (used / total),
Created At, and
As prefix with database and file icons, for a server with
Database and File Backups type of setup, the database and file icon are highlighted. Whereas a file icon where database icon is greyed out, this means that it is setup as
Only Files Backups (beta) so only file backup is supported.
Hostname column shows the hostname along with its IP address after the hostname.
Status column shows the state of the agent (bartender) that is running in the server. It will indicate if the agent is
The Storage (used / total) column shows the total used over the available space of the storage. The total value is based on the aggregated value of all valid mounted journaling file systems. File systems such as
devtmpfs, vagrant file systems like
vboxsf are not counted.
Agent Version column shows the version of the agent currently running. You can also verify this by running the command below on the server where the bartender agent is running:
[[email protected] ~]# bartender --version Version: 1.0.0-295
Last Seen column determines the period of time the agent was identified as running.
Created At column shows the timestamp when was the server was registered in Backup Ninja.
Actions button contains the
More link which has three (3) dropdow items when clicked. These are
Upgrade Agent, and
Remove Agent. Each of these actions are listed below:
Configure Database Connection– This item will only show up if the server was configured as a
Only Files Backups(beta) during
Add Servertask. This option or dropdown item allows you to configure the server later as a
Database & Files Backupsonce you realize that the server has to also backup a database, and not only just as files backup.
Restart– Restart Backup Ninja agent (bartender) process on the database node.
Upgrade– Upgrade Backup Ninja agent (bartender) binary that is running on the database node. The agent daemon will be restarted automatically.
Remove Agent– This will stop the bartender agent and uninstalls the binary. The data and configuration files will remain intact. You can locate the configuration files and data at /var/lib/backup-agent/. Please make sure to save encryption keys and any other data before manually deleting the agent’s data directories.
Remove Agentwill also remove the server, the cloud credential configurations linked to the particular server.
Deleting The Server
Deleting the server, as mentioned previously, can be done by going over to
Actions column and click
More and select
When this action is selected, it will first remove the server in the UI. When the backup agent (bartender) is synced with the delete action as its server request, then it will remove the binary that is installed in the host system. It won’t delete the /var/lib/backup-agent directory, and it won’t delete the /var/log/bartender.log file as well.
For the bartender configuration which is situated in
/etc/bartender.yaml, it will be moved to
/etc/bartender.yaml.rpmsave (RHEL/CentOS) for example. Deleting the server will also not delete the backups taken from that server. It will also not delete any scheduled entries listed in the Schedule List page.
Any removal of the server will reflect in your next monthly invoice. That means, your subscription will be updated. Thus lowering the cost since the server and backup agent has been removed.