Hi,
Is there any service or process specific only to Veeam Proxies?
I need to set an alert threshold on my monitoring system for all the proxies. I could link it to the servers' names, but I would like to automate it when new proxies are added in the future.
A specific process or service is usually the way to go.
I saw the "VssProxySvc" and "Data Mover" services, but they are also running on other "non-proxy" Veeam servers.
Any idea?
-
- Novice
- Posts: 3
- Liked: never
- Joined: Sep 30, 2024 3:00 am
- Full Name: Saverio Ferracin
- Contact:
-
- Veeam Software
- Posts: 2836
- Liked: 647 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Process or service specific only to Veeam Proxy (v12.2)
Hi Saverio,
I think a combination of the server name + the services running + a few specific paths should be enough. Or if you deploy from a template, just include some file in a unique location and name it appropriately "deployed_veeam_proxy" and parse for that with your monitoring tools.
If you want to use services/processes:
You should have in services:
VeeamDeploySvc
VeeamTransportSvc
For processes:
Veeam.Guest.Interaction.Proxy
VeeamDeploySvc
VeeamTransportSvc
Depending on if you're using VMware or HyperV, you can check for:
VMware: Path C:\Program Files (x86)\Veeam\Backup Transport\x64\vddk_*
HyperV: It is implied any HyperV host added to Veeam is potentially an on-host proxy, so simply include your HyperV hosts added to Veeam
I think a combination of the server name + the services running + a few specific paths should be enough. Or if you deploy from a template, just include some file in a unique location and name it appropriately "deployed_veeam_proxy" and parse for that with your monitoring tools.
If you want to use services/processes:
You should have in services:
VeeamDeploySvc
VeeamTransportSvc
For processes:
Veeam.Guest.Interaction.Proxy
VeeamDeploySvc
VeeamTransportSvc
Depending on if you're using VMware or HyperV, you can check for:
VMware: Path C:\Program Files (x86)\Veeam\Backup Transport\x64\vddk_*
HyperV: It is implied any HyperV host added to Veeam is potentially an on-host proxy, so simply include your HyperV hosts added to Veeam
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Amazon [Bot], Bing [Bot], Google [Bot] and 31 guests