Hi Everybody,
one of my client facing problem in Veeam Repository. so that they create a new repository and manually copy all data in new repo.
Now they want to start incremental backup from new repo. is it possible ? any body know about this ?
Answer
Incremental Backup
+3Best answer by Mildur
Yes, incremental is possible if you map the backup files from the new location to the old backup job:
Step 8. Map Backup File - User Guide for VMware vSphere (veeam.com)
Shaokat
When you said manually copied, did you mean you created a backup copy job ?
Are you using the same backup server which you used for first repository?
+3When you said manually copied, did you mean you created a backup copy job ?
Are you using the same backup server which you used for first repository?
same server. i add another LUN in VBR server and create new repo. in new repo i copy all data from my old repo and import in my new repo.
Shaokat
+12Yes, incremental is possible if you map the backup files from the new location to the old backup job:
Step 8. Map Backup File - User Guide for VMware vSphere (veeam.com)
Senior Analyst, Product Management @ Veeam Software
+21Yes, incremental is possible if you map the backup files from the new location to the old backup job:
Step 8. Map Backup File - User Guide for VMware vSphere (veeam.com)
This plus after adding the new repo to the VBR server be sure to rescan it to import the backups in to the configuration database and then map them.
Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
+3Yes, incremental is possible if you map the backup files from the new location to the old backup job:
Step 8. Map Backup File - User Guide for VMware vSphere (veeam.com)
This plus after adding the new repo to the VBR server be sure to rescan it to import the backups in to the configuration database and then map them.
Let me try first in my R&D lab.
i think, for this job run successful last incremental backup must be error free.
Shaokat
+12As
Backups are like pizza, I love them. | Linkedin: @marco-fabbri-it
+7Add the new repo in your scale out repo, then evacuate date and seal the old repo
+21Add the new repo in your scale out repo, then evacuate date and seal the old repo
Another good suggestion for sure. Using SOBR to move data just hope not ReFS. 
+3i try it in my lab. it’s work in windows repo. not sure about Linux repo.
First i add new repo, then copy all data from my old repo to new repo.
import new repo data from VBR, change the repo location from backup job. start job again. its working 
Shaokat
+12i try it in my lab. it’s work in windows repo. not sure about Linux repo.
First i add new repo, then copy all data from my old repo to new repo.
import new repo data from VBR, change the repo location from backup job. start job again. its working
Thanks for the feedback.
Mapping is a cool feature.
That will work for all repo types :-)
Senior Analyst, Product Management @ Veeam Software
+12i try it in my lab. it’s work in windows repo. not sure about Linux repo.
First i add new repo, then copy all data from my old repo to new repo.
import new repo data from VBR, change the repo location from backup job. start job again. its working
Thanks for describing your solution!
Good to know: Currently this only works when you copied your backup-files upfront. If not, you would not be able to change target repository. Unless job did not start up to this moment. So if you need to change repository without coping data upfront, you can clone the job and change repo then. Of course, first backup will be a full.
Wolfgang | vnote42.net | @vNote42
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.