# Diva Restore Content Action

By using the Diva Restore Content Action node within a stream it is possible to trigger a restore object job in Diva.  Standard input parameters are URL with port, client ID (username…) and API key (… and password of the API user).

For proceeding the job an "Object name" must be referred. The "Object category" (a.k.a collection) must be an existing one in the system. The combination of these both values are unique in DIVA and stands for exact identification of the objects. The "Destination" identifies the destination (server or disk such as FTP or CIFS) to which the files should be restored (e.g. for FTP insert "ftp").

"Files path root" identifies the source root path from where the files should be archived from. Further, the "Quality of service" (Default, CacheAndDirect, CacheOnly, DirectAndCache, DirectOnly, NearlineAndDirect, NearlineOnly) can be defined. It controls how requests are cached during processing. The "Priority level" of the job may be configured as welland can be any number between -1 and 100 where -1 stands for unset and is the lowest and default value.

Optionally, "Comments" can be attached to the job in Diva. To visualize the status of the job a "Job start message" and "Job finish message" can be defined and will displayed in the native dashboard in case of a job object.

„Restore options“ identifies additional restore command options. These options typically are prefixed with a dash (similar to command line options). Some options can override parameters for the Source/Destination. Some typical restore options are a follows:

Rename certain files:

* rest\_renaming \<renamerule>

Use certain transcoders:

* tr\_names \<transcoder\_list>

Restored format:

* tr\_restore\_format \<format>

Generate a metadata file on restore:

* rm

<figure><img src="/files/UNp9F8EK3YnZ7WT3BNBJ" alt=""><figcaption><p>Diva Restore Content Action V1 node</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/v4.6.0/helmut4-components/streamdesigner/nodes/actions/third-party/diva/diva-restore-content-action.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.