Dear Kern,
Em Ter, 2014-09-09 às 17:21 +0200, Kern Sibbald escreveu:
> ...If you want to clearly separate Volume by clients, jobs, or by
> some other criteria, you probably should be using different Pools.
> Different pools are the most reliable way to ensure that only
> particular jobs, clients, ... go to a particular volume.
On my actual configuration, create a different pool for each service,
for each kind of backup, will result in 33 pools.
What I have done now is to create a volume per day, labeled with the
year, month and date, with use time of 23h, not recycling and truncate
action on purge, so the volumes purged will not use disk space. all the
backups of the day will be in the volume, something about 4 GB, and only
the Fulls will have about 300Gb.
It's not the ideal situation that I expected, but will simplify thinks,
attached are my pool configuration.
Thanks for your help, best regards.
Pool {
Name = Interna
Pool Type = Backup
Storage = Interno
Recycle = no
AutoPrune = yes
Volume Use Duration = 23h
Volume Retention = 60 days
Action On Purge = Truncate
LabelFormat = "${Year}-${Month}-${Day}"
Next Pool = Externa
}
Pool {
Name = Externa
Pool Type = Backup
Storage = Externo
Recycle = no
AutoPrune = yes
Volume Use Duration = 23h
Volume Retention = 60 days
Action On Purge = Truncate
LabelFormat = "${Year}-${Month}-${Day}"
}
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
