Hello,
On 05.10.2005 15:10, Michael Koppelman wrote:
OK, thanks anyway...
?
Michael
On Oct 3, 2005, at 8:49 PM, Michael Koppelman wrote:
I've been searching the archive and it looks like I'm not the only
one confused by pool behavior. I apologize if this is redundant but I
can't seem to find an authoritative answer.
My goal is simple: put all Full backups in the Full pool, put all
Differentials in the Differential pool and put all Incrementals in
the Incremental pool. If a backup gets upgrade to Full, it should go
in the Full pool.
I'm sure this works, because I've got it set up like this. Although
automatically upgraded jobs need manual intervention, because I want
them to go to different storage as well...
Part of my confusion is that I'm expecting `status dir` to list the
pool the backup will go in. So far, I've never successfully gotten
the scheduled jobs to appear as if they are going to go to the pool
I've requested.
Hmm. The volume "status dir" reports is usually not correct when you
work with "Incremental Pool", "Full Pool", etc. directives. That's a
known issue, but as the guessed volume is almost never the one a job
goes to (because of pruning, tape changing, tape filling etc.) taht's
not much of a problem for me (and others).
First I tried this:
Schedule {
Name = "CWAnnualCycle1"
Run = Level=Full Pool=Full on jan 1 at 1:05
Run = Level=Full Pool=Full on jul 1 at 1:05a
Run = Level=Differential Pool=Diff monthly on 1 at 1:05
Run = Level=Incremental Pool=Inc daily at 1:05
}
But when the job ran it went to Pool=Default, the last thing I would
have expected.
That job was probably automatically upgraded, and the setting in the job
resource was "Pool=Default"?
Then I tried this:
JobDefs {
Name = "CWJob"
Type = Backup
Level = Incremental
Client = neutron-fd
FileSet = "www"
Storage = File
Messages = Standard
Pool = Full
Full Backup Pool = Full
Incremental Backup Pool = Inc
Differential Backup Pool = Diff
Priority = 10
}
...but all my scheduled jobs list volumes from Pool=Default again!
That's interesting. Did you do a reload or a restart of the DIR after
changing the configuration?
I'm sure I'm just being stupid and I apologize for what is probably a
recurring question.
No need to apologize, only I just don't see the reason for this
behaviour yet.
I'd suggest you stop the DIR, pick one job setup where you verify the
settings in the job resource as well as the overrides in the schedule,
start the DIR again, see what the status report says, and watch what
actually happens when the job runs. The last two items might indeed show
a difference, but usually things are running correctly...
Arno
Thanks,
Michael
PS - I think bacula has tremendous potential. We are looking forward
to deploying it in production if we can get it doing what we think we
are telling it to do.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,
discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
