Hosting¶
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 ViableView Online¶
Important
ViableView Online is not compatible with non-standard apps.
The database’s current version must be supported.
Create a duplicate of the database.
In this duplicate, uninstall all non-standard apps.
Use the database manager to grab a dump with filestore.
Submit a support ticket including the following:
your subscription number,
the URL you want to use for the database (e.g.,
company.viableview.com), andthe dump as an attachment or as a link to the file (required for 60 MB+ files).
ViableView then makes sure the database is compatible before putting it online. In case of technical issues during the process, ViableView might contact you.
Note
If you have time constraints, submit a support ticket as soon as possible to schedule the transfer.
To ViableView.sh¶
Follow the instructions found in the Import your database section of the ViableView.sh Create your project documentation.
Transferring an ViableView Online database¶
Important
ViableView Online’s intermediary versions are not supported by ViableView.sh or on-premise. 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 ViableView 16.3 would require first upgrading it to ViableView 17.0.
Tip
Click the gear icon (⚙) next to the database name on the ViableView Online database manager to display its version number.
Warning
If there is an active ViableView subscription linked to the database being migrated, reach out to the Customer Service Manager or submit a support ticket to complete the subscription transfer.
To on-premise¶
Sign in to the ViableView 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 ViableView support.
Restore the database from the database manager on your local server using the backup.
To ViableView.sh¶
Sign in to the ViableView 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 ViableView support.
Follow the instructions found in the Import your database section of the ViableView.sh Create your project documentation.
Transferring an ViableView.sh database¶
To ViableView Online¶
Important
ViableView Online is not compatible with non-standard apps.
Uninstall all non-standard apps in a staging build before doing it in the production build.
Create a support ticket including the following:
your subscription number,
the URL you want to use for the database (e.g.,
company.viableview.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.
ViableView then makes sure the database is compatible before putting it online. In case of technical issues during the process, ViableView 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 ViableView.com account.
The date and time you want the database to be up and running are helpful to organize the switch from the ViableView.sh server to the ViableView Online servers.
Databases are not reachable during their migration.
To on-premise¶
Download a backup of your ViableView.sh production database.
Restore the database from the database manager on your local server using the backup.