Move all backup files to the new backup repository first как исправить

JamesNT

Service Provider
Posts: 63
Liked: 8 times
Joined: Feb 15, 2016 2:28 pm
Full Name: James Summerlin
Contact:

Move all backup files to the new backup repository first

We have a client we were using a QNap box for onsite backup. The QNap was taken out by a recent thunderstorm because someone thought it was a good idea not to put the QNap on UPS like everything else in the office was (hence why everything else survived).

Anyway, we put a new device in and need to point the onsite backups to the new device. Create a new repository, try to change backup job to new respository and we get this error:

MOVE ALL BACKUP FILES TO THE NEW BACKUP REPOSITORY FIRST.

Yes, I’d be happy to, except the original backup files no longer exist. So, now I have to create a new backup job and try to get all the settings correct again.

It would be nice to have the option to change repositories on a backup job and be given the option to START OVER or something rather than having to create a whole new job.

James




Paxx

Novice
Posts: 6
Liked: never
Joined: Oct 18, 2019 3:50 pm
Contact:

Re: Move all backup files to the new backup repository first

Post

by Paxx » Oct 18, 2019 4:04 pm

veremin wrote: ↑Aug 21, 2019 6:31 pm
Then, remove obsolete backups from configuration, right-click on them -> Remove from configuration. After that point existing jobs to new repository. Thanks!

If your destination is a Veeam Cloud repository, the option «Remove from configuration» isn’t available and you can only «Delete from disk».
In this case the solution above can’t be applied.
Do you have other another solution for this scenario?




Paxx

Novice
Posts: 6
Liked: never
Joined: Oct 18, 2019 3:50 pm
Contact:

Re: Move all backup files to the new backup repository first

Post

by Paxx » Oct 18, 2019 5:12 pm

I have opened a case they give me a solution, it looks like some brilliant mind in Veeam have decided to hide this option (and not the «Delete from disk») so you can see only holding the «ctrl» button:

1.Disable Backup.

2. Navigate to Backups>Cloud and select the backup set in question

3. HOLD down CTRL button on your keyboard and right click on the backup set at the same time (DO NOT let GO off ctrl) and Remove from Configuration => This will remove the records of this backup from the list.

After that, you will be able to change the repository for the backup Job to the new Datastore.


foggy

Veeam Software
Posts: 20967
Liked: 2087 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Move all backup files to the new backup repository first

Post

by foggy » Oct 21, 2019 11:33 am

This functionality was hidden due to possible issues it might cause, but still can be used with care in cases like yours. Thanks for updating the thread with the resolution!


Paxx

Novice
Posts: 6
Liked: never
Joined: Oct 18, 2019 3:50 pm
Contact:

Re: Move all backup files to the new backup repository first

Post

by Paxx » Oct 21, 2019 12:50 pm

Imagine the issue that can generate the «Delete from disk» that is still there…
Anyway, I don’t see any problem if someone put a couple more of confirmation windows if you want be sure the Admin is aware of what he is doing, instead of hide the option and generate this kind of waste of time (two hour for the internet search + one hour of case management).


foggy

Veeam Software
Posts: 20967
Liked: 2087 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Move all backup files to the new backup repository first

Post

by foggy » Oct 21, 2019 1:29 pm

Imagine the issue that can generate the «Delete from disk» that is still there…

This would be a clear consequence of the user action. While the issues with the ‘Remove from configuration’ option were database-related and sort of unexpected. We’re going to address those though to bring the option back.


Anguel

Expert
Posts: 184
Liked: 18 times
Joined: Apr 16, 2015 9:01 am
Location: Germany / Bulgaria
Contact:

Re: Move all backup files to the new backup repository first

Post

by Anguel » Nov 18, 2022 12:57 pm

Today I also wasted time trying to point a job to a new repo after having deleted the old backups via «Delete from disk» already.
Veeam just kept telling me to «MOVE ALL BACKUP FILES TO THE NEW BACKUP REPOSITORY FIRST» — but well — the backups were already deleted and gone.
Obviously, I also did not see any «remove backups from configuration» option as there were no more backups under «Disk (Copy)».
The trick I found that solved it for me was to rerun the job to the old repo in order to make it start creating some new backups just until I start seeing those new backups under «Disk (Copy)».
Then I just canceled the job but now the option «remove backups from configuration» appeared (as there were some backups) an I could finally «detach» the job from the old repo and just point it to the new one.


Who is online

Users browsing this forum: Baidu [Spider], Google [Bot] and 7 guests

Обновлено 21.07.2015

Ошибка 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-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

Ошибка 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.

Материал сайта pyatilistnik.org

Июл 21, 2015 17:33

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.  Please refer to vee.am/kb2321

                                                    

Solution

                                    

Important! If you have attempted to manually import the backup files using the Import button in the ribbon prior to performing the steps below you must first «Remove from configuration» any backups that were manually imported. These will 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.

User-added image


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 you want to map 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 which created the restore points initially.


