Provide Customer With Database Export of Open edX Site - Appsembler

Help & How-to

Your comprehensive knowledge base for Open edX, Tahoe LMS, and Virtual Labs. Dive into in-depth documentation, tutorials, troubleshooting guides, and best practices to help with your integration of Appsembler's products.

Provide Customer With Database Export of Open edX Site

FOR ENGINEERS:

For now, backups are sent to S3. We may need to revise this procedure in the future if we’re using gcloud storage.

  1. Sign into AWS and navigate to the S3 dashboard and select the correct S3 bucket.
  2. Click the checkbox to the left of the MySQL backup you’d like to provide the customer.
  3. Click the “properties” button on the top right
  4. Expand the “permissions” section and click the “add more permissions” link
  5. For “grantee” select “everyone,” click the checkbox next to “open/download,” then click the blue “save” button
  6. In the top right panel, there will be a label “link” with a corresponding URL (e.g. https://s3.amazonaws.com/edx-docker-backups/2d621c34_mysql_20150723.tar.gz). Email this link to the intended recipient.
  7. Repeat steps 2-6 for the Mongo db as well.

After the customer has had sufficient time to download the dbs (roughly a week), remove the “everyone” “open/download” permissions.

FOR CUSTOMER SUCCESS:

Data Format

Each of the data pieces will be in a different format:
MySQL: SQL (single-file) dump of database
MongoDB: full dump in .bson/.json formats
Tracking logs: text (that is, non-binary) logfiles

File Size

We’ll know more when we do the exports, but generally database dumps are in the tens to hundreds of megabytes. Exceptions are the tracking logs, which can–depending on the site activity–be up in the gigabyte range.