Page tree
Skip to end of metadata
Go to start of metadata

If you wish to try out MCOECN hosting, the easiest way is to migrate a copy of one of your local Redesign instances to the MCOECN.  

Creating a Backup and Getting it to the MCOECN

There are two ways to do upload a backup to the MCOECN:

  1. Create a backup on your local docker instance, and upload it to SSDT-UPLOADS, the same as you would when requesting support from SSDT.
    This backup process is documented in the following SSDT WIKI article:
    https://wiki.ssdt-ohio.org/display/rtd/Backup+USxS+Databases
    The upload process is documented in the following SSDT WIKI article:
    https://wiki.ssdt-ohio.org/display/rtd/Securely+Send+Files+to+SSDT+for+Support

  2. The MCOECN provides a hosted virtual machine for Docker testing to each ITC, and some ITCs do scripted backups of their local Redesign instances to this server.  If you are already backing up local instances to MCOECN, you already have a backup that you can use.
    This process is documented in this following SSDT WIKI article:
    https://wiki.ssdt-ohio.org/display/rtd/Using+Remote+Backup+Script

Backup Naming Convention

NOTE: It is important that the backup filename follows a rigid format: <IRN>-<District Name>-<Application>db.<timestamp>.backup.gz
Examples: 
  USPS                   047589libertycenter-uspsdb.2022-03-01-03-10-06.backup.gz
  USAS                   043679bryan-usasdb.2022-02-08-02-26-01.backup.gz
  WORKFLOWS      051201ct-workflowsdb.2022-03-03-01-09-35.backup.gz
  INVENTORY        046011unionlocal-inventorydb.2022-02-11-13-00-05.backup.gz

Whatever follows the IRN for the district name/code  is what will be used in the final URL to access the application.

IRN must be a full six digit IRN padded with Leading Zeros.  This is important...the VRA item to create the test instance will fail if it cannot find the full IRN.



  • No labels