Database profiles and data copying
Save connections to your database servers and choose which one SHM should use.
Where to find it: Server > Configuration > Database Server > MariaDB Profiles.
Available to: Root only.
What this page does
A SQL profile identifies a database endpoint. Remote profiles require a name, host, port, and administrative credentials. SHM tests the connection before saving; client tools may be required even when the database itself is remote.
Before you start
Back up destination data before copying or overwriting. Source and destination must be different SQL endpoints, not just two different profile names pointing at the same host and port.
Sync Metadata or Copy Profile Data
| Operation | What it changes |
|---|---|
| Sync Metadata | Uses SHM account metadata to create missing database/user definitions and reapply grants. It does not copy or overwrite table data. Existing user passwords change only if the overwrite option is enabled. |
| Copy Profile Data | Copies the selected database data, users, and grants from one profile to another. Overwrite users and overwrite databases are separate explicit choices. |
| Per-item results | Review copied, skipped, and failed items. A completed request is not evidence that every item succeeded. |
How to use it
- Add the remote profile and use Test Connection & Save.
- Choose Sync Metadata for missing definitions/grants, or Copy Profile Data for actual data transfer.
- Confirm distinct endpoints and select only the required data/users/grants and overwrite options.
- Run the operation and review each item’s result.
- Verify application connectivity and representative queries on the intended destination.
Result and next check
The destination contains the intended verified data and grants. Do not remove the source or change application connection settings until destination checks pass.
Theme color