>On 1/5/2015 9:20 AM, philhu wrote:
>I added 8tb to my nas, all machines show the new size/free etc, but bacula
>decided that because
>the NAS drive size is bigger, it will do a Full on all my backups/sets.
>
>Why should the nas getting bigger cause all new fulls? The data on the drive
>did not change
>
>It wouldn't. Perhaps growing the nas was only coincidental. Did the
>retention period for the previous fulls expire? Did the FileSets change
>for any reason?
Well, looking through bacula-dir.conf, I see that I forgot and left the client
resource parameter "File Retention = 60 days", It was supposed to be set to '2
years'. I started using Bacula in Oct'14 and this occurred in middle of
December, so is that the cause? Here is part of my config:
Client {
Name = bacula-fd
Address = bkpcentos7
FDPort = 9102
Catalog = MyCatalog
Password = "<<redacted>>" # password for FileDaemon
File Retention = 60 days # 60 days
Job Retention = 6 months # six months
AutoPrune = yes # Prune expired Jobs/Files
}
Pool {
Name = LTO4Tapes
Pool Type = Backup
Volume Retention = 730 days
Recycle = no
AutoPrune = no
Cleaning Prefix = CLN
# Maximum Volume Bytes = 2000G
}
+----------------------------------------------------------------------
|This was sent by p...@isone.biz via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+----------------------------------------------------------------------
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
