Page History

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
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-dbinventorydb.2022-02-11-13-00-05.backup.gz