Availability for the Always-On Enterprise
Post Reply
pj888888888888
Enthusiast
Posts: 36
Liked: 1 time
Joined: Jan 03, 2017 2:58 pm
Full Name: Paul Janeway
Contact:

Condition code change with scale-out repos

Post by pj888888888888 » 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 :) )

foggy
Veeam Software
Posts: 16832
Liked: 1361 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Condition code change with scale-out repos

Post by foggy » 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.

pj888888888888
Enthusiast
Posts: 36
Liked: 1 time
Joined: Jan 03, 2017 2:58 pm
Full Name: Paul Janeway
Contact:

Re: Condition code change with scale-out repos

Post by pj888888888888 » 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.

Post Reply

Who is online

Users browsing this forum: No registered users and 40 guests