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

Add note about when it's safe to fsyncUnlock after EBS snapshot

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 01112017-cleanup
    • None
    • ecosystem
    • None

    Description

      For this page: http://docs.mongodb.org/ecosystem/tutorial/backup-and-restore-mongodb-on-amazon-ec2/#unlock-the-database

      From the AWS documentation (bolding is mine):

      You can take a snapshot of an attached volume that is in use. However, snapshots only capture data that has been written to your Amazon EBS volume at the time the snapshot command is issued. This might exclude any data that has been cached by any applications or the operating system. If you can pause any file writes to the volume long enough to take a snapshot, your snapshot should be complete. However, if you can't pause all file writes to the volume, you should unmount the volume from within the instance, issue the snapshot command, and then remount the volume to ensure a consistent and complete snapshot. You can remount and use your volume while the snapshot status is pending.

      The current sentence is not clear about this

      After the snapshots have been created, the database can be unlocked.

      I propose changing this to something along the lines of

      Once the snapshots are in state "pending" (as in the above example), the database can be unlocked.

      Attachments

        Activity

          People

            Unassigned Unassigned
            joanna.cheng@mongodb.com Joanna Cheng
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              8 years, 34 weeks, 4 days ago