Entity Relationships 🔗
Visualize how Slide entities relate to each other. Understanding these relationships is key to building effective tools and integrations.
Slide Cloud
Orchestrates everything, stores cloud replicas
Slide Box
Has many Protected Systems (via paired Agents)
Stores many Snapshots locally
Generates Alerts for device-level issues
Can host VMs (virtualizations) for recovery
Slide Agent
Installed on one Protected System
Creates Snapshots on schedule
Has Retention Policy (determines snapshot lifecycle)
Generates Alerts for backup failures, connectivity
Has encryption passphrase (Slide-managed or user-managed)
Snapshot
Point-in-time image of protected system
Can exist locally (Box) and/or in Cloud
Has retention tags (intra-daily, daily, weekly, monthly...)
Has verification status (integrity check result)
⭐ HAS SCREENSHOT (visual verification of bootable backup)
Enables: Virtualization, File Restore, Image Export
Key Relationship Rules 📋
- Agent → Box: Many-to-one. Multiple Agents pair with a single Box via pairing codes
- Agent → Snapshots: One-to-many. Each Agent creates multiple snapshots over time
- Snapshot → Locations: Snapshots exist in two locations (Box local storage AND Cloud)
- Box → Cloud: One-to-one replication. Each Box syncs all successful backups to Cloud
- Snapshot → Restores: One snapshot can spawn multiple restore operations
Entity Quick Reference 📊
| Entity | Contains | Belongs To | Creates/Manages |
|---|---|---|---|
| Slide Cloud | All Boxes, retention policies | — | Coordination, DR |
| Slide Box | Snapshots, VMs | Slide Cloud | Local storage, virtualization |
| Slide Agent | Configuration, history | Slide Box (via pairing) | Snapshots |
| Snapshot | Backup data, metadata, ⭐ screenshot | Agent + Box + Cloud | Restore operations |
| Virtualization | Running VM | Snapshot | Recovery access |