To perform testing on an instance of Devolutions Server without altering the data in production, deploy a test instance based on a copy of the production instance.
Before deploying a Devolutions Server instance, it is recommended to run a few tests to make sure everything is working properly. See Devolutions Server staging checklist for more details.
The following steps describe how to create a test instance hosted on the same machine as the production instance.
Copying a production instance of Devolutions Server to a staging environment can impact privileged accounts if the PAM module is in use. To avoid this, remove the privileged accounts from the staging instance and create new ones specifically for the staging environment.
Perform a full backup of the production database.
Restore the database under a new name.
Export the encryption keys from the production instance of Devolutions Server (if this is not already done).
Create a new instance in the Devolutions Server Console. It is recommended to create the test instance using the same version as the production instance.
In the database step, enter the information related to the database copy created on step 2.
Once prompted for it, provide the encryption key file exported in step 3.From this point on, you can perform the Devolutions Server Console upgrade and update the test instance. The console is designed to support earlier versions of Devolutions Server.
Make a full backup of the staging database when the creation is complete.
Install and test all the additional features, such as the scheduler service, the recording server, and the Devolutions Gateway.
The instructions above can be used to migrate the Devolutions Server instance to a new server.
If desired, you can disconnect the old machine from your domain and rename the new one to match the original machine name. Doing so eliminates the need to update the access URI and the Devolutions Server data source in Remote Desktop Manager.
If you plan to migrate the SQL database to a new server, this should be done after completing the Devolutions Server migration. Once the database has been migrated, update the database configuration via the Devolutions Server Console.
If you plan to move the Devolutions Server instance to a new identity provider, you can also use the authentication migration tool to transfer users and user groups to the new provider seamlessly.
Follow the steps below to migrate an SQL Server from a Devolutions Server to another. This method is useful for those wanting to switch from SQL Express to SQL Server, for example.
-
Perform a full backup of your database.
-
Restore the database under a new name.
Make sure your service accounts are present in the new SQL Server. The DVLS_Owner must still be a DB_Owner on the restored database and have the Alter any login from the securable.
-
In the Devolutions Server Console, under Edit – Database, point the Devolutions Server instance to the new SQL Server and database.
-
In the Advanced credentials section of the same tab, check Apply least permissions on both the Web Application and the Scheduler service. Click on Save.
-
Stop and restart the Devolutions Server instance to apply the changes.
Share your feedback