Skip to main content
Question

Veeam Backup and Replication Failed to mount files: Mounter is in 'failed' state Mount Process aborted Agent failed to process method (Mount.GenericMount


Hello. 

Used VEEAM 12.2.0.334 

Veeam Cloud Virtual Machine 

Using agents for Windows operating systems, I copy and backup data. 

Virtual machines on Linux can recover granular files. 

When trying to restore Windows files, an error occurs when mounting FLR browser.

Veeam is installed on a Windows 2019 server, reduplication is enabled on it. 

Using the agent, I make AD backups and can restore files.  

But if I do exactly the same task on a friend’s virtual machine, changing only the virtual machine that I want to copy, I can’t restore the files.  

It turns out to do instance recovery and extract data from the running VM.

But when copying, exchange does not allow you to restore letters. If I backup only drive C, then I can restore the files of the Windows guest operating system.  

Although the tasks are completed without errors.  

It turns out that the backup browser works very selectively. 

Maybe because some virtual machines have a server core?

7 comments

coolsport00
Forum|alt.badge.img+20
  • Veeam Legend
  • 4133 comments
  • October 16, 2024

Hi @scalexey -

Hmm..not sure why FLR works sometimes and sometimes not. Server Core is supported, as long as you have the Desktop Experience feature installed, as per the User Guide:

https://helpcenter.veeam.com/docs/backup/vsphere/system_requirements.html?ver=120#microsoft-windows-server-core

You could look at the logs in: C:\ProgramData\Veeam\Backup\<restore-name>.log and see if there’s anything in those to help pinpoint the issue.


coolsport00
Forum|alt.badge.img+20
  • Veeam Legend
  • 4133 comments
  • October 16, 2024

As far as for Sys Req’s for use with Veeam Agent, Core is supported as long as you manage the Agents through Veeam Backup:
https://helpcenter.veeam.com/docs/agentforwindows/userguide/system_requirements.html?ver=60

Take note: “Veeam Agent operating in the standalone mode does not support Server Core installations


  • Author
  • New Here
  • 3 comments
  • October 16, 2024

Let me try to clarify again, I have veeam on a 2019 server with a GUI.  

The servers that I want to copy to have OS server windows core installed/ and with the core versions there is a problem loading FLR backup browser


coolsport00
Forum|alt.badge.img+20
  • Veeam Legend
  • 4133 comments
  • October 16, 2024

If you don’t have Desktop Experience on them @scalexey , then yes...according to the Guide, you probably won’t be able to use that OS. You can contact Veeam Support to verify.


  • Author
  • New Here
  • 3 comments
  • October 17, 2024

Привет.

Журнал неудачного резервного копирования exchange, обмен графическим интерфейсом

 

[17.10.2024 12:32:14.989] 1 (17352) Сервер: БКП-02 (ЦП: 4, ОЗУ: 8,0 ГБ) 

[17.10.2024 12:32:14.989] 1 (17352) Сеть: 

[17.10.2024 12:32:15.020] 1 (17352) IPv4: 10.0,01,1, IPv6: N/A, Адаптер: Ethernet0 

[17.10.2024 12:32:15.020] 1 (17352) ОС: Microsoft Windows NT 10.0.17763.0 (x64) 

[17.10.2024 12:32:15.020] 1 (17352) Дата и время UTC: 17.10.2024 09:32:15 

[17.10.2024 12:32:15.020] 1 (17352) Часовой пояс: (UTC+= 

[17.10.2024 12:32:15.020] 1 (17352) Дневное время: Россия TZ 2 Стандартное время 

[17.10.2024 12:32:15.020] 1 (17352) Учетная запись: домен\a.name 

[17.10.2024 12:32:15.020] 1 (17352) Уровень журнала: По умолчанию 

[17.10.2024 12:32:15.020] 1 (17352) ================================= =========================================== 

[17.10.2024 12:32:15.020] 1 (17352) Veeam.Exchange.Explorer.exe: Версия=12.1.0.1300 

[17.10.2024 12:32:15.020] 1 (17352) Параметры командной строки: 

[17.10.2024 12:32:15.020] 1 (17352) /VBRSession=9b37385e-89f5-43c2-bdaf-be7e0cdf8e62 

[17.10.2024 12:32:15.020] 1 (17352) /VBRColorTheme=1 

[17.10.2024 12:32:15.020] 1 (17352) /VBRSessionName=VEX exch-01 

[17.10.2024 12:32:15.399] 1 (17352) Инициализация интернет-прокси... 

[17.10.2024 12:32:15.399] 1 (17352) Интернет-прокси включен 

[17.10.2024 12:32:15.399] 1 (17352) Источник настроек: IEConfig 

[17.10.2024 12:32:15.792] 10 (17228) Подсчет товаров в: Все магазины... 

[17.10.2024 12:32:16.367] 1 (17352) Обнаружен VeeamMountSvc версии 12.2.0.334. 

[17.10.2024 12:32:16.417] 1 (17352) VeeamMountSvc запущен. 

[17.10.2024 12:32:16.417] 1 (17352) Включение интеграции с Veeam Backup and Replication... 

[17.10.2024 12:32:16.687] 1 (17352) Спецификация сеанса: 

[17.10.2024 12:32:16.688] 1 (17352) Идентификатор точки восстановления: 79c73713-d8fa-429f-80b4-959b423fd88d 

[17.10.2024 12:32:16.688] 1 (17352) Имя виртуальной машины: exch-01 

[17.10.2024 12:32:16.689] 1 (17352) Время создания резервной копии: 17.10.2024 12:16:01 

[17.10.2024 12:32:16.691] 1 (17352) Запрос информации о часовом поясе из резервной службы... 

[17.10.2024 12:32:16.697] 1 (17352) Получен часовой пояс: (UTC+ 

[17.10.2024 12:32:16.698] 1 (17352) Инициализация информации о лицензии... 

[17.10.2024 12:32:16.751] 1 (17352) Получена редакция продукта: Veeam Backup and Replication - EnterprisePlus 

[17.10.2024 12:32:16.811] 1 (17352) Получена редакция продукта: Veeam Agent for Windows - Server (идентификатор точки восстановления: 79c73713-d8fa-429f-80b4-959b423fd88d) 

[17.10.2024 12:32:16.903] 10 (17228) найдено 0 элементов. 

[17.10.2024 12:32:16.903] 10 (17228) Загрузка всех товаров магазина... 

[17.10.2024 12:32:16.904] 10 (17228) Загрузка завершена. 

[17.10.2024 12:32:16.922] 14 (11504) Монтаж (ID: 9b37385e-89f5-43c2-bdaf-be7e0cdf8e62, Имя: exch-01)... 

[17.10.2024 12:32:16.922] 14 (11504) Идентификатор точки восстановления: 79c73713-d8fa-429f-80b4-959b423fd88d 

[17.10.2024 12:32:27.664] 14 (11504) Ошибка: Не удалось смонтировать файлы: Монтировщик находится в состоянии «сбой» 

Процесс монтирования прерван 

Агенту не удалось обработать метод {Mount.GenericMount}. 

 

[17.10.2024 12:32:27.664] 14 (11504) Тип: Системное.Исключение 

[17.10.2024 12:32:27.664] 14 (11504) Стек: 

[17.10.2024 12:32:27.664] 14 (11504) Трассировка стека сервера:  

[17.10.2024 12:32:27.664] 14 (11504) в Veeam.Backup.MountServiceLib.CExplorerManagementServiceStub.WaitForOperationIsCompletedSuccessfully(Guid sessionId, CExpOperationUid expOperUid, TimeSpan timeout, CExpOperationProgress& expOperationProgress) 

[17.10.2024 12:32:27.664] 14 (11504) в System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs) 

[17.10.2024 12:32:27.664] 14 (11504) в System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) 

[17.10.2024 12:32:27.664] 14 (11504) Исключение повторно создано в [0]:  

[17.10.2024 12:32:27.664] 14 (11504) в System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) 

