<?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" xml:lang="sl">
<info>
  <desc>Kaj storiti, če datotek ni mogoče obnoviti?</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>Creative Commons Attribution-Share Alike 4.0 Unported License</p></license>
</info>

<title>Ko gre vse narobe</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/-/work_items/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>To bo postalo tehnično. Če nič od tega ni smiselno, naj vas ne bo strah <link xref="support">prositi za pomoč</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>Prvo možnost, ki jo bomo poskusili, je enostavno obnavljanje vseh vaših podatkov. Predpostavljamo, da so vse datoteke na vašem zunanjem mediju naložene kot <file its:translate="no">/media/backup</file> in želite šifrirati varnostno kopijo poskusite naslednje:</p>
<screen its:translate="no">restic restore --repo=/media/backup --target=/tmp/restore latest</screen>

<p>Če varnostne kopije niste šifrirali ukazu dodajte <cmd its:translate="no">--insecure-no-password</cmd>.</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>Obnavljanje z Duplicity</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>Prvo možnost, ki jo bomo poskusili, je enostavno obnavljanje vseh vaših podatkov. Predpostavljamo, da so vse datoteke na vašem zunanjem mediju naložene kot <file its:translate="no">/media/backup</file> in želite šifrirati varnostno kopijo poskusite naslednje:</p>
<screen its:translate="no">duplicity restore file:///media/backup /tmp/restore</screen>

<p>Če varnostne kopije niste šifrirali ukazu dodajte <cmd its:translate="no">--no-encryption</cmd>.</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>Če <app>duplicity</app> ne deluje, še vedno obstaja upanje. Oblika varnostne kopije je zapletena in težka za urejanje. Vendar če ste vztrajni, je vredno poskusiti.</p>

<p>Če ste uporabili oddaljen strežnik ali oblak za shranjevanje vaših varnostnih kopij, najprej prejmite vse datoteke <app>duplicity</app>  in jih shranite v mapo na svojem računalniku. Nato pojdite v to mapo v terminalu.</p>

<p><app>Duplicity</app> shranjuje vaše podatke v majhnih delčkih imenovanih nosilci. Nekateri prostori pripadajo občasnih 'polnim' ali svežim varnostnim kopijam in ostale v 'inc' ali koračni varnostni kopiji. Obnoviti boste morali vsako datoteko posebej pri čemer začnite s polnimi varnostnimi kopijami pri nosilcu 1.</p>

<p>Če ste šifrirali svojo zbirko podatkov, jo morate prvo odšifrirati v nosilcu z <cmd its:translate="no">gpg</cmd>. Recimo, da imate <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>Ali da izdelate vse na enkrat (zagotovite da imate dovolj prostora!):</p>
<screen its:translate="no">gpg --multifile --decrypt duplicity-full.20110127T131352Z.*.difftar.gpg</screen>

<p>Sedaj imate nosilec <file its:translate="no">.difftar</file> ali <file its:translate="no">.difftar.gz</file> (odvisno od tega ali ste ga odšifrirali ali ne). Uporabite <cmd its:translate="no">tar</cmd> na enemu od njih za razširitev posameznih popravkov:</p>
<screen its:translate="no">tar xf duplicity-full.20110127T131352Z.vol1.difftar</screen>

<p>Ali še enkrat, storite vse na enkrat:</p>
<screen its:translate="no">for t in duplicity-full.20110127T131352Z.*.difftar; do tar xf $t; done</screen>

<p>Popravek bo v mapi <file its:translate="no">multivolume_snapshot</file> and <file its:translate="no">snapshot</file>. Vsaka datoteka, ki deli nosilce bo v <file its:translate="no">multivolume_snapshot</file>. Recimo, da ste izdelali varnostno kopijo <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>Za obnovitev podatkov iz koračne varnostne kopije uporabite <cmd its:translate="no">rdiff</cmd> za združitev datotek skupaj. Oglejte si <cmd its:translate="no">rdiff</cmd> za uporabo.</p>

</section>
</section>

</page>
