From 175cb0a715fc42051f43d6db1430e00ac0d3d504 Mon Sep 17 00:00:00 2001
From: plattnat <97075651+plattnat@users.noreply.github.com>
Date: Tue, 4 Jan 2022 03:33:13 +0000
Subject: [PATCH] Update Backups.md

Updating backup.md based on recent experiences where the wording wasn't clear and discord help was required.
---
 docs/admin/Backups.md | 25 ++++++++++++++++++++++++-
 1 file changed, 24 insertions(+), 1 deletion(-)

diff --git a/docs/admin/Backups.md b/docs/admin/Backups.md
index 26838a9..659846b 100644
--- a/docs/admin/Backups.md
+++ b/docs/admin/Backups.md
@@ -263,6 +263,8 @@ RunScript {
 
 Restart Bacula. `systemctl restart bacula-dir`
 
+If you're using additional machines, for example one machine1 is your hosting server and machine2 is your backup server you need to complete step 1 on machine1 and the rest on machine2 where the bacula-dir is located on.
+
 ## Troubleshooting
 
 ### Malformed message... Maximum permitted 1000000
@@ -274,4 +276,25 @@ Bacula may report this in its messages. Malformed messages happen from rogue cli
 systemctl status firewalld
 # Restart firewalld
 systemctl restart firewalld
-```
\ No newline at end of file
+```
+
+## Additional Notes
+
+Using the install provided my apiscp your backup server will backup itself as the client level will be installed on your backup server, you will need to disable the job or 'null' the backup file to prevent it doing this (if you want too). To 'null' the file go to /etc/bacula/local.d/servers/1/self.conf and edit it as such;
+
+```
+Device {
+Name = self
+Media Type = NULL
+Device Type = Fifo
+Archive Device = /dev/null
+LabelMedia = yes
+Random Access = no
+AutomaticMount = no
+RemovableMedia = no
+MaximumOpenWait = 60
+AlwaysOpen = no
+}
+```
+
+The backup will still run but this way it won't actually backup any data about itself. Only use this if you backup machine is used for backing up other devices and is not used a hosting platform itself.