backup

Considering issues like #5954 are bad to solve / debug without this information, borg should debug log full paths of all caches / indexes it uses.

My understanding is that Velero is non-destructive during a restore. But, I don't believe that it is called out anywhere in the docs. I would suggest we add something like this to the restore reference doc:

During a restore, Velero is non-destructive. That means that Velero will never overwrite a pre-existing resource which has the same name as

What went wrong?

I'm getting deprecation warnings with openSSL encryption.

[2019/09/05 08:38:52][info] Using Encryptor::OpenSSL to encrypt the archive.
[2019/09/05 08:40:22][warn] Pipeline STDERR Messages:
[2019/09/05 08:40:22][warn] (Note: may be interleaved if multiple commands returned error messages)
[2019/09/05 08:40:22][warn]
[2019/09/05 08:40:22][warn] *** WARNING : depre

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...

The copy button and 3 dot menu button is making the UI looks cluttered because the account name is getting truncated or spread to multiple lines...please add an option to hide the copy button and 3 dot menu button like aegis

**Describ

Hi

I have more than 10 snapshots so it only shows 10 snapshots in the list. I can set to more than 10 but it always resets it back to 10 after any UI tab/window change.

thanks

When using a clearly bad configuration file, Barman throws a python exception. I'd expect only a clear error message, not a python exception. This was distilled from a customer configuration, so fixing the test case will bring a simpler (less scary) message for the end user when they should fix their configuration file.

The following test case was produced in Barman 2.18.

For the obviously w