We’re running Veeam Backup & Replication 12.3.2.3617 Community Edition and during the Backup Copy job that copies to a USB drive the “Backup Copy USB.vbm” is not saving backup meta.
Error message:
Failed to save backup meta to [\\ServerName|usb|Backup Copy USB|Backup Copy USB.vbm] Error: Failed to call RPC function 'FcRenameFile': An unexpected network error occurred. Failed to rename file from [\\ServerName\usb\Backup Copy USB\Backup Copy USB.vbm_13_tmp] to [\\ServerName\usb\Backup Copy USB\Backup Copy USB.vbm].
I went through several troubleshooting steps in Veeam Backup to try to fix the recurring error with the VBM file.
Troubleshooting steps taken were firstly to disable Indexing on the USB external hard drive.
I also forced Veeam to rebuild the .VBM file on the external USB hard drive.
I copied existing VBM file, deleted it off USB hard drive, then resynced the Disk (Copy) to USB backup job. Veeam then automatically rebuilt the .VBM. This worked, but the same error is still occurring.
Previously I also disabled any power saving setting on the USB hard drive and USB ports.
Tried logging a Support ticket with Veeam, but it was Closed as we’re using Community edition only.
Could this be possibly linked to Antivirus software? We are running SentinelOne.
Thanks in advance for any suggestions - I would greatly appreciate it.
Best answer by MicoolPaul
Hi,
Theres some details missing here that would be of use:
USB Drive - how is this configured as a backup repository? Is the server it’s connected to defined as a windows backup repository with local storage? Are you planning to rotate between USB drives? If so have you configured the setting within the repository to define that it is a rotated drive.
I typically have seen that error when firewalls are closing sessions but AV file locks have caused it too. On the AV side have you configured your exclusions based upon https://www.veeam.com/kb1999? And what is the network topology between the source backup repository, the VBR, and the backup copy target? Is it the same L2 network or is it an off site copy being routed via some VPN or MPLS?
Thanks @MicoolPaul! Much appreciated.
The USB Drive is configured as a SMB backup via a file path - i.e. \\servername\sharename However, the USB drive is directly connected to the server that Veeam runs on. So it presumably could be changed to Direct attached (local) storage instead.
Yes, it is rotated between USB rives and it is correctly configured within the repository to define that it’s a rotated drive.
No, I haven’t yet configured these AV exclusions, but I’ll look into doing so with our SentinelOne AV.
The network topology is the same L2 local network between all these.
Hi. You’re unnecessarily creating bottlenecks and a lot of unnecessary complexity here so add it as local storage, this will mean the Veeam components write locally to the data, and you can configure this as rotated USB media too if necessary.
Theres some details missing here that would be of use:
USB Drive - how is this configured as a backup repository? Is the server it’s connected to defined as a windows backup repository with local storage? Are you planning to rotate between USB drives? If so have you configured the setting within the repository to define that it is a rotated drive.
I typically have seen that error when firewalls are closing sessions but AV file locks have caused it too. On the AV side have you configured your exclusions based upon https://www.veeam.com/kb1999? And what is the network topology between the source backup repository, the VBR, and the backup copy target? Is it the same L2 network or is it an off site copy being routed via some VPN or MPLS?
It can be linked to AV for sure, another thing worth checking - Windows events at the moment of failure, maybe there you will be able to see which service is blocking it exactly?
Depending if you remove the USB or not check the settings in Device Manager too as you can change it for fast removal or performance. If you leave it try changing the setting.
Theres some details missing here that would be of use:
USB Drive - how is this configured as a backup repository? Is the server it’s connected to defined as a windows backup repository with local storage? Are you planning to rotate between USB drives? If so have you configured the setting within the repository to define that it is a rotated drive.
I typically have seen that error when firewalls are closing sessions but AV file locks have caused it too. On the AV side have you configured your exclusions based upon https://www.veeam.com/kb1999? And what is the network topology between the source backup repository, the VBR, and the backup copy target? Is it the same L2 network or is it an off site copy being routed via some VPN or MPLS?
Thanks @MicoolPaul! Much appreciated.
The USB Drive is configured as a SMB backup via a file path - i.e. \\servername\sharename However, the USB drive is directly connected to the server that Veeam runs on. So it presumably could be changed to Direct attached (local) storage instead.
Yes, it is rotated between USB rives and it is correctly configured within the repository to define that it’s a rotated drive.
No, I haven’t yet configured these AV exclusions, but I’ll look into doing so with our SentinelOne AV.
The network topology is the same L2 local network between all these.
It can be linked to AV for sure, another thing worth checking - Windows events at the moment of failure, maybe there you will be able to see which service is blocking it exactly?
Thanks @kira.bezhanova! Appreciated.
I did briefly look through the Windows event logs for this previously. However, I will dig deeper into this.
Depending if you remove the USB or not check the settings in Device Manager too as you can change it for fast removal or performance. If you leave it try changing the setting.
Thanks @Chris.Childerhose! Appreciated.
It’s set to “fast removal”, which is correct for how we rotate (hot swap) these USB drives.
Theres some details missing here that would be of use:
USB Drive - how is this configured as a backup repository? Is the server it’s connected to defined as a windows backup repository with local storage? Are you planning to rotate between USB drives? If so have you configured the setting within the repository to define that it is a rotated drive.
I typically have seen that error when firewalls are closing sessions but AV file locks have caused it too. On the AV side have you configured your exclusions based upon https://www.veeam.com/kb1999? And what is the network topology between the source backup repository, the VBR, and the backup copy target? Is it the same L2 network or is it an off site copy being routed via some VPN or MPLS?
Thanks @MicoolPaul! Much appreciated.
The USB Drive is configured as a SMB backup via a file path - i.e. \\servername\sharename However, the USB drive is directly connected to the server that Veeam runs on. So it presumably could be changed to Direct attached (local) storage instead.
Yes, it is rotated between USB rives and it is correctly configured within the repository to define that it’s a rotated drive.
No, I haven’t yet configured these AV exclusions, but I’ll look into doing so with our SentinelOne AV.
The network topology is the same L2 local network between all these.
Hi. You’re unnecessarily creating bottlenecks and a lot of unnecessary complexity here so add it as local storage, this will mean the Veeam components write locally to the data, and you can configure this as rotated USB media too if necessary.
