[DOCS-5772] Cloud Manager storage engine change process leaves behind backup files Created: 02/Jul/15 Updated: 24/Feb/16 Resolved: 14/Jul/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Sommer | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 8 years, 32 weeks, 6 days ago | ||||
| Description |
|
As part of the Cloud Manager's process for changing a deployment's storage engine via automation, backup files are created. They are not removed at the end of the process, but rather left behind as a precaution. Assuming a dbpath for the mongod of /data/mongo the backup file will be /data/mongo.bak.UNIQUENAME where UNIQUENAME is a randomly generated string. Given the unique name, conflicts with future change attempts are not a problems. However, these backups will use up disk space. Users should be informed of the backups' existence and advised to remove them at the appropriate time. |