Hi, Thanks for the suggestion - we already run auto-recycling with a limit on the number of volumes (60 full, 60 incremental). Most of our schedules run full backups once a week and incrementals in between, with a thirty day expiry on the incremental volumes and three months on the fulls. Rotating this once a month through three NAS disks means that at any one time we have about one year's worth of backups available. We are not archiving, so that suits us fine!
Although we are up to the 60 fulls now, we have (as yet) never needed more than about 20 incremental volumes before they start recycling, so all that happened when the NAS was offline was that Bacula created two new incrementals with names the same as the last two it used (IYSWIM) as they were nowhere near full! I couldn't find a definitive description of what would happen if I tried to purge the jobs in the catalog that were missing from the backup files (either in terms of whether it would do it, or what the result on subsequent backups would be) so I decided to try and rebuild the catalog. I couldn’t quickly find out where the indicators for the next volume to use were kept and hence couldn't get backups to work again after the rebuild... Thanks Mike _____________________________________________________________________ This message has been checked for all known viruses by KMSinternet, powered by Messagelabs. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
