Dave, I think you're going to think about the archive process first. I've been through this several ways and they all led to different processes (and therefor products).
SDSC.EDU offers an archive service. It was based on HPSS, huge tape robots (Powderhorn) and has a projected lifetime of "forever". You the user decide what to out into the archive, and it will be there. Forever. I've gotten things out that I put in over 15 years ago. Process - up to the user Policy about what gets archived - up to the user lifetime - (up to) forever, but up to the user technology - big tape size - probably 10 Petabytes by now Here at the $currentjob we want to archive a project when it completes. We want to capture art, code, video, audio, etc. We want to be selective about what we archive due to the expense, and time to create the archive. Process - IT and the project owner go through the live project repositories and choose what will be saved Policy - company policy about what kinds of assets are to be archived lifetime - at least 10 years technology - don't know yet Each of these will lead to completely different solutions. As an aside, we worked on a project for the National Archives. Interesting mission statement: "Data for the lifetime of the Republic". They are talking about archives spanning a dozen or more centuries! Best, --tep
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
