Restoring a database snapshot with JetBackup

Export the current database and record the application version. Choose a recovery point matching the required code and data state. Put a write-heavy site into a suitable maintenance state and plan how newer transactions will be preserved.

1. Open JetBackup and choose the Databases area. Select the correct full database name and recovery timestamp.
2. Review whether the associated database-user item also needs restoration. Database data and database users are separate backup items, so selecting one does not automatically prove the other is included.
3. Choose Restore and inspect the selected-items summary. Remove unrelated databases or account components.
4. Read the restore conditions and options carefully, then queue the selected restoration and wait for a completed result.
5. Check application connectivity, key records and recent data expectations before allowing new writes again.

Imagine a store has a database snapshot from 08:00. A change at 11:00 breaks a setting, but orders arrived between 08:00 and 11:00. Restoring the entire 08:00 database can remove those newer orders from the store even though the broken setting is recovered.

1. Preserve the current database and identify the orders or other records created after 08:00.
2. Agree whether a focused application repair can recover the setting while retaining current data, or whether a broader restore and reconciliation is required.
3. If restoration is needed, pause new writes through the appropriate maintenance process and agree the data-preservation procedure before confirming it.
4. After recovery, verify both the repaired function and the expected recent orders before reopening normal processing.

The times are illustrative. A backup-tool merge option should not be treated as a substitute for an application-aware order reconciliation plan.

The application should use the intended recovered database with the correct user grants. Verify data dates and business records explicitly, including anything created since the snapshot.

If connectivity fails after restoring users, compare the application password and grants with the restored state. If the wrong snapshot was chosen, stop writes and use the pre-restore export or support-assisted recovery.

Do not assume so. Backup-level merge behaviour is not application-aware reconciliation. Discuss the exact database restore semantics and transaction-preservation plan before restoring an active store.

• Restoring one file with JetBackup when it is included
• Exporting a recoverable database backup in phpMyAdmin
• Diagnosing database access denied after a hosting migration
• Recovering a mailbox snapshot with JetBackup

• JetBackup: Restoreanddownload