Changes between Version 19 and Version 20 of Csle2022/Agenda/bacula

Timestamp:

Nov 12, 2022, 12:58:57 AM (3 years ago)

Author:

geethike

Comment:

--

Csle2022/Agenda/bacula

@@ -305 +305 @@
 
 Save and exit when you are done.
+
+'''Verify Director Configuration'''
+
+Let’s verify that there are no syntax errors in your Director configuration file:
+{{{
+sudo bacula-dir -tc /etc/bacula/bacula-dir.conf
+}}}
+If you are returned to the shell prompt, there are no syntax errors in your Bacula Director’s configuration files.
+
+'''Restart Bacula Director'''
+
+To put the configuration changes that you made into effect, restart Bacula Director:
+{{{
+sudo service bacula-director restart
+}}}
+Now your Client, or remote host, is configured to be backed up by your Bacula Server.
+
+== Test Client Connection ==
+We should verify that the Bacula Director can connect to the Bacula Client.
+
+On your Bacula Server, enter the Bacula Console:
+{{{
+sudo bconsole
+*status client
+}}}
+
+{{{
+Select Client resource: ClientHost-fd
+The defined Client resources are:
+     1: BackupServer-fd
+     2: ClientHost-fd
+Select Client (File daemon) resource (1-2): 2
+}}}
+
+The Client’s File Daemon status should return immediately. If it doesn’t, and there is a connection error, there is something wrong with the configuration of the Bacula Server or of the Client’s File Daemon.
+
+== Test Backup Job ==
+Let’s run the backup job to make sure it works.
+On the '''Bacula Server''', while still in the Console, use this command:
+{{{
+*run
+}}}
+You will be prompted to select which Job to run. Select the one we created earlier,
+ '''e.g. “4. !BackupClientHost”:'''
+{{{
+Select Job resource: BackupClientHost
+The defined Job resources are:
+     1: BackupLocalFiles
+     2: BackupCatalog
+     3: RestoreLocalFiles
+     4: BackupClientHost
+Select Job resource (1-4): 4
+}}}
+At the confirmation prompt, enter “yes”:
+{{{
+Confirmation prompt:
+OK to run? (yes/mod/no): yes
+}}}
+'''Check Messages and Status'''
+After running a job, Bacula will tell you that you have messages. The messages are output generated by running jobs.
+
+Check the messages by typing:
+{{{
+*messages
+}}}
+The messages should say “No prior Full backup Job record found”, and that the backup job started. If there are any errors, something is wrong, and they should give you a hint as to why the job did not run.
+
+Another way to see the status of the job is to check the status of the Director. To do this, enter this command at the bconsole prompt:
+{{{
+*status director
+}}}
+If everything is working properly, you should see that your job is running or terminated with an “OK” status.