Re: [Bacula-users] Dual-pool backups

[Simon Gornall via Bacula-users]

Hi Heitor,

Definitely the same drive :) 
https://www.backupworks.com/Quantum-superloader-3-LTO-8-16-Slot.aspx 
 - you 
can see the left and right magazines with the single drive slot in the center. 
Here’s a link to the magazine on the right side 
https://www.amazon.com/Quantum-Superloader-Eight-cartridge-Magazine-Include/dp/B000HWVLX6
 


Really, the only reason for splitting the backups like this is so I can easily 
take the entire magazine off-site once every 2 weeks or so. It’s far faster to 
unload the magazine than it is to unload each tape individually.

If I can pretend that each magazine is a drive, perhaps the built-in one would 
work ?

Cheers
Simon


> On Jan 4, 2021, at 1:04 PM, Heitor Faria  wrote:
> 
> Hello Simon,
> 
> I never heard of performing backups to alternate TL magazines and any benefit 
> of that. Are you sure you are not talking about different tape drives? 
> Anyway. The Bacula Enterprise Edition earlier versions already perform 
> automatic tape drives round robin usage.
> I believe CBacula V. 11 *might* have this featured ported. You gotta check 
> the code change log.
> 
> Regards,
> --
> MSc Heitor Faria
> CEO Bacula LatAm
> mobile1: + 1 909 655-8971
> mobile2: + 55 61 98268-4220
> 
> América Latina
> [ http://bacula.lat/]
> 
> 
> 
>  Original Message 
> From: Simon Gornall via Bacula-users 
> Sent: Monday, January 4, 2021 03:49 PM
> To: bacula-users@lists.sourceforge.net
> Subject: [Bacula-users] Dual-pool backups
> 
> So I’ve just ordered myself a Quantum Superloader-3 LTO-8 tape drive, and I’m 
> planning on using it to back up the home network. Looking around, bacula 
> seemed to fit to a ’T’, but I thought I’d ask if what I’m planning actually 
> *does* fit well :)
> 
> The SL3 has 2 magazines, of 8 tapes each. I think a full backup + 
> incrementals every day will fit onto a single magazine (each is 96TB, 
> uncompressed). The main source is the 112TB NAS, which is where the Macs (5 
> of them) do their Time-Machine backups to, it holds all the movies and photos 
> for the family etc. etc. We’re only using about 50TB of the NAS at the moment.
> 
> The plan then, is to create two pools, each of 8 volumes, and to rotate 
> backups between magazines, so it’ll do:
> 
> Week 1: use Pool 1
> 
> Sun: Full backup
> Mon..Sat: Incr backup // Maybe split this with a differential backup on Wed.
> 
> Week 2: use Pool 2
> 
> Sun: Full backup
> Mon..Sat: Incr backup // Maybe split this with a differential backup on Wed.
> 
> + swap tapes in Pool 1 with offsite ones
> 
> … and repeat, giving me a ,  and  pool> in a way that makes it easy to just pull a magazine at a time from the 
> machine and replace it with another. Making backup-related jobs easy to do is 
> the best way I’ve found of them actually happening …
> 
> 
> Looking at the docs, I think I can create a schedule with alternating weeks. 
> I was wondering if there was a better way to do it than:
> 
> Schedule {
> Name = “Monthly”
> Run = Level=Full Pool=LeftMagazine 1st|3rd|5th sun at 21:01
> Run = Level=Incremental Pool=LeftMagazine 1st mon-sat at 21:01
> 
> Run = Level=Full Pool=RightMagazine 2nd|4th sun at 21:01
> Run = Level=Incremental Pool=RightMagazine 2nd mon-sat at 21:01
> }
> 
> It also occurs to me that you could happen to get a backup on the 5th week 
> which used the left magazine, and then switch to the first week of the next 
> month, which would again use the left magazine. I think I could work around 
> that using week-of-year maybe, but then it starts getting to be quite a long 
> config line… 
> 
> Schedule {
> Name = “Monthly”
> Run = Level=Full Pool=LeftMagazine 
> w01|w03|w05|w07|w09|w11|w13|w15|w17|w19|w21|w23|w25|w27|w29|w31|w33|w35|w37|w39|w41|w43|w45|w47|w49|w51
>  sun at 21:01
> Run = Level=Incremental Pool=LeftMagazine 
> w01|w03|w05|w07|w09|w11|w13|w15|w17|w19|w21|w23|w25|w27|w29|w31|w33|w35|w37|w39|w41|w43|w45|w47|w49|w51
>   mon-sat at 21:01
> 
> Run = Level=Full Pool=RightMagazine 
> w02|w04|w07|w08|w10|w12|w14|w16|w18|w20|w22|w24|w26|w28|w30|w32|w34|w36|w38|w40|w42|w44|w46|w48|w50|w52
>  sun at 21:01
> Run = Level=Incremental Pool=RightMagazine 
> w02|w04|w07|w08|w10|w12|w14|w16|w18|w20|w22|w24|w26|w28|w30|w32|w34|w36|w38|w40|w42|w44|w46|w48|w50|w52
>  mon-sat at 21:01
> 
> }
> 
> … but that’s a bit clumsy. Is there any better way to specify alternating 
> weeks ?
> 
> 
> I haven’t actually got the machine yet, so I’m just thinking about how I want 
> to set it up. Any advice much appreciated :)
> 
> Cheers
> Simon
> 
> ___
> 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

