Re: [Bacula-users] Use Copy Incremental Job as Weekly Job

Hello Carlo,

From a previous post, you said "I will copy the last incremental in the "DestinationPool". When dealing with incremental backups, for a full restore, you need the last full and all subsequent incrementals. Maybe you need to use differential backups, where you just need the last full + last differential volumes ok?

On Wed, Sep 23, 2015 at 11:14 AM, Carlo Filippetto <carlo.filippetto AT gmail DOT com> wrote:

Can I ask you another question?

I have a daily volumes that contain all Daily Job..
After seven days it is recycled. I want that one a week, the oldest one, will be copied in the 'weekly' pool, but how has to be this Job?

Copying just the oldest one (incremental volume) will not be enough for your restores... I´m not sure, but are you going to copy the last one before it is recycled? Is this your goal here? If so, then you can use the "selection type = OldestVolume" in you copy job. But if you intend to use these volumes for restores, you will need the last full and all of your incremental subsequents backups since the last full.

I have to create a special Job?
I have to specify in the "weekly" pool (that is the Next Pool) the option below?
Selection Type = OldestVolume

The job must have a "client" information, I have to use one a random?

Yes, to accomplish this (copy the oldest volume in the daily pool into the weekly pool), you need a copy job (a special job). This job can be like this:

Job {

Name = CopyJob

Type = Copy

Selection Type = OldestVolume

...

}

The option "Selection Type = OldestVolume" must be specified in the Copy Job resource, not in Pool.

The client directive must be present despite the fact that it is not used. Since the copy jobs work with backup data present in the volumes, there is no need of client communication to SD for sending the data.

The same question is for the VBackup, every month I have to create a VirtualFull, I think that for these I don't have to create nothing and it is only a configuration like "type = VBackup" and "NextPoll=Monthly" in the Scheduler?

The VirtualFull Backups are configured with Level=VirtualFull, there is no VBackup type. You can set NextPool=Monthly in the schedule resource to override the Next Pool in the Pool resource.

It's correct?

Thank you

You´re welcome.

Best regards,

Ana

2015-09-23 15:38 GMT+02:00 Carlo Filippetto <carlo.filippetto AT gmail DOT com>:
Great!

You solve me a lot of questions

^_^

2015-09-23 15:07 GMT+02:00 Ana Emília M. Arruda <emiliaarruda AT gmail DOT com>:
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.filippetto AT gmail DOT 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 <emiliaarruda AT gmail DOT 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.filippetto AT gmail DOT com> wrote:
Thank you very mutch

^_^

Il 22/set/2015 18:50, "Ana Emília M. Arruda" <emiliaarruda AT gmail DOT 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.filippetto AT gmail DOT 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.filippetto AT gmail DOT 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 AT lists.sourceforge DOT 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 AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users