Thanks for clearing all this up, that makes sense about not using the schedule
when
executed manually and the default behavior when not specified (As I was
specifying
it in the schedule).
I spoke to soon, looking at the schedule, it correctly showed the
intended Job Type. It started with a Full
I spoke to soon, looking at the schedule, it correctly showed the
intended Job Type. It started with a Full on the specified time in
the Schedule and the next few scheduled times after that had specified
Differential's so the schedule showed this.
When it came time to run it (on its own as per
I have a schedule defined as follows:
Schedule {
Name = Server Data Weekly Cycle
Run = Level=Full mon at 18:00
Run = Level=Differential tue-fri at 18:00
}
A job as follows:
Job {
Name = Backup-Data-client
Client = client-fd
JobDefs = Default
Pool = Svr_Data
Storage = name
Joseph L. Casale wrote:
When I run it the first time, it does a FULL, when I add data, and
run it again, it does am Incremental?
What am I missing? I was expecting a Differential?
When you ran the job the first and second time, do you mean you
initiated the job manually (i.e. with the
When you ran the job the first and second time, do you mean you
initiated the job manually (i.e. with the run command in the console)
or do you mean you sat back, did nothing, and let bacula start the job
all by itself based on the schedule?
I used the run command (Well weBacula did actually). I
Joseph L. Casale wrote:
When you ran the job the first and second time, do you mean you
initiated the job manually (i.e. with the run command in the console)
or do you mean you sat back, did nothing, and let bacula start the job
all by itself based on the schedule?
I used the run
On 9/11/2009 9:16 PM, Joseph L. Casale wrote:
When you ran the job the first and second time, do you mean you
initiated the job manually (i.e. with the run command in the console)
or do you mean you sat back, did nothing, and let bacula start the job
all by itself based on the schedule?
You're not actually testing your schedule settings when you run the job
manually.
Cedric/Mike,
Thanks for clearing all this up, that makes sense about not using the schedule
when
executed manually and the default behavior when not specified (As I was
specifying
it in the schedule).
It's now
