[FEATURE REQUEST] - Global Helper

[CarlosEsteves]

Hello team,

Is there a plan to have an option that we can configure a global helper to be used during healthy check operations?

* not sure if this is already in place *

Thanks

[vnikiforov]

Hello, Carlos,

No global setting today, and where the appliance runs is the reason. It sits on the storage side: for Amazon S3, Azure Blob and Google Cloud we deploy a temporary instance inside that cloud and remove it when the operation finishes, and each one needs its own account and network settings. That only makes sense per repository. With S3 compatible storage you pick a Windows or Linux server from your backup infrastructure instead.

[CarlosEsteves]

Hello,

Back to this topic.

I understand the situation, but a global helper will make things easier as I have 300 storage account and I need today to prepare a helper for each. Massive job.

Any plan to at least think about it ?

Thanks

[HannesK]

Hello,
can you maybe describe the "full scenario"? Maybe using one mount server / gateway server that is placed "correctly" (aka not causing egress costs) might be an alternative?

If you do not configure the helper appliance, Veeam Backup & Replication will use a mount server (for the direct connection mode) or a gateway server (for the gateway server connection mode)

Best regards
Hannes

[CarlosEsteves]

In the company we have 1 storage account for each APP and one job for each storage account, meaning that if I want to enable healtch I need to deploy one helper for each job + each storage account.

If we have a global setup where we can create a global health check helper to be used in any job, will be good

[HannesK]

Hello,
the helper appliance is optional. What do you think about the suggestion I wrote above?

Best regards
Hannes

[CarlosEsteves]

It is optional but if don´t use can have costs, how to solve this ? I did not understand your suggestion, explain again, please

[HannesK]

the cost statement is about avoiding to download the data and having egress costs. if you place the mount server / gateway server "correctly" (in AWS) and avoid egress costs, then it feels like everything is solved.

the only thing that might be relevant is that the gateway / mount server always runs, while the helper is running only "on demand". as you 300 storage accounts, I would assume that some backup components run in AWS already and this is not an issue.