EBS snapshot backups from a FreeBSD zfs file system: zpool freeze?

Berend de Boer berend at pobox.com
Wed Jul 3 09:15:55 UTC 2013


>>>>> "Markus" == Markus Gebert <markus.gebert at hostpoint.ch> writes:

    Markus> 1. snapshot the zfs at the same point in time you'd issue
    Markus> that ioctl on Linux
    Markus> 2. take the EBS snapshot at any time
    Markus> 3. clone the EBS snapshot to the new/other VM
    Markus> 4. zfs import the pool there
    Markus> 5. zfs rollback the filesystem to
    Markus> the snapshot taken in step 1 (or clone it and use that)

That seems like a very good first step!

It's unfortunately not automatic, but for recovery purposes it should
do.

Do you think (yes, I will definitely test this), that ZFS can mount a
file system consisting of a couple of disk (raidz2 setup), and access
it even though every disk might be a backup taken at a slighty
different time?

Obviously I'm going to throw away the mounted state and rollback to my
snapshot, but it has to be able to mount a set of disks which might be
in a terrible state first.


    Markus> Also, taking the zfs snapshot should take much less time,
    Markus> because you don't have to wait for the EBS snapshot to
    Markus> complete before you can resume IO on the filesystem. So
    Markus> you don't even depend on EBS snapshots being quick when
    Markus> using the zfs approach, a big advantage in my opinion.

You don't have to wait for an EBS snapshot to complete. That can take
hours. EBS simply takes the moment in time you give the command, and
starts the backup from there. Normal I/O to the disk continues (so
uses some kind of COW system I suppose)

--
All the best,

Berend de Boer


          ------------------------------------------------------
          Awesome Drupal hosting: https://www.xplainhosting.com/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP Digital Signature
URL: <http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20130703/4a0c8273/attachment.sig>


More information about the freebsd-fs mailing list