Dear list,
This path contains a chain of full and incremental backups
going back
months. Any competent backup program is expected to not
corrupt its
storage and then proceed without errors to add further
incrementals
in a way that it cannot restore .
As to how to check the directory listing on AWS S3, I don't know
what
file name to look for, especially given the limitation that S3 can
only
search on a name prefix, not arbitrary wildcards.
The partition in question contains terabytes of data, that should
not
be lost under any circumstance, and this is the fire drill test of
the
restore procedure. If duplicity cannot handle this basic task, I
will
need to look for other solutions for continuous system backup.
On 2023-08-11 18:54, Kenneth
Loafman via Duplicity-talk wrote:
That specific error says that volume 272 difftar of
the backupset is missing. Not a good error message by
any means.
You can check on S3 to see if somehow it did not get
downloaded, but my guess is that it is indeed missing.
Did you have any restarts during the backup? Did you
verify the backup?
...Ken
Dear
all,
I am testing the viability of my backups by restoring to a
blank Linux
computer loaded up with the decryption keys and the same
patched
duplicity 1.2.1 that I used for the backup (just a patch for
the doubled
--encrypt option and one for lowering the threshold for
displaying
actual progress numbers instead of "Stalled").
However when restoring a large partition, instead of
restoring, it fails
with the error messages below, the message doesn't say what
the error is
or what it was trying to do, just an error number and
traceback of the
stack with no specific context:
Added incremental Backupset (start_time: Thu May 25 02:13:30
2023 /
end_time: Thu Jun 22 11:50:21 2023)
Added incremental Backupset (start_time: Thu Jun 22 11:50:21
2023 /
end_time: Mon Jul 3 09:17:24 2023)
Added incremental Backupset (start_time: Mon Jul 3 09:17:24
2023 /
end_time: Mon Jul 17 18:50:05 2023)
Added incremental Backupset (start_time: Mon Jul 17 18:50:05
2023 /
end_time: Wed Jul 19 22:32:43 2023)
Added incremental Backupset (start_time: Wed Jul 19 22:32:43
2023 /
end_time: Mon Jul 24 03:50:01 2023)
Added incremental Backupset (start_time: Mon Jul 24 03:50:01
2023 /
end_time: Mon Aug 7 21:33:50 2023)
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Thu May 25 02:13:30 2023
Processing local manifest
b'/bkup4/archive/wisemo-bk-real-more/wisemo-bk-real-more/wisemo-bk-real-more_duplicity-full.20230525T021330Z.manifest'
(82148726)
Found 11293 volumes in manifest
Traceback (innermost last):
File "/usr/local/bin/duplicity", line 86, in <module>
with_tempdir(main)
File "/usr/local/bin/duplicity", line 70, in with_tempdir
fn()
File
"/usr/local/lib/python3.11/dist-packages/duplicity/dup_main.py",
line 1575, in main
do_backup(action)
File
"/usr/local/lib/python3.11/dist-packages/duplicity/dup_main.py",
line 1658, in do_backup
restore(col_stats)
File
"/usr/local/lib/python3.11/dist-packages/duplicity/dup_main.py",
line 749, in restore
restore_get_patched_rop_iter(col_stats)):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"/usr/local/lib/python3.11/dist-packages/duplicity/dup_main.py",
line 801, in restore_get_patched_rop_iter
file_names.append(backup_set.volume_name_dict[vol_num])
~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
KeyError: 272
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
|