Hello,
I am seeing the following entry on our firewall NIDS "ET INFO Commonly Abused File Sharing Domain (wasabisys .com)" coming from wasabi to our hyper server. My Veeam backup server is copying backup jobs to wasabi so I believe that is what the NIDS is seeing but it seems a little strange that the source is the actual Hyper-V server and not the backup server. Does any one have any thoughts?
Thank you,
Marc
-
maface99
- Novice
- Posts: 3
- Liked: never
- Joined: Nov 03, 2017 8:42 pm
- Full Name: Marc Facella
- Contact:
-
HannesK
- Product Manager
- Posts: 15818
- Liked: 3520 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: NIDS HyperV to wasabi
Hello,
if your backup jobs are targeting Wasabi and no gateway server is set in the Wasabi repository settings, then the traffic goes directly from the Hyper-V on-host proxy to Wasabi (assuming that you don't use off-host proxy).
Best regards
Hannes
if your backup jobs are targeting Wasabi and no gateway server is set in the Wasabi repository settings, then the traffic goes directly from the Hyper-V on-host proxy to Wasabi (assuming that you don't use off-host proxy).
Best regards
Hannes
-
Andreas Neufert
- VP, Product Management
- Posts: 7357
- Liked: 1584 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: NIDS HyperV to wasabi
Hi Marc,
thanks for reaching out here.
In general there are 2 datamover services involved when we write Hyper-V backups to the Object Repositories.
1) A source Data Mover that is in your case the OnHost Proxy
2) A second Data Mover that is the system that interacts with your Wasabi Storage.
In several configurations the first server where a source data mover server is started is used to reach out to the storage directly.
You can define a gateway server to enforce the usage of a specific server for the communication. It is described here: https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
thanks for reaching out here.
In general there are 2 datamover services involved when we write Hyper-V backups to the Object Repositories.
1) A source Data Mover that is in your case the OnHost Proxy
2) A second Data Mover that is the system that interacts with your Wasabi Storage.
In several configurations the first server where a source data mover server is started is used to reach out to the storage directly.
You can define a gateway server to enforce the usage of a specific server for the communication. It is described here: https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
-
maface99
- Novice
- Posts: 3
- Liked: never
- Joined: Nov 03, 2017 8:42 pm
- Full Name: Marc Facella
- Contact:
Re: NIDS HyperV to wasabi
Thanks Andreas and HannesK!
-
Andreas Neufert
- VP, Product Management
- Posts: 7357
- Liked: 1584 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: NIDS HyperV to wasabi
I updated my entry.
Who is online
Users browsing this forum: No registered users and 9 guests