software:squirrel:stub_files
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| software:squirrel:stub_files [2025/08/28 16:13] โ [๐ Benefits of Stub Files] support@smikar.com | software:squirrel:stub_files [2026/01/11 10:29] (current) โ support@smikar.com | ||
|---|---|---|---|
| Line 17: | Line 17: | ||
| This approach allows organizations to save on storage while preserving usability for end users. | This approach allows organizations to save on storage while preserving usability for end users. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== ๐ Administrative Guidance ==== | ||
| + | |||
| + | For predictable restore behaviour, SmiKar recommends: | ||
| + | |||
| + | * Avoid moving stubs immediately before restoring files. | ||
| + | * Allow sufficient time for SharePoint changes to be processed before initiating restores. | ||
| + | * Treat stub relocation as an organisational aid, not a guaranteed method of changing restore targets. | ||
| + | * Removing redundant stubs manually if restores are performed before movement processing completes. | ||
| + | |||
| + | If your organisation requires defined operational controls around stub movement, contact SmiKar support for guidance on recommended handling practices. | ||
| ---- | ---- | ||
| Line 51: | Line 64: | ||
| - **๐จ Customisation** | - **๐จ Customisation** | ||
| Stub files can be branded with your organization' | Stub files can be branded with your organization' | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== ๐ Stub File Movement and Location Behaviour ==== | ||
| + | |||
| + | Stub files are standard SharePoint files and can be moved, renamed, and organised by users like any other document. However, because Squirrel processes SharePoint changes asynchronously, | ||
| + | |||
| + | Squirrel monitors SharePoint activity and processes changes such as file moves, renames, and modifications on a scheduled cycle. As a result, updates related to stub movement may take up to 24 hours to be detected and reflected within the Squirrel system. | ||
| + | |||
| + | Key behaviours administrators should be aware of: | ||
| + | |||
| + | * Stub movements are tracked on a best-effort basis and are not guaranteed to be captured in all scenarios. | ||
| + | * Movement updates typically appear within 24 hours, depending on processing windows. | ||
| + | * If a stub is moved and immediately restored before processing completes, the file will restore to its original archived location. | ||
| + | * In this scenario, the moved stub will remain in the new location and may require manual deletion. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== ๐ Moving Stubs Between Sites ==== | ||
| + | |||
| + | If a stub file is moved to a different SharePoint site, Squirrel will attempt to detect this and retarget the stub so that future restores occur in the new location. | ||
| + | |||
| + | Because this relies on SharePoint change processing and site-level behaviours: | ||
| + | |||
| + | * Cross-site stub movement is tracked on a best-effort basis. | ||
| + | * Successful retargeting is not guaranteed. | ||
| + | * In some cases, restored files may return to their original site and path rather than the new stub location. | ||
| + | |||
| + | For environments where strict restore-location control is required, it is recommended that stub files are not moved between sites. | ||
| ---- | ---- | ||
software/squirrel/stub_files.txt ยท Last modified: 2026/01/11 10:29 by support@smikar.com
