nbv4 wrote:
All thats left now is my postgres and mysql databases. Whats the easiest way to copy these over? I already tried "pg_dumpall > backup" but when I tried to "psql < backup" it brought up a ton of errors. My postgres database uses PostGIS, which I think is messing things up.
At least for PostgreSQL, I think the dump/reload is the best bet. pg_dumpall is in fact the right way to dump an entire cluster (e.g., all databases, roles, and access rights). One important thing to remember is that when you try to reload it into the database you will have to connect as a superuser (by default postgres) in order to be able to execute the various create operations.
An alternate approach is to use pg_dumpall just to dump the roles (-r) and then use pg_dump to individually dump any databases. You can then install the roles (with psql) and restore each database in turn (with psql or pg_restore) which can give you a little more control if desired. Also, for larger databases, the custom format for pg_dump (-Fc) is compressed so can take up much less space.
You will want to make sure that any modules (languages, etc..) you have installed in the old cluster are also installed in the new cluster.
Can you summarize any of the more frequent errors? It might help indicate which piece is missing.
I might also suggest (to help with the test process) - leave your current Linode operational as 64-bit. Create a brand new Linode temporarily (you'll only get billed for the days you use it) as 32-bit. Then you can have both databases live at the same time and make testing methods of transferring the data easier (e.g., pg_dumpall -h xxxx | psql).
Once everything is done and you're happy with it, clone your new disk images back to your old Linode and delete the new Linode.
-- David