General Considerations

Before using the Bacula Configuration GUI module, there are a few things that you should take into consideration.

• The configuration module is capable of creating, modifying, and saving the above mentioned Bacula .conf files.

• You may either start from scratch — with the default configuration files — or start with existing configuration files.

• If you start with existing configuration files, the configuration module will read them in, and keep them in its own internal format. This format is probably different from the original configuration file layout that you have. When the files are written out, they will be rearranged into a format that is compatible with the Bacula daemons but slightly different from any prior configuration files. For example, each resource is kept in a separate file in a directory of resources, and any Bacula configuration comments are not kept in the process. Depending on how your FileSet contents are organized, Bacula may force a new full backup after the BMS initialization. See Important Note About FileSet for more details.

• Once the new configuration files are written, you may modify them either with the configuration GUI or manually or using any scripts you may have developed.

See also

Go to:

• Getting Started

• Defining New Jobs

• Define Retention Policy

• Configure Remote Clients

• If Something Goes Wrong

• Current Limitations

Go back to the Configuring Bacula with BMS chapter.

Go back to the Bweb Management Suite chapter.

Go back to the Bacula Enterprise User Interfaces.