Ubuntu 17.04 was fresh installed in early July 2017, and I've since
upgraded to 17.10 (I did not fresh install 17.10). I did not reconfigure
Deja Dup before or after that upgrade.
When I did the fresh install and then set up the backup, I already had a
backup directory on the secondary drive that my previous Ubuntu install
had been using. But, I never configured this install to use that same
directory; I've used a new directory with a different name from the get-
go. So that shouldn't matter.
Looking in the backup directory, the oldest file is dated August 2,
2017. And under scheduling I have Deja Dup configured to keep at least
six months, so I think that date is the real date I first configured the
backup.
I have not tried configuring Deja Dup to use a new storage location
since this problem started occuring. Should I try that?
Also, I should note that the backup window shows the message "Creating a
fresh backup to protect against backup corruption. This will take longer
than normal." Wouldn't this mean that Deja Dup is not trying to create
an incremental backup on top of what was backed up in Ubuntu 17.04?
** Changed in: deja-dup (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729695
Title:
ASCII decode error, but not due to filenames in backup target
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1729695/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
