Hello Carlo,
Thank you very much for your kind words :).
Yes, you can specify the "Next Pool" directive in your Job rescource or in
your Schedule resource. If you specify it in the Job resource, it will
override the one specified in the Pool resource. If you specify it in the
Schedule resource, it will override the ones in the Job and Pool resources.
Best regards,
Ana
On Wed, Sep 23, 2015 at 9:56 AM, Carlo Filippetto <
carlo.filippe...@gmail.com> wrote:
> since you are so kind and prepared,
> I have another question:
>
> All my strategy will be based on Incremental, so every weekly I will copy
> the last incremental in the "DestinationPool", and every Month I have to
> perform a VirtualFull..
>
> If I understood well, in both case I have to set a 'Next Pool' into the "
> OriginalPool", can I set different "Next Pool" for this 2 Jobs?
>
> How can I do?
>
> Thank you
>
>
> 2015-09-23 3:39 GMT+02:00 Ana Emília M. Arruda <emiliaarr...@gmail.com>:
>
>> You're welcome :).
>>
>> I'm sorry I made a mistake with the directive for the volume retention
>> period in the Pool definition. The bellow is correct:
>>
>> Pool {
>> Name = OriginalPool
>> Pool Type = Backup
>> Volume Retention = 7 days
>> ...
>> Next Pool = DestinationPool
>> }
>>
>> Pool {
>> Name = DestinationPool
>> Pool Type = Backup
>> Volume Retention = 30 days
>> }
>>
>> Best regards,
>> Ana
>>
>> On Tue, Sep 22, 2015 at 6:38 PM, Carlo Filippetto <
>> carlo.filippe...@gmail.com> wrote:
>>
>>> Thank you very mutch
>>>
>>> ^_^
>>> Il 22/set/2015 18:50, "Ana Emília M. Arruda" <emiliaarr...@gmail.com>
>>> ha scritto:
>>>
>>>> Hello Carlo,
>>>>
>>>> Yes. You can have a "Next Pool" directive configured for being used by
>>>> your copy job. This way, you can configure the pool for 30 days retention:
>>>>
>>>> Job {
>>>> Name = OriginalJob
>>>> Type = Backup
>>>> ...
>>>> Pool = OriginalPool
>>>> }
>>>>
>>>> Pool {
>>>> Name = OriginalPool
>>>> Pool Type = Backup
>>>> Retention Period = 7 days
>>>> ...
>>>> Next Pool = DestinationPool
>>>> }
>>>>
>>>> Pool {
>>>> Name = DestinationPool
>>>> Pool Type = Backup
>>>> Retention Period = 30 days
>>>> }
>>>>
>>>> Job {
>>>> Name = CopyJob
>>>> Type = Copy
>>>> Pool = OriginalPool
>>>> ...
>>>> }
>>>>
>>>> Best regards,
>>>> Ana
>>>>
>>>> On Tue, Sep 22, 2015 at 8:00 AM, Carlo Filippetto <
>>>> carlo.filippe...@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>> Noone have idea if the copy job can have a retention bigger that the
>>>>> original volumes?
>>>>> I have to modify it from "Update" command in bconsole?
>>>>>
>>>>> Thank you
>>>>>
>>>>>
>>>>>
>>>>> 2015-09-21 16:33 GMT+02:00 Carlo Filippetto <
>>>>> carlo.filippe...@gmail.com>:
>>>>>
>>>>>> Hi all
>>>>>>
>>>>>> I would like to modify my backup strategy: it is possible to use Copy
>>>>>> Job as Weekly Job?
>>>>>>
>>>>>> I'll explain:
>>>>>> I need to make every day incremental, to move this volumes outside
>>>>>> for restore in second site, but I can't use 30 Volumes, to cover all the
>>>>>> month. Can I use 7 daily volumes and every Sunday make a Copy of the last
>>>>>> Volumes (with retention 30days) and let them leave for a month?
>>>>>>
>>>>>> Thank you
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>>
>>>>> _______________________________________________
>>>>> Bacula-users mailing list
>>>>> Bacula-users@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>>>>
>>>>>
>>>>
>>
>
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
