AddAdministrativeRestoreJob
AddAdministrativeRestoreJob is used to restore files to the same device or from one device to another. The equivalent options in the dashboard are on the Restore tab for a device.
If you expect to restore often with the API, you may want to set up one or more dedicated restore devices. Create and install these devices, including pushing an automated installation, the same way you would devices you are backing up. Consider using a unique naming scheme for these devices so they are easy to identify. You may want to have a dedicated policy set to assign to these devices so the restored data is not backed up. A dedicated policy set also allows you to configure unique bandwidth settings for these devices. Because the restore only performs basic file name and type searching, you may need to restore all data and then use an eDiscovery tool to search for what you need.
If you want to restore all files to the same place on your network, use the following steps as a guideline.
- Make sure each restore device is domain joined.
- Modify the Data Protection Service on each restore device to use the Local System account.
- Create a folder on the network, giving Domain Computers (all computers) or the specific computers you need to restore full control to the folder.
- Share the folder, giving Domain Computers (all computers) or the specific computers you need to restore full control to the share.
When you restore, you can specify the UNC path for the share. For example, if you specify \\Path\SharedFolder\{UserEmail}\{DateTime}, you will be able to distinguish the restores in the shared location. You can keep this location locked to only certain people have access to the restored files, or if the user who needs access to the restore files also has access to the shared location, the user can access the files immediately after the restored.
If you performing multiple restores and are concerned about bandwidth usage, keep in mind the following.
- QuickCache bandwidth management—Use a QuickCache to manage bandwidth. If you set up your restore devices to use a QuickCache, you can adjust the allowed download bandwidth for peak and off-peak times. This bandwidth is across all devices using that QuickCache.
- Policy set bandwidth management— The default bandwidth limit for a device downloading from the vault is 2 MB/second. If you have multiple devices in the same location without a QuickCache, you may want to decrease the download rate. If you have a single device performing large restorations and are in a location with sufficient connectivity you may wish to increase the download rate. This option is available in the dashboard in Edit Policy Details, Bandwidth Management, Maximum download rate.
- Reuse same QuickCache—If you are restoring to the same location as the original backup, and the restoring device can use the same QuickCache as the backup device, any data that is cached on the QuickCache will be used, improving your time to restore.
See AddAdministrativeRestoreJob for an example PowerShell script.
Signature
ServiceResponse AddAdministrativeRestoreJob (CallingContext callingContext, AddAdministrativeRestoreJobInput input, out AddAdministrativeRestoreJobResult result);
Data structure
The input to AddAdministrativeRestoreJob is an array of AddAdministrativeRestoreJobInput structures which contain the information for the restoration.
[DataContract]
public class AddAdministrativeRestoreJobInput
{
public AddAdministrativeRestoreJobInput ()
{
}
[DataMember]
public Guid CompanyID;
[DataMember]
public string ExtensionCategoryToApplyToFolders;
[DataMember]
public string FileOrFolderNameSearchFilterToApplyToFolders;
[DataMember]
public List<string> FoldersToRestore { get; set;};
[DataMember]
public Guid HostDeviceIds();
[DataMember]
public bool IncludeDeletedFiles;
[DataMember]
public bool IncludeFilesThatShouldHaveBeenDeletedIfDeviceWasNotOnLegalHold;
[DataMember]
public bool IncludeUSMTLoad;
[DataMember]
public string RestoreFileReplacementRules;
[DataMember]
public bool RestoreFirstVersionAfterRestoreTimeIfFileDoesNotYetExist;
[DataMember]
public bool RestoreTheMostRecentFileInstances;
[DataMember]
public DateTime RestoreTimeUtc;
[DataMember]
public bool RestoreToOriginalLocation;
[DataMember]
public string RestoreToThisSpecificLocationPath;
[DataMember]
public Guid SourceDeviceIds();
[DataMember]
public string SpecificFilesToRestore();
[DataMember]
public Guid SubmissionID;
}
You can specify one or more fields in AddAdministrativeRestoreJob.
- CompanyID—Specify the company that contains the device you want to restore.
- ExtensionCategoryToApplyToFolders—Specify a pre-defined file extension filter to limit the returned results. The restore will be performed on items that match the specified filter. The file extensions are identified by the following values.
- All Files
- Pictures
- Presentations
- Documents
- FileOrFolderNameSearchFilterToApplyToFolders—Specify a custom filter to limit the returned results. You can use a name of a file or folder or a file extension. The restore will be performed on items that match the specified filter.
- FoldersToRestore—Specify the folders to restore. An array can be used to specify multiple folders.
- HostDeviceIds—Specify the device where the files should be restored. The device must have OpenText Core Endpoint Backup installed and activated.
- IncludeDeletedFiles—When true, this fields indicates deleted files will be included. When false, deleted files will be excluded.
- IncludeFilesThatShouldHaveBeenDeletedIfDeviceWasNotOnLegalHold—When true, this field indicates deleted files being held in the vault longer than the retention period due to a legal hold will be included. When false, deleted files will be excluded.
- IncludeUSMTLoad—When true, this field indicates the Microsoft User State Migration Tool (USMT) configured in the dashboard will be used to restore user settings. When false, USMT will not be used.
- RestoreFileReplacementRules—Specify how to handle a file that already exists in the specified restoration location, using one of the following values.
- DontRestoreFileIfItExistsInRestorationLocation—If the file already exists in the specified restoration location, do not restore the file.
- Rename—If the file already exists in the specified restoration location, leave the existing file and rename the new file. The new file name will have .restored* inserted between the file name and the extension, where * is an incrementing number if the same restored file name already exists. For example, if you backed up File.doc , the restored file name will be File.restored.doc. If you restored that file again, the second restored file name will be File.restored2.doc. Restoring again would be File.restored3.doc and so on.
- Overwrite—If the file already exists in the specified restoration location, the file will be overwritten by the restored file.
- RestoreFirstVersionAfterRestoreTimeIfFileDoesNotYetExist—When true, this field indicates the next version of a file after the requested point-in-time restore point will be included. For example, if a point-in-time request was for March 17 and the file only existed as of March 29, then the March 29 version will be included with the March 17 files. When false, the next version of a file will be excluded.
- RestoreTheMostRecentFileInstances—When true, this field indicates the most recent version of the files will be included. When false, the files from RestoreTimeUtc will be included.
- RestoreTimeUtc—Specify a point-in-time restore point to use. The included files will be from the backup prior to the specified date and time. This option is not used if RestoreTheMostRecentFileInstances is set to true.
- RestoreToOriginalLocation—When true, this field indicates the files will be restored to the original location. When false, the files will be restored to RestoreToThisSpecificLocationPath.
- RestoreToThisSpecificLocationPath—Specify the path where the files should be restored. You can use UNC paths. You can specify the following variables to help identify the restoration, for example if you are restoring multiple devices to a single device location, like D:\Restores\{UserEmail}\{DeviceName}\. The following variables are available.
- {DeviceID}—This variable will specify the GUID of the device that was protected.
- {DeviceName}—This variable will specify the alias of the device that was protected.
- {UserEmail}—This variable will specify the email address assigned to the device that was protected.
- {DateTime}—This variable will specify the date and time the restoration process was started.
- SourceDeviceIds—Specify the device you are restoring from.
- SpecificFilesToRestore—Specify the files to restore. An array can be used to specify multiple files.
- SubmissionID—Specify a unique GUID for every submission.
Result
The result is the BaseServiceResult described in General API structure.
[DataContract]
public class AddAdministrativeRestoreJobResult : BaseServiceResult
{
public AddAdministrativeRestoreJobResult()
{
}
}