Backup a ZFS dataset with bareos.

[kune...@gmail.com]

A question how best to save a ZFS snapshot about bareos?
The bareos client should create the snapshot for this and then save everything and resolve the snapshot again after the data backup.

[diamaunt]

On Tuesday, April 10, 2018 at 6:16:42 AM UTC-5, kune...@gmail.com wrote:
> A question how best to save a ZFS snapshot about bareos?
> The bareos client should create the snapshot for this and then save everything and resolve the snapshot again after the data backup.

What I'm doing is to have a RunBeforeJob to create the snapshot, then I'm backing up the snapshot itself (out of the .zfs/snapshot directory) then a RunAfterJob to delete the snapshot.

I'm doing that with some database file systems.

[Oliver Weinmann]

I create the snapshots on the storage system (daily,weekly,monthly,yearly etc.) anyway, so I don't need to create them via bareos. Then I have a small bash script that creates a bareos fileset config file where I can specifiy what snapshots to backup. Works like a charm. :)



Oliver Weinmann
Head of Corporate ICT
Telespazio VEGA Deutschland GmbH
Europaplatz 5 - 64293 Darmstadt - Germany
Ph: +49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799
oliver....@telespazio-vega.de
www.telespazio-vega.de
Registered office/Sitz: Darmstadt, Register court/Registergericht: Darmstadt, HRB 89231; Managing Director/Geschäftsführer: Sigmar Keller-----Original Message-----
From: bareos...@googlegroups.com [mailto:bareos...@googlegroups.com] On Behalf Of diamaunt
Sent: Dienstag, 10. April 2018 20:31
To: bareos-users <bareos...@googlegroups.com>
Subject: [bareos-users] Re: Backup a ZFS dataset with bareos.

--
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...@googlegroups.com.
To post to this group, send email to bareos...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[michael masterson]

I thought about doing that, since I'm also doing the standard every 15
minute snapshots that are aged off to hourly, daily, weekly, monthly,...
but doing a special snap, for the backup, whenever it happened, was
easier for me, than parsing out whatever the latest existing snap was
whenever the backup happened.

Of course, one of the great things are the multiple ways of doing things
in unix.

[kune...@gmail.com]

ok. will try RunBeforeJob & RunAfterJob.
What does your fileset look like, if I may ask?

[michael masterson]

FileSet {
  Name = "woden-db"
  Description = "Backup all regular filesystems, determined by
filesystem type."
  Include {
    Options {
      Signature = MD5 # calculate md5 checksum per file
      OneFS = No     # change into other filessytems
      Compression = LZ4
      noatime = yes
    }
    File = /opt/postgres/data/.zfs/snapshot/backup
    File = /var/mysql/.zfs/snapshot/backup
  }
#  Exclude {
#  }
}

I set that up when first starting to learn how to do this, so if there's
stupidity in it, someone feel free to point it out ;)


I have tested restores from it, and brought up both the mysql and
postgres without any problems.