> At first, the volume retention of two days for full > backups looks like a > very dangerous mistake. Maybe it should be 2 weeks? If > this was for some > testing, it's ok. But remember to fix this before you > expect the system > really works as it should...
Yes, I'm doing just testing before production deploy. :-) > Then, the actual problem is, that incremental backups all > go to the same > volume day after day? My goal is explained here: 1. I would like to make a full backup on Thursday evening in a specified file WeeklyFull that must be recycled every week. 2. The other days (from Friday to Wednesday) I would like to add incremental backup on another file called IncrDaily. When the cycle come to end, I would like to add another WeeklyFull (to mantain them for a mounth) and instantly recycle IncrDaily for the new week. > > You need to limit somehow when Bacula stops using the > volume, then it will > recycle the oldest one in the pool. So, consider adding > one of these into > IncrDaily pool spesification: > - Use Volume Once = yes > - Maximum Volume Jobs = xx > - Volume Use Duration = xx hours > - Maximum Volume Bytes = xxGB I've tried to simulate a "short week" made of 3 days of 65 minutes: Job { Name = "BackupRapid" Type = Backup Level = Incremental Client = test.localdomain-fd FileSet = "Test Set" Schedule = "RapidDiskDaily" Storage = RapidDiskBck Messages = Standard Pool = RapidIncrDaily Priority = 10 Write Bootstrap = "/var/bacula/working/BckTestServerEtc.bsr" } Client { Name = test.localdomain-fd Address = 192.168.1.2 FDPort = 9102 Catalog = MyCatalog Password = "12345" # password for Centos Test File Retention = 30 days # 30 days Job Retention = 6 months # six months AutoPrune = yes # Prune expired Jobs/Files } Pool { Name = RapidFullWeek Pool Type = Backup Recycle = yes Use Volume Once = yes AutoPrune = yes Volume Retention = 1h Volume Use Duration = 1h } Pool { Name = RapidIncrDaily Pool Type = Backup Recycle = yes AutoPrune = yes Volume Retention = 1h Volume Use Duration = 1h Maximum Volume Jobs = 1 Maximum Volumes = 1 Recycle Oldest Volume = yes } FileSet { Name = "Test Set" Include { Options { signature = MD5 compression=GZIP9 } File = /etc } } Schedule { Name = "RapidDiskDaily" Run = Level=Full Pool=RapidFullWeek at 16:45 Run = Level=Incremental Pool=RapidIncrDaily at 16:50 Run = Level=Full Pool=RapidFullWeek at 17:50 Run = Level=Incremental Pool=RapidIncrDaily at 17:55 Run = Level=Full Pool=RapidFullWeek at 18:55 Run = Level=Incremental Pool=RapidIncrDaily at 19:00 Run = Level=Full Pool=RapidFullWeek at 20:00 Run = Level=Incremental Pool=RapidIncrDaily at 20:05 Run = Level=Full Pool=RapidFullWeek at 21:05 Run = Level=Incremental Pool=RapidIncrDaily at 21:10 Run = Level=Full Pool=RapidFullWeek at 22:10 Run = Level=Incremental Pool=RapidIncrDaily at 22:15 } Storage { Name = RapidDiskBck Address = 192.168.1.1 # N.B. Use a fully qualified name here SDPort = 9103 Password = "abcde" Device = RapidDiskBck Media Type = File } The trouble is this: the Full Backup volume is correctly recycled because is set Use Volume Once, but the incremental backup is alway appended to Incremental Volume without expiration... Now I'm just trying to understand the Bacula functioning, after this test phase I'll pass to production use. Thanks for your time. Simone ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users