/
Upload a Local Docker Backup to the MCOECN

Upload a Local Docker Backup to the MCOECN

Owned by Chad Carson
Last updated: Feb 21, 2025
2 min read

If you wish to try out MCOECN hosting, you can deploy a test copy of one of your local State Software applications to the MCOECN very easily.

The steps to do this are

  1. Upload a backup to MCOECN

  2. Log into https://cloud.managementcouncil.org with your MCOECN username/password. Email dco-help@managementcouncil.org if you have no access to https://cloud.managementcouncil.org and we can help you get access.

  3. Deploy “State Software Test” from the available Service Broker options. See this page for detailed instructions Create a Test Deployment of Redesign Applications

 

There are two ways to 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 automated nightly backups of their local State Software Applications to this server.  If you are already backing up locally-hosted applications 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 VERY important that the backup filename follows a rigid format for the Cloud Service Broker automation to work.

The format is <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
ESS 010226mcoecn-essdb.2025-02-21-16-07-48.backup.gz

The IRN must be a full six digit IRN padded with Leading Zeros.  This is important...the Service Broker searches for backups by IRN, not district name, so deploying a test will fail if it cannot find an available backup that matches the full IRN.

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

Example: 051201ct-workflowsdb.2022-03-03-01-09-35.backup.gz will become https://laca-ct-workflows.ssdt-ohio.org

 

 

 

Related content