Condition code change with scale-out repos

Availability for the Always-On Enterprise

Condition code change with scale-out repos

Veeam Logoby pj888888888888 » Tue Dec 05, 2017 9:54 pm 1 person likes this post

So we had an issue with one of our physical storage repos, and I put it in maint. mode in a scale-out repo.
The jobs are all failing now, simply because it cannot access the repo because its in maint. mode and cannot expire the backups.
Would it be possible to have this instead of being a failure, maybe just have it be a warning?
I view failures as a failure to backup data, not failure to expire old backups (thats just me though :) )
pj888888888888
Influencer
 
Posts: 17
Liked: 1 time
Joined: Tue Jan 03, 2017 2:58 pm
Full Name: Paul Janeway

Re: Condition code change with scale-out repos

Veeam Logoby foggy » Mon Dec 11, 2017 12:54 pm

Hi Paul, currently retention is considered a part of the job, which defines the behavior you're seeing. This is something to think about, so let's consider this a feature request.
foggy
Veeam Software
 
Posts: 15394
Liked: 1142 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Condition code change with scale-out repos

Veeam Logoby pj888888888888 » Mon Dec 11, 2017 3:59 pm

Excellent!
I think it would be good if it were a warning instead, granted it would be good to know for storage consumption, but its flood the failed list right now, and its making it hard to find actual problems vs. a non-issue.
pj888888888888
Influencer
 
Posts: 17
Liked: 1 time
Joined: Tue Jan 03, 2017 2:58 pm
Full Name: Paul Janeway


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: NightBird, Yahoo [Bot] and 1 guest