There is no supported way to restore a volume backup into a separate isolated service or environment. Backups can only be restored into the same project and environment they were created in. A restore never writes into the live volume. It creates a new volume from the backup and stages a change that swaps your service onto it, and nothing changes until you deploy that staged change. Discarding the staged change leaves your service on its current volume, but the restored copy is then just an unattached volume, and we don't support attaching it to another service to inspect it. Restoring a volume backup also requires the Pro plan.

For newer backups, the volume backups documentation describes the current behavior. The restored volume carries copies of the backups up to and including the one you restored. Newer backups are not deleted. They stay on the previous volume, which remains in your project unmounted from the service.

Backup schedules (daily, weekly, monthly) are configured in the service's Backups tab, and that tab lists each backup by date stamp, so it is where you can confirm scheduled backups are completing.