Is it correct that every Volume needs to have an Unique Slot number?
Its not possible to have multiple devices using a different Slot?
Op 07-02-13 01:30, John Drescher schreef:
>>> http://sourceforge.net/projects/vchanger/
>> I've been playing a bit with the vchanger and disk-changer now.
>> But
>> http://sourceforge.net/projects/vchanger/
> I've been playing a bit with the vchanger and disk-changer now.
> But am I right about the following:
>
> You can specify a number of slots, but there is a hardcoded slot limit,
> so also a hardcoded Volume Limit?
>
> Because currenly I have "Max Jobs
Op 06-02-13 18:53, John Drescher schreef:
>> Not the pool, your storage has two devices. For multiple devices in a
>> Backup2Disk Storage you have to use a script to emulate a tape library
>> with two or more devices and an autochanger. For Bacula your Backup2Disk
>> storage is like a library with
> Not the pool, your storage has two devices. For multiple devices in a
> Backup2Disk Storage you have to use a script to emulate a tape library
> with two or more devices and an autochanger. For Bacula your Backup2Disk
> storage is like a library with one tape.
Agreed. For disk based storage I hi
On Wed, 6 Feb 2013, Jean-Louis Dupond wrote:
>
> How can a Pool be defined with 2 Storage devices?
> The Pool defines:
> Storage = ApolloFile
>
> But you can't define 2 devices for 1 storage?
>
> Any change to get an example? Cause the Virtual Full documentation is not
> always as clear.
>
Not t
On 2013-02-06 10:46, Jummo wrote:
> On Wed, 6 Feb 2013, Jean-Louis Dupond wrote:
>
>> 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
On Wed, 6 Feb 2013, Jean-Louis Dupond wrote:
> 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 cur
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 Volum
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 = B
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 Poo
10 matches
Mail list logo
