Versions Compared

Old Version 2

changes.mady.by.user Chad Carson

Saved on

compared with

New Version 3

changes.mady.by.user Chad Carson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.  When hosting with the MCOECN, the URL to access your application will be of the format:
   

...

Panel
borderColor#000099
bgColor#eeeeee
titleColor#ffffff
borderWidth2
titleBGColor#000099
borderStylesold
titleCreating a Backup

First, you will need to get a backup uploaded to the MCOECN.  There are two ways to do this.

  1. Create a backup and upload it to SSDT-UPLOADS, the same as you would when requesting support from SSDT.

  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.

Backup Naming Convention

NOTE: It is important that the backup filename follows a rigid format: <IRN>-<District Name>-<Application>db.<timestamp>.backup.gz
One small nuance, there is no dash between USAS and "DB" ,USPS and "DB", and WORKFLOWS and "DB" in the name, but there IS a dash between "Inventory" and "DB" in the backup filename.
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-inventory-db.2022-02-11-13-00-05.backup.gz

Training instances will have "train" at the beginning of the URL.

...


Getting your data to MCOECN

...