<?xml version="1.0" encoding="utf-8"?>
<!--
SPDX-License-Identifier: CC-BY-SA-4.0
SPDX-FileCopyrightText: Michael Terry
--><page xmlns="http://projectmallard.org/1.0/" xmlns:its="http://www.w3.org/2005/11/its" its:version="2.0" type="topic" style="task" id="restore-worst-case" lang="af">
<info>
  <desc>Wat om te doen as jy nie jou lêers kan nie restoureer</desc>
  <link type="guide" xref="index#restore"/>
  <credit type="author" its:translate="no">
    <name>Michael Terry</name>
  </credit>
  <license href="http://creativecommons.org/licenses/by-sa/4.0/"><p>Kreatiewe Gemene Attribuution-Deel Alike 4.0 Unported Lisensie</p></license>
<credit type="translator copyright"><name>Bernard Stafford</name><email>https://launchpad.net/~bernard010</email><years></years></credit></info>

<title>Wanneer Alles Verkeerd Gaan</title>

<p><app>Déjà Dup</app> may fail.  Maybe it crashes or gives you an error when you try to restore.  When you really need your data back, the last thing you want do deal with is a bug.  Consider filing a <link href="https://gitlab.gnome.org/World/deja-dup/-/issues/new">help request</link> but in the meantime, here are some approaches to workaround a misbehaving <app>Déjà Dup</app> and get your data back.</p>

<note><p>Hierdie is gaan tegnies raak. As geeneen hiervan vir jy sin maak nie, moenie bang wees om <link xref="support">vra vir hulp</link>.</p></note>

<note><p>These instructions assume you have a command line available. Open a <app>Terminal</app> window first.</p></note>

<section id="which-backend">
<title>Restic or Duplicity?</title>

<p>Over time, <app>Déjà Dup</app> has used different backup tools under the covers. Originally, it used <app>Duplicity</app>. Nowadays, it uses <app>Restic</app>.</p>
<p>Your backup might be in either format, depending on when you created it.</p>
<p>Look in the folder where your backup is kept:</p>
<list>
  <item><p>If the filenames all start with <cmd its:translate="no">duplicity-</cmd>, then it's a <app>Duplicity</app> backup. Read the <app>Duplicity</app> sections below.</p></item>
  <item><p>If you see a <cmd its:translate="no">config</cmd> file and a few folders like <cmd its:translate="no">keys</cmd>, then it's a <app>Restic</app> backup. Read the <app>Restic</app> sections below.</p></item>
</list>
</section>

<section id="restic">
<title>Restoring with Restic</title>

<p>On the assumption that <app>Déjà Dup</app> is just not working for you right now, let’s use the command line tool <app>Restic</app> that is used by <app>Déjà Dup</app> behind the scenes to back up and restore your files.</p>

<note style="advanced"><p>If you want more information about <app>Restic</app> than presented here, run <cmd its:translate="no">restic --help</cmd>.</p></note>

<p>Die eerste ding wat ons sal probeer is 'n eenvoudige restoureer van al jou data. Die aanvaarding van jou lêers op 'n eksterne ry gemonteer as <file its:translate="no">/media/backup</file> en jy het gekies om die rugsteun te enkripteer, probeer dit:</p>
<screen its:translate="no">restic restore --repo=/media/backup --target=/tmp/restore latest</screen>

<p>As jy die back-up nie het enkripteer, voeg <cmd its:translate="no">--insecure-no-password</cmd> tot die beveel.</p>

<p>If you need to do more advanced debugging, read their <link href="https://restic.readthedocs.io/en/stable/077_troubleshooting.html">troubleshooting guide</link>.</p>
</section>

<section id="duplicity">
<title>Restoureer tans met Dubbeldheid</title>

<p>On the assumption that <app>Déjà Dup</app> is just not working for you right now, let’s use the command line tool <app>duplicity</app> that is used by <app>Déjà Dup</app> behind the scenes to back up and restore your files.</p>

<note style="advanced"><p>If you want more information about <app>Duplicity</app> than presented here, read <link href="http://duplicity.gitlab.io/docs.html">its online documentation</link>.</p></note>

