<turbo-stream action="update" target="wiki_card"><template>

<h1>Backup and Restore</h1>
<div class="trix-content"><p>Every Rapidi service automatically creates a daily backup of its configuration. These backups let you roll a service back to any of the last several days if a configuration change causes problems, or if you simply need to compare or recover a previous setup.</p><p>In addition to the automatic daily backup, you can trigger a backup manually at any time, and remove old backups that are no longer needed.</p><blockquote><strong>Access:</strong> This panel is only visible to Rapidi staff - clients do not have access to it themselves. If a client needs a restore (e.g. after an unwanted configuration change on their side), they should contact Rapidi support and request it; a Rapidi team member will then perform the restore on their behalf.</blockquote><p>The <strong>Backup and Restore of service configuration</strong> panel is available on the service configuration page (Rapidi internal access only). It contains two actions and a history table:</p><ul><li><strong>Backup now</strong> - creates an on-demand backup of the current service configuration, in addition to the automatic daily one.</li><li><strong>Remove old Backups now</strong> - clears out older backups according to the retention rules, freeing up space and keeping the list manageable.</li></ul><h2>Reading the backup table</h2><p><br></p><figure class="attachment attachment--content"><table class="table table-bordered"><thead><tr><td>Column</td><td>Description</td></tr></thead><tbody><tr><td>Backup</td><td>The filename of the backup, in the format <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">dbbconfig&lt;serviceID&gt;.&lt;YYYYMMDDHHMMSS&gt;.sql</code>.</td></tr><tr><td>Datetime</td><td>The backup date in <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">YYYYMMDD</code> format, for quick scanning.</td></tr><tr><td>Number of cdbtransfer rows</td><td>The count of transfer configuration rows (<code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">cdbtransfer</code>) captured in that backup.</td></tr><tr><td>Action</td><td>The <strong>Restore</strong> link, used to roll the service back to that specific backup.</td></tr></tbody></table><figcaption class="attachment__caption"></figcaption></figure><p></p><p>Backups are listed newest first, with one automatic backup created per day (normally overnight, based on the timestamp pattern), plus any additional backups you've triggered manually with <strong>Backup now</strong>.</p><h2>Creating a backup on demand</h2><p>Before making a risky configuration change - a bulk update to mappings, a schema change, a big cleanup - click <strong>Backup now</strong>. This captures the current state immediately, independent of the nightly automatic backup, so you have a known-good point to return to regardless of when the change goes wrong.</p><h2>Removing old backups</h2><p>Click <strong>Remove old Backups now</strong> to clean up backups that fall outside the retention window. This is mainly housekeeping — it doesn't affect the ability to restore recent backups, it just trims the list and the underlying storage.</p><h2>Restoring a backup</h2><p>Click <strong>Restore</strong> next to the backup you want to roll back to. This restores the service configuration to exactly the state it was in at that backup's timestamp.</p><h3>What is restored</h3><p>A restore brings back the full service configuration as it existed at backup time, including transfer setups, mappings, and other configuration data captured in the backup.</p><h3>What is <em>not</em> touched</h3><p>Two things are deliberately excluded from backup/restore and are left untouched, regardless of which backup you restore:</p><ul><li><strong>RTIs</strong> (Real-Time Integration settings/state)</li><li><strong>Link storage values</strong></li></ul><p><br>This means a restore will not roll back or overwrite RTI state or link storage values - only the rest of the service configuration is affected. Keep this in mind when troubleshooting: if an issue is related to RTIs or link storage, restoring an older backup will not resolve it, since those areas are unaffected by the restore.</p></div>
</template></turbo-stream>

