[DOCS-7943] Clarify how backup capacity is scaled by adding more Backup Daemons Created: 23/May/16 Updated: 11/Jan/17 Resolved: 26/May/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Kai Orend | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Epic Link: | OM Backup Daemon |
| Description |
|
we say: To increase your storage and to scale horizontally, you can run multiple instances of the Backup Daemon. We should probably clarify here that scaling in this context means that (only) the available storage for the head dbs is increased and not the available space for snapshot storage. |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |