Josip DeanovicOn Tuesday 2017-11-21 14:18:56  wrote:
> On Tuesday 2017-11-21 10:36:59 Heitor Faria wrote:
> > Hello, Bacula Users,
> > 
> > Until now I think the most elegant way of doing this was not
> > mentioned.
> > 
> >  1. ClientRunBeforeJob virsh disk snapshot creation.
> >  2. Bacula FileSet regular image files backup.
> >  3. ClientRunAfterJob blockcommit to resume machine state.
> > 
> > Source: https://gist.github.com/cabal95/e36c06e716d3328b512b
> 
> I'll add one more link that better explains how it works:
> https://fedoraproject.org/wiki/Features/Virt_Live_Snapshots
> 
> Pros:
> This is nice because the snapshot can be done on the live
> machine and the writes will be sent to the external file.
> Once the backup of the original VM image file is performed
> the snapshot can be (and should be) merged back into the
> original VM image file.
> 
> Cons:
> Don't know if this feature is stable enough and I wouldn't
> put it into production without heavy testing.
> I am particularly concerned about the merging the snapshot
> back to the original image's blocks. If it fails in the process
> of merging blocks that could result in data loss or at least
> in the longer downtime while the backed up image is restored.

Another thing that should be taken into consideration.
https://fedoraproject.org/wiki/Talk:Features/Virt_Live_Snapshots


-- 
Josip Deanovic

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to