In the "Configuring the Director" document, there's an entry regarding backups
"every 10 minutes", as follows:
Schedule {
Name = "TenMinutes"
Run = Level=Full hourly at 0:05
Run = Level=Full hourly at 0:15
Run = Level=Full hourly at 0:25
Run = Level=Full hourly at 0:35
Run = Level=Ful
Oops,
Sorry folks, I realized after I emailed this question that the question
itself was poorly framed (e.g., the Storage Directive must be of type File)
-- I presume that the Pool choices to restore from (Differential,
Incremental, Full) are presented to the administrator via the console.
Sorry
Philip, et al,
What about for Jobs that are Restore Types? Can one specify the Full Backup,
Incremental Backup and Differential Backup Pool directives for Restore jobs
rather than a mere "Pool" directive and thus ability to override a mere
"Storage" directive?
Best regards,
-H
On 10/10/07, Phil
Philip,
Thank you very much for checking my logic. I also think its logically makes
sense to take your suggestion of including the multiple pools within the Job
resource as you suggest (instead of relying solely on indirect reference to
these pools via the Schedule Resource Job overrides) -- even
Hello all --
In the Director Daemon configuration file (bacula-dir.conf), I am defining a
simple backup Job Resource that points to a Schedule Resource. My Schedule
Resource contains three backup types (with corresponding Pool Resources that
I have also in the configuration file):
# When to do th
Hi,
Our backups are run in 3 phases (7pm, 9pm, and 4am) to allow
certain tasks (ie. Windows ntbackup jobs, mysql dumps, etc.) to complete before
backing them up. We do differential backups mon-thu, and full backups on
Fridays. The first Full backup of the month becomes an archive backup
Maurizio Santini wrote:
> Hi,
>
> Just a question about the schedule resource. If the Pool directive is
> not defined like in
>
> # This schedule does the catalog. It starts after the WeeklyCycle
> Schedule {
> Name = "WeeklyCycleAfterBackup"
> Run = Full sun-sat at 1:10
> }
>
> ...does
On Fri, Sep 02, 2005, Maurizio Santini wrote:
> Hi,
>
> Just a question about the schedule resource. If the Pool directive is
> not defined like in
>
> # This schedule does the catalog. It starts after the WeeklyCycle
> Schedule {
> Name = "WeeklyCycleAfterBackup"
> Run = Full sun-sat a
Hi,
Just a question about the schedule resource. If the Pool directive is
not defined like in
# This schedule does the catalog. It starts after the WeeklyCycle
Schedule {
Name = "WeeklyCycleAfterBackup"
Run = Full sun-sat at 1:10
}
...does it mean that it uses the "Default" pool?
Thank
More on this. I checked bacula-dir.conf and after the clients assigned
to the Pool=Monitor_pc comes the client assigned to the Pool=gateway.
It looks like that instead of respecting the Schedule, bacula is backing
up the clients listed in bacula-dir.conf one after the other.
Why is that?
Mauriz
Hello,
I have the schedule resource
Schedule {
Name = "WeeklyCycle"
Run = Level=Full Pool=Home_Directory 1st fri at 21:00
Run = Level=Full Pool=Monitor_pc tue at 12:05
Run = Level=Full Pool=Test_server 1st sun at 05:00
Run = Level=Full Pool=gateway 1st sat at 04:00
Run = Level=Di
11 matches
Mail list logo
