2017-05-14 21:37:45 +02:00
|
|
|
<!--
|
2017-08-11 21:36:10 +02:00
|
|
|
NOTE: Not filling out the issue template needs a good reason, otherwise it may
|
|
|
|
|
take a lot longer to find the problem! Please take the time to help us
|
|
|
|
|
debugging the problem by collecting information, even if it seems irrelevant to
|
|
|
|
|
you. Thanks!
|
|
|
|
|
|
|
|
|
|
If you have a question, maybe the forum at https://discourse.restic.net is a
|
|
|
|
|
better place.
|
2017-05-14 21:37:45 +02:00
|
|
|
-->
|
|
|
|
|
|
2016-02-21 00:35:58 +01:00
|
|
|
## Output of `restic version`
|
|
|
|
|
|
|
|
|
|
|
2017-08-11 21:36:10 +02:00
|
|
|
## How did you run restic exactly?
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
Include the complete command line and any environment variables you used to
|
|
|
|
|
configure restic's backend access. Make sure to replace sensitive values!
|
|
|
|
|
-->
|
2017-04-17 18:30:20 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
## What backend/server/service did you use?
|
|
|
|
|
|
|
|
|
|
|
2016-02-21 00:35:58 +01:00
|
|
|
## Expected behavior
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Actual behavior
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Steps to reproduce the behavior
|
|
|
|
|
|
|
|
|
|
|
2017-04-17 18:30:20 +02:00
|
|
|
## Do you have any idea what may have caused this?
|
2017-08-11 21:36:10 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
## Do you have an idea how to solve the issue?
|
