seen from Russia
seen from China
seen from United States
seen from Australia
seen from United Kingdom
seen from China
seen from Italy
seen from Sweden
seen from Finland
seen from Italy
seen from Italy
seen from United States
seen from Sweden
seen from Singapore
seen from United States
seen from United States
seen from Japan
seen from Finland
seen from China
seen from Finland
How to make a dump of remote database
Mysql
mysqldump -u root -p1234 -h remotehost database > backup.sql mysql -u root -p4321 -h localhost database < backup.sql
PostgreSQL
sudo -u postgres pg_dump mrchnt_core_v2_development > dump.sql sudo -u postgres psql -d mrchnt_core_v2_development -f dump.sql
Faster Approach for MySQL Dump file restore
Restoration of huge databases like 30Gigs will take long time restore, mostly because of default settings.In general mysql default settings for innodb of innodb_buffer_pool_size, innodb_additional_mem_pool_size, innodb_log_file_size, innodb_log_buffer_size would be in 8MB,1MB,5MB and 1MB As these buffer sizes are way too small and also every single transaction is committed to disk with default which causes a huge amount of IO for every transaction. running below queries confirm these mysql -uflixtrix -p -e "select @@innodb_buffer_pool_size, @innodb_additional_mem_pool_size, @@innodb_log_file_size, @@innodb_log_buffer_size, @@innodb_flush_log_at_trx_commit" mysql -uflixtrix -p -e "select @@innodb_doublewrite" would return 1 The restoration time can be reduced by increasing the innodb engine settings as per below steps, 1. sudo su 2. vi /etc/mysql/conf.d/innodb.cnf 3. Paste the following into innodb.cnf:
[mysqld]
innodb_buffer_pool_size = 1024M
innodb_log_file_size = 1024M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 0
innodb_doublewrite = 0
now restart mysql 4. service mysql restart and run mysql -uflixtrix -p -e "select @@innodb_buffer_pool_size, @@innodb_additional_mem_pool_size, @@innodb_log_file_size, @@innodb_log_buffer_size, @@innodb_flush_log_at_trx_commit" if these are set to the above values then every thing is fine, otherwise in most cases ( mysql ver 5.5) refuses to start ... (mysql ver 5.1) seems to start but without innodb support you can verify this using mysql -u flixtrix -plocal -e "show variables" | grep innodb will have result like have_innodb NO ignore_builtin_innodb OFF move ahead to step 4 4.'sudo su' to root again and run cd /var/lib/mysql 5.rm ibdata1 ib_logfile0 ib_logfile1 now restart mysql 6.service mysql restart 7.Run the command mysql -u flixtrix -plocal -e "show variables" | grep innodb you should see mysql have_innodb YES and the other variable set at step 3. With these changes the datbase dump should get restored in mins (with default mysql settings it was taking 18hrs+ in my case), this can reduced by further varying the innodb settings. PS: please note that these results are on a PC with dual core procy and 4gig ram
