Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: deja-dup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/16
Thanks Naël, your suggestion on Comment #6 worked for me on Ubuntu
17.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1651396
Title:
Backup fails every time after one incremental
Hello!
There is obviously nothing we can do about packages which got corrupted
on the backup media or during transfers.
So what exactly is this bugreport asking for?
Best Regards
Vej
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
Can't you read Vej?
People have to use "a workaround" which isn't explained anywhere in the
documentation if a backup gets corrupted. It isn't even obvious from the
error message that an earlier backup got corrupted.
--
You received this bug notification because you are a member of Desktop
Packa
Have you tried to verify your backup or do a new full backup?
> Can someone recommend a better backup software for personal use?
http://lmgtfy.com/?q=personal+backup+software+linux
There is a reason, though, that Deja Dup (which you are already using)
is the default in Ubuntu -- it is a pretty go
> Have you tried to verify your backup or do a new full backup?
http://lmgtfy.com/?q=deja+dup+new+full+backup
Shows basically nothing... Where's the option for that? Maybe you should
tell me something concrete instead of pasting smart ass links?
--
You received this bug notification because you
To create a new full backup, simply backup to a new location, or move
the files in the current location to some other place. Déjà Dup will
detect the absence of previous backups and start a new full backup.
The backup location is the directory that stores the duplicity files
that Déjà Dup produces
The only error message that shows up is the one I already posted here.
DUPLICITY: ERROR 21
DUPLICITY: . Invalid data - SHA1 hash mismatch for file:
DUPLICITY: .
duplicity-inc.20161219T001458Z.to.20161220T001456Z.vol1.difftar.gpg
DUPLICITY: . Calculated hash: 3dde403f81e36268ce9b7f53478d9dd8301a
Thanks for this log. It shows that your current backup chain started on
Oct 10, contains the offending incremental backup (Dec 19 to Dec 20),
and has later incremental backups (three more on Dec 20, one on Dec 21,
one on Dec 22, one on Dec 30). You can see for yourself under "primary
backup chain"
9 matches
Mail list logo