Hello everybody.
I have an error with a backup job on veeam backup for windows that was installed on a virtual server with the next specifications
- 2 Hard Drive disks, 1 of 200 GB and the other is 1.5 TB
- 8 GB RAM
I do not remeber what is teh number of VCPUs that contain in this server, but I had created a backup job backing up the first two hard drives to our repository, once created it was run and it took about 4 to 5 days in the process, reaching 300 GB of backup, the task stopped indicating an error in the socket, we checked between the logs and we believed possibly a disconnection in the server's network.
Then we tried to separate by two backups where the first was kept with the information of the 200 GB hard drive and in another backup job the information of the 1 TB hard drive, the one with the 200 GB backup worked but the other 1 TB did not let me run it and mark a socket error similar to startup.
I share with you the number of my case is Case # 04799854 - Error: Socket has been forcibly closed. Failed to recover connection
Grettings
-
- Novice
- Posts: 4
- Liked: never
- Joined: May 13, 2021 1:48 am
- Full Name: AlejandroOrtiz
- Contact:
-
- Product Manager
- Posts: 14840
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: I can´t generate a backup job of one Hard Disk Drive
Hello,
if you have a virtual machine running on VMware, Hyper-V or Nutanix AHV, I recommend using Veeam Backup & Replication with VM-based backup instead of agent based backup.
As your case was closed because you use a free product, only guessing is left post368036.html?hilit=Socket%20forcibly ... ed#p368036
You could also try to find a reason in C:\ProgramData\Veeam\Endpoint... - but probably your environment is unstable. I mean, 4-5 days for that little amount of data... my laptop does it faster to a single cheap 7k spinning hard-disk
Best regards,
Hannes
if you have a virtual machine running on VMware, Hyper-V or Nutanix AHV, I recommend using Veeam Backup & Replication with VM-based backup instead of agent based backup.
As your case was closed because you use a free product, only guessing is left post368036.html?hilit=Socket%20forcibly ... ed#p368036
You could also try to find a reason in C:\ProgramData\Veeam\Endpoint... - but probably your environment is unstable. I mean, 4-5 days for that little amount of data... my laptop does it faster to a single cheap 7k spinning hard-disk
Best regards,
Hannes
Who is online
Users browsing this forum: No registered users and 31 guests