Re: [Bacula-users] Q: Your advice for my re-design of backup layout regarding pools and volumes (backups of and in homelab)
On 10/24/23 15:37, Justin Case wrote:
can you paste how you select the fulls for copy jobs?
This is my methodology:
Job {
Name = "Archive Copy"
Type = Copy
Enabled = Yes
Pool = Full-Disk
Level = Full
Client = ALL
Fileset = DUMMY
Storage = epsilon3-archive
Selection Type = SQL Query
Selection Pattern = "SELECT DISTINCT J.JobId
FROM Job J
JOIN Pool P ON P.PoolId = J.PoolId
LEFT JOIN Job J2 ON J2.PriorJobId = J.JobId
WHERE P.Name = 'Full-Disk'
AND J2.JobId IS NULL
AND J.Type = 'B'
AND J.JobStatus IN ('T','W')
AND J.JobBytes > 0
AND J.StartTime > now() - interval 7 day"
Messages = Daemon
Priority = 20
Rerun Failed Levels = yes
Allow Duplicate Jobs = no
Cancel Queued Duplicates = yes
Schedule = "Full Backup Archive"
}
--
Phil Stracchino
Babylon Communications
ph...@caerllewys.net
p...@co.ordinate.org
Landline: +1.603.293.8485
Mobile: +1.603.998.6958
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: Your advice for my re-design of backup layout regarding pools and volumes (backups of and in homelab)
can you paste how you select the fulls for copy jobs? > On 24. Oct 2023, at 20:53, Phil Stracchino wrote: > > On 10/24/23 14:42, Justin Case wrote: >> I realized that my fulls and incrementals have the same retention time, so I >> made 1 pool for both. >> I guess you are using X > Y months for fulls and Y > Z months >> fordifferentials and Z months for incrementals? > > That's the basic idea, yes. I do a nightly incremental kept for 3 weeks, > weekly differentials kept for 3 months, and monthly Fulls which if memory > serves I keep for one year. > > > > -- > Phil Stracchino > Babylon Communications > ph...@caerllewys.net > p...@co.ordinate.org > Landline: +1.603.293.8485 > Mobile: +1.603.998.6958 > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: Your advice for my re-design of backup layout regarding pools and volumes (backups of and in homelab)
On 10/24/23 14:42, Justin Case wrote: I realized that my fulls and incrementals have the same retention time, so I made 1 pool for both. I guess you are using X > Y months for fulls and Y > Z months fordifferentials and Z months for incrementals? That's the basic idea, yes. I do a nightly incremental kept for 3 weeks, weekly differentials kept for 3 months, and monthly Fulls which if memory serves I keep for one year. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: Your advice for my re-design of backup layout regarding pools and volumes (backups of and in homelab)
> On 24. Oct 2023, at 17:15, Phil Stracchino wrote: > > On 10/24/23 10:59, Justin Case wrote: > > Disclaimer: My situation is a little different from yours, I'm doing > disk-to-disk-to-removable-disk. > > >> For tier 1: does it make sense to have different volumes for full jobs and >> incr jobs? Does it make sense to have these volumes in seperate pools, or >> full and incr together in a pool? Would you recommend having different pools >> for different groups of jobs? > > I keep Full, Differential and Incremental jobs in separate Pools. That way I > can purge job batches as they become obsolete on their own schedules and > recover the space. I realized that my fulls and incrementals have the same retention time, so I made 1 pool for both. I guess you are using X > Y months for fulls and Y > Z months fordifferentials and Z months for incrementals? >> For tier 2: here I wil use copy jobs. Since copy jobs really do not >> differentiate full and incr backups, there will be full and incr copies >> together in volumes. Would you recommend having different pools for >> different groups of copy jobs? > > I use copy jobs, but I copy only FULL backups to removable disk. (The > removable disk zpools are then exported, unmounted, and stored > offline/airgapped.) > on second thought that could make more sense, as it allows for a longer retention. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Q: Your advice for my re-design of backup layout regarding pools and volumes (backups of and in homelab)
On 10/24/23 10:59, Justin Case wrote: Disclaimer: My situation is a little different from yours, I'm doing disk-to-disk-to-removable-disk. For tier 1: does it make sense to have different volumes for full jobs and incr jobs? Does it make sense to have these volumes in seperate pools, or full and incr together in a pool? Would you recommend having different pools for different groups of jobs? I keep Full, Differential and Incremental jobs in separate Pools. That way I can purge job batches as they become obsolete on their own schedules and recover the space. For tier 2: here I wil use copy jobs. Since copy jobs really do not differentiate full and incr backups, there will be full and incr copies together in volumes. Would you recommend having different pools for different groups of copy jobs? I use copy jobs, but I copy only FULL backups to removable disk. (The removable disk zpools are then exported, unmounted, and stored offline/airgapped.) -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Q: Your advice for my re-design of backup layout regarding pools and volumes (backups of and in homelab)
Hi there, I am currently rethinking the setup of my backups for my home lab (has a lot of VMs and a few physical machines). I want to have 2 backup tiers: tier 1 on a virtual FS across several HDDs and tier 2 using vchanger on external HDDs. As I am mainly backing up VMs on 1 hypervisor and all goes to same same SD, parallel jobs do not really boost the overall performance significantly. For tier 1: does it make sense to have different volumes for full jobs and incr jobs? Does it make sense to have these volumes in seperate pools, or full and incr together in a pool? Would you recommend having different pools for different groups of jobs? For tier 2: here I wil use copy jobs. Since copy jobs really do not differentiate full and incr backups, there will be full and incr copies together in volumes. Would you recommend having different pools for different groups of copy jobs? Again, physically spreading workload is not really possible in my lab, so I mainly use sequential jobs. My main concern is a good tradeoff of "order" regarding which jobs are together in volumes and not wasting too much on space overhead by using different pools for different jobs. You input is appreciated. JC___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] FD windows server 2019 - VSS
Hello , Do some of you have some error during initialization of the VSS Create snapshot on Windows server 2019, Mine often have an error and dont know why its sometimes ok sometimes non ok I look at the vssagent on the server and even none are in default or in running state the failure become. SERV-fd JobId 10248: Error: VSS API failure calling "BackupComplete". ERR=Object is not initialized; called during restore or not called in correct sequence. SERV-fd JobId 10248: Fatal error: vss.cpp:509 Backup is not Initialized SERV-fd JobId 10248: Fatal error: vss.cpp:509 Backup is not Initialized SERV-fd JobId 10248: Fatal error: vss.cpp:451 Backup is not Initialized SERV-fd JobId 10248: Fatal error: VSS CreateSnapshots failed. ERR=Lopération a réussi. SERV-fd JobId 10248: Generate VSS snapshots. Driver="Win64 VSS" I have no windows backup running .. Im still in 9.6.6 (dir and fd) smime.p7s Description: S/MIME cryptographic signature ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
