Database Auto Backup v1.0.1

Database Backup System

A reliable, automated solution for securely backing up your MySQL/MariaDB databases
— locally or to the cloud — with comprehensive notification support.

Written in Go, it's optimized for large-scale backups with configurable part sizes (buffer)
and multi-threaded execution for maximum performance.​

Features​

• Secure & Reliable
  Back up single or multiple databases with full control over credentials and storage format.
• Storage Options
  Store backups:
  • Locally using any directory
  • To S3 or S3-compatible storage with multipart upload support
  • RClone (Drive-Based Storage) e.g Google Drive, One Drive, TeraBox
• Automatic Purge
  Remove old backups automatically with configurable expiration settings.
• Webhook Notifications
  Get real-time updates to:
  • Custom Webhooks
  • Discord Channels (rich embed messages supported)
• Customizable
  • Flexible filename and timestamp formatting
  • Placeholder-based messages
  • Discord embeds with thumbnails, colors, and detailed fields
  • Multi-Threaded Workers (fast and efficient)

Configuration Example​

# =============================
# DATABASE AUTO BACKUP
# =============================
# Developed By Muhammad Yudha Abhista (@Yusta)
# Licensed by Raznar
# =============================
database:
- label: "YOUR_LABEL" # A unique name to identify this database backup
host: "127.0.0.1" # Database server IP (change if not local)
port: 3306 # Default port for MySQL/MariaDB
username: "your_user" # Your database login username
password: "your_password" # Your database login password
database_name: [] # List of databases to back up (leave empty to back up all)
auto_purge:
enabled: false
expire_time: 3 # Number of days before a file is considered expired
# ==================
# STORAGE SETTINGS
# ==================
storage:
workers: 2 # Number of concurrent worker threads to use for processing backups.
max_retry: 3 # Maximum number of retry attempts
format:
file_date_time_format: "2006-01-02_15-04-05" # Format used for timestamps in backup file names
file_format: "%database_name%-%datetime%.sql" # Template for naming the backup file
directory:
out: "/var/backups/out" # Path to store final (processed/compressed) backup files
archive: "/var/backups/archive" # Temporary archive location before being moved to final storage
method: "local" # Final storage method: "local" (store on disk) or "s3" (upload to object storage) or "rclone" for various options
# Optional S3 configuration — only used if method is set to "s3"
s3:
concurrent_upload: 4 # Number of concurrent upload parts (multi-part upload)
endpoint: "https://s3.raznar.id" # Custom S3-compatible endpoint
region: "us-west-2" # Region used for the S3 bucket
bucket_name: "raznar-backup" # Bucket where backups will be stored
access_key: "YOUR_ACCESS_KEY" # Your S3 access key
secret_key: "YOUR_SECRET_KEY" # Your S3 secret key
max_part_size: 8388608 # Max size of each upload part (8MB)
storage_class: "STANDARD" # S3 storage class (e.g., STANDARD, GLACIER)
use_path_style: true # Use path-style URLs (true for custom endpoints like MinIO or Wasabi)
max_workers: 5 # Max parallel uploads for S3
# Optional rclone configuration — if using rclone as a backend
rclone:
remote_name: "drive" # Remote name defined in your rclone.conf
config_file: "rclone.conf" # Path to rclone config file
concurrent_upload: 4 # Number of concurrent rclone uploads
buffer_size: 33554432 # Buffer size per transfer (32MB)
webhooks:
custom:
- enabled: true
url: "https://hooks.example.com/webhook"
content_type: "application/json"
placeholders:
timestamp: "02 Jan 2006 15:04"
start_backup: '{"event": "start", "database": "%database_name%", "label": "%database_label%", "time": "%timestamp%"}'
failed_backup: '{"event": "failed", "database": "%database_name%", "error": "%error_message%", "time": "%timestamp%"}'
success_backup: '{"event": "success", "database": "%database_name%", "size": "%backup_size%", "time": "%timestamp%"}'
complete_backup: '{"event": "complete", "label": "%database_label%", "total_success": %total_success%, "total_failed": %total_failed%, "time": "%timestamp%"}'
discord:
- enabled: true
url: "https://discord.com/raznar" # Replace with your actual Discord webhook URL
placeholders:
timestamp: "02 Jan 2006 15:04"
custom_messages:
enabled: false
start_backup: '{"content": "[%database_label%] Starting to backup the database"}'
failed_backup: '{"content": "[%database_label%] Failed backup database %database_name%"}'
success_backup: '{"content": "[%database_label%] Success backup database %database_name%"}'
embed_messages:
start_backup:
author:
name: "Backup System"
title: " Database Backup Started"
description: "The backup process for %database_label% has been initiated."
color: 16776960
fields:
- name: " Database Label"
inline: true
value: "%database_label%"
- name: " Timestamp"
inline: true
value: "%timestamp%"
footer:
text: "Backup process is now running..."
thumbnail:
url: "https://cdn.discordapp.com/attachments/1114219896822300862/1353315676437090364/cloud-computing.png"
failed_backup:
author:
name: "Backup System"
title: " Database Backup Failed"
description: "The backup process failed for %database_label%."
color: 15158332
fields:
- name: " Database Name"
inline: true
value: "%database_name%"
- name: " Error Details"
inline: false
value: "%error_message%"
footer:
text: "Please check the logs for further details."
thumbnail:
url: "https://cdn.discordapp.com/attachments/1114219896822300862/1353315676118319145/cloud.png"
success_backup:
author:
name: "Backup System"
title: " Database Backup Successful"
description: "Backup completed successfully for %database_label%!"
color: 3066993
fields:
- name: " Database Name"
inline: true
value: "%database_name%"
- name: " Backup Size"
inline: true
value: "%backup_size%"
- name: " Timestamp"
inline: true
value: "%timestamp%"
footer:
text: "Backup has been securely stored."
thumbnail:
url: "https://cdn.discordapp.com/attachments/1114219896822300862/1353315676806185015/check.png"
complete_backup:
author:
name: "Backup System"
title: " Database Backup Completed"
description: "The backup process for %database_label% has completed successfully."
color: 65280
fields:
- name: " Database Label"
inline: true
value: "%database_label%"
- name: " Total Size"
inline: true
value: "%total_size%"
- name: " Successful Backups"
inline: true
value: "%total_success%"
- name: " Failed Backups"
inline: true
value: "%total_failed%"
- name: " Total Backups"
inline: true
value: "%total_count%"
- name: " Timestamp"
inline: true
value: "%timestamp%"
footer:
text: "Backup process has finished."
thumbnail:
url: "https://cdn.discordapp.com/attachments/1114219896822300862/1353322887972524113/delivery.png"

Click to expand...

Use Cases​

• Web hosting companies that need automated daily backups
• Internal IT teams managing critical SQL data
• Developers wanting peace of mind before deployments
• Any service requiring reliable offsite backup support

Why Us?​

Simple YAML configuration​

One-click install – get started instantly​

Zero dependencies – just run the binary​

Discord-ready out-of-the-box​

Works with any S3-compatible cloud provider​

Custom webhook support for full integration into your workflow​