Re: [Bacula-users] Dual-pool backups

[Heitor Faria]

Hello Simon,

I never heard of performing backups to alternate TL magazines and any benefit 
of that. Are you sure you are not talking about different tape drives? 
Anyway. The Bacula Enterprise Edition earlier versions already perform 
automatic tape drives round robin usage.
I believe CBacula V. 11 *might* have this featured ported. You gotta check the 
code change log.

Regards,
--
MSc Heitor Faria
CEO Bacula LatAm
mobile1: + 1 909 655-8971
mobile2: + 55 61 98268-4220

América Latina
[ http://bacula.lat/]

 Original Message 
From: Simon Gornall via Bacula-users 
Sent: Monday, January 4, 2021 03:49 PM
To: bacula-users@lists.sourceforge.net
Subject: [Bacula-users] Dual-pool backups

>So I’ve just ordered myself a Quantum Superloader-3 LTO-8 tape drive, and I’m 
>planning on using it to back up the home network. Looking around, bacula 
>seemed to fit to a ’T’, but I thought I’d ask if what I’m planning actually 
>*does* fit well :)
>
>The SL3 has 2 magazines, of 8 tapes each. I think a full backup + incrementals 
>every day will fit onto a single magazine (each is 96TB, uncompressed). The 
>main source is the 112TB NAS, which is where the Macs (5 of them) do their 
>Time-Machine backups to, it holds all the movies and photos for the family 
>etc. etc. We’re only using about 50TB of the NAS at the moment.
>
>The plan then, is to create two pools, each of 8 volumes, and to rotate 
>backups between magazines, so it’ll do:
>
>Week 1: use Pool 1
>
>   Sun:Full backup
>   Mon..Sat:   Incr backup // Maybe split this with a 
> differential backup on Wed.
>
>Week 2: use Pool 2
>
>   Sun:Full backup
>   Mon..Sat:   Incr backup // Maybe split this with a 
> differential backup on Wed.
>
>   + swap tapes in Pool 1 with offsite ones
>
>… and repeat, giving me a ,  and pool> in a way that makes it easy to just pull a magazine at a time from the 
>machine and replace it with another. Making backup-related jobs easy to do is 
>the best way I’ve found of them actually happening …
>
>
>Looking at the docs, I think I can create a schedule with alternating weeks. I 
>was wondering if there was a better way to do it than:
>
>Schedule {
>   Name= “Monthly”
>   Run = Level=Full Pool=LeftMagazine 1st|3rd|5th sun at 21:01
>   Run = Level=Incremental Pool=LeftMagazine 1st mon-sat at 
> 21:01
>
>   Run = Level=Full Pool=RightMagazine 2nd|4th sun at 21:01
>   Run = Level=Incremental Pool=RightMagazine 2nd mon-sat at 
> 21:01
>}
>
>It also occurs to me that you could happen to get a backup on the 5th week 
>which used the left magazine, and then switch to the first week of the next 
>month, which would again use the left magazine. I think I could work around 
>that using week-of-year maybe, but then it starts getting to be quite a long 
>config line… 
>
>Schedule {
>   Name= “Monthly”
>   Run = Level=Full Pool=LeftMagazine 
> w01|w03|w05|w07|w09|w11|w13|w15|w17|w19|w21|w23|w25|w27|w29|w31|w33|w35|w37|w39|w41|w43|w45|w47|w49|w51
>  sun at 21:01
>   Run = Level=Incremental Pool=LeftMagazine 
> w01|w03|w05|w07|w09|w11|w13|w15|w17|w19|w21|w23|w25|w27|w29|w31|w33|w35|w37|w39|w41|w43|w45|w47|w49|w51
>   mon-sat at 21:01
>
>   Run = Level=Full Pool=RightMagazine 
> w02|w04|w07|w08|w10|w12|w14|w16|w18|w20|w22|w24|w26|w28|w30|w32|w34|w36|w38|w40|w42|w44|w46|w48|w50|w52
>  sun at 21:01
>   Run = Level=Incremental Pool=RightMagazine 
> w02|w04|w07|w08|w10|w12|w14|w16|w18|w20|w22|w24|w26|w28|w30|w32|w34|w36|w38|w40|w42|w44|w46|w48|w50|w52
>  mon-sat at 21:01
>
>}
>
>… but that’s a bit clumsy. Is there any better way to specify alternating 
>weeks ?
>
>
>I haven’t actually got the machine yet, so I’m just thinking about how I want 
>to set it up. Any advice much appreciated :)
>
>Cheers
>   Simon
>
>___
>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

