Skip to content

For HA, state how to restore a replica; in DR note instructions are only for lost clusters #671

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
leenamba opened this issue Nov 21, 2016 · 3 comments
Assignees
Labels
area/enterprise Issue affects Docker Enterprise lifecycle/locked

Comments

@leenamba
Copy link
Contributor

Problem description

A DDC customer Finnish Rail thought backup and restore applied to single replicas and not for the entire cluster. This caused them to loose a day of work and opened up several support tickets.

Project version(s) affected

DTR 2.0 and 2.1

Suggestions for a fix

State clearly in the HA section how to restore a replica with join command.
State clearly in the DR section that this is only if you've lost the entire cluster.

@londoncalling
Copy link
Contributor

londoncalling commented Apr 5, 2017

About the topics

This set of issues is related to setting up HA with DTR, starting with the 2.0 docs: https://docs.docker.com/datacenter/dtr/2.0/high-availability/

The current version of this topic is: https://docs.docker.com/datacenter/dtr/2.2/guides/admin/configure/set-up-high-availability/

Related issues and PRs

Open

#1750

Closed but list several other issues, some still open

#1785, #1724, #1792

@johndmulhausen johndmulhausen changed the title Feedback for: datacenter/dtr/2.0/high-availability/index.md For HA, state how to restore a replica; in DR note instructions are only for lost clusters Aug 29, 2017
@joaofnfernandes
Copy link
Contributor

This will be addressed in the next release of DTR. We've done a ton of content changes for the next version, but unfortunately they are not that easy to backport, so you won't get those goodies for now.

@docker-robott
Copy link
Collaborator

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

@docker docker locked and limited conversation to collaborators Nov 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/enterprise Issue affects Docker Enterprise lifecycle/locked
Projects
None yet
Development

No branches or pull requests

6 participants