When :Recover is available to your Organization and specifically enabled for your Account, you can access Archive content as described in this article. For configuration details, refer to the article, Using :Recover.
NOTE: If/ when :Recover is temporarily disabled for your Account, you will not be able to Restore/ Rebuild Archive content.
Accessing Restore/ Rebuild
Navigate to the :Confidential Files display using the notification panel's context menu item of the same name. When using :Recover, you can Restore content from any of the Host, Version, or Archive Panels though Rebuild operation is only available from the Host and Archive Panels:
General Restore/ Rebuild Operation
Choose one (or more) files from the Host, Version, or Archive Panel then Restore/ Rebuild. SSProtect will loop through each selected item and attempt to acquire the latest Version from the (Cloud) Archive, then place results in the native target. In this example, Open Calls.xlsx will be placed in the D:\SupportDocs folder.
If the target folder does not exist, the file is placed in the Overflow Folder, which in this case happens to match the native destination. Success utilizes INFO notification text in Host Debug Logs, while failure is reflected with ERROR entries. Formatting is adjusted such that multi-select operation results in items that can be quickly identified from additional output.
Restoring Versioned Instances
When you Restore a Versioned Instance from the Version Panel, the resulting file reflects the individual Version you selected from the list (you can select more than one here as well). As such, the target filename will be <filename>-vx.<ext>, where x reflects the Version instance for each selected item.
Restore and Rebuild operations in all other cases use the native Filename as shown in UI displays.
Archive Instances Used for Restore/ Rebuild
For each file, the latest instance you created with a save/ close operation gets used for all associated Restore and Rebuild operations. Future versions will utilize Third Party Trust policy to determine if externally modified content can be acquired, though at present this is not permitted (and only Privileged Users can enumerate externally created Version instances in the Version Panel).
Note that the Restore/ Rebuild candidate is the same instance reflected in Archive Panel list enumeration, since this carries Version and Size information associated with the same scoped item.
Date/ Time Information
:Recover retains Versioned instance date/ time information, applied to recovered content once an item is restored or rebuilt (using the host-local timezone). This allows you to retain visibility into secured, managed access over time, despite moving content from one host to another using SSProtect. This also facilitates name collision processing, as described below.
Prompts for File Conflicts
If a target file already exists in local storage, unless you have checked Auto Repl, you will be prompted to Replace the target file or Skip the given instance:
Choose Apply to remaining cases if you wish to use the same answer for any future conflict (in the present multi-select operation), then Replace or Skip.
Replacing Existing Files
Once SSProtect has been instructed to overwrite existing content, the pending Archive instance is compared with the existing instance to determine which of the two is more recent. The older file is renamed to <filename>.<ext>.000, and the newer file replaces the target <filename>.<ext>. If/ when <filename>.<ext>.000 exists, SSProtect increments the counter until an appropriate target filename is found.
As such, after a multi-select Restore/ Rebuild operation, you can review the target file and associated numbered instances to retain items of interest and delete unnecessary content (as all files are in ciphertext format).
NOTE: Though the final target file will not be different, multi-select specifics change the order in which content is processed. This is reflected by the sorting you use and resulting multi-select scope. Operation begins with the top item in the selected set, then proceeds downward through the selection set, in order. If you change the sort order and choose the same set of files, then repeat the operation (with a clean set of target folders), interim file content that uses numbered extensions (noted above) will not be the same.
Rebuild vs. Restore
Rebuild and Restore differ only in that Rebuild seeks to re-create the native folder structure, whereas Restore attempts to utilize an existing (matching) folder structure. In some cases, however, Rebuild cannot recreate the necessary target folders, for example when Archive content comes from a D:\ volume that does not exist on the current Host. In this case, Rebuild recreates the folder structure inside the Overflow Folder such that you can then move entire portions of the resulting structure to localhost destinations for continued operation.
Host Rebuild vs. Archive Rebuild
Host Rebuild is purposed to reconstruct content when it is moved, deleted, or sabotaged on a large scale. Host Rebuild is in fact only available when target Host List files do not exist (else the button is gray). Restore is more often suitable given the folder structure most often already exists, at least once a Profile is created and operation commences.
As such, Host Rebuild does not attempt to recreate the target folder structure inside the Overflow Folder.
Archive Rebuild, by contrast, is more closely aligned with :Recover data scope, over the lifetime of an Account (or Profile). As such, Archive Rebuild will always attempt to recreate the folder structure in the Overflow Folder when the native target cannot be created.
Remote Deployment and :Expand -rebuild
:Expand supports Remote Profile Deployment with the -deploy command. Use the optional -rebuild switch to initiate an Archive Rebuild operation that supplements automated deployment.
Refer to the article, Remote Profile Deployment, for more information.
For More Information
For information regarding product features and content, consult the Document Index, or send email with specific questions to firstname.lastname@example.org.
This article was updated w/ v7.1.3 of the :Foundation Client