[Bacula-users] Dual-pool backups

[Simon Gornall via Bacula-users]

So I’ve just ordered myself a Quantum Superloader-3 LTO-8 tape drive, and I’m 
planning on using it to back up the home network. Looking around, bacula seemed 
to fit to a ’T’, but I thought I’d ask if what I’m planning actually *does* fit 
well :)

The SL3 has 2 magazines, of 8 tapes each. I think a full backup + incrementals 
every day will fit onto a single magazine (each is 96TB, uncompressed). The 
main source is the 112TB NAS, which is where the Macs (5 of them) do their 
Time-Machine backups to, it holds all the movies and photos for the family etc. 
etc. We’re only using about 50TB of the NAS at the moment.

The plan then, is to create two pools, each of 8 volumes, and to rotate backups 
between magazines, so it’ll do:

Week 1: use Pool 1

Sun:Full backup
Mon..Sat:   Incr backup // Maybe split this with a 
differential backup on Wed.

Week 2: use Pool 2

Sun:Full backup
Mon..Sat:   Incr backup // Maybe split this with a 
differential backup on Wed.

+ swap tapes in Pool 1 with offsite ones

… and repeat, giving me a ,  and  in a way that makes it easy to just pull a magazine at a time from the 
machine and replace it with another. Making backup-related jobs easy to do is 
the best way I’ve found of them actually happening …


Looking at the docs, I think I can create a schedule with alternating weeks. I 
was wondering if there was a better way to do it than:

Schedule {
Name= “Monthly”
Run = Level=Full Pool=LeftMagazine 1st|3rd|5th sun at 21:01
Run = Level=Incremental Pool=LeftMagazine 1st mon-sat at 
21:01

Run = Level=Full Pool=RightMagazine 2nd|4th sun at 21:01
Run = Level=Incremental Pool=RightMagazine 2nd mon-sat at 
21:01
}

It also occurs to me that you could happen to get a backup on the 5th week 
which used the left magazine, and then switch to the first week of the next 
month, which would again use the left magazine. I think I could work around 
that using week-of-year maybe, but then it starts getting to be quite a long 
config line… 

