It looks like the write error does indeed mean that the client file
being saved at the end of that tape is indeed not recoverable:
[...]
Run Restore job
JobName: RestoreFiles
Bootstrap: /var/lib/bareos/bareos-dir.restore.2.bsr
Where: /var/tmp
Replace: Always
FileSet
Can anybody confirm that this is a suitable query to identify the last
file written to a specific volume?
SELECT
client.name AS client,
path.path,
filename.name,
File.FileId,
JobMedia.EndFile
FROM File
JOIN Filename on File.FilenameId = Filename.FilenameId
JOIN Path on File.PathId = Path
Just my $0.02
I have saved copies of the tape key and all other keys and bareos config files
in an encrypted vault like Vault, 1Password, Cyberark, so I’ll have all me
keys replicated in another location but in an encrypted way.
I use as part of my catalog backup after script rclone the catalog
Many thanks for sanity-checking my thoughts.
On Thu, Jun 17, 2021 at 10:54 AM Philipp Storz wrote:
> In general, I think that disaster recovery and encryption are no good friends.
True as that may be, storing data unencrypted is not an option for me :-).
It certainly makes it harder though, but
Hello,
Am 16.06.21 um 19:40 schrieb 'Christian Svensson' via bareos-users:
> Hi Bareos list,
>
> I am trying to wrap my head around how I can create a good disaster
> recovery procedure.
> The documentation has some ideas, but specifically what I'd like to do
> is extract the BackupCatalog job's
