New DVLS Server

New DVLS Server

avatar
elaineberenguer

Hi!

We did a Devolution Server + PAM POC and now, after receiving a new trial license for a few more days to present the solution, we're going to install the DVLS in a new server (so we it can be in the definitive server if we do adquire your solution). The question here is... I would like to use the existing database (from our POC) in this new installation. I've already read about DVLS staging, but it's not the case, since we're not to use the current server.
Must I install it using a fresh database and create a new instance pointing to that existing database? Will it work? I want to keep all providers, policies, permissions and everything else I've set up...
Thanks!
Regards,
Elaine Berenguer

All Comments (2)

avatar
Alexandre Bélisle

Hi Elaine,
Yes, that will work, and you will keep everything (providers, policies, permissions, entries, etc.) since it all lives in the database. You don't need a fresh database; just point the new instance to your existing POC database.
The staging article you read is actually the same procedure we use to move DVLS to another server. In short:

  1. On the POC server, export the encryption keys (Devolutions Server Console > your instance > Encryption Keys > Export). This step is critical: without these keys, the data in the database cannot be decrypted.
  2. Take a full backup of the POC database (just in case).
  3. On the new server, install the Devolutions Server Console and create a new instance, ideally with the same DVLS version as your POC.
  4. At the database step, enter your existing POC database information.
  5. When prompted, provide the encryption keys file exported in step 1.
  6. Reinstall the companion components on the new server (Scheduler service for PAM, Devolutions Gateway, etc.) and apply your new trial license.
  7. Stop or decommission the POC instance so that only one instance uses the database.

If the new machine keeps the same name as the POC server, you won't need to update the access URL in Remote Desktop Manager; otherwise, simply update the workspace URL.
Reference: Migrating Devolutions Server to another server
Let us know if you have any questions.
Best regards,

Alex Belisle

avatar
elaineberenguer
Hi Elaine,
Yes, that will work, and you will keep everything (providers, policies, permissions, entries, etc.) since it all lives in the database. You don't need a fresh database; just point the new instance to your existing POC database.
The staging article you read is actually the same procedure we use to move DVLS to another server. In short:
  1. On the POC server, export the encryption keys (Devolutions Server Console > your instance > Encryption Keys > Export). This step is critical: without these keys, the data in the database cannot be decrypted.
  2. Take a full backup of the POC database (just in case).
  3. On the new server, install the Devolutions Server Console and create a new instance, ideally with the same DVLS version as your POC.
  4. At the database step, enter your existing POC database information.
  5. When prompted, provide the encryption keys file exported in step 1.
  6. Reinstall the companion components on the new server (Scheduler service for PAM, Devolutions Gateway, etc.) and apply your new trial license.
  7. Stop or decommission the POC instance so that only one instance uses the database.
If the new machine keeps the same name as the POC server, you won't need to update the access URL in Remote Desktop Manager; otherwise, simply update the workspace URL.
Reference: Migrating Devolutions Server to another server
Let us know if you have any questions.
Best regards,


@Alexandre Bélisle
Hi! Thank you very much for your explanation... I was unsure if just pointing to the 'POC db' would work... :) I will follow your instructions and will let you know! :)
Regards!
Elaine Berenguer

1