Skip to content

slideRecipes

Connecting…

WORKSPACE

Overview Live dashboard Verification Table maker Version finder Runbooks Mobile console

CONNECTED TOOLS

Reports ↗ Slide Chat ↗ TRMNL display ↗

BUILT WITH THE SLIDE API

Tools for a clearer view of your backups.

API documentation ↗

Connect your Slide account in Recipes. Connect account →

Runbooks

Your runbooks 0

Trash

Execution history is retained.

Execution history

Live recovery consoles

Watch the real machines boot. Select Take control to send mouse and keyboard input; select View only to stop. Service and application verification is your final checkpoint.

Slide Recipes

Delete runbook?

Move this runbook to Trash. You can restore it later. Existing executions continue and their history stays available.

Runbook documents

1POpen 1-pagerOpens in a new tab · scan or photograph to reopen every step↗ PDFOpen full PDFOpens in a new tab · print or save from the viewer↗ DOCXDownload WordEdit the document↓

Include original source passages

Other formats

Markdown JSON with evidence

NEW RUNBOOK

Generate runbook

Client

What should the recovery team know?

Include operational context, not passwords. Missing facts become explicit questions in the runbook.

✦ GPT-6 Astra

DOCUMENT → TASKS

Import runbook

Client Choose document or photoPDF, Word, text, JPG, PNG, WebP, or HEIC · up to 10 MB Take photo

Document text

Photos without a recovery QR, document text, and client system names are sent to OpenAI. Remove passwords and secrets first.

Turning the document into tasks…

✦ GPT-6 Astra

PREPARE EXECUTION

Prepare execution

Your name Execution mode Run rehearsal automaticallyChecks recovery points and simulates VM actions and manual checkpoints. No guest commands run and no live acceptance is certified.

Where should machines recover?

Keeps each selected recovery point when possible; otherwise chooses the newest usable point within the age limit. Review individual targets below.

Test recovery creates real VMs. Review the API plan once, then networking and VM startup run automatically. Verify services and applications in the live consoles at the end.

Recovery network A new network is owned by this run and removed by cleanup. Existing networks are retained. No production bridge, VPN peers or port forwards are copied.

Recovery network settings

Router address / subnet

Allow outbound Internet accessEnabled by default so recovered machines can reach Internet services. Turn off for an offline test.

DHCP is configured automatically outside observed machine addresses. No VPN or inbound port forwards are created.

Start VMs concurrently Start all VMs after checking every recovery point. Leave off to start machines in the runbook order.

VM resources Provider defaults

Leave both blank to use provider defaults, or set both CPU and memory.

CPUs per recovery VMMemory per VM (MB)

Maximum acceptable recovery point age (hours)

Review individual recovery points & locations

Execute the recovery API plan automaticallyCreates real VMs and the selected recovery network. Service and application verification is one final checkpoint. Original document instructions remain available in the runbook.

Source evidence

Release recovery VM

This deletes the recovery VM created by this run and discards changes made inside that VM. An active run will pause.

Type the VM ID to confirm