What to protect
- JKPanel Pro database.
- Deployment-specific application environment configuration.
- Customer-uploaded or runtime data stored outside reproducible application code.
- Integration configuration required to restore service.
- Web-server and PHP-FPM configuration where appropriate.
- Updater rollback snapshots required by the active software lifecycle.
Database backups
Database backups should be consistent and should be validated rather than assumed to be usable because a dump file exists.
Recovery sequence
- Identify failure boundary
Determine whether the issue affects code, database, configuration or infrastructure.
- Protect evidence
Preserve logs and the failed state where investigation is required.
- Select recovery source
Choose the appropriate known-good backup or updater snapshot.
- Restore
Restore only the components required by the defined recovery procedure.
- Validate
Check application version, PHP, database access, migration state and HTTP health.
- Return to service
Remove maintenance restrictions only after validation succeeds.
Test recovery
A backup strategy is incomplete until restoration has been tested. Periodic recovery tests should confirm that the organisation can actually return the application to an operational state.