Host-based backup of VMware vSphere VMs.
Post Reply
rreed
Veteran
Posts: 354
Liked: 72 times
Joined: Jun 30, 2015 6:06 pm
Contact:

Veeam.Backup.AgentProvider.AgentClosedException, #01674090

Post by rreed »

Afternoon, all. Fresh v9 install on a fresh VM. Removed a few existing proxies from our old v8 setup, added to our new v9 server (upgraded agent, installer, etc. successfully). Disable old job on old server, build from scratch on new, map backup to existing backup files on repository. Sees everything fine.

Random jobs fail w/ "Error: Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown." Case #01674090 being worked, log files sent, etc. A few things found in logs pointing to Oracle servers and VMware workstation, neither of which do we have here.

CBT has been reset, file locks, temp data, reboots, etc. No change. Anyone else seeing this in a fresh install/migration of v9? Searching shows up some old hits from way back that don't appear relevant to our case.
VMware 6
Veeam B&R v9
Dell DR4100's
EMC DD2200's
EMC DD620's
Dell TL2000 via PE430 (SAS)
rreed
Veteran
Posts: 354
Liked: 72 times
Joined: Jun 30, 2015 6:06 pm
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by rreed »

Having been going on from the get-go, after a handful of days now it seems it happens more frequently w/ some VM's than others, but overall still a bit random.
VMware 6
Veeam B&R v9
Dell DR4100's
EMC DD2200's
EMC DD620's
Dell TL2000 via PE430 (SAS)
rreed
Veteran
Posts: 354
Liked: 72 times
Joined: Jun 30, 2015 6:06 pm
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by rreed »

So far have narrowed this down to a bad proxy. Working w/ support and continuing to investigate.
VMware 6
Veeam B&R v9
Dell DR4100's
EMC DD2200's
EMC DD620's
Dell TL2000 via PE430 (SAS)
Einar
Enthusiast
Posts: 25
Liked: 1 time
Joined: Sep 02, 2015 9:28 am
Full Name: Einar Steinsson
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by Einar »

I am having this problem.
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by foggy »

Einar, please contact support for investigation.
rreed
Veteran
Posts: 354
Liked: 72 times
Joined: Jun 30, 2015 6:06 pm
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by rreed » 1 person likes this post

Confirmed ours was just a bad proxy. Uninstalled/re-installed all Veeam agent, etc. still no good. I'll be wiping the VM and re-cloning a fresh one.
VMware 6
Veeam B&R v9
Dell DR4100's
EMC DD2200's
EMC DD620's
Dell TL2000 via PE430 (SAS)
rreed
Veteran
Posts: 354
Liked: 72 times
Joined: Jun 30, 2015 6:06 pm
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by rreed »

