Restoring Recordings and Importing

Hi Iain,

Thank you for opening this thread.

The recording files are not re-indexed automatically, but there is a button in the Devolutions Server Administration panel to run a re-indexing operation manually.

Indeed, when files are moved around using, for example, automatic backup softwares, until re-indexation occurs, some sessions may appear as having no recording even though the file was restored, and vice versa, some sessions may appear as having a recording when in fact the file is somewhere else and it’s not possible for the Devolutions Gateway to serve it anymore.
It’s typically not a problem since most users are not actively watching old, backed-up recordings unless an incident occurs.
When watching an old recording that was moved somewhere else is required because of an incident, the approach we recommend is to restore the files and run the re-indexing operation. Restoring itself also is typically a manual operation, so most users are not bothered by this.

Is running the operation manually on a per-need basis enough for you?
We could consider adding a job in the Devolutions Server Scheduler module to run periodic re-indexing if that’s a concern.

Best regards,

Hi Benoit,

Ah I think I see it.
So we would restore the file to the GW folder location. Log on to the server select Administration > System Settings > Recording Server and then re-index and select the GW we have restored to.

Would this place the recording under the session it was record for or would it place it at the root level of the vault?
As I assume if the session recording was imported was quite old and the session used was no longer a valid session in the vault it would be viewed at the root level?

Hopefully those questions make sense..

Hi Iain,

So we would restore the file to the GW folder location. Log on to the server select Administration > System Settings > Recording Server and then re-index and select the GW we have restored to.

That is correct!

Would this place the recording under the session it was record for or would it place it at the root level of the vault?
As I assume if the session recording was imported was quite old and the session used was no longer a valid session in the vault it would be viewed at the root level?

Hopefully those questions make sense..

Your questions absolutely make sense!
And actually, they are very timely.

Currently, recordings can only be retrieved and watched from the entry used to start the session initially.
As you pointed out, this may be a problem when the connection entry is deleted afterwards.
It becomes hard to find the recording, and the only way is to access the filesystem manually.

Obviously, this is not great.
Hopefully, we have an important item planned on our roadmap for Devolutions Servior 2025.2 to address this.
The recording would not be placed at the root level of the vault, but instead a separate view would list all the available recordings and other useful information related to privileged sessions.

I’ll link the internal ticket to this thread so we don’t forget to keep you updated once this is available.

Best regards,

Thank you Benoit, and thanks for the information.

Hello Iain,

The feature was implemented in RDM and DVLS v2025.2.

You can now explore sessions and the associated recordings using advanced filters:

There is a similar interface in the Devolutions Server web interface.

You can see more in the What’s New blog post: https://blog.devolutions.net/2025/06/whats-new-in-devolutions-server-20252/#new-privileged-sessions-view

Best regards,