-
- Service Provider
- Posts: 85
- Liked: 11 times
- Joined: Jul 17, 2017 12:37 pm
- Contact:
Self Restore portal on Seperate Server
Hi,
Quick one when enabling the self restore portal on a seperate server it does not have an option to create a application ID.
Is it a just a case of
1. enable on vbo main server create application ID
2. disable on main server
3. Copy across application ID to portal server
Quick one when enabling the self restore portal on a seperate server it does not have an option to create a application ID.
Is it a just a case of
1. enable on vbo main server create application ID
2. disable on main server
3. Copy across application ID to portal server
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Self Restore portal on Seperate Server
Hi Badabing
Yes, that's the easiest way to do it.
Remember to export the certificate from the VB365 server and import it to the Restore Portal Server.
Another one is to use a script. Chris has build one and posted it on community.veeam.com.
Yes, that's the easiest way to do it.
Remember to export the certificate from the VB365 server and import it to the Restore Portal Server.
Another one is to use a script. Chris has build one and posted it on community.veeam.com.
Product Management Analyst @ Veeam Software
-
- Veeam Software
- Posts: 118
- Liked: 14 times
- Joined: Nov 05, 2018 8:35 am
- Full Name: Janne Haatainen
- Location: Finland
- Contact:
Re: Self Restore portal on Seperate Server
You can also check this blog post if you want to do it manually, https://finitguy.blogspot.com/2022/05/i ... -m365.html
Systems Engineer | Finland
-
- Service Provider
- Posts: 85
- Liked: 11 times
- Joined: Jul 17, 2017 12:37 pm
- Contact:
Re: Self Restore portal on Seperate Server
Hi,
Thanks for the link
Does Veeam have any doco around best practices in a multi-tenanted environment and the use of a currently active azure tenancy to create the initial appID linkage and this is then applied to other org for restore portal access.
Is best practice to use a new tenancy just for this purpose or is using an existing tenancy fine?
Thanks for the link
Does Veeam have any doco around best practices in a multi-tenanted environment and the use of a currently active azure tenancy to create the initial appID linkage and this is then applied to other org for restore portal access.
Is best practice to use a new tenancy just for this purpose or is using an existing tenancy fine?
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Self Restore portal on Seperate Server
If you have a existing service tenant, I would use that one and not your production tenant.
Just to keep your own tenant and your services apart.
Just to keep your own tenant and your services apart.
Product Management Analyst @ Veeam Software
-
- Lurker
- Posts: 2
- Liked: never
- Joined: May 29, 2022 9:15 am
- Contact:
Re: Self Restore portal on Seperate Server
Hello everyone,
don't wanna to create seperate thread becouse current is the same in some degree.
One question, what is better instal the resotre portal on the home server where repository is stored or is better to seperate resotre portal on other server (anwyay taking into account that these two server anyway is located in same AD). What is better ? Some advantages and disadvantages ?
don't wanna to create seperate thread becouse current is the same in some degree.
One question, what is better instal the resotre portal on the home server where repository is stored or is better to seperate resotre portal on other server (anwyay taking into account that these two server anyway is located in same AD). What is better ? Some advantages and disadvantages ?
Who is online
Users browsing this forum: No registered users and 16 guests