Method A: Same Job, New Backup location

  1. In [Backup Infrastructure] > [Backup Repositories], create a new repository for the new location where backup files will be located.
  2. Manually move the backup files to the new repository path. You must include the metadata file (.vbm), full backup files (.vbk), and any needed incremental files (.vib or .vrb).

        Notes:

    • It is recommended to move all backup files, but you can omit incremental files if needed. If you decide to not move/copy all backup files to the new storage, you will need to use the “Forget Missing Restore Points” function to clear any references to backup files that were not moved/copied.
    • Also keep in mind that there will be folders created inside the directory/path for job names.
              If your repository path is set as E:Backups, Job A will go to E:BackupsJob A.
  3.     
  4. Rescan the new repository.     

    User-added image

        

  5. If the backup files are not encrypted, skip this step.
        If the backup files are encrypted, the encrypted backup will appear under the Backups > Disk (encrypted) node in the inventory pane. In the working area, select the imported backup and click Specify Password on the ribbon or right-click the backup and select Specify password. More Information This is also relevant for encrypted Veeam Agent backups.
  6. Edit the BackupBackup Copy Job. Go to the StorageTarget tab, and from the drop-down menu, select the new repository.     

    User-added image

        

  7. Press Finish to finalize the setting. If you no error occurs, and the job now lists the new repository in its Repository column, the mapping has been completed.
        Note: If you encounter the following error: “Move all backup files to the new backup repository first”, some restore points the software was expecting to find were not found in the new repository. Cancel out of the job configuration and check both the old repository location and the new location to verify that all restore points have been moved. Then return to step 3 again.

If the steps above do not work, and you still get stopped at the «Move all backups files to the new backup repository first» error, please contact Veeam Support. You may also attempt Method B below.

Method B: New Job, New Backup location

To map the existing backup files to a new or different job, follow these steps:

  1. Under Backups > Disk, right click the job you are changing repository for, and do either Remove From Backups (v8) or Remove from Configuration (v9).    

    User-added image

        

  2. If you are mapping the backup set from one job to another, but the backup location will stay the same, skip this step.
        If you are moving the backup files to a new location create a new repository for the new location where backup files are located.
  3. Rescan the repository where the backup files are located.     

    User-added image

        

  4. If the backup files are not encrypted, skip this step.
        If the backup files are encrypted, the encrypted backup will appear under the Backups > Disk (encrypted) node in the inventory pane. In the working area, select the imported backup and click Specify Password on the ribbon or right-click the backup and select Specify password. More Information This is also relevant for encrypted Veeam Agent backups.
  5. Edit the BackupBackup Copy Job. Go to the StorageTarget tab, and from the drop-down menu, select the repository where the backup files you wish to map are located.     

    User-added image

        

  6. Click Map Backup and select the existing backup chain     

    User-added image

        


If you are attempting to seed failover cluster Veeam Agent for Microsoft Windows job’s restore points please follow the actions below (it has a bit different workflow due to the product design):

  1. Clone the source cluster job
  2. Remove the source job (it will also remove from configuration its points; not from the disk but from Veeam config only)
  3. Move the source backup folder to a new backup folder;
  4. Rescan the new repository to import the moved files 
  5. Change the cloned backup job to the new repository and map the imported points there 

  • #1

Здравствуйте, есть сервер с Veeam BR 9.5, настроены 2 репозитория и есть резервные копии. Как переместить цепочку резервных копий из репозитория А в репозиторий Б ?

  • #2

Когда я пытаюсь в свойствах задания указать новый репозиторий вим говорит:

Move all backup files to the new backup repository first

22222.png

Surf_rider


  • #3

Ставите задание бэкапа в состояние отключено (disable). Затем копируете папку в другой репозиторий. Далее в свойствах задания выбираете нужный репозиторий и выбираете опцию Map Backup.

We received an error message from Veeam One V9 which reported our lab environment backup repository is running out of hard disk space and backup job start to failed.

Screenshot on Veeam One Monitor which reported backup repository has no free space:-

Screenshot on email notification:-

Then we use Veeam Backup and Replication Console to change the backup path but encountered this error message which request us to move existing backup files first.

You can increase your backup repository hdd size. But how about your current backup repository has limited size. Lucky enough that Veeam VBR allowed us to add an additional backup repository and move to new destination. To do so, please follow below step:

[ Resolution ]

1. Use VBR Console to remove from backup. Select your backup and «Remove from configuration»

2. Manual copy backup from existing backup repository to new repository

 3. Click Rescan repository both backup repository

 4. Then go to Jobs to edit existing backup job and change to new repository path.

5. Finally try perform a backup and you will notice backup is now working as expected.

Simple right! Please try this method when your current backup repository is running out of space and you would like to move to new backup repository.

Понравилась статья? Поделить с друзьями:
  • Как найти эквивалентную массу элемента
  • Как найти ярлык word
  • Как найти критические точки для функции
  • Найти телефон во сне как
  • Как составить реквизиты ооо образец