Backup Copy Seeding and Mapping for Cloud Connect

KB ID: 2264
Product: Veeam Backup & Replication | 9.5 | 10 | 11
Veeam Cloud Connect | 9.5 | 10 | 11
Published: 2017-03-28
Last Modified: 2022-06-06
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.

Objective

This article documents how to seed a Backup Copy job for use with a Cloud Repository from a Veeam Cloud Service Provider.

Solution

Backup Copy Mode impact on seeding

Starting with Veeam Backup & Replication v10, there are now two different backup copy modes:

  • Immediate copy
  • Periodic copy

Note: The mode used to create the seed must match the mode used by the final copy job. It is not possible to use the seed of one mode of Backup Copy job for the other mode.

The steps differ slightly from regular (Non-Cloud Connect) backup copy seeding. This KB details how to create a backup copy seed within the software with instructions specific to Cloud Connect. Please contact your provider for their preferred method of receiving seed data. The provider may have their own process for you to use.
 
The Tenant must perform these steps first.

  1. Create a new Backup Copy job. This job will initially be used to generate the seed, but after seeding is complete, this job will map to the seed. Add servers to this job that need to be seeded. This new Backup Copy job must not target the same Repository as the existing Backup job is targeting.

    Ask your Cloud Provider if your Cloud Repository is on a Scale-Out Backup Repository (SOBR). If it is, then the Backup Copy job will have the stipulations listed below. 

    1. There should not be any spaces or unsupported by SOBR special symbols in the Backup Copy Job name. (any spaces needed can be substituted with an underscore "_")

    2. If the SOBR is using Per-Machine, then the repository the seed Backup Copy Job is targeting should also use Per-Machine.

    (Please note this process is different than migrating to a SOBR as described in https://www.veeam.com/kb2236 and migration still requires contacting Veeam support for assistance)

  2. Run the Backup Copy job once to create a full backup file (VBK) and a metadata file (VBM) in the intermediate backup repository, then disable the job.

  3. Perform a ‘Remove from configuration’ on the backup set that was just created under [Backups] > [Disk (Copy)]

  4. Contact your provider for the preferred method of receiving data.

  
The Provider must then perform these steps second.

  1. Upon receiving the tenant’s backup seed data (VBK with VBM metadata file), move these to the tenant’s backup directory. Example: E:\Backups\<TenantName>\<JobName>\*

    If the Cloud Repository is a SOBR, then the requirements listed below must be met.

    1. The VBM file must be copied to the folder path specified above for each of the extents of the SOBR when seeding. Even if the VBK and/or VIBs are not on an extent, the VBM must exist in what would be the job folder for that tenant on each extent.
    2. If Performance Mode is in use on the SOBR, and the Tenant has provided a seed containing a VIB file, that VIB must be placed in the backup folder path on an extent other than the extent where the VBK is placed.

    (Please note this process is different than migrating to a SOBR as described in https://www.veeam.com/kb2236 and migration still requires contacting Veeam support for assistance)

  2. Once data is in place, inform the tenant that data has been transferred to their repository location.

The Tenant must then perform these steps last.

  1. Rescan the cloud repository. Backup files should then appear under [Backups] > [Cloud]  

    Note: If the original backup copy files were encrypted, you will need to input the password for the backup copy set under [Backups] > [Encrypted] before moving forward.

  2. Edit the original backup copy job to change the repository to the Cloud Repository.

  3. Click ‘Map Backup’ and select the Backup Copy chain that is imported.

  4. Enable the Backup Copy job, right-click the job, and select ‘Sync Now.’



NOTE: Please be aware that the VBMs that were placed on an extent without a VBK or VIB may be cleaned up after the Tenant begins running the job after seeding.

Click here to send feedback regarding this KB, or suggest content for a new KB.
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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.