The term “granular restore function” refers to the ability to restore data not only as a full system, complete backup set, or entire database, but selectively down to individual items (e.g., specific files, emails, database objects, or application objects). The goal is to fix data loss quickly and precisely without restoring large volumes unnecessarily and without prolonged downtime caused by full restores.
Item-level restoration: Restoring individual files, folders, objects, or records instead of entire systems.
Search & filtering within backups: Making backups searchable by name, metadata, timestamps, sender/recipient (e.g., for emails), or object attributes.
Point-in-time restore (specific timestamp): Restoring a defined state at a specific time, e.g., before a misconfiguration or ransomware incident.
Application-aware restore options: Granular recovery for applications such as email systems, collaboration platforms, databases, directory services, or virtual environments.
Restore of individual mailboxes/items: Restoring single emails, calendar entries, contacts, Teams/channels, SharePoint items, or similar application objects.
Database object restore: Restoring individual tables, schemas, views, stored procedures, or specific records (depending on the product).
Restore to alternative locations/environments: Restoring to a different path, a test environment, or a quarantine folder for validation.
Cross-restore (different target system): Restoring to another server, tenant, or instance where supported.
Permissions and version handling: Restoring including access rights/ACLs and selecting specific file versions.
Preview/validation before restore: Previewing or validating content/metadata to ensure an exact restore.
A user deleted a single project file—IT restores only that file from backup, not the entire file server.
After a phishing incident, a specific email including its attachment is restored from backup without rolling back the whole mailbox.
A database contains faulty changes—only one table is reverted to yesterday’s state (point-in-time).
A SharePoint document was overwritten—the previous version is selected from backup and restored.
After a misconfiguration in an application, only the affected configuration objects are restored instead of reinstalling the entire application.