Where should backups be stored?
After checking the FHS, there's a bit of confusion about this issue. There are 3 possible locations: /srv, /var/backups and /var/spool/backups.
I have decided to put them in /var/backups since it's mentioned in the FHS and it's relevant to me.
Nevertheless, Southern_Gentlem; of irc://freenode.net/#fedora suggested to use /srv since he uses it and Red Hat uses it.
Anyway, please, feel free to discuss this here. Renich 00:41, 28 January 2010 (UTC)
- When you ask "where should backups be stored", what exactly do you mean? Bacula can write it's backups to tape, dvd, removable media. Do you mean the backup database, which can also be stored under the database system?
- Any files used as volumes for bacula should be stored in a location of the user's choice: the user needs the ability to be able to add capacity as necessary. For the catalogue, this is probably best stored in the default database location. --Barry905 02:23, 1 March 2010 (UTC)
- Well, you're right. I should've specified the case of using a SAS or NAS. It should be mounted, according to the FHS, in /var/backups. This is all.
- I think it's an important matter, since we use SELinux. This should be standarized and secured by SELinux. A umask of 177 should be used too.
- In the case the user chooses an alternate location (for example, /mnt or /srv) we should note the correct SELinux context to be used and how to configure, don't you think? Renich 04:04, 1 March 2010 (UTC)
Password generation
I have run intro trouble while using signs in the passwords. I'd rather advise people to use lower and upper caps and numbers. I'd like some feedback about this, if possible. Renich 21:23, 19 February 2010 (UTC)
- One of the biggest problems with passwords in the bacula system is relating passwords to each other: in other words which passwords should match which other. Some sort of architecture is really required here. --Barry905 02:33, 1 March 2010 (UTC)
- Well, I really recommend using apg. This tool helps a lot with password generation and it's available in the repos.
- We should, also, specify, the password relationships, as you say. Renich 04:07, 1 March 2010 (UTC)
Distributed configuration
I like creating:
/etc/bacula/conf.d/
And adding all the specific conf files there. Afterwards, I just add the following to /etc/bacula/bacula.dir.conf:
@/etc/bacula/conf.d/foo-client.conf @/etc/bacula/conf.d/bar-client.conf @/etc/bacula/conf.d/jobs.conf
I'd love some feedback and suggestions on how to make this even better; so one can just add clients and jobs and stuff and have them well organized. A script for generating this would be awesome! ;) Renich 21:27, 19 February 2010 (UTC)
General Comments
This how-to could use a general discussion of the architecture of bacula: a description of the functionality of each component (the director, the client daemon, the file daemon, the catalogue database) and how they interact.
A discussion on backup strategies might also be in order. The strategy adopted for backups drives to a large degree the volumes, pools and jobs to be configured. The most time consuming part of setting up bacula is to create the .conf files to configure each of the components. Installation is relatively easy. --Barry905 03:04, 1 March 2010 (UTC)
- I agree with you, totally. We should, also, point out this at the current bacula manual. There's a concept definition somewhere... ;) Renich 04:09, 1 March 2010 (UTC)
SELinux
I haven't had much trouble with SELinux. Yet, I'm not so well informed on the creation of policies and stuff so, If anyone can tell me anything about this, would be awesome! Renich 21:29, 19 February 2010 (UTC)