Backup, restore and migration | Mingcedar

<div class="manual-doc-article manual-doc-article-section"><h2 id="migration-backup">User guide: Backup, restore and migration</h2>

Back up data, project files, published releases, scripts and runtime configuration. Settings exports only its own fields.

<div class="doc-card-list doc-tutorial">

<article class="doc-card">

<h3 id="migration-backup-item-1">Select backup contents</h3>

<p>Identify backup locations from the installation tree or persistent container volumes.</p>

<ol>

<li>Back up PostgreSQL/TimescaleDB and record the matching application and database versions.</li>

<li>Back up the actual user-page directory shown in Screen Files, all referenced assets, and the upload history under SCREEN_FILE_HISTORY_DIR. If the project also uses published releases, back up SCREEN_PUBLISH_ROOT_DIR.</li>

<li>Preserve script sources, dependency manifests and offline packages, plus the config / configs locations actually used, popup templates, media channels, certificates, node identities and project credentials.</li>

<li>Document the roles of data, logs and backups in the deployment. Store keys and licensing material in a controlled backup location.</li>

</ol>

</article>

<article class="doc-card">

<h3 id="migration-backup-item-2">Perform backup and restore</h3>

<p>Use a database-supported consistent backup method. Copying a live database directory does not ensure recoverability.</p>

<ol>

<li>For an installation-wide file backup, schedule maintenance and stop the relevant runtime and data services using the package procedure.</li>

<li>Prepare matching versions at the restore destination, then restore the database, assets and upload history, any published releases in use, scripts and configuration.</li>

<li>After startup, inspect database, Redis, the five services and license, followed by screens, device quality, alarms, trends, scripts and permissions.</li>

</ol>

</article>

<article class="doc-card">

<h3 id="migration-backup-item-3">Move to new hardware or addresses</h3>

<p>Migration affects access endpoints, device identity and collection responsibility.</p>

<ol>

<li>Update Portal and Screen endpoints and certificates, and verify both from clients.</li>

<li>Activate replacement hardware as required by the License page. Recheck site connection identities and capabilities.</li>

<li>Confirm the old node has relinquished collection responsibility for the target PLC before enabling the new node. Verify quality, timestamps and source in Tag Diagnostics.</li>

</ol>

</article>

</div>

</div>