Forum Discussion
Power BI On Prem Gateway Migration
Hi,
I have a requirement to migrate existing On-Prem gateway to one server to another windows server. Can you please advise if its straight forward to migrate and copy all the data sources ?
- Hi there
First make sure that you can have downtime while the installation happens
What you need to do is the following:
1. Make sure you know the Recovery key password. If you do not know it you can reset it on your current Gateway.
2. Install the Gateway on the New Server.
3. During the installation you will be prompted if you want to recover/migrate from another Gateway.
4. Here you will put in the Recovery Key.
5. Continue with the installation.
Once complete it will now be running on the new gateway and all your data sources will be working.
5 Replies
- GilbertQ
Super User
Hi there
First make sure that you can have downtime while the installation happens
What you need to do is the following:
1. Make sure you know the Recovery key password. If you do not know it you can reset it on your current Gateway.
2. Install the Gateway on the New Server.
3. During the installation you will be prompted if you want to recover/migrate from another Gateway.
4. Here you will put in the Recovery Key.
5. Continue with the installation.
Once complete it will now be running on the new gateway and all your data sources will be working.- GilbertQNo worries, glad to help!
Hi. I'm getting an error on the migration screen attempting to use the migration open during a new installation. The gateways I wish to migrate from are clustered. The entire error message is :
One or more errors occurred.
Response status code does not indicate success: 403 (Forbidden)
Request Id: 9fe74342-f453-429f-9e6c-7315c54a4ca6
Timestamp: 8/25/2022 11:19:13 PM +00:00
at Microsoft.PowerBI.DataMovement.ExternalClient.PowerBIDataMovementClientExtensions.<EnsureSuccessfulDMMSRequest>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.DataMovement.ExternalClient.PowerBIDataMovementClientExtensions.<UpdateClusterGateway>d__43.MoveNext()
Any troubleshooting advice is greatly appreciated.
I reinstalled and it worked the second time. Although, using Powershell and the ClusterID to get the information regarding the name of the gateway, nodes, and machine names...the machine name is correct (the new machine), but the gateway name retained the old name even after I renamed in on the Gateway admin page. Interesting.