SaaS Backup
Find the cloud data your client needs back.
Explore protection and recovery for Microsoft 365 and Google Workspace, with the exact workload and provider limits in view.
From a backup status to a recovery check.
01 / The problem
A completed job is only a starting point.
The client needs data back. A backup status alone does not establish recoverability.
- Recovery request
- Restore requested
- Point + destination
- Destination to check
- Restore checks
- Result unverified
02 / Connect the work
Define the recovery path.
Review the workload, recovery point, destination and authorized restore scope.
- Recovery request
- Workload scoped
- Point + destination
- Recovery point selected
- Restore checks
- Checks prepared
03 / Illustrative outcome
Keep the checks beside the result.
Record the verification steps and exceptions before accepting the restore.
- Recovery request
- Restore record linked
- Point + destination
- Checks documented
- Restore checks
- Exceptions retained
Connect the recovery point, destination and verification plan before calling a restore usable.
Book a walkthrough Concept example. Check current scope.Start with the recovery decision
What needs to come back?
Pool protected-user coverage across customer tenants with visible snapshot and restore state.
Google Workspace: Gmail, Drive, Shared Drives, Contacts, Calendar, Groups, and supported metadata
Vultr regional object storage
SaaS backup
Searchable protection across SaaS tenantsRestore searchExample scope
Search protected items⌘ K
Microsoft 365Selected clientVersions
Protected document
IndexedVersions and original location available for review.
Mailbox item
ReviewAlternate-location restore path available.
Illustrative workflow · explore the steps · no action is executed
01
Connect and discover
Complete provider consent, validate scopes, and discover supported users, groups, sites, drives, and workloads.
Confirm this step for your release, permissions and environment.02
Protect and index
Run incremental, versioned jobs with throttling, integrity, retention, and searchable metadata.
Confirm this step for your release, permissions and environment.03
Search and restore
Choose the item, version, target, conflict policy, approvals, and evidence path.
Confirm this step for your release, permissions and environment.Find the exact cloud record and restore only what the provider supports.
Run point-in-time, original-target, alternate-target, and export workflows where provider APIs allow.
Inside the workflow
The work this connects.
- Microsoft 365 coverage
- Protect supported Exchange, OneDrive, SharePoint, Teams, Groups, calendar, contact, and related resources.
- Google Workspace coverage
- Protect supported Gmail, Drive, Shared Drive, Calendar, Contacts, Groups, and metadata.
- Incremental versioned snapshots
- Maintain workload-aware cursors, versions, indexes, schedules, and retention state.
- Search and point-in-time recovery
- Find permitted mail, file, calendar, contact, site, team, and group records by version.
- Alternate restore and export
- Restore or export to supported alternate users, folders, sites, teams, or domains with approval.
- Protection evidence
- Report jobs, coverage, failures, throttling, anomaly signals, legal hold, and restore outcomes.
Try one useful scenario
A recovery drill with acceptance evidence
Fictional drill: select a test restore point and an isolated destination. Obtain overwrite authorization, retrieve the data, check a known file and application behavior, then remove temporary access.
Illustrative evaluation scenario, not a recorded product result.What a useful result must show
Record requested and observed RPO/RTO, start/end times, retrieval waits, key custody, failed objects, reviewer and cleanup sign-off. Integrity checks, boot tests and application checks are separate results.
Get the evaluation worksheet →Check the support boundaries
- Files, images, VM and bare-metal recovery
- SaaS content, metadata and excluded objects
- Export, original and alternate restore destinations
- Keys, overwrite approval, region and retrieval timing
No workload-by-mode production matrix is established by this illustration. Protected-user and retained-storage charges can apply; retrieval/egress treatment and archive timing need written confirmation.
Check public evidence and availability →Scope, availability and evaluation details
Provider API coverage, permissions, rate limits, and restore behavior are authoritative.
Modern Google Sites content is not claimed as exportable or restorable where the provider exposes metadata/version evidence only.
The proposed $99 monthly model includes the target product scope for evaluation, unlimited technicians, unlimited customers, and the first 50 managed devices. Final terms require confirmation. See transparent pricing →
Review full environment and integration scope
Microsoft 365 and Google Workspace
Microsoft Graph and Google APIs connect Exchange, OneDrive, SharePoint, Teams, Groups, Gmail, Drive, Shared Drives, Contacts, Calendar, and Sites where provider APIs allow.
Scoped consent and regional storage
OAuth or administrator consent defines provider scope; throttled crawlers, version indexes, restore/export workers, and immutable snapshot ledgers use selected-region Vultr Archival Object Storage.
OAuth/admin consent, provider scopes, backup jobs, retention, legal hold, restore evidence, and reporting remain connected.
Questions, answered
Before you choose your next step.
Which Microsoft 365 workloads are covered?
Dayrook’s target scope includes Exchange, OneDrive, SharePoint, Teams, Groups, calendar, contacts, and related shared resources where the provider APIs make them available.
Which Google Workspace workloads are covered?
Dayrook’s target scope includes Gmail, Drive, Shared Drives, Calendar, Contacts, Groups, and provider-available site metadata.
Can an item be restored somewhere else?
Alternate restore is available where the provider API supports the destination and the user passes the required access and approval checks.
How are API limits handled?
Provider workers use workload-aware throttling, bounded retry, checkpoints, and visible failure state rather than hiding partial results.