This article shows you how to Restore and Replicate managed content.
Managed Files/ Restore (:Confidential Files)
When :Recover is available to your Organization and specifically enabled for your Account, securely-accessed content is stored in the KODiAC (Cloud) Archive for later secure retrieval. This also permits Authorized Users to Restore and Replicate content.
For configuration details, refer to the article, Using :Recover.
Accessing Restore/ Rebuild
Navigate to the Managed Files/ Restore display using the notification panel's context menu item of the same name. When using :Recover, you can Restore content from the Hostlist, Versionlist, or Archivelist Panels (though Replicate is only available from the Archivelist):
General Restore/ Rebuild Operation
Select one (or more) files from any of the UI Panels, then choose Restore. SSProtect will loop through each selected item and attempt to acquire the Latest Qualified Version (see below) from the KODiAC Managed Data Archive and place results in the depicted location. In this example, Open Calls.xlsx will be placed in the C:\SupportFiles folder.
If the target folder does not exist, the file is placed in the Default Folder, sometimes directly and sometimes in a folder structure matching the last-used destination (as with Replicate), depending on the scenario. See below for details.
Success utilizes INFO notification text in Host Debug Logs, while failure is reflected with ERROR entries.
If you are not configured for INFO level logging, check the Log Restore option. This automatically includes INFO Restore entries without affecting your log settings.
* Refer to the section on the Archivelist Specific Paths setting to understand how this affects file placement.
Restoring Versioned Instances
When you Restore a Versioned Instance from the Versionlist 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 Replicate) operations, in all other cases, use the native Filename shown in the UI.
Archive Instances Used for Restore/ Rebuild
For each file, when you Restore from the Hostlist or Archivelist, the latest available Version instance is used. Availability is restricted to items present in the KODiAC Managed Data Archive and also those created by certain Sharing Peers. Details depend on the Operating Mode you use to create the items. This determines the Latest Qualified Version further described at the end of this article.
Date/ Time Information
:Recover retains Versioned instance date/ time information for the resulting file. Times are mapped to the local time zone (though displayed in UTC time). This allows you to retain visibility into secured, managed access over time, despite moving content from one host to another. This also facilitates name collision processing, as described below.
Prompts for File Conflicts
If a target file already exists in local storage, 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 click 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/ Replicate operation, you can review the target file and associated numbered instances to retain items of interest and delete unnecessary content (as all files are Restored in protected 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 ordered the same way.
Replicate vs. Restore
Replicate seeks to re-create a file's native folder structure inside your Default Folder, whereas Restore attempts to utilize an existing (matching/item-native) path. Replicate duplicates the pre-existing file structure which allows you to place files in a, "permanent working location" for further use. As such, Replicate does not, "Activate" the target file, whereas Restore does, placing it in your active Hostlist for further use.
In some cases, Restore cannot recreate the necessary target folder(s), for example when Archive content comes from a D:\ volume that does not exist on the current Host. When operating from the Hostlist or Archivelist panes, and the target folder uses a root drive mapping that does not exist, Restore operates like Replicate, creating the necessary folder structure inside the Default Folder. In the same situation, when performing Restore from the Versionlist, content is placed directly in the Default Folder without the contextual folder structure.
If, however, the target folder shares a volume mapping that does exist though SSProtect cannot create or access it, the operation simply fails. Failure details are listed in the Host Debug Log (even when not specifically logging Restore/ Replicate operations).
Restoring and Replicating w/ Archivelist Specific Paths
The Archivelist checkbox, Specific Paths, affects the attempted target destination of both Restore and Replication operation. When this option is checked, the Archivelist shows the Last Qualified Version's (see below) path used, which may be different if the Version Instance was created on another Host computer with a different Default Folder (by you as the Owner, an Organization Peer, or if using Double Conversion, a Third Party Trust). Subsequent Restore and Replicate operation, using Specific Paths, will use the noted target locations, and as expected, utilize Replicate behavior inside your Default Folder when the target location exists with a root drive mapping not present on your host computer.
Compare this to the Default Folder behavior and the Hostlist: The files and associated paths of the Hostlist reflect, "working data" on the active host computer. This differs from Archive content which can be viewed from any number of different host computers that are configured with your Profile. As such, the Hostlist automatically redirects content to the proper locations (using the Default Folder as the point of indirection for each specific Host) and does not benefit from the use of Specific Paths.
Note however that transitions from the Archivelist to the Versionlist affect the target folder, which reflects the Last Available Version Instance's path as determine by use of the Specific Paths checkbox in the Archivelist pane. For this reason, the Versionlist displays the Specific Paths setting (which does not change as you navigate through various display panes and/ or dismiss and re-display the Managed Files interface) and also the target path at the top of the list of Version Instances.
Remote Deployment and :Expand -rebuild
:Expand supports Remote Profile Deployment with the -deploy command. Use the optional -rebuild switch to initiate an Archive Replicate operation that supplements automated deployment.
Latest Qualified Version
As previously noted, Restore/ Replicate finds the Latest Qualified Version of a file to recall from the KODiAC Managed Data Archive. In some instances, legitimate, stored content is not acquired simply because you will not be able to access it. This is obviously the reality when content is not available (i.e. Size=0) due to the use of Optimized Offloading (purposed or as a result of failure fallback) or Retention Policy removal. It is also the reality in certain circumstances based on other Operating Modes as follows:
Accessible - Double Conversion from an Organization Peer
Accessible - Double Conversion from a Third Party Trust
Accessible - Hybrid Conversion from an Organization Peer
Not Accessible - Hybrid Conversion from a Third Party Trust
Not Accessible - Optimized Offloading (Size=0), from Any User
The Operating Mode is set by the Data Owner, the Account that creates Version 1 of any managed file (creating a new Version Chain). Shared access to managed content follows the pre-existing Conversion method set by the Owner's Operating Mode, only changing when:
- The Data Owner doesn't have enough Quota space for KODiAC Managed Data Archive storage
- The localhost Policy size limit is set lower than the size of the target file.
In these cases, the peer's instance will, "fallback" to Optimized Offloading. Else, the Conversion method changes only when the Data Owner's Account Policy differs from that associated with an accessed instance. Stated another way, the Operating Mode is only affected by the Owner's Operating Mode at the time a new managed instance is created (upon Managed Access Save/ Close).
You can verify the Data Owner of a Version Chain by navigating to the Versionlist and scrolling down to the Version 1 instance to see the associated Username. As of v9.3.2, you should never find an item that holds a Version 1 instance with a Username different from your own. This is by design and specific to the requirement that :Recover Restore/ Replicate functionality limit access to content stored in your KODiAC Managed Data Archive (and thus accruing storage space against your Quota).
NOTE: :xRecovery may scope data differently, depending on the KODiAC instance deployed in your default Server Set. For more information, refer to :xRecovery Section articles.
Refer to the Walkthrough, :Recover w/ Shared Content, for more insight on related terms as well as ordered guidance through examples that show you how to take advantage of SSProtect's data management facilities.
You can also search this site for more information on various topics, or use this link to submit a specific request. You can also send email directly to firstname.lastname@example.org, and our staff will respond to your needs as soon as possible.
This article was updated w/ v10.8.4 of the :Foundation Client