Storage Backend

Use Silo Control Centre → Storage Backend to move supported Silo data from SQLite to MySQL or MariaDB while keeping the current database active until the replacement has been verified.

Refresh current state

For a remotely placed Silo, refresh its database state before making a change. Bridge asks the owning Execution Node for the current non-secret status.

Choose the data areas

Select the supported data areas you intend to move and enter the target database details.

Save & Test Target

Test the target before migration. Resolve connection, credential, database-access or Node-support errors before copying data.

Migrate

Migration copies and verifies the selected data while the live Silo stays on its current database.

Switch Database

When the verified target is correct, choose Switch Database. Micro CMS creates the required protection and switches only when the final verification is safe. If the switch cannot complete, the previous database remains active.

Unlock Verified Migration

Use Unlock Verified Migration when you need to abandon the verified target and change the migration details. Unlocking does not erase an external database.

Execution Node requirements

A remotely placed Silo requires a current compatible Execution Node and the database driver needed for the target. Upgrade or correct the Node when Bridge reports that the required storage capability is unavailable.

After cutover

Check Admin, representative public pages, Media, interactions and Analytics where those areas were moved. Keep the previous database copy until you are satisfied that the new storage is operating correctly.