VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Update,I contacted Veeam support, they asked me for log files of this job and after analyzing the logs, they found that VeeamBR server cannot communicate with hyper-v server when backup job reaches 65 %. So I did a test using another hyper-v server in the same segment of VeeamBR and everything works fine. I went back to our Forcepoint firewall and found that the IPS detected the NFS communications between hyper-V and our Dell data domain as a Log4j threat. A rule to allow this communication solves this problem. Thanks, you are the best.
Hi @MicoolPaul, I Will Check if Dell Data domain Offre this option. Thank you.
Hi, I found this.https://helpcenter.veeam.com/docs/backup/vsphere/limitations-for-sobr.html?ver=120 If a backup repository is added as an extent to the scale-out backup repository, you cannot use it as a regular backup repository. You cannot target jobs to this backup repository. Instead, you have to target jobs to the configured scale-out backup repository.
Hi, Even after increasing memory and CPU, the problem still persists. I suspect there is something wrong with these Linux VMs, as I created a new Windows Server 2016 VM on the same hypervisor and the backup went fine.
Hi @coolsport00, I will increase the memory to 32 GB and do a test.
Here is part from the backup log. [17.05.2023 10:01:22] <17> Info Meta file saved to disk, Elapsed Time: 00:00:00.2413671, in seconds: 0,2413671[17.05.2023 10:01:22] <17> Info [Mutex] Releasing mutex [Global\BackupMeta[c4734c1a-e03b-4c43-8dba-a870691fa11a]][17.05.2023 10:01:22] <17> Info [BackupMetaUpdater] Backup meta generated, Elapsed Time: 00:00:01.4752865, in seconds 1,4752865[17.05.2023 10:04:30] <20> Info [HvWmiProxy:srv-xxxxx-xxxx.zzzz.local] Closing connection[17.05.2023 10:04:30] <20> Info [CProxyRpcInvoker] RpcInvoker [57616766] was disposed[17.05.2023 10:23:41] <28> Error Processing SRV-SFTP-02[17.05.2023 10:23:41] <28> Error Shared memory connection has been forcibly closed by peer. (Veeam.Backup.Common.CCppComponentException)[17.05.2023 10:23:41] <28> Error in c++: Failed to write data into shared memory IO device.[17.05.2023 10:23:41] <28> Error
Hi @coolsport00,1 - What is your Veeam server setup?All in one2 - How much resources did you give your VBR server and components?4 CPU, 12Gb Ram, 60Gb HDD “C”, 60Gb HDD “D”Did you meet minimum system requirements as noted in the Guide?I think it meet the minimim. I can backup the Windows VMs hosted on the same hypervisor without problem, The problem is only with Linux VMs.
Hi, To elaborate on this, based on your subject title, is this a Hyper-V edition of Windows Server or Windows Server 2019 with the Hyper-V role installed? Most common troubleshooting steps: If your Hyper-V server isn’t domain joined, ensure the local user is formatted as “.\<Username>“ If this is a Windows Server 2019 installation, make sure the service has been installed and then the server rebooted Does the server have UAC control enabled? UAC being enabled and having a non-domain joined server can cause problems accessing the admin shares for component deployment Does the server have Windows Firewall or a third-party firewall installed? Are the required ports opened if so? Thanks @MicoolPaul, the “.\” before the administator account fixed my problem.
Hi @Chris.Childerhose, Okay Thank you. Thank you all, have a nice day.
Hi, Yes, the appliance console show me the same values. Thank you @JMeixner
Hi @JMeixner, Thanks for your feedback. So, can i trust in the free value reported by the appliance or i have to check with Dell EMC ?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
