You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

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

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


Getting your data to MCOECN

To copy a locally hosted docker redesign instance to the MCOECN for testing, follow these step:

  1. Make sure you can log into http://cloud.managementcouncil.org and see "Service Broker", and the catalog items. If this is the first time your ITC is using MCOECN Hosting, we may need to create an MCOECN.ORG account for you, or grant access to the VRA portal to your existing account.

  2. Create a backup of your local docker instance using the SSDT provided tools.  Use the same procedure you use to send a copy of a docker-hosted instance to the SSDT for support.
  3. Upload the backup to SSDT-Uploads using the SSDT provided scripts.
                          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" or USPS and "DB", but there IS a dash between "Inventory" and "DB" and Workflows and "db" in the backup filename.
                          Example:  USPS                   047589libertycenter-uspsdb.2022-03-01-03-10-06.backup.gz
                                          USAS                   043679bryan-usasdb.2022-02-08-02-26-01.backup.gz
                                          INVENTORY         046011unionlocal-inventory-db.2022-02-11-13-00-05.backup.gz
                                          WORKFLOWS     

    NOTE: Whatever follows the IRN for the district name/code  is what will be used in the final URL to access the application.
    NOTE: IRN must be a full six digit IRN padded with Leading Zeros.  This is important for the next step, to be able to find your backup.

  4. From the VRA Service Broker, run "USxS-RunAsTest" and choose the information for the district you want to test out.

  5. The VRA script will find your backup file by IRN, will automatically create a new instance of USAS/USPS/INVENTORY/WORKFLOWS, will restore your backup into it, and will email you a notice when the task is complete (takes about 10 minutes or less).

  6. Access your application at the URL included in the email notification. You should be able to log in with the same username/password combinations you use locally.
  7. If you connect your local USAS/USPS to your own Active Directory, you will need to work with the Management Council Data Center Operations (DCO) team to allow access from our hosted environment to your Active Directory server(s).
  • No labels