Hi,
Thanks for the answer.
But what about this then:
If you then want to do subsequent backups, you may need to move the
Virtual Full Volume back to your normal backup pool. Alternatively, you
can set your Next Pool to point to the current pool. This will cause
Bacula to read and write to Volumes in the current pool.
So what would be the correct way to create VirtualFull's then?
Thanks
Jean-Louis
On 2013-02-06 10:37, Jummo wrote:
> Hi Jean-Louis,
>
> On Tue, 5 Feb 2013, Jean-Louis Dupond wrote:
>
>> Hi,
>> I've been playing with Bacula a bit lately, and it works quite fine
>> :)
>> But now I want to use Virtual Full backup's. This to minimize
>> bandwith used by Bacula.
>> I have the following Pool:
>> Pool {
>> Name = ApolloFile
>> Pool Type = Backup
>> Storage = ApolloFile
>> Maximum Volume Jobs = 2
>> Next Pool = ApolloFile
>> Recycle = yes # Bacula can automatically
>> recycle Volumes
>> AutoPrune = yes # Prune expired volumes
>> Volume Retention = 30 days
>> Action On Purge = Truncate
>> Maximum Volumes = 100 # Limit number of Volumes in
>> Pool
>> LabelFormat = "FileApollo"
>> }
>> Storage:
>> Storage {
>> Name = ApolloFile
>> Address = xxx.xxx.xx
>> SDPort = xxx
>> Password = "xxxxxx"
>> Device = FileStorage
>> Media Type = ApolloFile
>> Maximum Concurrent Jobs = 20
>> }
>>
>
> Bacula can't use the same pool for reading and writing at the same
> time [1].
>
> Best Regards,
> Patrick
>
> [1]
>
> http://www.bacula.org/5.2.x-manuals/en/main/main/Released_Version_3_0_3_3_0_.html#SECTION00427000000000000000
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
