Subscribe

Compliance clock different to system clock

Hi,

I have a problem because I can't delete a snaplock compliance volume. It's seems that compliance clock differ to system clock:

I have this message:

Thu Oct 10 16:50:01 CEST [FILER: snaplock.clock.skewed:warning]: The Compliance Clock time (Fri Apr 23 15:36:52 CEST 2010) is skewed from the appliance clock (Thu Oct 10 16:50:01 CEST 2013) by more than one hour.

FILER> date -c

Compliance Clock: Fri Apr 23 15:41:18 CEST 2010

FILER> date

Thu Oct 10 16:54:47 CEST 2013

Do you have an idea to restablish compliance clock ?

Re: Compliance clock different to system clock

Hmmm...typically the CC can slip time at a very slow rate to catch up (think around a week per *year*) - mainly to avoid malicious hands messing with data.

Sounds like you might want to contact support to see if they can help with some workaround.

thanks

Mike

Re: Compliance clock different to system clock

I have a similar issue.  I wonder if the compliance clock was never initialized?  I don't think there's anything to do at this point - but if you learn otherwise, or someone knows otherwise, I'm interested....

Bill