The real question to me is what do you want to do with the archived data? The requirements you given are really vague. The 2 big options that I think of are Documentum and Microsoft Office Sharepoint server (and you can even get solutions that combine the 2). In a very very simplified and generic way the basic difference between the 2 is how data is treated once it's archived.
Documentum is an admin managed, policy driven, document lifecycle manager at its core (eg document x is 6 months old so it's migrated to never never land, it contains Mr. Jones' notes). To get to those notes you (or usually an admin) retrieves the document. It's very efficient at storing docs.
Sharepoint on the other hand is not as space efficient at storing docs (it's much better in 2010) but Sharepoint's point of view is that docs contain data that can be reported on(with images you might track the metadata) and that users should be able to represent data in whatever view suits thier current need. So you might not even need to retrieve Mr Jones' notes because all you needed was his data that got aggregated into a sharepoint report (of course you can always go back to the source)
I don't think there is anything out of the box that will do exactly what you want so plan on budgeting some consulting time as well. Talk to the various departments and make sure you fully understand and have documented their requirements (saying you need to archive and retrieve data is not a great requirement list) although good to know size and document end of life are not boundaries either (except to know that you want san hardware to be supported for at least a "few" years). Really dig in to what the business is going to need to do with this data. It may turn out that you don't need any sort of document lifecycle management but simply hierarchical storage management (another reason to like compellent)
For san hardware I've found nothing that compare to compellent sans