Restore without overwriting your database
Choose a recovery point, test the copy, then switch when you are ready.
The default is a separate server
A restore creates another database instance. Your original deployment stays unchanged while you test the recovered copy. The restore screen should show any temporary server costs before you confirm.
Pick a full backup or a point in time
Choose a completed full backup, or choose a time inside the available recovery window. The restore worker validates the backup and replays recovery logs as required. Progress stays visible in your workspace.
Check the recovered application data
Connect using the new instance's credentials and allowlist. Check the records and application behavior you expected to recover. Restoring a copy does not automatically move your application to it.
Switch connections deliberately
Plan how to stop writes to the original database and update your application's connection settings. If both copies receive new writes, their data can diverge. Keep the original until you have verified the switch and decided its retention.