I faintly remember seeing something like this where no data had changed since the last snapshot, but I'd recommend checking the logs. There should be a clear message from the time of the missed snapshot that indicates what happened.

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Basil Sent: Monday, July 11, 2016 3:25 AM To: NGC-pdg-uow.edu.au pdg@uow.edu.au Cc: toasters@teaparty.net Subject: Re: is this a bug ?

So your policy has snapshots that are supposed to happen, but just aren't taken? I've never seen that, personally, but if you think that background work is choking the ability for the filer to take them, maybe try adjusting the policy to take the dailies at a different time.

On Sun, Jul 10, 2016 at 7:02 PM, Peter D. Gray <pdg@uow.edu.aumailto:pdg@uow.edu.au> wrote: Hi guys

I am running 8.2.3 cluster mode. We usually run 30 days of daily snaps on our volumes. We also use snapmirror dr extensively.

What I am noticing is that we are missing daily snapshots with regularity. I think the problem is that than the time for dailys rolls around, if the volumes are involved in a snapmirror operation at the time, the daily snap is missed.

Anybody seen this and if so, is it a known bug or is this documented behaviour or am I barking up the wrong tree entirely?

Regards, pdg

_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters