software:squirrel:restore_process
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| software:squirrel:restore_process [2026/01/10 16:12] – support@smikar.com | software:squirrel:restore_process [2026/01/10 16:29] (current) – support@smikar.com | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== 🧾 Restore | + | ===== 🔄 File Restore |
| - | In the [[https:// | + | In the [[https:// |
| - | Stub files allow users to continue working within SharePoint, OneDrive, or Microsoft Teams as though | + | This page explains how the restore process works when an end user clicks the **Restore** option from a Squirrel stub file, and what happens behind the scenes. |
| ---- | ---- | ||
| - | ==== ⚙️ How Stub Files Work ==== | + | ==== 👤 End User Restore Experience |
| - | When a file is archived using Squirrel: | + | From the end user’s perspective, |
| - | 1. The original | + | * The user locates the stub file in SharePoint, OneDrive, or Microsoft Teams. |
| - | 2. A **stub file** | + | * The user opens the stub file and clicks the **Restore** button. |
| - | 3. This stub retains the original filename, extension, and metadata — but is only a few kilobytes in size. | + | * A Squirrel restore page opens, showing |
| - | 4. When the stub is clicked, the original | + | * Once complete, |
| + | * Open the file directly, or | ||
| + | * Open the file location | ||
| - | This approach allows organizations to save on storage while preserving usability for end users. | + | The restored file then behaves exactly like any normal SharePoint file. |
| + | |||
| + | > ✅ No administrator involvement is required. | ||
| + | > ✅ No special client software is required. | ||
| + | > ✅ The experience is browser-based and fully integrated into SharePoint. | ||
| ---- | ---- | ||
| - | ==== 🌟 Benefits of Stub Files ==== | + | ==== ⚙️ What Happens During Restore |
| - | - **📉 Reduced Storage Usage** | + | When a user triggers a restore from a stub file, Squirrel performs the following operations: |
| - | Significantly lowers SharePoint storage consumption by offloading actual | + | |
| - | - **👤 Transparent to End Users** | + | |
| - | | + | - Squirrel validates the file, tenant, and restore request. |
| + | - The archived file is located in the customer’s Azure Blob Storage. | ||
| + | - The file is **decrypted and decompressed**. | ||
| + | - The file is **streamed back into SharePoint**. | ||
| + | | ||
| + | - The restore is finalized | ||
| - | - **💰 Cost Efficiency** | + | Throughout this process, the user can monitor progress in real time from the restore page. |
| - | Optimize Microsoft 365 storage without compromising accessibility or user experience. | + | |
| ---- | ---- | ||
| - | | **Example Stub File UI** | {{: | + | ==== 🗂️ Versions and Metadata Preservation ==== |
| - | The stub file interface provides administrators with all the metadata needed to restore | + | Squirrel |
| - | - **📄 Filename to Restore** | + | During restore, Squirrel attempts to: |
| - | Displays the full filename and extension (e.g., `pptx_5MB_v2_11877.pptx`) | + | |
| - | - **🌐 SharePoint Site Info** | + | |
| - | | + | |
| + | * Preserve SharePoint metadata. | ||
| + | | ||
| - | - **🔗 Full File URL** | + | The objective of the restore process is to return |
| - | A complete path to the file in SharePoint. Admins can use this to verify | + | |
| - | - **🔄 Restore Link** | + | Because restore operations depend on the state of the source environment |
| - | A clickable link at the bottom | + | ---- |
| - | - **🎨 Customisation** | + | ==== 🔁 End-to-End Restore Lifecycle ==== |
| - | | + | |
| + | - User clicks | ||
| + | - Squirrel validates and initiates the restore job. | ||
| + | | ||
| + | - Data is decrypted | ||
| + | - File content and available versions are restored to SharePoint. | ||
| + | - The stub is removed and replaced with the original file. | ||
| + | - The user is offered options to open the file or its location. | ||
| ---- | ---- | ||
| - | ==== 👩💻 End User Restore Experience | + | ==== 🎯 What Administrators Should Know ==== |
| - | Squirrel makes it easy for end users to restore archived files: | + | For customer administrators, |
| + | |||
| + | * No service desk involvement | ||
| + | * No manual handling of blobs, containers, or exports. | ||
| + | * Files are restored back into their **original SharePoint location**. | ||
| + | * File history, structure, and metadata remain intact. | ||
| + | * End users remain in control of day-to-day retrieval. | ||
| + | |||
| + | This enables large-scale archiving without introducing operational overhead or disrupting business users. | ||
| + | |||
| + | ---- | ||
| - | - Stub files behave like normal files within SharePoint, OneDrive, and Teams. | + | ==== 🌐 Visual Walkthrough ==== |
| - | - When clicked, the file is automatically restored to its original location. | + | |
| - | - A real-time **progress bar** shows the status of the rehydration process. | + | |
| - | - All file versions and metadata are retained during the restore. | + | |
| - | > ✅ Files restored through stub files are seamless — no admin involvement | + | A full visual walkthrough of the end-user restore experience |
| - | Want to see it in action? | + | 👉 [[https:// |
| - | 👉 [[https:// | + | |
| ---- | ---- | ||
| - | Need help customizing your stub file layout | + | If you need assistance with stub configuration, |
software/squirrel/restore_process.1768021955.txt.gz · Last modified: 2026/01/10 16:12 by support@smikar.com
