Re: Long term database archival

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Karl O. Pinc wrote:
>
> On 07/12/2006 09:25:45 AM, Jan Wieck wrote:
>> On 7/6/2006 8:03 PM, Karl O. Pinc wrote:
>>
>>> On 07/06/2006 06:14:39 PM, Florian G. Pflug wrote:
>>>> Karl O. Pinc wrote:
>>>>> Hi,
>>>>>
>>>>> What is the best pg_dump format for long-term database
>>>>> archival? That is, what format is most likely to
>>>>> be able to be restored into a future PostgreSQL
>>>>> cluster.
>>>
>>>> Anyway, 20 years is a _long_, _long_ time.
>
>> The best way is to not only backup the data. With todays VM technology
>> it should be easy enough to backup a virtual disk that contains a full
>> OS and everything install for every major Postgres release.
>
> I think that that's the answer, put the whole OS and db on a
> bootable cd or DVD.

It's *highly* *unlikely* that a DVD-R will be readable in 20 years.

CSV files on DLT is a definite plan.

Also, and "archive server", with a simple CPU, not "much" RAM and
slots for 3.5" SATA drives. Populate with with large, affordable
drives as needed.

> In 20 years they'll surely be no
> problem running the whole thing from RAM so media access
> speed should not be an issue.
>
> The only thing to worry about is if the underlying architecture
> goes away entirely. I suppose if you choose something common
> they'll be an emulator.

That's how people are still running VAX/VMS...

- --
Ron Johnson, Jr.
Jefferson LA USA

Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEtRxeS9HxQb37XmcRAuHcAKCDs+AUv90ZSg2IpXAAF4q9pg7fpACgqXkq
WXHDz9yMyIUs63RDTop9lR0=
=ZKDb
-----END PGP SIGNATURE-----