Hi,
I am currently trying to create a report on how my backup set changed
over the years, especially in size and time.
With "backup set" I mean the following. We are doing daily incremental
on all systems and weekly (starting from friday evening) full backups of
all local systems and virtual full of all remote systems. Then, the
latter are copied to tape.
This is how it looks like (shortened):
1 Tue 05-Nov-2019 23:00 WeeklyRemoteCycle Level=Incremental
2 Tue 05-Nov-2019 23:05 WeeklyCycleAfterBackup Level=Full
3 Tue 05-Nov-2019 23:00 WeeklyCycle Level=Incremental
4 Wed 06-Nov-2019 23:00 WeeklyRemoteCycle Level=Incremental
5 Wed 06-Nov-2019 23:05 WeeklyCycleAfterBackup Level=Full
6 Wed 06-Nov-2019 23:00 WeeklyCycle Level=Incremental
7 Thu 07-Nov-2019 23:00 WeeklyRemoteCycle Level=Incremental
8 Thu 07-Nov-2019 23:05 WeeklyCycleAfterBackup Level=Full
9 Thu 07-Nov-2019 23:00 WeeklyCycle Level=Incremental
10 Fri 08-Nov-2019 23:04 WeeklyRemotePrepareCyc
11 Fri 08-Nov-2019 23:05 WeeklyRemoteCycle Level=VirtualFull
12 Fri 08-Nov-2019 23:00 WeeklyRemoteCycle Level=Incremental
13 Fri 08-Nov-2019 23:05 WeeklyCycleAfterBackup Level=Full
14 Fri 08-Nov-2019 23:00 WeeklyCycle Level=Full
15 Sat 09-Nov-2019 23:11 NotifyBackupCompleted
16 Sat 09-Nov-2019 23:15 CopyToTapeCompleted Pool=Tape [...]
17 Sat 09-Nov-2019 23:10 CopyToTape
18 Mon 11-Nov-2019 23:00 WeeklyRemoteCycle Level=Incremental
19 Mon 11-Nov-2019 23:05 WeeklyCycleAfterBackup Level=Full
The backup sets - in my definition - would be all jobs which are started
by the schedules in the following lines
* Line 1- 3
* Line 4- 6
* Line 7- 9
* Line 10-17
* Line 18-...
(5 backup sets)
When everything runs smoothly and nothing changes over the years, I am
able to create a query which separates the schedtime column at every
Friday 22:55 to group the jobs table, but I find this overly complicated
and brittle, especially when looking a long time back in the job history.
My rough idea would be a new resource
Backup Set {
Name = "Weekly"
Start = Fri at 22:55
End = Mon at 10:00 # defaults to Start -1s
# maybe this directive is too much...
}
and a job directive Backup Set (overrideable by schedule).
When a job with this directive set to "Weekly" is scheduled, the
schedtime is floored to the previous backup set Start and a name is
generated for the backup set. For example (Backup Set Start = Fri at 22:55):
Job Schedtime Name
Mon, 4.11.2019 20:00 Weekly_2019-11-01_22.55.00_00
Sat, 2.11.2019 20:00 Weekly_2019-11-01_22.55.00_00
Fri, 1.11.2019 20:00 Weekly_2019-10-25_22.55.00_00
This generated name is then stored in the job dataset an can be used for
sql group clauses, etc. The generated name should also be available as a
variable to be used in admin jobs.
Is there already a something like this or is somebody have a nice
solution for this?
Are there other people out there with have this problem?
If yes, could/should this or something like this a future feature?
Thanks for reading,
Christian
--
ifu Hamburg - Member of iPoint Group
"Productivity meets Sustainability"
ifu Institut für Umweltinformatik Hamburg GmbH
Max-Brauer-Allee 50 - 22765 Hamburg - Germany
fon: +49 40 480009-0 - fax: +49 40 480009-22 - email: i...@ifu.com
Managing Director: Jan Hedemann - Commercial Register: Hamburg, HRB 52629
www.ifu.com - www.umberto.de - www.e-sankey.com
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/5abf877a-c31d-780c-4c45-46d0d8469cc0%40ifu.com.
