This post is more than 5 years old
4 Posts
0
3121
VSS:/ Saveset with retention of 2038
Currently we have ran into a issue of VSS:/ SaveSets with the clone retention period of 2038 (shows 1938 on the NMC). We dont have any policies in place to keep clones till the year of 2038, also nor have i see such a saveset called VSS:/ in NMM 2.4.x. The current setup is NWC 8.0.1.5 and Client of 8.0.1.2-3 and NMM 2.4.x. This just started to happen about a month ago and i have not been able to figure out what we have a retention period of 2038.
o17Uu33DCF12520
1.1K Posts
0
January 2nd, 2014 19:00
After a VSS snapshot backup with NMM a save set "VSS:\" is created and registered in the media db. The retention time on this save set is "1/18/2038".
The VSS:/ save set is used to create the index records for the writers and volume nodes (GUI presentation objects).
The retention time for the 'VSS:\' save set is, by design, set to 1/18/2038. This save set will be deleted when the associated data save set has expired and is removed from the media database. This lifecycle is handled through nsrsnapck, which is automatically run at the start of a snapshot enabled group or is run automatically once every 24 hours, whichever comes first.
Make sure you have installed the latest Cumulative Fixes package for your NetWorker server.
ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes
Refer to http://en.wikipedia.org/wiki/Year_2038_problem:
The standard Unix “time_t” is a signed integer data type, traditionally of 32 bits. Being 32 bits means that it covers a range of about 136 years in total. The minimum representable time is 1901-12-13, and the maximum representable time is 2038-01-19. At 03:14:07 UTC 2038-01-19 this representation overflows.
To resolve this issue:
Run the following mminfo command on NetWorker server, it shows the correct retention time:
#mminfo -avot -q ssid= -r ssretent(33)
If you would like to modify the retention time manually, you may run following command on NetWorker server. It will return the cloneid for the saveset.
Note: should be the retention time you would like to set.
Note: If you copy the 1/18/38 to Excel it will auto change it to 1/18/1938, this is not a NetWorker issue. This is caused by the settings in Excel.
For example:
403476435 1359777654 (001) 2/1/13 8:00:54 PM 1/18/38 7:14:06 PM full checkpoint, recoverable 14 MB crk
403476435 1359777654 (001) 2/1/2013 20:00 1/18/1938 19:14 full checkpoint, recoverable 14 MB crk
Workaround:
Use the GMT time zone to specify these time values. For example, in the above instance, the line should be specified as:
# save … -y "12/31/2038 23:59:59 GMT" test.txt
If you specified policy times using a time zone other than GMT and no error occurred, this change is not necessary.
Note: The UNIX man page for nsr_getdate (this man page also applies to Windows) provides more information on general date input issues under the BUGS section in the man page.
If you need more than 25 years retention on a clone, you might want to use the Archive rather than the Clone so no date is set and the time will be “Forever”.
please mark my answer as "correct/helpful" answer if it helps.
TimQuan
1.2K Posts
0
January 2nd, 2014 18:00
any screenshot?