Hi, 07.12.2007 08:39,, Johan van Vliet wrote:: > Hi, > > I have two questions about doing backups to harddisk with bacula. I'll > put them in seperate emails to keep this clean but they are somewhat > related: > 1st - What is a good "volume/poll" setup? (Experience question) > 2nd - Why does my solution now only use inc-0003? (Config question). > > > I'll use this email for the first question: > > I have an almost working solution (execpt for email 2). I used the > default configs and adjusted them with the aid the examples in the > manual. I'm just not sure I made some good choices. For example I would > now like to add another machine and need to change Pool parameters to > make this work. Because the number of clients is directly tied to "Max > Volume Jobs" (#client * #needed_volumes". Same for "Maximum Volumes" > (#clients * #iwant-to-keep). > > > Question: > Who has a working/extenable configuration? I'm more interested in the > idea behind it than the actual config but the config may help to build > it. But it's the idea's and insight I'm looking for (bacula manual can > help me with the config).
No configuration, but some hints which may or may not help you... My experience is that it's usually not very effective to limit the volume use by the number of jobs. While this looks like a good solution, it has some disadvantages: - It breaks if you add or remove jobs, - it breaks if you run out of disk space, - it breaks if, for whatever reasons, you skip jobs or run extra jobs. Usually, you're limited by the available storage capacity, so it's more useful to limit the pool size by size. Just allow a maximum number of volumes, with a fixed maximum volume size. As Bacula can easily manage the volumes to use, from Baculas point of view there's no problem. You do need a reasonable estimate of the amount of data for the pools, though, but you can adjust the settings rather easily. I usually start with a setup where I limit the number of volumes per pool a bit below what I expect will be needed, and once I get notifications that more volumes are neede, I just increase the "Maximum Volumes" parameter. After a full backup cycle, I add some extra volumes, and usually find that I don't have to touch the setup unless more clients are added or data grows quicker than expected. If you want to keep your jobs together, for example to more easily copy volumes from certain days to an external storage device, that's another thing... which could be (partly) solved by using migration, though. Such a setup is more flexible, and does need less management, so I prefer that. Arno -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
