A recoverable backup includes the data, files and installation context needed to interpret current reservations. Restoring code alone does not reverse schema changes, provider transactions or privacy erasure.
Prepare and verify a recovery set
Capture the database and relevant files, including exact Free/Pro/theme packages, uploads, custom templates and protected configuration. Inventory booking/item/nightly/service/tax snapshots, payments/refunds, account linkage, policy/invoice history, mail queues, external inventory blocks and source-owned integration state.
Store credentials and database dumps privately. Verify the archive can be listed, the dump is readable and an isolated restore can load the intended schema and representative records. A successful backup command alone is insufficient. Preserve the original packages/checksums and a record of what occurred after the snapshot.
Contain and inspect
- Record UTC time, first symptom, exact source/package/runtime versions, affected routes and current queue/integration state.
- Restrict the affected access or integration while preserving bookings, inventory blocks, ledger and audit evidence. Do not truncate logs or delete blocks to make health indicators green.
- Identify the owning credential or capability before rotating it. A leaked room iCal export token, a provider secret and WordPress salts have different effects.
- Reproduce with synthetic data on an isolated copy that cannot send real mail, charge/refund money, run real OTA sync or contact license services accidentally.
Salt rotation invalidates previously issued anonymous confirmation tokens and can affect other installation-keyed credentials. Coordinate it as an installation-wide security action; privacy erasure or account detachment is not a substitute for token revocation.
Restore with a reconciliation plan
For a code update, replace the same canonical Free folder kimorapro-hotel-booking; Pro remains a separate hotel-booking-pro plugin. Legacy Free identity migration follows its own reviewed maintenance procedure. Do not Delete/uninstall to upgrade.
A database restore can lose new bookings, revive old inventory, replay queues or reintroduce erased personal data. Reconcile post-snapshot reservations, financial/provider outcomes, privacy requests and scheduled work before reopening. Cloned installations need their own license identity and gateway-operation authorization; copied enablement must not authorize live refunds.
Verify before reopening
Check counts, saved totals/taxes, ledger, external blocks and retained/privacy state. Run a minimal controlled Search → Book Now → Pay at hotel/approved sandbox → Confirmation flow, then inspect language routes, mail queues and iCal health where used. Check external provider facts separately from restored local labels.
Keep a redacted incident timeline and use the approved private reporting route. See upgrade and rollback and privacy handling.