<p>Die eerste ding wat ons sal probeer is 'n eenvoudige restoureer van al jou data. Die aanvaarding van jou lêers op 'n eksterne ry gemonteer as <file its:translate="no">/media/backup</file> en jy het gekies om die rugsteun te enkripteer, probeer dit:</p>
<screen its:translate="no">duplicity restore file:///media/backup /tmp/restore</screen>

<p>As jy die back-up nie het enkripteer, voeg <cmd its:translate="no">--no-encryption</cmd> tot die beveel.</p>

<section id="duplicity-locations">
<title>Other Storage Locations</title>
<p>If you backed up to a remote or cloud server, the syntax you use with <app>Duplicity</app> will be different than the external drive example above.</p>
<p>Read the <app>Duplicity</app> documentation for instructions on how to connect to your server, or try downloading all the <app>Duplicity</app> files yourself to a local folder and following the simpler example above.</p>
</section>

<section id="duplicity-by-hand">
<title>Restoring Duplicity Files by Hand</title>

<p>Indien selfs <app>dubbeldheid</app> werk nie vir u nie, daar is miskien min hoop. Die rugsteunlêerformaat is ingewikkeld en word nie maklik gemanipuleer nie. Maar as u desperaat is, is dit die moeite werd om te probeer.</p>

<p>As jy gebruik 'n afgeleë of wolk bediener om jou rugsteun stoor, eerste af te laai al die <app>dubbeldheid</app> lêers en plaas dit in 'n lêergids op jou rekenaar. Voer dan die lêergids in jou terminale in.</p>

<p><app>Dubbeldheid</app> stoors jou data in klein stukkies genoem volumes. Sommige volumes behoort tot die periodieke ‘full’ of vars rugsteune en ander om die ‘inc’ of inkrementele rugsteune. Begin tans met 'n volledige stel volumes by volume 1, moet jy lêers volume vir volume restoureer.</p>

<p>As jy jou rugsteun geïnkripteer, eers moet jy die volume met decrypt met <cmd its:translate="no">gpg</cmd>. Sê jy het <file its:translate="no">duplicity-full.20110127T131352Z.vol1.difftar.gpg</file>:</p>
<screen its:translate="no">gpg --output duplicity-full.20110127T131352Z.vol1.difftar --decrypt duplicity-full.20110127T131352Z.vol1.difftar.gpg</screen>

<p>Of om alle tegelyk te doen (sorg dat jy genoeg ruimte het!):</p>
<screen its:translate="no">gpg --multifile --decrypt duplicity-full.20110127T131352Z.*.difftar.gpg</screen>

<p>Nou het jy óf 'n <file its:translate="no">.difftar</file> of 'n <file its:translate="no">.difftar.gz</file> volume (afhangende van of jy het om dit te dekripteer of nie). Gebruik <cmd its:translate="no">tar</cmd> op watter een jy ook al die individuele pleisterlêers moet uittrek:</p>
<screen its:translate="no">tar xf duplicity-full.20110127T131352Z.vol1.difftar</screen>

<p>Of weer, om alle tegelyk te doen:</p>
<screen its:translate="no">for t in duplicity-full.20110127T131352Z.*.difftar; do tar xf $t; done</screen>

<p>Nou sal die pleister lêers in wees <file its:translate="no">multivolume_snapshot</file> en <file its:translate="no">snapshot</file> vouers. Elke lêer wat oor verskeie volumes strek sal in wees <file its:translate="no">multivolume_snapshot</file>.  Kom ons sê jy rugsteun up <file its:translate="no">/home/jane/essay.txt</file>:</p>
<screen its:translate="no">cd multivolume_snapshot/home/jane/essay.txt
cat * &gt; essay.txt</screen>

<p>Om data van inkrementele rugsteun te herstel, gebruik <cmd its:translate="no">rdiff</cmd> om die lêers saam te stik. Sien <cmd its:translate="no">man rdiff</cmd> vir gebruike.</p>

</section>
</section>

</page>
