#1 Global Leader in Data Resilience

How to Manually Seed a Replica

KB ID: 1760
Product: Veeam Backup & Replication | 10 | 11 | 12 | 12.1 | 12.2
Published: 2013-05-30
Last Modified: 2022-03-04
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Purpose

Under certain circumstances, the seeding function used by a Replication job may not function correctly. If this occurs, an alternate seeding method is to manually pre-create the replica from a backup and then use the mapping function of the Replication job to map to that restored VM.

 

Automated seeding is documented in the user guide:

Solution

Part 1: Restoring the VM to the Destination

  1. Using restore points on the destination side, perform an Entire VM Restore.
  2. On the Restore Mode tab, select "Restore to a new location or with different settings".
  3. On the same tab, click Pick Proxy to Use and select the proxy on the destination side.
  4. On the Host tab, select the target host you want the replica to reside on.
  5. On the Resource Pool tab, select whichever resource pool, if any, you want the replica to use.
  6. On the Datastore tab, select each VM disk and set the Disk Type to "Thin".
  7. On the Folder tab, change the VM name by highlighting the VM and clicking “Name…” at the bottom. It is suggested to add the suffix “_replica”.
  8. On the Network  tab, specify how the new location’s network.
  9. On the Summary tab,  do NOT check "Power on VM after restoring"
  10. Click Finish to start the restore.

Part 2: Mapping to the restored VM

  1. When the restore completes, create/edit the replication job.
  2. On the Name tab, mark the Replica seeding (for low bandwidth DR sites) option.
  3. On the Destination tab, make sure the settings match the present location of the restored VM that will become the replica.
  4. On the Seeding tab, check Map replicas to existing VMs, and configure the mapping:
    • Highlight the production VM
    • Click ‘Edit’
    • Map it to the VM you restored on the TARGET site in Part 1 of this KB.
  5. Once you have mapped the restored VM (now replica) to the original VM, next through until you have completed the rest of the job settings.
  6. Finish configuring the job, and run it.

During the initial run after mapping, the job will need to "Calculate disk digest," which will take some time. The disk digest calculation task can be tracked by double-clicking on the job to open the job's statistics and then clicking on the VM to see the digest task.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.