[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Duplicity-talk] Error means old full backups not accessible
From: |
Adam Huffman |
Subject: |
[Duplicity-talk] Error means old full backups not accessible |
Date: |
Tue, 16 Aug 2011 13:00:39 +0100 |
Duplicity was running quite happily on a Fedora workstation, backing
up to a Centos server. However, recently it complained:
<lots of similar messages snipped>
Deleting local
/home/<user>/.cache/duplicity/8964c8943d1058781d103a16e1af8282/duplicity-new-signatures.20110727T230201Z.to.20110728T230202Z.sigtar.gz
(not authoritative at backend).
Deleting local
/home/<user>/.cache/duplicity/8964c8943d1058781d103a16e1af8282/duplicity-new-signatures.20110728T230202Z.to.20110729T230201Z.sigtar.gz
(not authoritative at backend).
Deleting local
/home/<user>/.cache/duplicity/8964c8943d1058781d103a16e1af8282/duplicity-new-signatures.20110729T230201Z.to.20110730T230201Z.sigtar.gz
(not authoritative at backend).
Deleting local
/home/<user>/.cache/duplicity/8964c8943d1058781d103a16e1af8282/duplicity-new-signatures.20110730T230201Z.to.20110731T230201Z.sigtar.gz
(not authoritative at backend).
Deleting local
/home/<user>/.cache/duplicity/8964c8943d1058781d103a16e1af8282/duplicity-new-signatures.20110731T230201Z.to.20110801T230201Z.sigtar.gz
(not authoritative at backend).
Last full backup date: none
No signatures found, switching to full backup.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1311, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1304, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1279, in main
full_backup(col_stats)
File "/usr/bin/duplicity", line 451, in full_backup
sig_outfp.to_remote()
File "/usr/lib64/python2.7/site-packages/duplicity/dup_temp.py",
line 176, in to_remote
src_iter = SrcIter(src)
File "/usr/lib64/python2.7/site-packages/duplicity/dup_temp.py",
line 246, in __init__
self.fp = src.open("rb")
File "/usr/lib64/python2.7/site-packages/duplicity/path.py", line 533, in open
result = open(self.name, mode)
IOError: [Errno 2] No such file or directory:
'/home/<user>/.cache/duplicity/8964c8943d1058781d103a16e1af8282/duplicity-full-signatures.20110802T230201Z.sigtar.part'
and since then each time it's tried to run this is the output:
Local and Remote metadata are synchronized, no sync needed.
Last full backup left a partial set, restarting.
Last full backup date: Wed Aug 3 00:02:01 2011
RESTART: The first volume failed to upload before termination.
Restart is impossible...starting backup from beginning.
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
No signatures found, switching to full backup.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1311, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1304, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1279, in main
full_backup(col_stats)
File "/usr/bin/duplicity", line 451, in full_backup
sig_outfp.to_remote()
File "/usr/lib64/python2.7/site-packages/duplicity/dup_temp.py",
line 176, in to_remote
src_iter = SrcIter(src)
File "/usr/lib64/python2.7/site-packages/duplicity/dup_temp.py",
line 246, in __init__
self.fp = src.open("rb")
File "/usr/lib64/python2.7/site-packages/duplicity/path.py", line 533, in open
result = open(self.name, mode)
IOError: [Errno 2] No such file or directory:
'/home/<user>/.cache/duplicity/8964c8943d1058781d103a16e1af8282/duplicity-full-signatures.20110803T230220Z.sigtar.part'
It now won't recognise the earlier full backups, even once I've copied
over the manifest and sigtar files from the remote server.
It's running version 0.6.14
Any suggestions?
Adam
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Duplicity-talk] Error means old full backups not accessible,
Adam Huffman <=