Tag Info

New answers tagged

0

I got the best answer here. The best way to do this is to create the dump file directly on the receiving server by dumping the source database remotely: pg_dump -h remoteserver -U remoteuser remotedbname -Fc -f my_old_server_backup.dump This is way more reliable than writing a huge SQL file over a network filesystem. I now have a functioning, migrated ...


0

you can try and directly import it via this oneliner: mysqldump --add-drop-table --extended-insert --force --log-error=error.log -uUSER -pPASS OLD_DB_NAME | ssh -C user@newhost "mysql -uUSER -pPASS NEW_DB_NAME" but not being able to copy reliable over network. Are you sure there is no networking or filesystem issues?


0

Try AFS (Andrew FS). This file system is per se designed to be scalable and network-oriented and could provide a good solution to your problem. In case of Ubuntu use OpenAFS. Keep in mind though that it will require some configuration and setting up, before you establish a reliable connection.


0

What about mounting an external NFS share first on sever1 and mounting to server2 after the dump? That's the way I perform Oracle databases datapump and RMAN backups (similar to your dumps) with best results duplicating production server (server1) to test server (server2) and restoring backups. Our external NFS relies on a NAS but any Gnu/Linux will do the ...



Top 50 recent answers are included