#1 Global Leader in Data Resilience

Backup Copy Seeding and Mapping for Cloud Connect

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

Objective

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

Solution

Critical Notes
  • Starting with Veeam Backup & Replication v10, there are now two different backup copy modes: Immediate copy and Periodic copy. The mode used to create the seed must match the mode used by the final copy job. It is impossible to use one mode's seed to seed the other mode.
  • This seeding process is different from the process for migrating to a SOBR. SOBR migration for service providers requires contacting Veeam support for assistance.
  • As documented in the Veeam Cloud Connect User Guide:

    The Service Provider (SP) should not import tenant backups in the SP Veeam backup console to restore data from these backups. To perform such data restore tasks, the SP must deploy a separate backup server in its backup infrastructure. The SP can use its existing Veeam Cloud Connect license on this backup server.
This seed process 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.

Part 1: Tenant Generates Backup Copy Seed

  1. Tenants must gather the following details from their service provider:
    1. Is the tenant's Cloud Repository stored on a Scale-Out Backup Repository?

      If so, the Backup Copy Seed job name must not contain spaces or unsupported by SOBR special symbols.
      As an alternate to spaces using underscores ( _ ).
    2. Is the underlying Service Provider side repository where the tenant's Cloud Repository is based using Per-Machine Backup Files?

      If so, the tenant's Backup Copy seed job must target a repository on the tenant's site that is also configured to use Per-Machine Backup Files.
  2. Create a new Backup Copy job containing the servers the job will send to the Cloud Repository.
    This job will be used to generate the seed, and after seeding is complete, this job will map to the seed.
  3. Run the Backup Copy job once to create a single full backup file (VBK) and a metadata file (VBM) in the on-prem backup repository.
  4. Disable the Backup Copy job.
  5. Under the Backups > Disk (Copy) section, perform Remove from configuration on the backup copy seed that was created to detach the files from the job.
  6. Contact your Service Provider and arrange for the seed to be sent to them.

Part 2: Service Provider Places Seed in Storage

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

    If the tenant's Cloud Repository is backed by a Scale-Out Backup Repository (SOBR), review these additional steps that must be performed.
    1. Place the VBM file from the seed into the same <TenantName>\<JobName>\ path on each Performance Tier extent of the SOBR.
      Even if the VBK file is not actually stored on an extent, the VBM must be present in the path that would be the tenant's job folder.
      These extra VBM files may automatically be cleaned up after the Tenant begins running the job, but they must be present initially.
    2. If the SOBR is using Performance Mode, 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.
  2. Once seed data is in place, inform the tenant to proceed with the next steps.

Part 3: Tenant Rescans and Maps Backup Files

  1. The tenant rescans their Cloud Repository, and the seeded Backup files should appear under [Backups] > [Cloud].

    Note: If the backup copy seed files were encrypted, they will be located under [Backups] > [Encrypted] and must be decrypted before proceeding.
  2. Edit the Backup Copy job used to create the seed, switch to the Target tab, select the Cloud Repository, and map to the backup files.
  3. Right-click on the Backup Copy job, and select Sync now or Start (depending on the job type).
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.