[17.10.2024 12:32:27.664] 14 (11504) в System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&

 

msgData, тип Int32) 

[17.10.2024 12:32:27.664] 14 (11504) в Veeam.Backup.Interaction.Explorer.IExplorerManagementService.WaitForOperationIsCompletedSuccessfully(Guid sessionId, CExpOperationUid operUid, TimeSpan timeout, CExpOperationProgress& operationProgress) 

[17.10.2024 12:32:27.664] 14 (11504) в Veeam.Integration.Adapters.V12_1.Services.ExplorerOperations.WaitForOperationIsCompletedSuccessfully(Guid sessionId, ExpOperationUid operationUid, TimeSpan timeout, ExpOperationProgress& operationProgress) 

[17.10.2024 12:32:27.664] 14 (11504) в Veeam.Integration.Remoting.Client.Vbr.Services.ExplorerManagementService.ExplorerOperations.<>c__DisplayClass11_0.<WaitForOperationIsCompletedSuccessfully>b__0() 

17.10.2024 12:32:27.664] 14 (11504) в Veeam.Core.AsyncSafe.Call[TResult 

17.10.2024 12:32:27.664] 14 (11504) в Veeam.Integration.Remoting.Client.Vbr.Services.ImpersonatedCall.Call[T 

[17.10.2024 12:32:27.664] 14 (11504) в Veeam.Integration.Remoting.Client.Vbr.Services.ExplorerManagementService.ExplorerOperations.WaitForOperationIsCompletedSuccessfully(Guid sessionId, ExpOperationUid operationUid, TimeSpan timeout, ExpOperationProgress& operationProgress) 

[17.10.2024 12:32:27.664] 14 (11504) в Veeam.Integration.VBRMount.VBRMounter.WaitForOperationCompletion(операция IVBROperation, Действие`1 statusCallback) 

[17.10.2024 12:32:27.664] 14 (11504) в Veeam.Integration.VBRMount.VBRMounter.InternalMount(ExpMountOibOperationSpec spec, Action`1 statusCallback) 

[17.10.2024 12:32:27.664] 14 (11504) в Veeam.Integration.VBRMount.VBRMounter.Mount(Action`1 statusCallback, Boolean enableChangeTracking, ExpWriteCacheParamsSpec cacheParams) 

[17.10.2024 12:32:27.664] 14 (11504) в Veeam.Integration.Extensions.VBRMountExtension.MountAction(IVBRMount mount, Действие`1 mountAction) 

17.10.2024 12:32:27.664] 14 (11504) в Veeam.Integration.Extensions.VBRSessionExtension.MakeMount[TMount 

[17.10.2024 12:32:27.664] 14 (11504) в Veeam.Exchange.Explorer.Tasks.AsyncMounter.Run(IProcessObserver observer, CancellationToken ct) 

[17.10.2024 12:32:27.664] 14 (11504) в Veeam.Presentation.Async.VisualAsyncTask.Execute(IProcessObserver наблюдатель) 

[17.10.2024 12:32:32.931] 1 (17352) Ошибка: загруженное крепление не найдено. 

[17.10.2024 12:32:32.931] 1 (17352) Тип: Системное.Исключение 

[17.10.2024 12:32:32.931] 1 (17352) Стек: 

[17.10.2024 12:32:32.931] 1 (17352) в Veeam.Integration.Controllers.IntegrationControllerBase`2.HoldPermamentMount() 

[17.10.2024 12:32:32.931] 1 (17352) в Veeam.Exchange.Explorer.Controllers.IntegrationController.ActivateWithMount() 

[17.10.2024 12:32:32.931] 1 (17352) в Veeam.Exchange.Explorer.Controllers.IntegrationController.Activate(Boolean silent) 

[17.10.2024 12:32:32.931] 1 (17352) в Veeam.Exchange.Explorer.Controllers.ControllerManager.Activate(IEnumerable`1 хранилища) 

[17.10.2024 12:32:32.931] 1 (17352) в Veeam.Exchange.Explorer.ExplorerViewModel.ActivateBackupIntegration() 

[17.10.2024 12:32:32.931] 1 (17352) в Veeam.Exchange.Explorer.Controllers.IntegrationActivationController.ActivateIntegration() 

[17.10.2024 12:32:35.655] 1 (17352) Закрытие Veeam Explorer для Microsoft Exchange...


  • Author
  • New Here
  • 3 comments
  • October 17, 2024

three hours ago I could restore my letter. Now the equipment will not start. 

I asked to add the veeam folders to exceptions on the antivirus software solution.


coolsport00
Forum|alt.badge.img+20
  • Veeam Legend
  • 4133 comments
  • October 17, 2024

@scalexey -

When you post, please do so in English so we can try to help. That said, Veeam Support is really the place to share logs with.

For A/V exclusions, see Veeam’s KB1999:

https://www.veeam.com/kb1999

Hopefully adding those will help your issue.


Comment