VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
I tested to restore exchange on the next day again (incremental). No error. I tested today after full backup - no error as well. The exchange server itself didnt show any errors or faulty behaviour. I will keep an eye on it and report further errors. Thankes a lot :)
I did another test backup today without changing the configuration yet. Everything ran smooth and no backup got stuck. What I reconized was the low processing rate and a cpu load of sometimes 100%. Veeam services did cause some load, but each service not more than 5 to 15%. The highest load was caused by MS antimaleware service… I will monitor the next backups and report. When a backup job gets stuck again, I will reconfigure the proxies as adviced.One question about the proxies: Did I get that right, I have to change the transport mode from automatic selection to “virtual appliance”? And Chris, you ment that I should setup a new VM machine to be the proxy besides the backup server or did you mean i should setup a new VM proxy within Veeam? Thankes a lot so far and in advance :)
Ok, I went through some configuration of Veeam. I have two proxies added. One VM and one Agent. Both seem to work properly. What I couldnt find are the described modes for the proxies (like Hot-Add, NBD, etc.). Where do i configure those modes?
Our environment is pretty easily described: Gigabit switch for all physical machines. Backup server is an ESXi host connected with 2 gigabit network cards and a virtual Windows 2022 + Veeam installed. The server I backup is an ESXi host connected with 2 gigabit cards and 2 virtual Windows servers installed (2016 file server and 2012R2 exchange server). My storage is a Synology NAS connected with 2 gigabit cards and DSM operating system (no VM on it).
I am not that into all details of Veeam so I am not sure whether I understand every advice here. Just for additional Information: Our LAN is a small office network. The backup server is physically positioned right besides the storage NAS and physically connected via the same switch. There is no vCenter. Our backup server an our Veeam are absolute stand alone. The proxy: I dont understand, why i would need any proxy in our configuration (even a standard proxy)? I left the proxy option blank, so I guessed there is nothing in between the backup server and the storage NAS.
Unfortunatly I didnt watch the task manager during backup job, but i will have a look at it today. Veeam ist the only software installed and running on the backup server (virtual win 2022 server). I belive that the server was almost idle while stuck in the job. I dont use any proxies. The backup job is from IP to IP in the same LAN. And btw. this backup job ran for a week like charming… I didnt change anything. Today morning I recognized that Veeam aborted the stuck job after 4:41 hours and retry1 was successfull after 18 minutes.
its syntetic, inc.
Well, I tried all of your advices and it worked :) I cleaned up Exchange Server and won 10 GB extra space on disk and I started VSS Service (which was stopped); now backup is free from warnings. Thankes a lot again guys :)
Thankes a lot Moustafa for your advice. I checked free space and it was lower than i thought. but still there were 41 GB of 200 GB free. So that should have done it. Anyway, I cleaned up the System and got additional 10 GB now. I will report wether this has any impact or effect.
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.