|
|
3682.
|
|
|
These services and applications can be run on multiple servers and clients, or they can be installed on one machine if backing up a single disk or volume.
|
|
|
|
|
(no translation yet)
|
|
Translated by
Adi Roiban
|
|
Reviewed by
Adi Roiban
|
|
|
|
Located in
serverguide/C/backups.xml:587(para)
|
|
|
3683.
|
|
|
There are multiple packages containing the different <application>Bacula</application> components. To install Bacula, from a terminal prompt enter:
|
|
|
|
|
(no translation yet)
|
|
Translated by
Adi Roiban
|
|
Reviewed by
Adi Roiban
|
|
|
|
Located in
serverguide/C/backups.xml:594(para)
|
|
|
3684.
|
|
|
sudo apt-get install bacula
|
|
|
|
|
sudo apt-get install bacula
|
|
Translated by
Alexandru Iacob
|
|
Reviewed by
Adi Roiban
|
|
|
|
Located in
serverguide/C/backups.xml:599(command)
|
|
|
3685.
|
|
|
By default installing the <application>bacula</application> package will use a <application>MySQL</application> database for the Catalog. If you want to use SQLite or PostgreSQL, for the Catalog, install <application>bacula-director-sqlite3</application> or <application>bacula-director-pgsql</application> respectively.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/backups.xml:601(para)
|
|
|
3686.
|
|
|
During the install process you will be asked to supply credentials for the database <emphasis>administrator</emphasis> and the <emphasis>bacula</emphasis> database <emphasis>owner</emphasis>. The database administrator will need to have the appropriate rights to create a database, see <xref linkend="mysql"/> for more information.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/backups.xml:607(para)
|
|
|
3687.
|
|
|
<application>Bacula</application> configuration files are formatted based on <emphasis>resources</emphasis> comprising of <emphasis>directives</emphasis> surrounded by <quote>{}</quote> braces. Each Bacula component has an individual file in the <filename role="directory">/etc/bacula</filename> directory.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/backups.xml:617(para)
|
|
|
3688.
|
|
|
The various <application>Bacula</application> components must authorize themselves to each other. This is accomplished using the <emphasis>password</emphasis> directive. For example, the <emphasis>Storage</emphasis> resource password in the <filename>/etc/bacula/bacula-dir.conf</filename> file must match the <emphasis>Director</emphasis> resource password in <filename>/etc/bacula/bacula-sd.conf</filename>.
|
|
|
|
|
(no translation yet)
|
|
Translated by
Adi Roiban
|
|
Reviewed by
Adi Roiban
|
|
|
|
Located in
serverguide/C/backups.xml:622(para)
|
|
|
3689.
|
|
|
By default the backup job named <emphasis>Client1</emphasis> is configured to archive the <application>Bacula</application> Catalog. If you plan on using the server to backup more than one client you should change the name of this job to something more descriptive. To change the name edit <filename>/etc/bacula/bacula-dir.conf</filename>:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/backups.xml:628(para)
|
|
|
3690.
|
|
|
#
# Define the main nightly save backup job
# By default, this job will back up to disk in
Job {
Name = "BackupServer"
JobDefs = "DefaultJob"
Write Bootstrap = "/var/lib/bacula/Client1.bsr"
}
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/backups.xml:633(programlisting)
|
|
|
3691.
|
|
|
The example above changes the job name to <emphasis>BackupServer</emphasis> matching the machine's host name. Replace <quote>BackupServer</quote> with your appropriate hostname, or other descriptive name.
|
|
|
|
|
(no translation yet)
|
|
Translated by
Adi Roiban
|
|
Reviewed by
Adi Roiban
|
|
|
|
Located in
serverguide/C/backups.xml:644(para)
|
