Migrate gateway to new server - best practices?

[Anonymous]

Hi, we need to migrate our Enterprise gateway from a development VM to a dedicated new gateway VM. What is the best process for this?

We already have live users using the existing gateway with several reports / dashbaords so need to be as prepared as possible to minimize downtime. Ideally we want to avoid having to republish reports etc.

I believe we do have the recovery key if/when needed.

[v-shex-msft]

HI @Anonymous,

I agree with Eno1978's point of view, re-install and sign in the original gateway is the simply method to migrate gateway.

In addition, you can also install a new gateway in that server, then add original data sources to this gateway.

After these steps, you can choose to use which gateway to refresh.

Regards,

Xiaoxin Sheng

[GWPDX]

Hi Xiaoxin,

Is there any easy way to copy the existing data sources then restore them to the new gateway?

Thanks,

Gary

[asocorro]

I wouldn't classify it as "easy," but using PowerShell you can automate the process:

https://docs.microsoft.com/en-us/rest/api/power-bi/gateways/createdatasource

Cheers,
Adolfo

[Seth_C_Bauer · Accepted solution]

@Anonymous All you should need to do is install a new gateway on the new VM and use the recovery key and the gateway will pick up the load of everything using it in the Service.

[Anonymous]

Thanks for this. Completed this today and it worked as you suggested it would.