Hi Jacek, These are problems of technology migration. I thought we discussed this before on this direction without the right "jargon".
My understanding is that we will be having a backup of previous versions on the archival system. I don't have the notes to see if we also decided to backup or archive the "un-released" or "the-latest-n-greatest" db also. I think we add this to our archival list, our technology migration strategy should be fine. This might change the numbers (for media and associated cost) by a very little. Another very concerned (paranoid) action item is to also archive the software and configuration files that were used to manage the database. Cheers, Arun --------- PS: This mail was sent (typed offline) during my travel and might not be in sync with any latest developments or replies you might have sent to me or on any related mailing list. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jacek Becla > Sent: Monday, October 23, 2006 3:23 PM > To: LSST Data Management > Subject: [LSST-data] full db backup before db software upgrade? > > Keywords: DataAccWG > > Hello, > > I met with CERN Oracle DBAs today. One important point they > made was about making a full backup of database before > database software upgrade. They had a case where (a minor) > Oracle upgrade caused data corruption due to a bug in the > Oracle version they upgraded to. They are planning to keep > such backups for a long time, since often this sort of > problems is discovered weeks or even months after the upgrade > (3 months in their case). > Clearly we need to think about a strategy to deal with this > sort of problems. > > Jacek > _______________________________________________ > LSST-data mailing list > [email protected] > http://www.lsstmail.org/mailman/listinfo/lsst-data > _______________________________________________ LSST-data mailing list [email protected] http://www.lsstmail.org/mailman/listinfo/lsst-data
