Re: [Bacula-users] Problem with Virtual Full
Hello Carlo, Which version of Bacula are you running? Could you post your configurations for using VirtualFull backups? Is there a log for the virtual full job? Best regards, Ana On Tue, Nov 3, 2015 at 10:59 AM, Carlo Filippetto < carlo.filippe...@gmail.com> wrote: > Hi all, > I want to use VirtualFull as default policy for my backup, but I have some > problem that I'm not able to solve: > > - I create a specific pool on a new device (disk), and run the Vfull >the backup goes well, I can find the new volume into his specific > device, but I can't see the Job into "list jobs" command? >I can see only it into "terminated jobs" > > > | 326 | BackupCatalog | 2015-11-03 04:35:03 | B| F | >0 | 0 | T | > | 329 | job-test1 | 2015-11-03 12:46:01 | B| I | >2 | 32,357 | T | > > > Terminated Jobs: > 327 Full 0 0 Cancel 03-nov-15 12:28 job-test1 > 328 Full 81.185 M OK 03-nov-15 12:28 job-test1 > > > > After this test I run a new incremental, and now I would like to rerun a > new VFull based on this Incremental and on the last VFull... but bacula > fails with: >Could not > open(/data/bacula/data/v-virtual-0003,OPEN_READ_ONLY,0640): ERR=No such > file or directory > Why Bacula search the volume v-virtual-0003 into the default directory > and not into /data/bacula/*virtual*/ where he correctly create this > volume last time? > > How I have to do to run a new VFull based on the last VFull? > > Thank you > > > > > > > > > -- > > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > > -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Question about Volume Pools and Strategy
On 11/3/2015 6:38 PM, Wesley Render wrote: > Should each storage daemon/geographic storage location have it's own > set of Volume Pools? Or can I share one set of Volume Pools between > all of the storage daemons/storage locations? You may also use Media Type to tie volumes to particular devices. For example, if disk storage is being used at both locations, then setting the Media Type for the Device at location 1 to "File-1" and the Media Type for the Device at location 2 to "File-2", then volumes written at both sites can belong to the same pool. When Bacula selects a volume from a pool, it will not select a volume that does not have the same Media Type as the Storage resource being used by the job. > I am using auto labelling as well and it works great. > > > -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Question about Volume Pools and Strategy
It seems to be working a lot better with different volume pools at
each storage location. I have one server backing up to the server at
our office, and 2 servers backing up to the datacenter. Here is what I
have so far:
Pool {
Name = office-p-monthly
Pool Type = Backup
Volume Retention = 6 months
Recycle = yes
AutoPrune = yes
LabelFormat = office-p-monthly-
Maximum Volume Jobs = 1
Maximum Volumes = 9
}
Pool {
Name = office-p-weekly
Pool Type = Backup
Maximum Volume Jobs = 1
Volume Retention = 1 months
Recycle = yes
AutoPrune = yes
LabelFormat = office-p-weekly-
Maximum Volumes = 7
}
Pool {
Name = office-p-daily
Pool Type = Backup
Maximum Volume Jobs = 6
Volume Retention = 14 days
Recycle = yes
AutoPrune = yes
LabelFormat = office-p-daily-
Maximum Volumes = 6
}
Pool {
Name = datacenter-p-monthly
Pool Type = Backup
Volume Retention = 6 months
Recycle = yes
AutoPrune = yes
LabelFormat = datacenter-p-monthly-
Maximum Volume Jobs = 2
Maximum Volumes = 9
}
Pool {
Name = datacenter-p-weekly
Pool Type = Backup
Maximum Volume Jobs = 2
Volume Retention = 1 months
Recycle = yes
AutoPrune = yes
LabelFormat = datacenter-p-weekly-
Maximum Volumes = 7
}
Pool {
Name = datacenter-p-daily
Pool Type = Backup
Maximum Volume Jobs = 2
Volume Retention = 14 days
Recycle = yes
AutoPrune = yes
LabelFormat = datacenter-p-daily-
Maximum Volumes = 6
}
Quoting Carlo Filippetto :
> I think you have to use one set of pool for every storage.
> I think that you can write volumes of the same pool into different storage,
> the problem may arrive when you have to restore...
>
> Try to a restore job...
>
>
> This is my Schedule:
> Schedule {
>Name = "Custom"
>Run = Level=Full Storage=ST-data Pool=P-Monthly 1st sat at 21:30
>Run = Level=Differential Storage=ST-data Pool=P-Weekly 2nd-5th sat
> at 21:30
>Run = Level=Incremental Storage=ST-data Pool=P-Daily sun-fri at
> 22:00
> }
>
> As you can see I set the Storage and Pool into every line, you can change
> it.
>
> Why do you like to use a single pool?
> If you have 2 storage may be more clear and easy to find every single
> volumes if you have different pools..
>
> Bye
>
>
>
>
>
>
> 2015-11-04 0:38 GMT+01:00 Wesley Render :
>
>> Should each storage daemon/geographic storage location have it's own
>> set of Volume Pools? Or can I share one set of Volume Pools between
>> all of the storage daemons/storage locations?
>>
>> I am using auto labelling as well and it works great.
>>
>>
>>
>> --
>> Wesley Render, Consultant
>> OtherData
>>
>>
>> --
>> ___
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
--
Wesley Render, Consultant
OtherData
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Question about Volume Pools and Strategy
Ok. Thanks Josh. I've already created Pools for each storage location and done the initial full backups so I will most likely stick with this method. So far the backups appear to run a lot better using different pools for each storage location. Thanks, -- Wesley Render, Consultant OtherData -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Question about Volume Pools and Strategy
I think you have to use one set of pool for every storage.
I think that you can write volumes of the same pool into different storage,
the problem may arrive when you have to restore...
Try to a restore job...
This is my Schedule:
Schedule {
Name = "Custom"
Run = Level=Full Storage=ST-data Pool=P-Monthly 1st sat at 21:30
Run = Level=Differential Storage=ST-data Pool=P-Weekly 2nd-5th sat
at 21:30
Run = Level=Incremental Storage=ST-data Pool=P-Daily sun-fri at
22:00
}
As you can see I set the Storage and Pool into every line, you can change
it.
Why do you like to use a single pool?
If you have 2 storage may be more clear and easy to find every single
volumes if you have different pools..
Bye
2015-11-04 0:38 GMT+01:00 Wesley Render :
> Should each storage daemon/geographic storage location have it's own
> set of Volume Pools? Or can I share one set of Volume Pools between
> all of the storage daemons/storage locations?
>
> I am using auto labelling as well and it works great.
>
>
>
> --
> Wesley Render, Consultant
> OtherData
>
>
> --
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
