-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Description
Output of restic version
restic 0.7.0
compiled with go1.8.3 on windows/amd64
How did you start restic exactly? (Include the complete command line)
restic.exe --repo s3:s3.amazonaws.com/bucket-name -p repo-pass.txt migrate s3_layout
What backend/server/service did you use?
Amazon S3
Expected behavior
Migrate backend to new layout
Actual behavior
1st run: the process began running and I could see the data files being renamed in the bucket. After some time the process stopped with a connection error. I lost the message because I then ran check and it was longer than the console scrollback, but it was related to network connection - I've had lots of connection errors so this wasn't surprising.
2nd run: migration s3_layout cannot be applied: check failed
Steps to reproduce the behavior
I expect that disconnecting the network during the migration process would probably replicate this.
Do you have any idea what may have caused this?
The migration was interrupted, so it looks to me like the repo is in an inconsistent state.
Is there a way to continue the migration?