Hello everyone,
don't wanna to create seperate thread but i don't received any answer.
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 ? Only diffrence and pros in such aproach is operation efficiency ?
There is some other advantages and disadvantages ?
Kind regards
-
- Lurker
- Posts: 2
- Liked: never
- Joined: May 29, 2022 9:15 am
- Contact:
-
- Product Manager
- Posts: 14844
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Seperate restore portal pros\cons
Hello,
I would always install something that has direct incoming internet access (like the restore portal) to a separate machine (independent from the product). One reason: security / separation. Other arguments (e.g. complexity) are irrelevant for me over that.
Best regards,
Hannes
I would always install something that has direct incoming internet access (like the restore portal) to a separate machine (independent from the product). One reason: security / separation. Other arguments (e.g. complexity) are irrelevant for me over that.
Best regards,
Hannes
-
- Veeam Software
- Posts: 1495
- Liked: 655 times
- Joined: Jul 17, 2015 6:54 pm
- Full Name: Jorge de la Cruz
- Contact:
Re: Seperate restore portal pros\cons
Exactly what Hannes just mentioned,
Independently if you use some NAT on your routing which I guess you do, and probably VLANs, etc. I would put the REST/Restore Portal on a separate machine, following sizing of course: Moreover, you will have this REST/Restore Portal Server facing the Internet, meaning port 4443, or the one you select when you enable the RESTful API, and you will need to open from this server to the internal VB 365 server port 9194, as described here: So, really, nobody from the outside will be able to reach your Internal VB365 Server, as you are not exposing any port to the Internet, just the 9194 from that DMZ into the specific VB Server.
Let us know if you have any questions.
Independently if you use some NAT on your routing which I guess you do, and probably VLANs, etc. I would put the REST/Restore Portal on a separate machine, following sizing of course: Moreover, you will have this REST/Restore Portal Server facing the Internet, meaning port 4443, or the one you select when you enable the RESTful API, and you will need to open from this server to the internal VB 365 server port 9194, as described here: So, really, nobody from the outside will be able to reach your Internal VB365 Server, as you are not exposing any port to the Internet, just the 9194 from that DMZ into the specific VB Server.
Let us know if you have any questions.
Jorge de la Cruz
Senior Product Manager | Veeam ONE @ Veeam Software
@jorgedlcruz
https://www.jorgedelacruz.es / https://jorgedelacruz.uk
vExpert 2014-2024 / InfluxAce / Grafana Champion
Senior Product Manager | Veeam ONE @ Veeam Software
@jorgedlcruz
https://www.jorgedelacruz.es / https://jorgedelacruz.uk
vExpert 2014-2024 / InfluxAce / Grafana Champion
Who is online
Users browsing this forum: No registered users and 6 guests