<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mysqldump on Michael’s Domain</title><link>https://jeltsch.org/en/tags/mysqldump/</link><description>Recent content in Mysqldump on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/mysqldump/index.xml" rel="self" type="application/rss+xml"/><item><title>Updating drupal</title><link>https://jeltsch.org/en/updating_drupal/</link><pubDate>Tue, 19 Feb 2013 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/updating_drupal/</guid><description>&lt;p&gt;Here&amp;rsquo;s what I need to to to update 
 &lt;a href="https://jeltsch.org/en/tags/drupal/"&gt;drupal&lt;/a&gt;
 (minor updates, e.g. from 7.18 to 7.19) on my Ubuntu server. I have installed drupal from the drupal source itself and not from the Ubuntu repository (because the Ubuntu repository is usually quite old and not updated as frequently). Actually the update is quite painless; I am sure somebody automated that already somewhere…&lt;code&gt;cd /var/wwwsuwget http://ftp.drupal.org/files/projects/drupal-7.19.tar.gztar -xvzf drupal-7.19.tar.gz chown -R jeltsch:www-data drupal-7.19rm drupal-7.19.tar.gz cp -a drupal-7.18/sites/ drupal-7.19/&lt;/code&gt;The above cp command makes a copy of the complete site, which can take a long time and use lots of disk space. Instead, you can delete the &amp;ldquo;sites&amp;rdquo; subdirectory in the new drupal folder and make a link to the old &amp;ldquo;sites&amp;rdquo; subdirectory:&lt;code&gt;cd drupal-7.19rm -rf sitesln -s ../drupal-sites/ sites&lt;/code&gt;Here you should log into your site and put it into maintenance mode! &lt;code&gt;mysqldump -u root -p --databases drupal7_jeltsch_org drupal7_claudia_jeltsch_org drupal7_lammertlab_org &amp;gt; drupal7_all.sqlrm drupal7ln -s drupal-7.19/ drupal7&lt;/code&gt;Here you should click the link to the update script. After the updates were successfully performed you can put your site online again.** ****Drupal 9**Updating Drupal 9 is most easily done using composer:&lt;code&gt;composer update &amp;quot;drupal/core-*&amp;quot; --with-all-dependencies&lt;/code&gt;Also the modules can be updated. However, in my case the update was not always targeting the module that was actually in use but a module that was lower in the priority list in some other directory. For minor version updates:&lt;code&gt;composer update drupal/modulename --with-dependencies&lt;/code&gt;For major version updates:&lt;code&gt;composer require drupal/modulename:^2.0&lt;/code&gt;After this, don&amp;rsquo;t forget to visit 
 &lt;a href="https://yoursite.com/update.php" target="_blank" rel="noopener noreferrer nofollow"&gt;https://yoursite.com/update.php&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
!&lt;/p&gt;</description></item><item><title>Migrating the Mad Thought Blog to a new server (mysql, php)</title><link>https://jeltsch.org/en/migrating_the_mad_thought_blog_to_a_new_server_mysql_php/</link><pubDate>Wed, 04 Apr 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/migrating_the_mad_thought_blog_to_a_new_server_mysql_php/</guid><description>&lt;ol&gt;
&lt;li&gt;Dump the database data mysqldump &amp;ndash;host=localhost &amp;ndash;user=root -p journal &amp;gt;journal.sql&lt;/li&gt;
&lt;li&gt;Create the databse on the new machine mysql -u root -p CREATE DATABASE journal;&lt;/li&gt;
&lt;li&gt;Import the data into the database mysql -p -h localhost journal &amp;lt; journal.sql&lt;/li&gt;
&lt;li&gt;Create the user &amp;lsquo;journal&amp;rsquo; GRANT ALL PRIVILEGES ON &lt;em&gt;.&lt;/em&gt; TO &amp;lsquo;journal&amp;rsquo;@&amp;rsquo;localhost&amp;rsquo; IDENTIFIED BY &amp;lsquo;journal&amp;rsquo; WITH GRANT OPTION;&lt;/li&gt;
&lt;/ol&gt;</description></item><item><title>How to backup mysql databases (mysqlhotcopy, mysqldump)</title><link>https://jeltsch.org/en/how_to_backup_mysql_databases_mysqlhotcopy_mysqldump/</link><pubDate>Sat, 16 Dec 2006 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/how_to_backup_mysql_databases_mysqlhotcopy_mysqldump/</guid><description>&lt;p&gt;There are different possibilities. If you have access to the machine where mysql is running, you should use:&lt;code&gt;mysqlhotcopy&lt;/code&gt; On our RedHat 8 server you just type:&lt;code&gt;/usr/bin/mysqlhotcopy --user=root --password=sdjksjd journal /path/to/backup/directory&lt;/code&gt; Alternatively:&lt;code&gt;/usr/local/mysql/bin/mysqldump --user=username -p phpgedview &amp;gt;phpgedview&lt;/code&gt; The path of the command is specific for the mysql install on a MacOS X machine.If you want to back up from another machine you can use the mysqldump command: &lt;code&gt;mysqldump --host=hostname_or_ipaddress --user=username -p phpgedview &amp;gt;phpgedview&lt;/code&gt; This example backs up the database phpgedview which is on the machine hostname_or_ipaddress.The actual database files are in subdirectories in /var/lib/mysql in case you don&amp;rsquo;t remember their names.To automatically backup a database via the network you can put a file with the following content to the /etc/cron.hourly directory:&lt;code&gt;!/bin/sh mysqldump --host=hostname_or_ipaddress --user=USER -pPASSWORD journal &amp;gt;mysqldump_journal&lt;/code&gt; This would create every hour a fresh backupfile called mysqldump_journal in the /etc/cron.hourly directory.&lt;/p&gt;</description></item></channel></rss>