Hi all,
let me briefly explain my use case.
My current Veeam server runs in a server which i want to upgrade : move from to VM to physical, change Raid controller and disks.
To avoid any downtime, i was able to have another physical server available to replace current one, as long as needed : ).
Is it possible to configure my "temporary target server", while current is running, by adding existing proxies and repositories ? with no intention of running any jobs on "target" as long as switch is not done and "to be upgraded box" activities are stopped.
I use Veeam 11, Windows servers and vsphere.
-
- Influencer
- Posts: 10
- Liked: never
- Joined: Jan 11, 2022 9:33 am
- Full Name: Florian Cambot
- Contact:
-
- Product Manager
- Posts: 10945
- Liked: 3000 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Add proxies / repositories already used to prepare a switch
Hi Florian,
Please note that you are running V11, a version with known security vulnerabilities. I strongly recommend updating to our latest release, v12.3.2, which addresses these issues.
Did you mean "move from physical to VM to physical"?
You can always restore your configuration backup to the new virtual backup server. All repositories and proxies will be reconnected during the configuration restore to that virtual server.
Afterward, you can reconfigure and redeploy your physical backup server. Once the physical server is running again, restore a configuration backup from the virtual backup server to reconnect all repositories and proxies to the newly deployed physical server.
It becomes more challenging if your physical backup server has local disks containing backups. In that case, you will need to move those backups elsewhere before reformatting the disks in the physical server.
Please note that moving backups to other repositories is recommended to be done using our backup move functionality, which is FastClone-aware and was introduced in version 12.
Best regards,
Fabian
Please note that you are running V11, a version with known security vulnerabilities. I strongly recommend updating to our latest release, v12.3.2, which addresses these issues.
It seems like something is missing heremove from to VM to physical

You can always restore your configuration backup to the new virtual backup server. All repositories and proxies will be reconnected during the configuration restore to that virtual server.
Afterward, you can reconfigure and redeploy your physical backup server. Once the physical server is running again, restore a configuration backup from the virtual backup server to reconnect all repositories and proxies to the newly deployed physical server.
It becomes more challenging if your physical backup server has local disks containing backups. In that case, you will need to move those backups elsewhere before reformatting the disks in the physical server.
Please note that moving backups to other repositories is recommended to be done using our backup move functionality, which is FastClone-aware and was introduced in version 12.
Best regards,
Fabian
Product Management Analyst @ Veeam Software
-
- Influencer
- Posts: 10
- Liked: never
- Joined: Jan 11, 2022 9:33 am
- Full Name: Florian Cambot
- Contact:
Re: Add proxies / repositories already used to prepare a switch
HI,
oups, did not review properly my message , i meant move from a virtualised server to a physical one.
I'll try to be clearer
.
Current production server is a virtualised one, with it's proxies / repositories. He will be replaced, by a physical server. The "target" physical server is the Esxi host operating the veeam virtual machine, so in order to refit the host with more disk and a better raid Card, i must on a temporary basis move my veeam production server elsewhere.
This elsewhere is a physical server. I want to setup "from scratch" veeam on this server (to have thinsg better sorted out
), but reusing existing proxies / repositories.
My concern is : will i mess my current production server by adding "his" proxies/repositories to another server ? i don't plan to use proxy/repo on new server until i stop operation on current. Just want to save time.
The final step will be to backup config from temp server and restore to "definitive", this part was clear in my mind.
I'd like to move to version 12 but my infra is so old it can't cope with version 12 ...
oups, did not review properly my message , i meant move from a virtualised server to a physical one.
I'll try to be clearer

Current production server is a virtualised one, with it's proxies / repositories. He will be replaced, by a physical server. The "target" physical server is the Esxi host operating the veeam virtual machine, so in order to refit the host with more disk and a better raid Card, i must on a temporary basis move my veeam production server elsewhere.
This elsewhere is a physical server. I want to setup "from scratch" veeam on this server (to have thinsg better sorted out

My concern is : will i mess my current production server by adding "his" proxies/repositories to another server ? i don't plan to use proxy/repo on new server until i stop operation on current. Just want to save time.
The final step will be to backup config from temp server and restore to "definitive", this part was clear in my mind.
I'd like to move to version 12 but my infra is so old it can't cope with version 12 ...
Who is online
Users browsing this forum: Bing [Bot] and 36 guests