<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hello Thorsten,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><span class="VIiyi" lang="en"><span
class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="0"><span>thank
you for taking the time to answer me ! 😁</span></span></span></div>
<div class="moz-cite-prefix"><span class="VIiyi" lang="en"><span
class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="0"><span><br>
</span></span></span></div>
<div class="moz-cite-prefix"><span class="VIiyi" lang="en"><span
class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="0"><span>I
want to clarify my request. we are typically in a case of
libvirt/kvm virtualization. <br>
</span></span></span></div>
<div class="moz-cite-prefix"><span class="VIiyi" lang="en"><span
class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="0"><span><br>
</span></span></span></div>
<div class="moz-cite-prefix"><span class="VIiyi" lang="en"><span
class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="0"><span></span></span></span>for
the moment, i was using borgbackup in order to save VM-images and
snaphots from a local backups folder to a repository on a remote
server... it works perfectly.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><span class="VIiyi" lang="en"><span
class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="0"><span>actually,
VM-images are managed by <a moz-do-not-send="true"
href="https://github.com/dguerri/LibVirtKvm-scripts/blob/master/fi-backup.sh">fi-backup</a>,
a bash script which produces one snaphot per hour of each
VM, and which consolidates them at the end of the day into a
single qcow2 file ... then starts again the next day. <br>
</span></span></span></div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><span class="VIiyi" lang="en"><span
class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="0"><span>after
each snaphot creation, fi-backup copies the file to the
backups folder.</span></span><span class="JLqJ4b ChMk0b"
data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="1"><span>
when it consolidates all the snapshots (small files), it
also copies the new image (big file) to the backups folder.</span></span><span
class="JLqJ4b" data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="2"><span>
</span></span><span class="JLqJ4b ChMk0b"
data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="3"><span>it
uses the command "cp -u", which is expensive in time... <br>
</span></span></span></div>
<div class="moz-cite-prefix"><span class="VIiyi" lang="en"><span
class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="3"><span><br>
</span></span></span></div>
<div class="moz-cite-prefix"><span class="VIiyi" lang="en"><span
class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="3"><span>my
question is: would it be possible to replace the "cp -u" by
"borg create" (from /var/lib/libvirt/images to </span></span></span><span
class="VIiyi" lang="en"><span class="JLqJ4b ChMk0b"
data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="3"><span><span
class="VIiyi" lang="en"><span class="JLqJ4b ChMk0b"
data-language-for-alternatives="en"
data-language-to-translate-into="fr"
data-phrase-index="3"><span>/var/lib/libvirt/backups)</span></span></span>,
in order to benefit from the deduplication and to shorten
the copy times</span></span> <span class="JLqJ4b ChMk0b"
data-language-for-alternatives="en"
data-language-to-translate-into="fr" data-phrase-index="4"><span>?</span></span></span>
<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">the creation of dummy files would then
also be managed by fi-backup.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">What do you think ?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Thanks in advance,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Ernest.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Le 02/09/2021 à 15:48, Thorsten
Schöning a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:14910591148.20210902154848@am-soft.de">
<pre class="moz-quote-pre" wrap="">Guten Tag Ernest Chiarello,
am Donnerstag, 2. September 2021 um 15:08 schrieben Sie:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">but I don't see how to avoid this type of problem when saving large
files from time to time (qcow2 images)... 😕
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Things depend on if you ONLY store the large failes additionally and
never more current smaller ones as well. For most backup purposes this
is not the case, as some smaller files will most likely be available,
not only large images. If it's different in your case, you simply need
to make sure by creating some small dummy file to "trick" BorgBackup.
I did exactly that e.g. for VMs which I archive and don't change
anymore: VM-images are at timestamp X, dummy file is at timestamp X+1,
so no problem ever. If VM-images would change at some point again, one
would simply touch the dummy file again so that it's newer and things
work as before. My dummy fille even simply contains the content of the
linked FAQ, so that I always know why it's there. :-)
If you want to make things easier to use, I can suggest BorgMatic.
That allows you to have everythign in yome YAML-config and
additionally provides hooks being executed before the backup. Those
hooks can simply be used to touch your dummy file always.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">hooks:
# Custom preparation scripts to run.
before_backup:
- prepare-for-backup.sh
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
<a class="moz-txt-link-freetext" href="https://torsion.org/borgmatic/">https://torsion.org/borgmatic/</a>
Mit freundlichen Grüßen
Thorsten Schöning
</pre>
</blockquote>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Ernest CHIARELLO - <a class="moz-txt-link-abbreviated" href="mailto:Ernest.Chiarello@univ-fcomte.fr">Ernest.Chiarello@univ-fcomte.fr</a>
UMR6049 ThéMA - CNRS / Université de Franche-Comté
Service de gestion et production de l'information
32 rue Mégevand - F 25030 BESANCON Cedex
Tel : 03 81 66 53 66 Mob : 07 82 99 11 08
UAR3124 MSHE Ledoux - CNRS / UFC
Plateforme technologique SHERPA
1 rue Charles Nodier - F 25030 BESANCON Cedex
Tel : 03 81 66 53 66 Mob : 07 82 99 11 08
</pre>
</body>
</html>