Change hosting solution

The instructions to change the hosting type of a database depend on the current solution used and to which solution the database should be moved.

Transferring an on-premise database

To Juniper Online

Important

  • Juniper Online is not compatible with non-standard apps.

  • The database’s current version must be supported.

  1. Create a duplicate of the database.

  2. In this duplicate, uninstall all non-standard apps.

  3. Use the database manager to grab a dump with filestore.

  4. Submit a support ticket including the following:

    • your subscription number,

    • the URL you want to use for the database (e.g., company.Juniper.com), and

    • the dump as an attachment or as a link to the file (required for 60 MB+ files).

  5. Juniper then makes sure the database is compatible before putting it online. In case of technical issues during the process, Juniper might contact you.

Note

If you have time constraints, submit a support ticket as soon as possible to schedule the transfer.

To Juniper.sh

Follow the instructions found in the Import your database section of the Juniper.sh Create your project documentation.

Transferring an Juniper Online database

Important

Juniper Online’s intermediary versions cannot be hosted on-premise as that type of hosting does not support those versions. Therefore, if the database to transfer is running an intermediary version, it must be upgraded first to the next major version, waiting for its release if necessary.

Example

Transferring an online database running on Juniper 16.3 would require first upgrading it to Juniper 17.0.

Tip

Click the gear icon (⚙) next to the database name on the Juniper Online database manager to display its version number.

To on-premise

  1. Sign in to the Juniper Online database manager and click the gear icon (⚙) next to the database name to Download a backup. If the download fails due to the file being too large, contact Juniper support.

  2. Restore the database from the database manager on your local server using the backup.

To Juniper.sh

  1. Sign in to the Juniper Online database manager and click the gear icon (⚙) next to the database name to Download a backup. If the download fails due to the file being too large, contact Juniper support.

  2. Follow the instructions found in the Import your database section of the Juniper.sh Create your project documentation.

Transferring an Juniper.sh database

To Juniper Online

Important

Juniper Online is not compatible with non-standard apps.

  1. Uninstall all non-standard apps in a staging build before doing it in the production build.

  2. Create a support ticket including the following:

    • your subscription number,

    • the URL you want to use for the database (e.g., company.Juniper.com),

    • which branch should be migrated,

    • in which region you want the database to be hosted (Americas, Europe, or Asia),

    • which user(s) will be the administrator(s), and

    • when (and in which timezone) you want the database to be up and running.

  3. Juniper then makes sure the database is compatible before putting it online. In case of technical issues during the process, Juniper might contact you.

Note

  • If you have time constraints, submit a support ticket as soon as possible to schedule the transfer.

  • Select the region closest to most of your users to reduce latency.

  • Future administrator(s) must have an Juniper.com account.

  • The date and time you want the database to be up and running are helpful to organize the switch from the Juniper.sh server to the Juniper Online servers.

  • Databases are not reachable during their migration.

To on-premise

  1. Download a backup of your Juniper.sh production database.

  2. Restore the database from the database manager on your local server using the backup.