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 = DestinationPoo
Thank you very mutch
^_^
Il 22/set/2015 18:50, "Ana Emília M. Arruda" 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 = B
Hello,
The recommendation for Bacula versions are:
director = storage daemon >= file daemon
It seems you have your director and storage daemon running 5.2.5 version
and client running 5.2.10. Also, is your system 32 or 64 bits?
Best regards,
Ana
On Tue, Sep 22, 2015 at 2:48 AM, Radosław Korzen
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
Reten
Hi Wagar,
This is occuring because you have "Recycle = yes" configured in your Pool.
This way, when bacula needs a volume, it will try to find one that had
passed the retention period (in your case, 8 days). This is not a "volume
name reuse", but a "volume reuse" because of your configurations.
I
Hello,
It looks to be an issue with the AFS code, I pushed a fix in the git
repository (Branch-7.2), I would appreciate your feedback.
Thanks,
Best Regards
Eric
On 09/22/2015 02:15 PM, Wanderlei Huttel wrote:
> I'm running Debian GNU/Linux 8.2 (jessie) with Kernel Linux 4.2.0 and I
> can't comp
Hi, Waqar.
Logic of bacula work with hdd is emulate tape, so every you volume is a
virtual tape. Situation, what you offering is that you use new virtual
tape every time, that previous tape are full. So after mean while you
have are very box with volumes (tapes) :)
I'm not specialist in Bacula
Hi all.
Bacula version: 5.0.0
I asked this question yesterday and have been reading the docs to find a
solution but have not been able to do so.
I only do file volume backups (no tapes) and I copy all the volumes to a remote
location. In order to sync them I look at the volume names and decide
I'm running Debian GNU/Linux 8.2 (jessie) with Kernel Linux 4.2.0 and I
can't compile bacula in it.
Configuration on Tue Sep 22 07:52:30 BRT 2015:
Host: x86_64-unknown-linux-gnu -- debian 8.2
Bacula version: Bacula 7.2.0 (14 August 2015)
Source code locatio
I'm running Debian GNU/Linux 8.2 (jessie) with Kernel Linux 4.2.0 and I
can't compile bacula in it.
Configuration on Tue Sep 22 07:52:30 BRT 2015:
Host: x86_64-unknown-linux-gnu -- debian 8.2
Bacula version: Bacula 7.2.0 (14 August 2015)
Source code locatio
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 :
> Hi all
>
> I would like to modify my backup strategy: it is possible to use Copy Job
> as
11 matches
Mail list logo
