2038 is the end of UNIX epoch in 32bit systems. In 64bit systems is some ridiculous value after the sun explodes etc
Question is if you import those images from a 32 bits NetBackup to a 64 bit NetBackup, will they still expire in 2038 or automatically change to the 2^64 ? ----- Mensaje original ---- De: Justin Piszcz <[EMAIL PROTECTED]> Para: "Ellis, Jason" <[EMAIL PROTECTED]> CC: Veritas-bu@mailman.eng.auburn.edu Enviado: jueves, 18 de octubre, 2007 17:47:38 Asunto: Re: [Veritas-bu] I guess infinity isn't forever... On Thu, 18 Oct 2007, Ellis, Jason wrote: > 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? 2038 is the end of the UNIX epoch and that is why its associated with infinite retention > > > > Below is the bpexpdate command I ran: > > > > bpexpdate -backupid pasnas01a_1191283460 -d infinity -force > > > Jason Ellis > > > > _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ____________________________________________________________________________________ Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://advision.webevents.yahoo.com/reto/entretenimiento.html _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
