Hi Dan,
I believe that solved my problem, and explains why the new volume (which only
got created after making changes and running "reload") made it into the
"bryanslack-scratch" pool. But the other old volumes still around from before
the changes didn't seem to want to go into the scratch pool like I wanted.
Also I put some lines to kick off a "remove scratch pools" admin-job after my
job. After a migration the source volumes go to scratch, then after that, they
get deleted from the catalog and from the disk. I'm not sure if after or
before is right, in fact I am not sure if I'm using the scratch pools correctly
in the first place. But now when I run "list volume" I don't see anything in
the virtual pool anymore, which was what I was hoping for. They go to scratch,
and then the stuff below removes them.
Command = "sh -c \"/bin/echo run job=bryanslack-remove yes | bconsole -n\""
Then that job (bryanslack-remove) basically does nothing at all except it runs
this at the end,
Command = "/etc/bacula/scripts/removeScratchPools.sh %c"
And that command is converted from a perl script I found somewhere.
Thanks Dan and Phil for your time.
Bryan
On Jun 22, 2012, at 9:56 AM, Dan Langille wrote:
> On 2012-06-19 19:57, Bryan Harris wrote:
>> Hello all,
>>
>> I'm trying to place my volumes into a scratch pool of a custom name
>> using these lines. However, the volumes do not move into the scratch
>> pool after usage. Instead, they remain in the pool called
>> "bryanslack-virtuals". When I run "list volume" I get a volume in my
>> scratch pool. The listed volume says Recycle for VolStatus.
>>
>> I guess my question is, how can I move the volumes used by a job
>> right after that job runs?
>>
>> Pool {
>> Name = bryanslack-virtuals
>> Storage = bryanslack-virtuals
>> Pool Type = Backup
>> Use Volume Once = yes
>> Recycle = yes
>> Recycle Oldest Volume = yes
>> Recycle Current Volume = yes
>> Purge Oldest Volume = yes
>> Auto Prune = yes
>> Maximum Volumes = 100
>> Volume Retention = 1 minute
>> Maximum Volume Jobs = 1
>> Label Format =
>> "${Client}_${Year}-${Month:p/2/0/r}-${Day:p/2/0/r}_${Hour:p/2/0/r}:${Minute:p/2/0/r}-${Pool}-${JobId}"
>> Next Pool = bryanslack
>> Action On Purge = Truncate
>> Scratch Pool = bryanslack-scratch
>> Recycle Pool = bryanslack-scratch
>> }
>>
>> Pool {
>> Name = bryanslack-scratch
>> Pool Type = Backup
>> }
>
> After making these changes, did you run update in bconsole? You need to
> update the volume definitions from the pool definition.
>
> That is, you need to tell the existing volumes that their attributes have
> changes.
>
> --
> Dan Langille - http://langille.org/
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
