Chef-Bareos Cookbook

This cookbook installs and configures backups based on bareos software

Requirements

Attributes

<table>
<tr>
<th>Key</th>
<th>Type</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<td><tt>["bareos"]["database_type"]</tt></td>
<td>string</td>
<td>Specify the database type.</td>
<td><tt>postgresql</tt></td>
</tr>
<tr>
<td><tt>["bareos"]["dbdriver"]</tt></td>
<td>string</td>
<td>Specify the database driver.</td>
<td><tt>postgresql</tt></td>
</tr>
<tr>
<td><tt>["bareos"]["dbname"]</tt></td>
<td>string</td>
<td>Specify the database default name.</td>
<td><tt>bareos</tt></td>
</tr>
<tr>
<td><tt>["bareos"]["dbuser"]</tt></td>
<td>string</td>
<td>Specify the db user name.</td>
<td><tt>bareos</tt></td>
</tr>
<tr>
<td><tt>["bareos"]["dbpassword"]</tt></td>
<td>string</td>
<td>Specify the db password.</td>
<td><tt>none</tt></td>
</tr>
</table>

Usage

bareos_base role (install the bareos client backup by default)

You need to create a base role called bareos_base like this:

{
  "name": "bareos_base",
  "description": "Base Role for chef-bareos Cookbook, used in searches, throws down sources for installs",
  "json_class": "Chef::Role",
  "default_attributes": {
  },
  "override_attributes": {
  },
  "chef_type": "role",
  "run_list": [
    "recipe[bareos]"
  ],
  "env_run_lists": {
  }
}

This role has to be applied to all your clients so they can be backed up by this cookbook.

bareos_server role (install the bareos server for backups)

For the server, you need a role named bareos_server, for example :

{
  "name": "bareos_server",
  "description": "Bareos Server Role",
  "json_class": "Chef::Role",
  "default_attributes": {
  },
  "override_attributes": {
  },
  "chef_type": "role",
  "run_list": [
    "role[bareos_base]",
    "recipe[bareos::database]",
    "recipe[bareos::server]",
    "recipe[bareos::storage]",
    "recipe[bareos::workstation]"
  ],
  "env_run_lists": {
  }
}

You need to run chef-client on the backup server every time you add a new node. All job will be automatically create for you.

Contributing

1. Fork the repository on Github
2. Create a named feature branch (like add_component_x)
3. Write your change
4. Write tests for your change (if applicable)
5. Run the tests, ensuring they all pass
6. Submit a Pull Request using Github

License and Authors

License

Copyright 2014 Léonard TAVAE

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Authors

• Léonard TAVAE