Afternoon, everyone. This error has come back again, and after opening another case (#01697389), apparently is was mostly just because one of our Data Domains was having another episode of not authenticating any connections.

In v8, we'd see a very clear "bad username/password" in the job status and subsequent report. Easy, just reboot the DD and be on our way in about 5 minutes. In v9, I see "Veeam.Backup.AgentProvider.AgentClosedException" is now its generic error when something fails, leaving me to comb through log files to find what the problem is rather than giving something useful at the console/emails/reports. Errors/issues so far have not been isolated to a single storage device needing a reboot, we've had other misc. issues since v9 that throw "Veeam.Backup.AgentProvider.AgentClosedException" whereas v8 would have given some hint at least. We lost a night or two of backups because I thought this error was somethign more serious than our stupid DD's being themselves; I could have rebooted it had Veeam thrown it's useful error.

Do we have some sort of generic alert turned on in our bone stock v9 install? Is there a switch I can flip somewhere that will replace the AgentClosedException error w/ its previous more useful information when something underneath fails? Hate to complain, but it's costing us more time and lost backups when we have to go chasing around log files, investigate, etc. rather than know right away what I need to go do to fix it.
VMware 6
Veeam B&R v9
Dell DR4100's
EMC DD2200's
EMC DD620's
Dell TL2000 via PE430 (SAS)
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by foggy »

In our lab, in case of insufficient permissions v9 correctly reports this event in the job log. QA briefly looked into your logs and apparently this does not come down to DD authentication issues only. There are multiple other access issues in the logs where DD is not involved (for example, when source agent connects to VMware). So seems like there are more global authentication issues in your environment and I recommend looking deeper into this with the help of our support engineers.
rreed
Veteran
Posts: 354
Liked: 72 times
Joined: Jun 30, 2015 6:06 pm
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by rreed »

Thanks foggy. So if I understand correctly, we're getting "Veeam.Backup.AgentProvider.AgentClosedException" in the status/reports because we have a permissions issue, regardless of the underlying cause (naughty DD, proxies actively refusing connections, etc.)? And yes sir, I'll open up a new ticket right away.
VMware 6
Veeam B&R v9
Dell DR4100's
EMC DD2200's
EMC DD620's
Dell TL2000 via PE430 (SAS)
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by foggy »

Cannot comment on what specific reason is behind this particular message, logs should tell.
nahuise
Influencer
Posts: 14
Liked: 2 times
Joined: Jan 02, 2012 9:43 am
Full Name: Edgar
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by nahuise »

Same problem here. I disabled the proxy on the veeam server and added an extra proxy. Let's see what happens next.
nahuise
Influencer
Posts: 14
Liked: 2 times
Joined: Jan 02, 2012 9:43 am
Full Name: Edgar
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by nahuise »

Just checked all backup jobs from the past weekend. After friday's adjustments all jobs went ok. So next question is how to repair the veeam backup proxy? I had to switch to this server because the old server (2008R2) didn't support the exchange filesystem. I moved all jobs from the old server to the new. Worked fine for one week till this problem occured.
veremin
Product Manager
Posts: 20270
Liked: 2252 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by veremin »

As a first step you try to re-install required components by removing and re-adding the proxy role to the given server. If this doesn't fix the issue, you'd better open a ticket with our support team and let them confirm your environment. Thanks,
nahuise
Influencer
Posts: 14
Liked: 2 times
Joined: Jan 02, 2012 9:43 am
Full Name: Edgar
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by nahuise » 1 person likes this post

Thanks. Tried the first step. I'll open a ticket this week.
boyjaew
Influencer
Posts: 17
Liked: 2 times
Joined: May 20, 2014 5:16 pm
Full Name: JB
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by boyjaew »

Case# 01872048
B&R v 9.0.0.1491
Server 2012 R2

Backup (7TB) and backup Copy (based on same backup). Backup copy was seeded initially and worked for about 2 months.
Randomly fail with:
1) Source WAN accelerator error: Socket recv operation timed out
2) 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown

While backup will complete occasionally I haven't gotten a viable backup copy of it off site in over a month. I have removed proxies as suggested in previous posts and thought that did the trick, but it has returned.
rhoughton
Novice
Posts: 3
Liked: never
Joined: Jan 20, 2016 9:21 am
Full Name: Richard Houghton
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by rhoughton »

Had the same for 2 months - so far my actual support call has been interesting!!

Searched the log file and found the error message myself

Support Ref: 01926820
Matt.Sharpe
Service Provider
Posts: 229
Liked: 19 times
Joined: Mar 29, 2016 3:37 pm
Full Name: Matt Sharpe
Contact:

[MERGED] WAN Accelerator Error

Post by Matt.Sharpe »

Hi Guys,

Has anyone seen this error before on the WAN accelerator.

Receiving it on one of our customer jobs:

Error: Target WAN accelerator error: Socket recv operation timed out.
PTide
Product Manager
Posts: 6408
Liked: 724 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by PTide »

Matt, please contact support for investigation and post your case ID.

Thanks
rnt-guy
Enthusiast
Posts: 61
Liked: 1 time
Joined: Feb 04, 2016 12:58 pm
Full Name: RNT-Guy
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by rnt-guy »

Anyone had luck with this? A job has been doing this for a while. All the VMs backup just fine, but it's getting this error multiple times per session during the merge process.

Case #02033450
Mike Resseler
Product Manager
Posts: 8044
Liked: 1263 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by Mike Resseler »

Hi RNT-Guy,

I have no solution for you unfortunately, but considering this entire post and many people who had the issue, I'm sure our support knows where too look. Please keep working with support and let us know the results
thanks
Mike
rnt-guy
Enthusiast
Posts: 61
Liked: 1 time
Joined: Feb 04, 2016 12:58 pm
Full Name: RNT-Guy
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by rnt-guy »

Thanks. So eventually a seed job that was also running for a few days straight finished and then the next attempt by this other copy job finished the merge process. I'm not sure how to explain it other than to say they got in one another's way?
Mike Resseler
Product Manager
Posts: 8044
Liked: 1263 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by Mike Resseler »

Did that seed job had anything to do with the other job?
rnt-guy
Enthusiast
Posts: 61
Liked: 1 time
Joined: Feb 04, 2016 12:58 pm
Full Name: RNT-Guy
Contact:

Re: Veeam.Backup.AgentProvider.AgentClosedException, #016740

Post by rnt-guy »

They were the same source storage running at the same time to the same destination, but that's about it. Different VMs.
Post Reply

Who is online

Users browsing this forum: No registered users and 83 guests