How to triage when metadata restore fails part way?

[rcplane]

File: datacenter/dtr/2.2/guides/admin/backups-and-disaster-recovery.md, CC @joaofnfernandes

Where are more detailed error logs?
I see that organizations and users have been applied but not repositories.

FATA[0012] Couldn't migrate database: exit code 126
FATA[0018] Failed to install DTR: Failed to execute phase 2: Phase 2 returned non-zero status: 1
read unix @->/var/run/docker.sock: read: connection reset by peer

[joaofnfernandes]

@rcplane you can try running the restore command in debug mode, since it will generate more verbose output.

docker run -it --rm docker/dtr:2.2.8 restore --debug ...

If you can't figure what's going on, I recommend filing a ticket with Docker's support team. They will be able to provide you some guidance.

[joaofnfernandes]

Closing due to inactivity, but feel free to comment if you have more feedback on this.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked