move all backup files to the new backup repository first как исправить
Move all backup files to the new backup repository first как исправить
Ошибка Move all backup files to the new backup repository first в Veeam backup & replication 7
Ошибка Move all backup files to the new backup repository first в Veeam backup & replication 7-01
Всем привет, сегодня хотелось бы рассказать как решается легкая ошибка Move all backup files to the new backup repository first в Veeam backup & replication 7. Напомню что Veeam backup & replication 7 это шикарная программа для резервного копирования виртуальных машин таких вендоров как VMware ESXI и Microsoft Hyper-V, Суть проблемы, есть один логический диск на который складываются бэкапы, место начинает не хватать под текущие задачи и добавляется новый диск,
при попытке изменить в задании место хранения текущего бэкапа, выскакивает ошибка Move all backup files to the new backup repository first в Veeam backup & replication 7.
Ошибка Move all backup files to the new backup repository first в Veeam backup & replication 7
Смысл данной ошибки заключается в том, что мастер настройки говорит вам, что есть другие бэкапы и их бы хорошо перенести в новое место хранения backup. Что мы с вами и сделаем берем просто вырезаем нужную вам папку и вставляем ее в новое место, после чего Backup repository легко получиться заменить и данная ошибка уйдет.
Вот так вот просто решается ошибка Move all backup files to the new backup repository first в Veeam backup & replication 7.
Veeam R&D Forums
Technical discussions about Veeam products and related data center technologies
Change Path of Default Backup Repository
Change Path of Default Backup Repository
Post by rhunt » Dec 13, 2011 7:24 pm 1 person likes this post
Re: Change Path of Default Backup Repository
Post by Gostev » Dec 13, 2011 7:38 pm this post
Re: Change Path of Default Backup Repository
Post by withanh » Dec 22, 2011 4:06 pm this post
After I create a new repository, I don’t see any way to remove or disable the ‘Default Backup Repository’.
Re: Change Path of Default Backup Repository
Post by foggy » Dec 22, 2011 4:15 pm this post
Re: Change Path of Default Backup Repository
Post by withanh » Dec 22, 2011 4:17 pm this post
Re: Change Path of Default Backup Repository
Post by foggy » Dec 22, 2011 4:23 pm this post
Re: Change Path of Default Backup Repository
Post by withanh » Dec 22, 2011 7:14 pm this post
Re: Change Path of Default Backup Repository
Post by smile_dav » Dec 30, 2011 4:39 am this post
Is there any way to hide the default proxy in the GUI or remove it using power shell?
Even though we can work around it by changing the transport mode and disable network mode, we’d prefer to remove it altogether.
Re: Change Path of Default Backup Repository
Post by Sethbartlett » Dec 30, 2011 5:17 am this post
You could also just disable it:
Re: Change Path of Default Backup Repository
Post by withanh » Dec 30, 2011 5:21 am this post
Is there a reason why we shouldn’t delete the default proxy or default repository? I get that you guys say it’s a bad idea, but why is it a bad idea? If I create my own repositories & proxies, then unless there’s a compelling reason to not remove them, I should be able to.
Re: Change Path of Default Backup Repository
Post by Sethbartlett » Dec 30, 2011 5:25 am this post
Re: Change Path of Default Backup Repository
Post by withanh » Dec 30, 2011 5:29 am this post
And I’ll fully acknowledge the disclaimer «Your mileage may vary»
Re: Change Path of Default Backup Repository
Post by Gostev » Dec 30, 2011 8:54 am this post
Re: Change Path of Default Backup Repository
Post by withanh » Dec 30, 2011 2:30 pm this post
Re: Change Path of Default Backup Repository
Post by johnlong » May 12, 2012 3:40 pm 1 person likes this post
Sure would be nice to be able to change the path of the default repository or delete it after creating a new one.
Re: Change Path of Default Backup Repository
Post by Gostev » May 13, 2012 8:17 pm 1 person likes this post
Re: Change Path of Default Backup Repository
Post by johnlong » Jun 12, 2012 11:47 pm this post
Just deleted it from my 6.1 server.
Re: Change Path of Default Backup Repository
Post by withanh » Jun 13, 2012 12:18 am this post
Re: Change Path of Default Backup Repository
Post by bragains » Nov 09, 2015 8:49 pm this post
Re: Change Path of Default Backup Repository
Post by dellock6 » Nov 09, 2015 10:20 pm this post
Luca Dell’Oca
Principal EMEA Cloud Architect @ Veeam Software
Re: Change Path of Default Backup Repository
Post by veremin » Nov 10, 2015 7:28 am this post
Re: Change Path of Default Backup Repository
Post by DeadEyedJacks » Aug 22, 2016 3:12 pm this post
Re: Change Path of Default Backup Repository
Post by veremin » Aug 25, 2016 9:27 am this post
Re: Change Path of Default Backup Repository
Post by NBSINGlenn » Aug 25, 2016 10:15 am this post
Would it be possible to shut down all of the services, backup and restore the disk to another disk then change the drive letters?
We have a lot of end point devices pointed at the default repository and it would be problematic to move them.
I have two repositories like this and if I could just backup the file to another disk and change the drive letter it should accomplish this task.
Re: Change Path of Default Backup Repository
Post by foggy » Aug 25, 2016 11:09 am this post
Re: Change Path of Default Backup Repository
Post by NBSINGlenn » Aug 25, 2016 11:20 am this post
The storage where the default repository is located is going away. So the data has to be migrated, its not just end points but doesn’t Veeam use the default repository for other things?
If I just delete it will there be issues?
Why wouldn’t this work
1: Create a new disk
2: Shut down the Veeam services
3: Backup the data
4: Restore the data to new disk
5: Swap the drive letters on the disks
6: Reboot
If Veeam is only looking at the drive letter then after the reboot it should start using the new disk and be oblivious to the back end change.
What is the process if the drive were to fail? Is there a process to recreate the default repository or is it safe to remove it in the latest version of the software?
How to Move Veeam Backup & Replication Backup Files
| KB ID: | 1729 |
| Product: | Veeam Backup & Replication 11, Veeam Backup & Replication 10a, Veeam Backup & Replication 9.5, Veeam Backup & Replication 9.0, Veeam Backup & Replication 8.0 |
| Published: | 2013-02-08 |
| Last Modified: | 2021-07-01 |
| Languages: | DE | IT | ES |
Purpose
This article provides a method to change the repository where backup files are stored.
For documentation on changing the backup location of Veeam Agent jobs not directly controlled by Veeam Backup & Replication, but targeting a Veeam Backup & Replication server’s repository, refer to vee.am/kb2321
Solution
If you have attempted to manually import the backup, prior to performing the steps outline in this article, you must first «Remove from configuration» any backups that were manually imported. These will be identifiable in the Backups > Disk (Imported) section. They will be listed with the suffix _imported and will have no repository listed in the Repository column.
There are two primary situations and respective methods that this KB article documents.
Below is a summary of both methods.
Method A:
You have physically moved the backup files to new storage and want to map the old jobs to the backup chain in the new location.
Method B:
You are seeding a job or mapping a job to a backup chain in a new location. This method does not require that the job doing the mapping be the same as the job that initially created the restore points.
Method A: Same Job, New Backup location
Veeam R&D Forums
Technical discussions about Veeam products and related data center technologies
Moving To New Repository
Moving To New Repository
Post by FROGGYJ » Feb 02, 2012 6:13 pm this post
Re: Moving To New Repository
Post by Vitaliy S. » Feb 02, 2012 8:18 pm this post
Hello Justin, have you tried this procedure?
[MERGED] Changing Backup Repository to Different Location
Post by habibalby » Mar 01, 2012 7:45 am this post
Hi,
I have configured Backup Jobs on 2 TB Repository and I would like to move some of the VMs to different Repository on the same Server by retaining the existing Backup Jobs to continue writing Full/Incremental to the new Repository.
Re: Moving To New Repository
Post by habibalby » Mar 01, 2012 8:59 am this post
Re: Moving To New Repository
Post by habibalby » Mar 05, 2012 9:33 am this post
I have moved some VMs from 1st Repository to 2nd Repository, I have used the following procedure in order to continue the backup jobs on the new Repository.
I’m sure I have done the above step, but when I re-run the job it should continue backing up to the old file which moved from 1st Repository to the 2nd Repository, in fact it’s not happening. When the job starts, it creates a new Folder of the VM instead of amending the existing one.
It has worked only for one VM and now whenever I move other VMs it doesn’t work at all.
Re: Moving To New Repository
Post by foggy » Mar 05, 2012 9:39 am this post
Re: Moving To New Repository
Post by habibalby » Mar 05, 2012 9:42 am this post
Hi Alex,
Yes, that’s what I did. I can capture a video for you to show the steps I’ve done, even though the job starts creating a new VM Directory.
Re: Moving To New Repository
Post by foggy » Mar 05, 2012 10:22 am this post
Just to be clear that we are talking about the same: are you editing the job specifying the new repository and also mapping it to the existing backup file (blue «Map backup» link on the same wizard step)?
I think you’d better start the case with support to have a webex session with them and demonstrate what you are doing exactly.
Re: Moving To New Repository
Post by habibalby » Mar 05, 2012 10:44 am this post
Hi,
The procedure of moving the backup files to a new repository is as follows:
1. Make sure you have at least one successful full job run after the upgrade to v6, and the *.vbm metadata file has been created (in case this job was created in version 5).
2. Once you have the metadata file created, create a new backup repository, and move all backup files to that repository.
3. Initiate rescan action on your new repository to locate all backup files.
4. Update your backup job according to your new configuration: specify the new repository in the job properties and setup backup mapping to point the job to the backups located in the new repository.
Mapping backup files wasn’t clear to me.
[MERGED] Cannot run backup job after it was moved
Post by Wil » Mar 28, 2012 7:31 pm this post
Hello,
I moved a backup job to another storage device and now i get the below message.
I had manually deleted some vib, and vbk files. Ever since then, the backups were working until i tried to moved them.
Is there any way i can maybe modify a file to update it?
Re: Moving To New Repository
Post by dellock6 » Mar 28, 2012 9:17 pm this post
Wait, you moved a VBK file of a forward incremental chain.
If so, the following incremental will fail for sure. You need to restore the vbk in place or create a new full backup.
Luca Dell’Oca
Principal EMEA Cloud Architect @ Veeam Software
Re: Moving To New Repository
Post by Wil » Mar 28, 2012 9:40 pm this post
Re: Moving To New Repository
Post by dellock6 » Mar 29, 2012 6:48 am this post
Luca Dell’Oca
Principal EMEA Cloud Architect @ Veeam Software
[MERGED] Move backups to new drives on existing server
Post by snowmizer » Apr 17, 2012 8:50 pm this post
I am in the process of migrating all of my VMs to our new storage array. One of the last VMs I have left is my Veeam B&R server. I would like to attach the two new disks I created on my new array to my VM and then copy the backups from the old array disks (drives D, F, and G) to the new disks. Once the files are copied then I will rename the two new disks to D and F and delete the old (D, F and G drives). I know I will probably have to recreate the repositories for the jobs that access the G drive. I’m wondering if this is feasible and is a good idea. I really don’t want to have to re-run the full backups again. Is there a better way to achieve what I’m trying to do?
Re: Moving To New Repository
Post by Vitaliy S. » Apr 17, 2012 10:27 pm this post
Re: Moving To New Repository
Post by chanreasey » May 12, 2012 4:36 am this post
Now I move to other repository is successfully but the problem is when I run job again on the new repository it perform full backup.
Question: After move to the new repository, can I perform incremental backup? How to do this?
Re: Moving To New Repository
Post by Vitaliy S. » May 12, 2012 8:19 am this post
Re: Moving To New Repository
Post by chanreasey » May 16, 2012 4:19 am this post
I do it already but it still can not perform incremental backup. Do you have other solution?
Re: Moving To New Repository
Post by Vitaliy S. » May 16, 2012 8:22 am this post
If you did everything according to the procedure described on the first page of this thread, then your job should be running an incremental run. There are no known issues around this functionality.
I would suggest opening a support ticket with our technical team so that they could take look at your logs and then guide you through the process of moving backup files to a different repository.
Re: Moving To New Repository
Post by chanreasey » May 18, 2012 3:47 am this post
Hi, Many thanks for your support. After I try to map backup job to the backup files in the new repository,now it is work without an error.
Re: Moving To New Repository
Post by cffit » May 29, 2012 8:21 pm this post
Re: Moving To New Repository
Post by cffit » May 29, 2012 8:27 pm this post
[MERGED] After moving amd importing repository starts with f
Post by babarc » Oct 12, 2012 7:12 am this post
Re: Moving To New Repository
Post by foggy » Oct 12, 2012 10:06 am this post
Re: Moving To New Repository
Post by babarc » Oct 12, 2012 10:17 am this post
Re: Moving To New Repository
Post by foggy » Oct 12, 2012 10:35 am this post
Re: Moving To New Repository
Post by habibalby » Oct 12, 2012 11:15 am this post
If you’ve moved the backup files and you rerun the job again and it creates a new full backup instead of continuing to the previous backup configuration, it means the mapping not correct or the CBN along with the vdm files are not moved completely.
Remove backup, move files to anew location, add the new location as repository, scan the new repository, when scan is detected a new backup files will be added, edit the backup job and map the vdm configuration to the new repository location. Start the job and it should continue the backup to the previous backup chain files.
[MERGED] Moving Location of Backup Repository
Post by nmace » Oct 31, 2012 3:09 pm this post
Re: Moving Location of Backup Repository
Post by veremin » Oct 31, 2012 3:56 pm this post
In the way I see it, updating location in the job properties will result in nothing but failing of the existing job, due to the fact, that in this case job will be trying to address to previous restore points, without much success, though.
So, in order to simplify your process of moving job to a new repository I give you complete description of time-proved method for doing it.
1)In Veeam B&R User-interface create a new repository on a new volume.
2)In your OS manually copy/paste previous backups from former repository to the new one.
3)In Veeam B&R User-interface right-click on the new repository and choose “Rescan” option.
4)After having done that, go to the properties of the job you want to move, particularly to the “Storage” settings.
5)Change Backup repository to the new one.
6)Click “Map backup” option, open your new repository by clicking “+”, and choose job you’ve already moved (Note, please, that the name of the job, files of which you’re trying to move to a new location, should be revealed. Otherwise, try to rescan new repository again or redo previous actions).
Hope this helps.
Thanks.
[MERGED] Running Backups offsite
Post by Zeon » Dec 06, 2012 12:54 am this post
Hey guys,
I’m just trying to figure out the correct way to seed an offsite backup server. The situation is we have two sites:
— Site A
— Site B
That are 15km from each other on a 100mbps connection. I am trying to backup a 1.8TB VM which takes around 4 days. However every time I try there is a 2minute outage sometime in those 4 days which cuts the backup off. I tried to make a backup on the local VEEAM server, copy to a USB HDD and take it to Site B however I couldn’t figure out how to use it to seed a new backup job.
Any tips or is this even possible?
Who is online
DISCLAIMER: All feature and release plans are subject to change without notice.
Powered by phpBB® Forum Software © phpBB Limited
Конфигурация репозитория
Репозиторий используется для хранения резервных копий а также файлов с метаданными реплик виртуальных машин. Veeam Backup & Replication поддерживает следующие типы репозиториев:
Если вы планируете использовать папку общего доступа в качестве репозитория, вам необходима учетная запись с доступом уровня Full Control к этой папке.
Конфигурация репозитория выполняется в два этапа:
Чтобы подключить машину:
При подключении сервера под управлением Microsoft Windows имя пользователя должно указываться в формате ДОМЕН\ИМЯПОЛЬЗОВАТЕЛЯ для учетных записей домена или КОМПЬЮТЕР\ИМЯПОЛЬЗОВАТЕЛЯ для учетных записей локальных пользователей.
Чтобы развернуть репозиторий на подключенной машине или папке общего доступа:
Если вы используете папку общего доступа, на шаге Share введите путь к папке в формате UNC и укажите данные учетной записи с правами администратора на эту папку.
