Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-5772

Cloud Manager storage engine change process leaves behind backup files

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Cloud Manager
    • Labels:
      None

      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.

            Assignee:
            Unassigned Unassigned
            Reporter:
            eric.sommer@mongodb.com Eric Sommer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              8 years, 44 weeks, 1 day ago