# Joplin server on a PI5 and power failures/lower disk writes

**URL:** <https://discourse.joplinapp.org/t/joplin-server-on-a-pi5-and-power-failures-lower-disk-writes/45206>\
**Category:** Support\
**Created:** [4 May 2025 07:08 UTC](https://discourse.joplinapp.org/t/joplin-server-on-a-pi5-and-power-failures-lower-disk-writes/45206 "2025-05-04T07:08:22Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![DBDigital](https://avatars.discourse-cdn.com/v4/letter/d/df705f/32.png) [@DBDigital](https://discourse.joplinapp.org/u/DBDigital)\
**Post date:** [4 May 2025 07:08 UTC](https://discourse.joplinapp.org/t/joplin-server-on-a-pi5-and-power-failures-lower-disk-writes/45206/1 "2025-05-04T07:08:22Z")

</div>

### Operating system

Linux

### Joplin version

3.3.13

### Sync target

Joplin Server

### What issue do you have?

I have set up a Joplin Server on a Pi5 with postgres as the database and I was wondering about power failures and corruption. It is writing to a Fat32 SD card, and of course if doing a sync is occuring during a power failure I am betting there will be corruption of the database. Is there any way to minimize this? Or recover from it? Or is the system robust enough not to worry about it?

I currently have it in my home directory in docker/joplin where my compose file is as well. I assume backing up that folder is all I need to do to have a copy of everything should it go sideways?

I also turned off heartbeats in the Joplin server admin settings to cut down on the number of writes to the SD card, is there anything else I should/could turn off to lower the writes further? And I assume turning off the heartbeats isn't a issue?

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [4 May 2025 08:10 UTC](https://discourse.joplinapp.org/t/joplin-server-on-a-pi5-and-power-failures-lower-disk-writes/45206/2 "2025-05-04T08:10:18Z")

</div>

For sure a power failure wouldn't cause any corruption so you shouldn't have to worry about this. Usually database corruption happens when the disk itself is failing so maybe an advise would be to use a quality disk. And also backups of course

---

<div class="post-metadata">

**Author:** ![DBDigital](https://avatars.discourse-cdn.com/v4/letter/d/df705f/32.png) [@DBDigital](https://discourse.joplinapp.org/u/DBDigital)\
**Post date:** [9 May 2025 02:07 UTC](https://discourse.joplinapp.org/t/joplin-server-on-a-pi5-and-power-failures-lower-disk-writes/45206/3 "2025-05-09T02:07:03Z")

</div>

Thanks Laurent, that is wonderful news. I hope to move from the SDCard to a SSD eventually which has a lot more durability. But I was careful to get a quality card first.

With regard to backups, did I have it right and just backup/copy the docker/joplin folder to another drive and restore that if needed? Of course doing  
Docker compose down  
first.

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [9 May 2025 07:51 UTC](https://discourse.joplinapp.org/t/joplin-server-on-a-pi5-and-power-failures-lower-disk-writes/45206/4 "2025-05-09T07:51:14Z")

</div>

It depends on the storage. By default, the server saves data to an SQLite file within the image I think, so you'd need to backup that SQLite file. If you use Postgres, you need pg\_dump. Basically you only need to backup the database

---

<div class="post-metadata">

**Author:** ![DBDigital](https://avatars.discourse-cdn.com/v4/letter/d/df705f/32.png) [@DBDigital](https://discourse.joplinapp.org/u/DBDigital)\
**Post date:** [12 May 2025 02:43 UTC](https://discourse.joplinapp.org/t/joplin-server-on-a-pi5-and-power-failures-lower-disk-writes/45206/5 "2025-05-12T02:43:48Z")

</div>

Ah I thought backing up the files would be enough. Glad to find out different now.

I did some searching and found:

> [@Function request: Joplin server data export](https://discourse.joplinapp.org/t/function-request-joplin-server-data-export/20826):
>
> Postgres is upgraded from 13.4 to 14.0. You need to delete all data and install it completely before it can run There is a problem. How should I export data from Joplin server before upgrading Postgres? Joplin server usually has multiple accounts, and the data of all accounts cannot be completely exported from Joplin client It is strongly recommended that Joplin server add the export function. The exported data includes accounts, notes, sharing, etc I can't speak English. I use Chinese Englis…

Where you mentioned two commands. I tried them but got a permissions error:  
permission denied while trying to connect to  
the Docker daemon socket at unix:///var/run/d  
ocker.sock: Get "http://%2Fvar%2Frun%2Fdocker  
.sock/v1.49/containers/joplin-server\_db\_1/jso  
n": dial unix /var/run/docker.sock: connect:  
permission denied

So I have the location right, now if I could figure out what permission is missing....

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/3X/1/c/1c948e33314e232a0927789508474d8624f4270b.png) [@system](https://discourse.joplinapp.org/u/system)\
**Post date:** [11 June 2025 02:44 UTC](https://discourse.joplinapp.org/t/joplin-server-on-a-pi5-and-power-failures-lower-disk-writes/45206/6 "2025-06-11T02:44:40Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.