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.

Suggested addition to: default_compressed_extensions.txt

.tib #Acronis True Image windows backup image software
.tibx #Acronis True Image windows backup image software
.mrimg #Macrium Reflect windows backup image software

I've used both im

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

First, thank you for maintaining this wonderful tool!

Is your feature request related to a problem? Please describe.
PBKDF2-HMAC-SHA1 is no longer recommended, and may become a problem if there are too few iterations (SHA1 is the issue, especially in conjunction with the small number of iterations), although a 16byte/128bit salt remains fine. This only offers security if used in conjunctio

Feature Request

A simple command that just pulls readable information from msdb..suspect_pages.

Problem to solve

At times you need to monitor the suspect pages a server may have or verify after you get logical errors returned from DBCC results, or even finding the dreaded 823/824 err

I see no documentation for the .kopiaignore format. A search in https://kopia.io/docs/ finds no matches (which looks like a bug in the docs search engine, since .kopiaignore is mentioned, but not described, in the documentation).

#773 suggests that .kopiaignore now behave similarly to .gitignore, but this is not mentioned in the documentation, and presumably there are some differences s

Unterminated string literal

failing query: '
CREATE TABLE `contact` (
  `id` char(36) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '',
  `account` varchar(20) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '',
  `name` varchar(30) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '姓名',
  `mobile` varchar(15) CHARACTER SET u