Backup Job

The following article aims at explaining what backup is, and introducing its types and levels.

In general, Backup refers to a Bacula Job that saves files. There are numerous types of backup. If you wish to read more about them, see the list below:

Levels of Backup Jobs

• Full
• Differential
• Incremental
• Virtual Full

Flow

As shown in in the figure below, when running a backup job:

• the Bacula Director will connect to the File Daemon and Storage Daemon,

• the Director will then send to the File Daemon the necessary information to actually realize the backup job, like the Level, the File Set, the Storage Daemon to contact, etc.

• then the File Daemon will contact the Storage Daemon, identify the Data to be sent and send them as well as the related meta data (file attributes) to the Storage Daemon

• the Storage Daemon will put them into one or more Bacula Volumes, according to the Pool Resource chosen for the Job

• the Storage Daemon will send metadata back to the Director.

The moment Bacula will run a Backup Job depends on how this job is started:

• manually through a Console

• automatically by a defined and referenced Schedule

• automatically by an external script or command like

  bconsole -c bconsole.conf << EOF
  run job=name-of-the-job ...
  EOF
  

See also

Go to:

• Restore

• Admin

• Verify

• Copy

• Migration

Go back to Jobs.

Go back to Bacula Enterprise Explained

Go back to the Bacula Enterprise Fundamentals chapter.