Schedule {
Name= “Monthly”
Run = Level=Full Pool=LeftMagazine 
w01|w03|w05|w07|w09|w11|w13|w15|w17|w19|w21|w23|w25|w27|w29|w31|w33|w35|w37|w39|w41|w43|w45|w47|w49|w51
 sun at 21:01
Run = Level=Incremental Pool=LeftMagazine 
w01|w03|w05|w07|w09|w11|w13|w15|w17|w19|w21|w23|w25|w27|w29|w31|w33|w35|w37|w39|w41|w43|w45|w47|w49|w51
  mon-sat at 21:01

Run = Level=Full Pool=RightMagazine 
w02|w04|w07|w08|w10|w12|w14|w16|w18|w20|w22|w24|w26|w28|w30|w32|w34|w36|w38|w40|w42|w44|w46|w48|w50|w52
 sun at 21:01
Run = Level=Incremental Pool=RightMagazine 
w02|w04|w07|w08|w10|w12|w14|w16|w18|w20|w22|w24|w26|w28|w30|w32|w34|w36|w38|w40|w42|w44|w46|w48|w50|w52
 mon-sat at 21:01

}

… but that’s a bit clumsy. Is there any better way to specify alternating weeks 
?


I haven’t actually got the machine yet, so I’m just thinking about how I want 
to set it up. Any advice much appreciated :)

Cheers
Simon

___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] bacula-sd - file driver - cloud resource

[Žiga Žvan]

Sorry, this message was to large to get to the list. Just a suggestion 
to update documentation regarding purge/truncate commands...

Regards, Ziga


On 30.12.2020 21:32, Žiga Žvan wrote:


Hello Heitor,

I have admin job (output bellow). I have followed instructions in 
bacula 9.6.x manual (page 228 of 
https://www.bacula.org/9.6.x-manuals/en/main/main.pdf).

After some testing I discovered that:
a)command "prune expired volume yes" changes the status of volume to 
purged and allows volume to be used again (data on disk does not change)
b)command "purge volume action=all allpools 
storage=FSOciCloudStandardChanger" does not do anything.


I have changed this command to "truncate AllPools 
storage=FSOciCloudStandardChanger" as indicated on link you provided. 
Now data on disk actually gets truncated.


Thank you for all your help.
Perhaps someone could update documentation. I think it is quite 
misleading.


Regards,
Ziga

PS: Because of my changes to SD conf, I got error on truncate command 
(is a directory...). I have reinitialized catalog database to solve this.



Job {
  Name = "BackupCatalog"
  JobDefs = "CatalogJob"
  Level = Full
  FileSet="Catalog"
  Schedule = "WeeklyCycleAfterBackup"
  # This creates an ASCII copy of the catalog
  # Arguments to make_catalog_backup.pl are:
  #  make_catalog_backup.pl 
  RunBeforeJob = "/opt/bacula/scripts/make_catalog_backup.pl MyCatalog"
  # This deletes the copy of the catalog
  RunAfterJob  = "/opt/bacula/scripts/delete_catalog_backup"
  #Prune
  RunScript {
    Console = "prune expired volume yes"
    RunsWhen = Before
    RunsOnClient= No
  }
  #Purge
  RunScript {
    RunsWhen=After
    RunsOnClient=No
    Console = "purge volume action=all allpools 
storage=FSOciCloudStandardChanger"

  }
  Write Bootstrap = "/opt/bacula/working/%n.bsr"
  Priority = 11   # run after main backup
}

*truncate pool=jhost05-weekly-pool storage=FSOciCloudStandardChanger
Using Catalog "MyCatalog"
Connecting to Storage daemon FSOciCloudStandardChanger at 
192.168.66.35:9103 ...
3929 Unable to open device ""FSOciCloudStandard1" 
(/mnt/ocisg/bacula/backup)": ERR=file_dev.c:190 Could not 
open(/mnt/ocisg/bacula/backup/jhost05-weekly-vol- 
0475,CREATE_READ_WRITE,0640): ERR=Is a directory




On 30.12.2020 14:01, Heitor Faria wrote:


Hello Ziga,

If you are using AutoPrune=No, you must automate some sort of routine 
to prune expired volumes, otherwise it will affect Bacula's 
capability of recycling volumes.
You can achieve that (e.g.) using an Admin Job and the prune expired 
command, such as in: 
https://www.bacula.lat/truncate-bacula-volumes-to-free-disk-space/?lang=en


Regards,
--
MSc Heitor Faria
CEO Bacula LatAm
mobile1: + 1 909 655-8971
mobile2: + 55 61 98268-4220

América Latina
[ http://bacula.lat/]

...



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users