Backup Error: Warning: unrecognized data found in configuration files

[Eccentric Butterfly]

When I go to backup my Qubes, the backup screen shows a red error at the bottom of the window saying "Warning: unrecognized data found in configuration files".

Why is this? Is there anything I need to do? Will this have any effect on my ability to backup and restore?

[awokd]

Eccentric Butterfly:

> When I go to backup my Qubes, the backup screen shows a red error at the bottom of the window saying "Warning: unrecognized data found in configuration files".

Try closing backup, then "rm
/etc/qubes/backup/qubes-manager-backup.conf" in dom0 terminal. This will
delete the configuration you saved last time you ran backup.

> Why is this? Is there anything I need to do? Will this have any effect on my ability to backup and restore?
>

Haven't seen it before so don't know if it would prevent backups or
restores.

[Daniel Allcock]

On Sun, 5 May 2019 20:24:07 +0000
"'awokd' via qubes-users" <qubes...@googlegroups.com> wrote:

> Eccentric Butterfly:
> > When I go to backup my Qubes, the backup screen shows a red error
> > at the bottom of the window saying "Warning: unrecognized data
> > found in configuration files".

I ran into this and it was innocuous. Probably you have deleted a qube
that you backed up the last time you ran backup. The system remembers
the choices you made in the last backup and sets them up as the
defaults. So it knows it is supposed to backup a qube that isn't there
anymore. So it says it's confused. You can follow awokd's advice
(the file will be recreated when you run backup; it is where the
previous-backup settings are stored). Or you can just ignore the
message and continue with your backup. I'd delete the file, just in
case something more serious is happening.

Best Wishes,
Daniel

[Eccentric Butterfly]

Thanks for your reply guys. I think it's a mix of what both of you are saying.

When I backup qubes to a hard drive, I make sure the qube is not connected to a network. When I'm done, I usually delete the qube. Though in this case, it wasn't deleted (or I re-made the qube with the same name). but it also wasn't running.

When I saw the contents of that file, I realised the path in the 'BACKUP' qube was no longer valid as 1) the qube was not running and 2) the hard drive would not be mounted. Thus, I ran the qube and mounted it and the error was gone.

Thanks for your help, it was much appreciated!
Butterfly.

[Eccentric Butterfly]

Speaking of which, is there really any security benefit in making sure the backup is not connected to a network? Provided the encryption password is secure. I don't think this was mentioned in the docs anywhere as something to consider so it's probably a bit excessive on my part. Of course, provided the password is long and secure.

[awokd]

Eccentric Butterfly:

> Speaking of which, is there really any security benefit in making sure the backup is not connected to a network? Provided the encryption password is secure. I don't think this was mentioned in the docs anywhere as something to consider so it's probably a bit excessive on my part. Of course, provided the password is long and secure.
>

Since all contents of all AppVMs you select pass through your Backup VM,
it's a good idea in general to be cautious about attaching it to a
network if you don't have to. Same with any other AppVM, really.
Security benefit is that it makes it harder to exfiltrate data.