Hello,
pt., 12 lis 2021 o 03:39 Shaligram Bhagat, Yateen (Nokia - IN/Bangalore) <
yateen.shaligram_bha...@nokia.com> napisał(a):
> Hi Radoslaw,
>
>
>
> Thanks.
>
> Well, that is what I thought.
>
>
>
> But my requirement is different.
>
> There are hundreds of clients and I want to create yearly archives (at
> present for past years and later for future years too) for each of them.
>
What do you mean "yearly archives"? Is it a backup job? A cloned/migrated
job to the other storage? Something else?
> This will create a job inventory that will run into thousand.
>
What is a "job inventory"? I never heard of it in Bacula.
Bacula has no problem handling hundreds of thousands of jobs.
> The simplest way could be to create one single archive job for each client
> and run it with a fileset defined for each year.
>
How is your filesets for this feature defined?
Why do you need to change filesets? It is so strange.
I wonder why there is no fileset override for a job in the schedule
> resource, when there are so many other overrides provided.
>
> This requirement may be an enhancement candidate ??
>
Let's assume you have a two totally distinct fileset resources, i.e.
Fileset {
Name = FS1
Include {
File = /home
}
}
Fileset {
Name = FS2
Include {
Plugin = "qemu: vm=vm1"
}
}
and every other day in the Schedule for Incremental level backup you switch
between them back and forth.
What is your expected result in this case, when you select the most recent
backup to restore?
The above question is to understand the requirements.
best regards
--
Radosław Korzeniewski
rados...@korzeniewski.net
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
