I guess I should try a Google search first,
of course I didn’t expect this to be that easy to find either:
http://seer.entsupport.symantec.com/docs/235014.htm
From: Mark.Donaldson AT cexp DOT com
[mailto:Mark.Donaldson AT cexp DOT com]
Sent: Thursday, October 18, 2007
9:25 AM
To: Ellis, Jason;
Veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] I guess
infinity isn't forever...
This is the end of time for unix.
The end of the unix clock.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]
On Behalf Of Ellis, Jason
Sent: Thursday, October 18, 2007
10:08 AM
To:
Veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] I guess
infinity isn't forever...
So I need to change the expiration date on a bunch of
images to infinity (for legal reasons). I plan to write a script to parse a
text file taken from a catalog search for the backupids of the needed images. I
tested out changing the expiration date of an image to infinity manually first.
When I ran a bpimagelist and converted the ctime for the expiration date I got
back an expiration of “Mon Jan 18 19:14:07 2038.”
My question is: Is this is just some random date that
NetBackup assigns to images that are never supposed to expire?
Below is the bpexpdate command I ran:
bpexpdate –backupid pasnas01a_1191283460 –d
infinity -force
Jason Ellis
