The procedure for configuring Replica Seeding in Veeam Backup and Replication 6, is different from the procedure used in Veeam Backup and Replication 5. In Veeam v5, there was the tick box under 'Initial replication' for 'Perform initial replication over this removable storage.' In Veeam v6, the seed is taken from a Veeam backup.
Fig.: VBR5 New Replication Job – Replica Destination & Initial Replication
Step by Step Walkthrough
Part 1: Transporting Seed Data to a DR Site
1.1: Create a backup of the server to be replicated.
Note: If you already have a backup, this is excellent, we can use this.
1.2: Copy the relevant vbm and vbk files to removable media (for example USB hard drive.)
Note I: The vbm file is important as this is the file that Veeam Backup reads from a backup repository to determine the backups that are present (if you have not copied the vbm file it is possible to import the backup from a vbk using the Import Backup function.)
Note II: If using reverse incremental, copying the the vbm and vbk (which holds the latest backup) is enough, the vrb files are not required to be copied also.
Note III: For traditional incrementals, the vib files that proceed the full backup vbk are required to be copied also. If you do not copy the vib files you will see an error like:
Error: Client error: File does not exist. File: [C:\0 Incremental\ExampleBackupIncremental2012-05-27T121234.vib]. Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://Tar2Text]. CHMOD mask: .
1.3: Transport removable media to the DR site, and plug into an available server.
Part 2: Setting up the Seeded Replica
At this stage there are two options:
Option 1: Configure a DR Site Server as a Backup Repository
Option 2: Restore to DR VMware host and Map Replica
2.1: Setting up Replica Seed from DR Site Backup Repository
2.1.1: Add a backup repository on a DR site server.
Note: If you already have a backup repository in the DR site, this is excellent, we can use this.
2.1.2: If not already added, add the backup files to the DR Site repository and rescan the repository so the software can see the backups.
126.96.36.199: Create a New Replication Job ticking the “Low connection bandwidth (enable replica seeding)” box.
188.8.131.52: Follow through the wizard, selecting Virtual Machines, Destination, Job Settings.
184.108.40.206: New Replication Job: Seeding, tick the “Get seed from the following backup repository” box and choose the DR site backup repository
220.127.116.11: Follow through the wizard to completion
2.1.4: Finally, kick of the newly created replica backup job to create the replica from the seed!
2.2: Setting up Replica Seed from a Restore and Map
In this instance, the replica VM is restored from backup – perhaps using a Veeam Backup server located in the DR site – to a DR site host.
Then a replication job is set up similarly to 2.1.3 above, except for at step 18.104.22.168, we tick the “Map replicas to existing VMs” instead, and edit to map the original VM to the replica VM.
when replication begins and when you check job progress screen, 2 servers show under the "VM name" is this normal? one says server name [seed] and the other server is just server to be replicated.ReplyDelete
What if the whole live infrastructure site, including the Veeam server (a vm in my case) itself, is taken out by some disaster ? Can you replicate the Veeam server using itself and how would you seed that to start with ?ReplyDelete
I am actually in the process of doing something similar now. A consultant configured our exchange server at site 1 to replicate via Veeam to site 2, however he configured the job on site 1 Veeam server. This makes no sense because if site 1 experiences a disaster, site 2 veeam server knows nothing about the job. Today, I disabled the replication job at site 1, created a new replication job at site 2 and followed the instructions for the replica mapping in the user guide.
So far it is seems to have mapped the replica and is processing at 14 % right now
Thanks for this reply. Since my post I've replicated the veeam server vm using itself (very nice feature!) without needing to use seeding from physical backup as the DR site is on a fast network and it seems to have gone ok. This should mean that in post disaster the site 2 veeam server vm can takeover as it knows the configuration.Delete