Hi Guillermo,
I'm still not quite sure if I get the full piture here... for example,
the process you have implemented may easily restore files with identical
paths, essentially overwriting older data with newer files. If that is a
problem depends on the data you backed up and particular requirements
which we are not aware of.
However --
Am 09.09.2024 um 17:31 schrieb Guillermo Martin Cabanillas:
Hi Arno,
At the end we found an easy solution to restore all Full backups from
one machine(client) from 2022 till today. We have to repeat this task
with every machine(client).
with a SQL select we get the full backups jobs ids:
select JobId from Job where JobStatus='T' and Type='B' and
Level='F' and Name='XXXX';
Then format the column results to commas
Then restore using this option:
3: Enter list of comma separated JobIds to select
If anyone knows a better option to do this task please let us know, thanks!
If that works and solves the problem, it surely is a valid solution. A
variant I would probably use would be to to use restore job prepartion
as intended for more complex user interfaces, setting up a catalog table
containing the information what to restore. You could do that using the
.bvfs commands or a customized SQL query. None of that will be easier to
understand than a piece of shell script including awk, sed, perl or
whatever toolchain you like, but it may be useful if you expect such
exercises to become routine.
In a more automated solution, I would probably restore each job or
sequence of jobs in their own directory tree, so that newer file
versions do not overwrite older ones.
All of this, however, are just suggestions which may or may not be
useful -- your solution, if it does what you need, is obviously good,
and "better" depends a lot on factors we're not aware of.
Cheers,
Arno
--
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users