Hello,
didn't noticed this before, hoenstly didn't do many fileserver jobs yet...
but now i'm at ah customer with like 30 or 40 indepenedet Fileservers, either phyiscal ones or VMs where only some Shares needs to be in ah backup for ah long term retention that we don't wanna cover with VM Backup retention.
now i added all these Fileservers to the Windows Hosts, transport agent has been installed (and vss components, etc.) ... but i just noticed these windows hosts get automatically also selected now as Guest Interaction Proxys! this is not what i wan't...
i understand i could now manually edit each job and disable the automatic selection and choose only selected Guest Interaction Proxys for the VM Backup, but this is also ah pain when you have many jobs! and its also failure prone, as when you add new proxy you've to edit everything again...
why is this also apparent, because when using gMSA for backup user, not all of my proxys are allowed to retrieve the gMSA (there are also 4 different active directorys in the game)
so overall there would be an option fine, when adding Windows Hosts, because of Fileshare Backup, you can select on per-managed-Server base if this host is used as an guest interaction proxy in the automatic selection! default setting would be just enabled, so someone knows what todo can disable this..
-
- Service Provider
- Posts: 283
- Liked: 41 times
- Joined: Jun 30, 2015 9:13 am
- Full Name: Stephan Lang
- Location: Austria
- Contact:
-
- Product Manager
- Posts: 9793
- Liked: 2586 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Feature Request: decouple "windows host" from Guest Interaction Proxy
Hello Stephan
On the first read, your request makes sense.
Let me think about and then share it with my colleagues.
Newly added managed windows server won't be added automatically to the backup jobs.
Let me see if I have the script ready somewhere.
Best,
Fabian
On the first read, your request makes sense.
Let me think about and then share it with my colleagues.
As a workaround, you can use a script to set the guest interaction proxies.i understand i could now manually edit each job and disable the automatic selection and choose only selected Guest Interaction Proxys for the VM Backup, but this is also ah pain when you have many jobs! and its also failure prone, as when you add new proxy you've to edit everything again...
Newly added managed windows server won't be added automatically to the backup jobs.
Let me see if I have the script ready somewhere.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Service Provider
- Posts: 283
- Liked: 41 times
- Joined: Jun 30, 2015 9:13 am
- Full Name: Stephan Lang
- Location: Austria
- Contact:
Re: Feature Request: decouple "windows host" from Guest Interaction Proxy
I found also another place where this "Proxys" are automatically in then.... In the Storeonce gateway config... You've to also manually take care there...
-
- Service Provider
- Posts: 128
- Liked: 59 times
- Joined: Feb 06, 2018 10:08 am
- Full Name: Steve
- Contact:
Re: Feature Request: decouple "windows host" from Guest Interaction Proxy
I understand this problem well, we had to script our way out of the issue years back, still necessary now.
-
- Service Provider
- Posts: 283
- Liked: 41 times
- Joined: Jun 30, 2015 9:13 am
- Full Name: Stephan Lang
- Location: Austria
- Contact:
Re: Feature Request: decouple "windows host" from Guest Interaction Proxy
i'm just into ah issue now that i can't add certain agents to the backup environment... and i have the bad feeling that the rescan job that is triggered now trying to run on some of these windows hosts now and is failiing because of this! i might have to open ah support case to verify my assumption.... (just run into another problem while generating ah proper log bundle to find out on which server the rescan job really is running... )
Who is online
Users browsing this forum: Paul.Loewenkamp, Semrush [Bot] and 67 guests