Hello
I was reading this forum post
microsoft-hyper-v-f25/installing-second ... 4809c6fa43
We have a primary ESXI that is hosting VM, we need to have another Veeam instance on another server which we already have incase of the primary server fails.
So I believe I have options?
Veeam Availability Orchestrator
As stated in the post "create replication jobs there and do a so-called "pull" replication (unlike "push" replication which is done by the source-side instance)"
Is there a Veeam Article on how to do the pull replication?
If there is more advice and suggestions I like to hear your opinon
Thank you
-
- Novice
- Posts: 6
- Liked: never
- Joined: Apr 22, 2022 2:01 am
- Contact:
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: DR Second Veeam Instance
Hi Kyoshi
Veeam Availability Orchestrator won't be supported with standalone ESXI hosts. vCenter is required. But you don't need it.
Pull replication just means that the DR site initiates and manages your replication task.
This allows you to failover the VMs without first powering on a second VBR server.
What you can do if you want to have the second VBR server running the replication jobs:
1. Deploy a second VBR server in your DR site
2. Deploy Veeam enterprise manager for central license management in your DR site
3. Use the VBR server in your primary site to manage the backup jobs.
4. Use the VBR server in your secondary site to manage the replica jobs.
The enterprise manager will allow you to use the same license on both VBR servers for backup and replica jobs.
Just make sure, that backup and replica jobs do not overlap. One of the jobs could fail if that happens.
If you want to have a single VBR server managing backup and replica jobs, you can also deploy only the VBR server in your DR site.
This DR VBR server will be able to manage proxy and repository server on your primary site as well. In this case you don't have to worry about overlapping jobs.
Thanks
Fabian
Veeam Availability Orchestrator won't be supported with standalone ESXI hosts. vCenter is required. But you don't need it.
Pull replication just means that the DR site initiates and manages your replication task.
This allows you to failover the VMs without first powering on a second VBR server.
What you can do if you want to have the second VBR server running the replication jobs:
1. Deploy a second VBR server in your DR site
2. Deploy Veeam enterprise manager for central license management in your DR site
3. Use the VBR server in your primary site to manage the backup jobs.
4. Use the VBR server in your secondary site to manage the replica jobs.
The enterprise manager will allow you to use the same license on both VBR servers for backup and replica jobs.
Just make sure, that backup and replica jobs do not overlap. One of the jobs could fail if that happens.
If you want to have a single VBR server managing backup and replica jobs, you can also deploy only the VBR server in your DR site.
This DR VBR server will be able to manage proxy and repository server on your primary site as well. In this case you don't have to worry about overlapping jobs.
Thanks
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 19 guests