Understanding remote management using XO
-
We have multiple client sites running HyperV and are looking to migrate to xcp-ng
The client sites all have one production server and one backup server.
I understand these remote client sites can be managed using XO from our office so no need to XO at each client site.
Does this mean that if I migrate a VM or backup a VM from the production server to the backup server the traffic will not be direct between the servers and instead flow:
Production Server (Client site) >> XO (Our office) >> Backup Server (Client site)If this is the case then we will need to run XO locally at the client site or would this be the case for a proxy?
-
@McHenry said in Understanding remote management using XO:
If this is the case then we will need to run XO locally at the client site or would this be the case for a proxy?
Yes, this is the reason that XO Proxy exists so that the traffic can be localized in the remote location.
-
I have a video breaking down how XCP-ng and XO work and at the 14:50 mark in my video here I break down how the XO Proxy works.
-
I am using CE so I do not think XO proxy is available at this time.
-
@McHenry said in Understanding remote management using XO:
I am using CE so I do not think XO proxy is available at this time.
You can setup a proxy yourself using the CE version, just like with everything with the CE version, your milage may vary.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login