- Knowledge Base Listing Page
- How to Move Replica Metadata
How to Move Replica Metadata
| KB ID: | 2165 |
| Product: | Veeam Backup & Replication | 10 | 11 |
| Published: | 2016-09-27 |
| Last Modified: | 2022-02-18 |
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
Purpose
This article documents the procedure for moving replica metadata between repositories. While moving the replica metadata is not required when changing which repository a replication job uses, moving the metadata will eliminate the need for a lengthy "calculating disk digest" task after the repository change.
The steps outlined in this KB Article are to be performed before changing which repository a replication job uses to store metadata. If the replica metadata repository has already been changed and the job has already completed a run, the steps below do not need to be performed.
Solution
All screenshots below are only examples. Job names, repository names, and storage locations are different for every environment.
The process below assumes the new repository where replica metadata will be stored has already been added.
- Disable the Replication Job by right-clicking on it and selecting Disable from the context menu.
- Edit the replication job and identify which repository the replication job currently uses.
- Set the new repository that will be used for replica metadata, and click Finish.
- Identify the actual storage locations that the original and new repository represent by checking the [ Backup Infrastructure > Backup Repositories ] section.
- Navigate to the storage location of the original repository. There will be a folder named "Replicas" within the root of the repository path.
- Within the 'Replicas' folder, identify the folders used for the VMs in the replication job.
The metadata folders have the following nomenclature:- vSphere: <jobname>_<uuid>_<Replica_VM_MOREF>
Note: If the Job Name was changed after it was created, the replica metadata folder might still have the old job name. - Hyper-V: <replica_name> [<replica_VM_GUID>]
To identify the Replica VM's MOREF\GUID, use the following PowerShell script:
- vSphere: <jobname>_<uuid>_<Replica_VM_MOREF>
Get-VBRReplica | ForEach{$_.GetBackupReplicas() | select TargetVmName,TargetVmRef}
- Copy the identified replica metadata folders to the 'Replicas' folder in the new repositories path.
Note: If a 'Replicas' folder does not exist in the root path of the new repository, it must be created manually.
- After the metadata folders have been moved to the new repository, enable the Replication job.
More Information
If the intent is to shift all replication jobs from using one repository to another, the process can be simplified to:
- Disable all replication jobs going to the same repository.
- Edit all replication jobs and configure them to use the new repository.
- Copy the 'Replicas' folder from the root of the original repository path to the root of the new repository path.
- Enable the replication jobs that were disabled in Step 1.
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.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
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
Verify your email to continue your product download
We've sent a verification code to:
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
Start using Veeam:
Download the product
&
Activate the license key
Thank you!
Your feedback has been received and will be reviewed.