12-11-2017 09:26 PM
12-12-2017 12:55 AM
The birthtime (backupid) and expiration time of an image is stored in unix Ctime in Netabckup . The infinity retention mapping to year 2038 is due to 'year 2038 problem' .
Reference
https://en.wikipedia.org/wiki/Year_2038_problem
DeepS
12-12-2017 07:10 AM
... also, we're not too sure when the 'end of time' actually is
;0)
From Wiki
The latest time that can be represented in Unix's signed 32-bit integer time format is 03:14:07 UTC on Tuesday, 19 January 2038 (231-1 = 2,147,483,647 seconds after 1 January 1970). Times beyond that will wrap around and be stored internally as a negative number, which these systems will interpret as having occurred on 13 December 1901 rather than 19 January 2038. This is caused by integer overflow. The counter runs out of usable digit bits, flips the sign bit instead, and reports a maximally negative number (continuing to count up, toward zero). Resulting erroneous calculations on such systems are likely to cause problems for users and other relying parties.
I'll take the oppotunity to point out it's not actually our fault, though I am sure someone will, or has already, tried to pin it on us ...
12-13-2017 11:04 AM
The reason is also explained in the NetBackup Administrator's Guide Volume I. For the version 8.0 doc, see page 228.