v6 Offsite Replication : Seeding How To

[integrated Systems]

I have a question. And it may have just been a typo.
I am trying to do the same scenario. I have a 3 ESX host setup with 3 Veeam backup servers at my primary site and would like to backup to a DR site. I have deployed another ESX server for the DR site (it is currently still physically located at my primary site so that I can seed it) on this DR site ESX server I have installed a Windows 2008 VM and have created enough disk space on it for my backups. I have added this 2008 VM to my Veeam Backup servers as Backup Proxies and Backup Repositories and I am currently running a backup job to it for seeding. What confused me was line 5 of the following segment. It says to create a replication job. My question is: Won't I need a Veeam license for the CPU Sockets at the DR site if I want to "Replicate" to that site as opposed to just doing "backup" jobs to a Windows VM at the DR site?

Vitaliy S. wrote:Here is the procedure you should follow:

1. Configure a backup job for the VM you want to perform initial seeding for.
2. Create and choose any local repository for the backup files.
3. Once you have backup files created, move them to a DR site and place them on the DR site repository (you should create it beforehand).
4. Scan DR site repository to populate backup files in the backup console.
5. After that just create a replication job with "Low connection bandwidth" checkbox enabled.
6. On the "Seeding" step of the replication job wizard specify DR site repository where you've placed VM backup files.
7. Finish configuration of replication job wizard and start replication job.

Hope this helps!

[foggy]

Mike, VBR licenses source host sockets (where the actual VMs you backup or replicate reside) only. This is covered in the sticky FAQ topic. Thanks.

Q: How the product is licensed?
A: Per physical CPU socket of "source" hypervisor host where processed virtual machines reside. Destination hosts (for replication, and migration jobs) do not need to be licensed.

[integrated Systems]

Thank you very much. I have one more question. In the Replication job setup wizard it is asking me to select a "repository for replica metadata" which is the best selection to make for a DR site replica? The local repository (C drive of my VEEAM backup server) or the remote repository (c drive of the windows VM at the DR site)

Thanks
Mike

[foggy]

The description above at this step is telling you that the backup repository should be located closer to the source.

[integrated Systems]

Yes I did that for the initial seed files but I am wondering after I move the seed to the DR site I have the option of where the "metadata repository" should reside

[foggy]

This comes in right after moving the seed to DR. Placing the metadata in the remote site will slow down the replication process as the source agent would have to pull it over WAN. Depending on the metadata size and the link speed, it could affect the replication time significantly.

[integrated Systems]

Perfect,

Thanks
Mike

[btn003]

[merged]

Hi -

Is there any tutorial on how to setup a Off-Site replication over WAN link?
I could not find any.

I wonder how to setup a proxie server, must Veeam be installed on both main and DR site, must there be a VPN tunnel between sites, etc.

Please advice.

Bjørn.

[joemagjr]

Is there any reason to NOT have the backup repository be a VM in the DR site for seeding purposes or does it even matter?
thanks in advance everyone.

[dellock6]

reading the User Guide at page 47:

The backup repository is deployed closer to the source host – so the source-side agent can easily communicate with the agent hosted on the repository to obtain metadata required for incremental job runs

It does not have to be deployed in the DR site. Here in DR you need a backup proxy.

Luca.

[joemagjr]

Yes, i understand that, I was just trying to stay with the post topic. I am currently seeding so that I can send my VM's to my DR site and create my new replication jobs following vitaliy's simple process below. I have a backup repository running at the production site as a physical box, I also have 2 proxies running as vm's at the production side for my daily vm backups. I have configured a third proxy that will run at the DR site for my replication purposes. I need to create a repository at the DR site to place my backed up vm's for seeding. So my question is can this repository that sits at the DR site be a VM? I have not been able to locate that information in the documentaion.

Vitaliy S. wrote:
Here is the procedure you should follow:

1. Configure a backup job for the VM you want to perform initial seeding for.
2. Create and choose any local repository for the backup files.
3. Once you have backup files created, move them to a DR site and place them on the DR site repository (you should create it beforehand).
4. Scan DR site repository to populate backup files in the backup console.
5. After that just create a replication job with "Low connection bandwidth" checkbox enabled.
6. On the "Seeding" step of the replication job wizard specify DR site repository where you've placed VM backup files.
7. Finish configuration of replication job wizard and start replication job.

Hope this helps!

[dellock6]

Ah, ok, I see.
Uhm, I think it does not matters, I will go for the fastest option, whatever it is. If you have a phyisical windows server at DR, it will be easy to connect the removable storage you bring from Production site, install Veeam agent and do the seeding.

Luca.

[Vitaliy S.]

So my question is can this repository that sits at the DR site be a VM? I have not been able to locate that information in the documentaion.

Yes, for sure.

[joemagjr]

Thanks so much for the reply,

Once I complete my seeding process, can I remove the repository from the DR site, or does it now need to stay as part of the process?

[Vitaliy S.]

Yes, backup files are no longer needed once you've performed initial replication.