cinder-backup not covered by HA guide

Bug #1667792 reported by Adam Spiers on 2017-02-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Frank Kloeker

Bug Description does not mention cinder-backup at all. We should document this. Salient points which I have just received from Michal Dulko:

- Before Mitaka, cinder-backup could not be active/active and had to be colocated with the cinder-volume serving the backend it wanted to backup.

- Since Mitaka, this colocation restriction has been lifted (the backup_use_same_host option now defaults to False) and you can run cinder-backup anywhere, scaling to as many instances as you want.

Darren Chan (dazzachan) on 2017-02-26
Changed in openstack-manuals:
importance: Undecided → High
status: New → Confirmed
Changed in openstack-manuals:
assignee: nobody → foundjem (foundjem-devops)
Njira Perci (njirap) on 2017-06-17
Changed in openstack-manuals:
assignee: foundjem (foundjem-devops) → Njira Perci (njirap)
Changed in openstack-manuals:
assignee: Njira Perci (njirap) → nobody
Changed in openstack-manuals:
assignee: nobody → Frank Kloeker (f-kloeker)
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers