---
title: "Discussion on \"Building backupctl: what it took to replace a cron job with a backup service\" | Hashnode"
description: "Discussion on \"Building backupctl: what it took to replace a cron job with a backup service\". Building backupctl: what it took to replace a cron job with a backup service\nIf you've ever strung pg_dump | gzip | rclone into a cron job and promised yourself you'd clean it up later — this post is for you. I've been there. And \"later\" usually arri..."
url: "https://hashnode.com/posts/building-backupctl-what-it-took-to-replace-a-cron-job-with-a-backup-service/69e85ab6eb4e2f4719e53098"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Building backupctl: what it took to replace a cron job with a backup service](https://vineethnk.hashnode.dev/building-backupctl-what-it-took-to-replace-a-cron-job-with-a-backup-service?utm_source=hashnode&utm_medium=feed)

Building backupctl: what it took to replace a cron job with a backup service If you've ever strung pg\_dump | gzip | rclone into a cron job and promised yourself you'd clean it up later — this post is for you. I've been there. And "later" usually arri...

Apr 22 · 11 min read · vineethnk.hashnode.dev  
Read the article

-   [#backup](https://hashnode.com/tag/backup)
-   [#hexagonal-architecture](https://hashnode.com/tag/hexagonal-architecture)
-   [#nestjs](https://hashnode.com/tag/nestjs)
-   [#open-source](https://hashnode.com/tag/open-source)
-   [#restic](https://hashnode.com/tag/restic)

## Written by

[Vineeth N K](https://hashnode.com/@vnknotes)

@vnknotes

  
[View profile](https://hashnode.com/@vnknotes)

What I learned the hard way. So you do not have to.

Hi, I am Vineeth (VNK). I am a software developer and DevOps engineer based in Kochi, India. I work across backend (Node.js, NestJS, PHP), infrastructure (Docker, MySQL, Linux), and frontend (Vue, React). I am currently building and operating products with BEO, where I do everything from architecture decisions to staging deployments to fixing the things that break at 9 PM on a Friday. I write about real problems from real work - the kind of things you do not find in tutorials. Production incidents, hard-won architecture lessons, team and process notes, and the occasional opinion piece. If something I shipped, broke, or learned might save someone else half a day, it goes here. No fluff. No ghostwritten thought leadership. Just notes from the terminal.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
