On Thu, Oct 9, 2008 at 9:41 AM, John Drescher <[EMAIL PROTECTED]> wrote: >> Could you point to some online docs on how to do it. Currently I have >> one volume with a size of 567GB, and my space is running low. How >> should the volumes be setup? 100gb each, and how do I set the rotation >> so it knows to pick next volume, or create next volume. >> > > I do not have a guide but I do have ideas. Do you have any other > machine on your network that can hold this 567GB volume? If you do and > you can transfer the volume file to the other machine you can setup > the second machine with a storage daemon to hold the backup data. Mark > this volume Used or full using update volume > > Then fix your current setup. Limit the pool size for new volumes so > that you do not get into this situation. > > http://www.bacula.org/en/dev-manual/Automatic_Volume_Recycling.html > > Maximum Volume Bytes = 10G > > I use 2G, 5G and 10G in a lot of my disk pools. > > At this point you can continue with backups on the original storage > daemon. If you can not wait for the retention time to expire you could > possibly use migration to migrate jobs from the large volume to the > new storage daemon. I have never used this feature so someone else > will have to say if this will work across 2 storage daemons. > > If you have any problems or questions ask the list. I will try to help > if I can add anything (that I consider useful) to the conversation.. > > John >
-- John M. Drescher ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
