Re: [Bacula-users] Lets open up a discussion about estimating required space for backups.
Hi Dmitri, WOW! I didn’t know about vchanger. I just read the wiki article about it and this could really change how I do disk based backup. I like using a NAS for bacula in the datacenter but some of my customers have it in their offices and this would really make things cheaper with higher retentions. Thanks.!! Jeff On Aug 15, 2014, at 11:39 AM, Dmitri Maziuk dmaz...@bmrb.wisc.edu wrote: On 8/14/2014 7:34 PM, Jeff MacDonald wrote: ... Is there a good way to plan ahead? If your backup is growing (they always are), you will eventually hit the limits. There are a couple of workarounds: 1. use hot-swappable drives and vchanger. That means manual swapping of drives re-labeling the volumes when your storage fills up. Some volumes will be offline. 2. Use resizable storage like zfs and hope drive capacity grows faster than your backup. Then you can keep replacing your drives w/ bigger ones keep up while keeping everything online. No vchanger means bacula's autolabeling will work, too. 3. Back up to cloud files. This one's ugly for many reasons but in theory the cloud will accommodate any number of file volumes, they'll all be online, autolabeled, etc. Dima -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Lets open up a discussion about estimating required space for backups.
You have a file based storage array available with a capacity of say 6 TB, and you have to back up 20 clients. Lets say I’m going with the default Full/Diff/Inc weekly schedule and that I’ve had an arbitrary retention time of 1 year on fulls 6 months on diffs and 1 month on incrementals. What strategies would you employ to manage disk space, estimate growth etc. Is there a missing variable here, witch is the size of your full backups? As for strategy I like to use GFS Rotation like explained on this diagram: http://www.bacula.com.br/?p=2271 Chhers, -- Heitor Medrado de Faria | Need Bacula training? 10% discount coupon code at Udemy: bacula-users https://www.udemy.com/bacula-backup-software/?couponCode=bacula-users +55 61 2021-8260 +55 61 8268-4220 Site: www.bacula.com.br Facebook: heitor.faria http://www.facebook.com/heitor.faria Gtalk: heitorfa...@gmail.com -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Lets open up a discussion about estimating required space for backups.
On 8/14/2014 7:34 PM, Jeff MacDonald wrote: ... Is there a good way to plan ahead? If your backup is growing (they always are), you will eventually hit the limits. There are a couple of workarounds: 1. use hot-swappable drives and vchanger. That means manual swapping of drives re-labeling the volumes when your storage fills up. Some volumes will be offline. 2. Use resizable storage like zfs and hope drive capacity grows faster than your backup. Then you can keep replacing your drives w/ bigger ones keep up while keeping everything online. No vchanger means bacula's autolabeling will work, too. 3. Back up to cloud files. This one's ugly for many reasons but in theory the cloud will accommodate any number of file volumes, they'll all be online, autolabeled, etc. Dima -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Lets open up a discussion about estimating required space for backups.
Hi, This has plagued me for a while… [ and while it sounds a lot like a home work question… its actually just be being curious and reaching out :) ] Imagine a scenario similar to this: You have a file based storage array available with a capacity of say 6 TB, and you have to back up 20 clients. Lets say I’m going with the default Full/Diff/Inc weekly schedule and that I’ve had an arbitrary retention time of 1 year on fulls 6 months on diffs and 1 month on incrementals. What strategies would you employ to manage disk space, estimate growth etc. I guess there are a few scenarios 1 : eventually you will find out that your arbitrary limits are just not possible to accomplish with given diskspace. OR 2: it will work fine and things will get recycled fine. Is there a good way to plan ahead? Thanks! Jeff. (Runkle on irc #bacula) -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
