Date/Timestamp for snapshots

evertonn · ‎2013-04-12

Has anyone ever come across this issue in SM? The date stamp of the snapshot is listed as May 17th 3956. This is a 7-Mode system and the version of SM is 2.1

evertonn · ‎2013-04-12

Below is the snap list output from the CLI for the specific volume. The snapshot of concern is highlighted in red below. It appears that the date stamp from ONTAP's perspective is correct. Perhaps this is some anomaly?

FAS3160ca> snap list v14_3_w_job016

Volume v14_3_w_job016

working...

%/used %/total date name

---------- ---------- ------------ --------

0% ( 0%) 0% ( 0%) Apr 11 22:51 SSSV_v14_3_w_job016.1365734580

0% ( 0%) 0% ( 0%) Apr 11 22:51 WchFAS3160ca(1873907323)_v14_3_w_job016-base.192 (busy,snapvault)

1% ( 1%) 0% ( 0%) Apr 10 23:06 SSSV_v14_3_w_job016.1365648180

1% ( 1%) 0% ( 0%) Apr 09 22:53 SSSV_v14_3_w_job016.1365561780

2% ( 0%) 0% ( 0%) Apr 08 23:08 SSSV_v14_3_w_job016.1365475380

2% ( 1%) 0% ( 0%) Apr 07 22:52 SSSV_v14_3_w_job016.1365388980

3% ( 0%) 0% ( 0%) Apr 06 22:55 SSSV_v14_3_w_job016.1365302580

3% ( 0%) 0% ( 0%) Apr 05 22:52 SSSV_v14_3_w_job016.1365216180

4% ( 1%) 1% ( 0%) Apr 04 22:54 SSSV_v14_3_w_job016.1365129780

4% ( 1%) 1% ( 0%) Apr 03 22:53 SSSV_v14_3_w_job016.1365043380

5% ( 1%) 1% ( 0%) Apr 02 22:55 SSSV_v14_3_w_job016.1364956980

5% ( 1%) 1% ( 0%) Apr 01 23:15 SSSV_v14_3_w_job016.1364870580

6% ( 1%) 1% ( 0%) Mar 31 22:53 SSSV_v14_3_w_job016.1364784180

6% ( 1%) 1% ( 0%) Mar 30 22:53 SSSV_v14_3_w_job016.1364697780

7% ( 0%) 1% ( 0%) Mar 29 22:52 SSSV_v14_3_w_job016.1364611380

7% ( 0%) 1% ( 0%) Mar 28 22:54 SSSV_v14_3_w_job016.1364524980

8% ( 1%) 1% ( 0%) Mar 27 22:53 SSSV_v14_3_w_job016.1364438580

8% ( 0%) 1% ( 0%) Mar 26 22:55 SSSV_v14_3_w_job016.1364352180

9% ( 1%) 1% ( 0%) Mar 25 23:31 SSSV_v14_3_w_job016.1364265780

9% ( 0%) 1% ( 0%) Mar 24 22:55 SSSV_v14_3_w_job016.1364179380

9% ( 1%) 1% ( 0%) Mar 23 22:52 SSSV_v14_3_w_job016.1364092980

10% ( 1%) 2% ( 0%) Mar 22 22:54 SSSV_v14_3_w_job016.1364006580

10% ( 0%) 2% ( 0%) Mar 21 22:56 SSSV_v14_3_w_job016.1363920180

11% ( 0%) 2% ( 0%) Mar 20 22:56 SSSV_v14_3_w_job016.1363833780

11% ( 1%) 2% ( 0%) Mar 19 22:56 SSSV_v14_3_w_job016.1363747380

12% ( 1%) 2% ( 0%) Mar 18 22:58 SSSV_v14_3_w_job016.1363660980

12% ( 1%) 2% ( 0%) Mar 17 22:58 SSSV_v14_3_w_job016.1363574580

12% ( 0%) 2% ( 0%) Mar 16 22:56 SSSV_v14_3_w_job016.1363488180

13% ( 1%) 2% ( 0%) Mar 15 23:12 SSSV_v14_3_w_job016.1363401780

13% ( 1%) 2% ( 0%) Mar 14 22:58 SSSV_v14_3_w_job016.1363315380

14% ( 1%) 2% ( 0%) Mar 13 22:52 SSSV_v14_3_w_job016.1363228980

14% ( 1%) 2% ( 0%) Mar 12 22:54 SSSV_v14_3_w_job016.1363142580

15% ( 1%) 2% ( 0%) Mar 11 23:13 SSSV_v14_3_w_job016.1363056180

15% ( 0%) 2% ( 0%) Mar 10 22:53 SSSV_v14_3_w_job016.1362969780

15% ( 1%) 3% ( 0%) Mar 09 22:52 SSSV_v14_3_w_job016.1362886980

16% ( 1%) 3% ( 0%) Mar 08 22:51 SSSV_v14_3_w_job016.1362800580

bazmercer · ‎2013-04-15

Hi

Yes we have several of those. It seemed to coincide with the clocks going back in our case. I just ignore it. We're running a pretty old version of ontap - 7.3.2, and SM 2.0.2