Comprehensive data protection for all workloads
Post Reply
tntteam
Enthusiast
Posts: 68
Liked: 5 times
Joined: Aug 28, 2015 12:40 pm
Full Name: tntteam
Contact:

Failed to proceed retention policy Error

Post by tntteam »

Hi there,

I got this strange error on one of my backupcopy job :

Failed to proceed retention policy Error: Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown.

What's weird is that the job have run perfectly on all VMs and the retention point have been created. Temporary bug ? What you think ?

http://postimg.org/image/m32c0gm5j/
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Failed to proceed retention policy Error

Post by foggy »

Please open a case with technical support. Threads discussing technical issues without providing case ID are eventually removed by moderators.
tntteam
Enthusiast
Posts: 68
Liked: 5 times
Joined: Aug 28, 2015 12:40 pm
Full Name: tntteam
Contact:

Re: Failed to proceed retention policy Error

Post by tntteam »

I was just looking for similar feedback, maybe it's just an error with no further complications that other ppl already got.

I'll open a support ticket next week when the backup copy job run again and if I still get the same error.
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Failed to proceed retention policy Error

Post by foggy »

This was never reported before here on forums and requires further logs review for investigation. So feel free to contact support for assistance.
tntteam
Enthusiast
Posts: 68
Liked: 5 times
Joined: Aug 28, 2015 12:40 pm
Full Name: tntteam
Contact:

Re: Failed to proceed retention policy Error

Post by tntteam »

Ok got the error again, opened a SR (01830952) I'll post here the results
tntteam
Enthusiast
Posts: 68
Liked: 5 times
Joined: Aug 28, 2015 12:40 pm
Full Name: tntteam
Contact:

Re: Failed to proceed retention policy Error

Post by tntteam »

ATM, nothing came out from logs. The problem has been solved by recreating the copy job + using a local vcenter account instead of AD domain account.

I'll open a SR with vmware because this error began when we migrated from vcenter 5.1 windows to vcsa 6.0.
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 176 guests