So... I decided make to myself and do this:
Pools:
Pool {
Name = WeeklyCycle
Pool Type = Backup
Maximum Volume Jobs = 1
Volume Retention = 1 weeks
Recycle = yes
AutoPrune = yes
LabelFormat = Weekly
}
Pool {
Name = MonthlyCycle
Pool Type = Backup
Maximum Volume Jobs = 1
Volume Retention = 1 months
Recycle = yes
AutoPrune = yes
LabelFormat = monthly
}
Jobs:
Job {
Name = WeeklyCycle
Type = Backup
Level = Full
Client = server-fd
FileSet = DADOS
Schedule = WeeklyCycle
Storage = SAMBA-WEEKLY
Pool = WeeklyCycle
Messages = Standard
}
Job {
Name = MonthlyCycle
Type = Backup
Level = Full
Client = server-fd
FileSet = DADOS
Schedule = MonthlyCycle
Storage = SAMBA-MONTHLY
Pool = MontlhyCycle
Messages = Standard
}
Storages:
Storage {
Name = SAMBA-MONTHLY
Password =
Address = 192.168.200.5
SDPort = 9103
Device = SAMBA-MONTHLY
Media Type = File
Maximum Concurrent Jobs = 20
}
Storage {
Name = SAMBA-WEEKLY
Password =
Address = 192.168.200.5
SDPort = 9103
Device = SAMBA-WEEKLY
Media Type = File
Maximum Concurrent Jobs = 20
}
Schedules:
Schedule {
Name = WeeklyCycle
Run = Level=Full 1st sun at 19:05
Run = Level=Incremental mon-sat at 19:05
}
Schedule {
Name = MonthlyCycle
Run = Level=Full Pool=MonthlyCycle 1st sun at 00:00
}
So, I hope all this right!
Thanks
2014-03-10 14:33 GMT-03:00 John Drescher <dresche...@gmail.com>:
> On Mon, Mar 10, 2014 at 1:14 PM, Gilberto Nunes
> <gilberto.nune...@gmail.com> wrote:
> > Hello friends
> >
> > I just wanna a suggestions about this Pools, Schedules and Jobs...
> > My idea here is using only one file to make Full and Incremental
> backup...
> > It's work quiet well, but I have doubt with Retention Volume...
> > When it reach day 30 it's make as used and recycle the volume and start
> > backup again over the same volume??
> >
> > Thanks
> >
> >
> > The Pool
> >
> > Pool {
> > Name = Samba
> > Pool Type = Backup
> > Volume Retention = 30 days
> > Recycle = yes
> > AutoPrune = yes
> > LabelFormat = DadosSamba
> > }
> >
> >
> > And the rest:
> >
> >
> > Schedule {
> > Name = BackupSambaFull
> > Run = Level=Full Pool=Samba 2nd sat at 22:30
> > }
> > Job {
> > Name = BackupSamba-Full
> > Type = Backup
> > Level = Full
> > Client = server-fd
> > FileSet = DADOS
> > Schedule = BackupSambaFull
> > Storage = BackupSamba
> > Pool = Samba
> > Messages = Standard
> > }
> > Job {
> > Name = BackupSamba-Incremental
> > Type = Backup
> > Level = Incremental
> > Client = server-fd
> > FileSet = DADOS
> > Schedule = BackupSamba-Incremental
> > Storage = BackupSamba
> > Pool = Samba
> > Messages = Standard
> > }
> > Schedule {
> > Name = BackupSamba-Incremental
> > Run = Level=Incremental Pool=Samba at 22:00
> > }
> >
>
>
> In your example volume retention will not happen in 30 days. bacula
> will fill up the filesystem containing your volume then mark your
> volume full asking you to label additional volumes. At the point that
> the volume is marked full the 30 days will begin..
>
>
> The solution to this problem is you must limit the # of jobs run on a
> volume, its use duration, volume size ...
>
> Also I do not recommend a single volume as it requires you to
> throwaway all of your old backups when you recycle.
>
>
> John
>
--
Gilberto Ferreira
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
