<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Backup on Percona Community</title><link>https://percona.community/tags/backup/</link><description>Recent content in Backup on Percona Community</description><generator>Hugo 0.147.5</generator><language>en</language><lastBuildDate>Mon, 14 Sep 2026 11:00:00 +0000</lastBuildDate><atom:link href="https://percona.community/tags/backup/index.xml" rel="self" type="application/rss+xml"/><item><title>Prove the Backup: A Percona Distribution for PostgreSQL Restore Drill on Windows</title><link>https://percona.community/blog/2026/09/14/percona-postgresql-restore-drill-on-windows/</link><pubDate>Mon, 14 Sep 2026 11:00:00 +0000</pubDate><guid isPermaLink="true">https://percona.community/blog/2026/09/14/percona-postgresql-restore-drill-on-windows/</guid><description>&lt;p>A backup is only useful if it can be restored. This lab seeds a source database, takes a logical archive, deliberately deletes the source database, restores into a clean target, and checks the recovered state. Percona Distribution for PostgreSQL does not provide a native Windows package. Windows is only the Docker Desktop host; PostgreSQL and its utilities run in Linux containers.&lt;/p>
&lt;p>The current Percona 17 Docker documentation uses &lt;code>percona/percona-distribution-postgresql:17.11&lt;/code>, requires &lt;code>POSTGRES_PASSWORD&lt;/code>, and exposes PostgreSQL on container port 5432. Docker Desktop is the recommended way to obtain Docker Engine, the CLI, and Compose on Windows. &lt;a href="https://docs.percona.com/postgresql/17/docker.html" target="_blank" rel="noopener noreferrer">Percona Docker guide&lt;/a> · &lt;a href="https://docs.docker.com/compose/install/" target="_blank" rel="noopener noreferrer">Docker Compose installation&lt;/a>&lt;/p></description></item><item><title>Backups for MySQL With mysqldump</title><link>https://percona.community/blog/2023/03/10/backups-for-mysql-with-mysqldump/</link><pubDate>Fri, 10 Mar 2023 00:00:00 +0000</pubDate><guid isPermaLink="true">https://percona.community/blog/2023/03/10/backups-for-mysql-with-mysqldump/</guid><description>&lt;h2 id="basic-usage">Basic Usage&lt;/h2>
&lt;p>&lt;a href="https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html" target="_blank" rel="noopener noreferrer">mysqldump&lt;/a> is a client utility that can be used for doing logical backups. It will generate the necessary SQL statements to reproduce the original database.&lt;/p>
&lt;p>
&lt;figure>&lt;img width="1200" height="799" sizes="(max-width: 1200px) 100vw, 1200px" srcset="https://percona.community/blog/2023/03/backup_hu_57edb02d454db55c.webp 768w, https://percona.community/blog/2023/03/backup_hu_1cb4869670b61f25.webp 480w, https://percona.community/blog/2023/03/backup_hu_c818de712ebc5b3a.webp 1200w" src="https://percona.community/blog/2023/03/backup_hu_c818de712ebc5b3a.webp" alt="Backup" loading="lazy" />&lt;figcaption>Backup by Nick Youngson CC BY-SA 3.0 Pix4free&lt;/figcaption>&lt;/figure>&lt;/p>
&lt;p>The following statements are some common uses of mysqldump:&lt;/p>
&lt;ol>
&lt;li>&lt;code>mysqldump -u username -p database_name [table_name] &amp;gt; dump.sql&lt;/code>&lt;/li>
&lt;li>&lt;code>mysqldump -u username -p --databases db1_name db2_name &amp;gt; dump.sql&lt;/code>&lt;/li>
&lt;li>&lt;code>mysqldump -u username -p --all-databases &amp;gt; dump.sql&lt;/code>&lt;/li>
&lt;/ol>
&lt;p>The first example is for backing up a single database. If you need to back up some specific tables instead of the whole database, write their names, space-separated.&lt;/p></description></item></channel></rss>