Move Object Storage to Proxy Pools

[raftbone]

Hello everyone

We just upgraded our Veeam M365 infrastructure to the new version 8 and I would like to make use of the new proxy pools feature.
However, I do not see any option to "move" an existing Object Storage from one proxy to the newly created proxy pool.

Does anyone have an idea on how to do that?

Many thanks
Rene

[Mildur]

Hi Rene

Currently, it is not possible to change the assigned proxy or proxy pool on an existing repository. However, you can add the original proxy server to a proxy pool, which will also change the configuration of the object storage repository from a single proxy to the newly created proxy pool. If you have deployed new machines for proxy servers, you can also add them to this proxy pool.

It is important to note that you can only add proxies to a pool that do not have local storage repositories attached to them.

Best,
Fabian

_______


From the user guide: https://helpcenter.veeam.com/docs/vbo36 ... y-settings

Editing the Backup proxy or proxy pool value is not possible. You cannot associate the object storage repository with another backup proxy server or backup proxy pool.

[raftbone]

Hi Fabian

Thanks for the hint. In the end, it was exactly what I needed. I have built up to Linux proxies and combined them in a pool. Since I can now also add the "old" Windows proxies, the jobs and Object Storage goes automatically into the proxy.

After that, I was able to put the Windows Proxies into Maintenance mode and delete them. So my jobs are now migrated to the Proxy Pool.

Thanks again

René

[mdiver]

Only downside here is, that it does not work with the default proxy on the VB365 server itself. This one cannot be added to a proxy pool.
There was said to be a way to bring even repositories bound to the default proxy into pools by un-mapping and re-mapping them again.
Is this going to be a supported process? Is it published already?

Thanks.

[raftbone]

That would be of interest for me as well, since one job is running on the default proxy unfortunately...

[Mike Resseler]

No, not yet published. It is possible but it will require a re-sync at this point in time if I am not mistaken. Issue is that this can take a lot of time depending how large your tenant is.

Also, if that job is pointing to a jet DB repository, it won't work as it is not supported.

[mdiver]

Thanks, Mike.
Would be of great interest still. Even if it takes a long time.
The alternative way would be to setup new buckets (e.g. in the same S3 stack) and do a full for everything.
This would also take a long time PLUS double the storage consumption for a while.

[Mike Resseler]

Yeah, I would not consider that an option.

Simply put:
1. Make sure you have the config for the job
2. Remove the job and remove the repository from the proxy
3. Add the repository to a different proxy (a standalone one to start with, which you then migrate into a proxy pool)
4. Recreate the job

That should do the trick but you will get that resync

[pat_ren]

I have a related question, I have 7 proxy's currently (may expand up to 10 now I can pool them) and over the last few years we've put various tweaks to the proxy config files as suggested by Veeam support to resolve issues and fix errors etc.
How will these kind of 'tweaks' be handled if those proxy servers are joined to a pool?

[DaStivi]

It is important to note that you can only add proxies to a pool that do not have local storage repositories attached to them.

hi

can you elaborate this further? whats about the S3 Cache "local storage repos" when they are on a proxy? can't i add these proxys then to a proxy pool? or are gonna get these cache repos obsolete after upgrade to v8's move of the metadata into postgreSQL and vb365 tells me that i can delete these cache repos then? i'vent done the update yet...

[Mildur]

whats about the S3 Cache "local storage repos" when they are on a proxy?

Those are not a thing anymore in V8.
When you upgrade to V8 and run the repository upgrade, that cache is migrated into the PostgreSQL database. No local cache jet database anymore with V8.

can't i add these proxys then to a proxy pool?

You need to upgrade your repositories and proxies before you can use them in V8:
https://helpcenter.veeam.com/docs/vbo36 ... components

Best,
Fabian

[t7MevELx0]

I need to migrate multiple backup repositories from the default backup proxy to the pool. However, reconfiguring them isn’t straightforward because, as an MSP, we don’t store copies of most client repository passwords. While we can select credentials from the list in the Veeam GUI, the API doesn’t allow adding a password hint when creating a repository. This makes it difficult to identify the correct credentials when reconfiguring.

Additionally, some client jobs are highly complex, making manual recreation impractical.

[t7MevELx0]

Just wanted to post back here and let you know that someone else in another post shared the PS Cmdlet with me. It does work! I was able to move everything off of my default backup proxy and to the pool.

Yay