this post was submitted on 05 Oct 2023
0 points (NaN% liked)

Selfhosted

39937 readers
373 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Hello everyone!

I had a container with a DB crap itself yesterday so I'm trying to speed up my learning to back up stuff.

I came across a script that taught me how to back-up a containerized postgres db at given intervals and it works. I managed to create db dumps and restore them. I've documented everything and now my whole docker-compose/env etc are on git control.

There's one part of the script I don't decypher but I'd like to maybe change it. It is about the number of back-up copies.

Here's the line from the tutorial: ls -1 /backup/*.dump | head -n -2 | xargs rm -f

Can someone explain to me what this line does? I'd like to keep maybe 3 copies just in case the auto-backup backs up a rotten one.

Thanks!

Full code below:

backup:
    image: postgres:13
    depends_on:
      - db_recipes
    volumes:
      - ./backup:/backup
    command: >
      bash -c "while true; do
        PGPASSWORD=$$POSTGRES_PASSWORD pg_dump -h db-postgresql -U $$POSTGRES_USER -Fc $$POSTGRES_DB > /backup/$$(date +%Y-%m-%d-%H-%M-%S).dump
        echo ""Backup done at $$(date +%Y-%m-%d_%H:%M:%S)""
        ls -1 /backup/*.dump | head -n -2 | xargs rm -f
        sleep 86400
      done"
top 7 comments
sorted by: hot top controversial new old
[–] doeknius_gloek@feddit.de 0 points 1 year ago* (last edited 1 year ago) (1 children)

This line seems to list all dumps and then deletes all but the two most recent ones.

In detail:

  • ls -1 /backup/*.dump lists all files ending with .dump alphabetically inside the /backup directory
  • head -n -2 returns all filenames except the two most recent ones from the end of the list
  • xargs rm -f passes the filenames to rm -f to delete them

Take a look at explainshell.com.

[–] klay@lemmy.world 0 points 1 year ago (1 children)

I just looked up the man page, and actually head -n -2 means "everything up to but not including the last two lines", so this should always leave two files remaining.

[–] doeknius_gloek@feddit.de 0 points 1 year ago (1 children)

You're right, I edited my comment. Thanks!

[–] mnmalst@lemmy.zip 0 points 1 year ago (1 children)

Your xargs comment is still wrong tho. It deletes ALL but the most recent two files.

[–] doeknius_gloek@feddit.de 0 points 1 year ago

Fixed, thanks.

[–] tburkhol@lemmy.world 0 points 1 year ago (1 children)

Others have explained the line.

Worth noting that not all implementations of head accept negative line counts (i.e. last n lines), and you might substitute tail.

i.e.: ls -1 /backup/*.dump | tail -2 | xargs rm -f

[–] doeknius_gloek@feddit.de 0 points 1 year ago* (last edited 1 year ago)

~~Yeah, tail would be the more obvious choice instead of negating head.~~

Fuck, I need coffee. @klay@lemmy.world is right (again).