Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-9049

Implement special backup cursor: backup:export

    • Type: Icon: New Feature New Feature
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT11.0.0, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • 5
    • Storage - Ra 2022-04-18, Storage - Ra 2022-05-02

      Summary
      WiredTiger needs to provide a new form of a backup cursor URI, called backup:export. When that is specified as the URI, WiredTiger will generate a different backup metadata table called WiredTiger.export. This will contain all the same information that today’s WiredTiger.backup contains, but with a different name so that a restart does not attempt to use it to start a system. When that special cursor is closed, WiredTiger will remove the WiredTiger.export file. This cursor will act in every way like a normal full hot backup cursor (but not an incremental backup cursor). That is, it will generate the same list of files and the user can walk the cursor retrieving the names for files for copying, including WiredTiger.export. Really the only difference is the naming of the metadata file.

      In the attachment, there is an example of metadata(metadata.txt) and WiredTiger.backup of a non-tiered database with a single table named "test".

      Also, there is metadata_tiered.txt which is the metadata of a tiered database with a single table named "test". "flush_tier" was called twice for the database.

        1. metadata_tiered.txt
          9 kB
        2. metadata.txt
          5 kB
        3. WiredTiger.backup
          3 kB

            Assignee:
            monica.ng@mongodb.com Monica Ng
            Reporter:
            alexey.anisimov@mongodb.com Alexey Anisimov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: