Our ESE Archiving functionality manages the life cycle of stub files. It keeps track of which files it stubs, and informs the Storage Platform. This ensures that stub data on the Platform will not be removed. ESE will by default rehydrate any files that do not meet the requirements for Archiving.
If you need to recover archived data after a ransomware attack or other issue and you prefer to restore the files as stubs, you can follow the steps below. This will prevent ESE from rehydrating the files instantly and potentially overfilling the restore target. However, it is only possible to do this successfully if the target machine is using the same ESE account with Archiving enabled, and even then there is a risk of data loss. If file size is the reason why rehydration is being avoided, we recommend rehydrating in phases instead of everything at once. This is safer than restoring as stubs.
Restoring as stubs is an advanced functionality and should only be used by users with a sound understanding of stubs and how they are managed. Incorrect use of this setting could result in the referenced data being removed from the Storage Platform.
To restore as stubs
From the command-line, run an InstantData script containing the minimum parameters of Server, Account, Key, Path, and Target as well as the DownloadOnDemandOnly
parameter, set to "True", separated by spaces. Please note that the path (including both drive letter and folders) is case sensitive and the path should not have a backslash (\) at the end.
For example:
InstantDataPermanent.exe Server=previewsp.redstor.com Account=collection\group\myaccount Key=mysecret
Backup=20160117180105 Path="C:\Database Files" Target="C:\Restore" DownloadOnDemandOnly="True"
The addition of this parameter means that only stub files will be created on the target and the data will only be downloaded as needed.
Note: It is possible to force Archiving by changing the last accessed date of files, but the process requires the use of PowerShell (example here) or a third-party app and should be approached with caution.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article