> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.8.0/helmut4-components/streamdesigner/nodes/actions/third-party/telestream/diva/diva-restore-content-action.md). # 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. This node is using SOAP. 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 the following - please have a look at this DIVA document for further informations: * Rename certain files: * rest\_renaming \ * Use certain transcoders: * tr\_names \ * Restored format: * tr\_restore\_format \ * Generate a metadata file on restore: * rest\_metdadata

Diva Restore Content Action V1 node

Following the example values from [Diva](/helmut4-releases/v4.8.0/helmut4-components/streamdesigner/nodes/actions/third-party/telestream/diva.md)\ \- Object category: PROJ PARK HELMUT\ \- Destination: EDITSHARE\_RESTORE --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.helmut.de/helmut4-releases/v4.8.0/helmut4-components/streamdesigner/nodes/actions/third-party/telestream/diva/diva-restore-content-action.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.