15-Minute Database Recovery: Automate Backups with the 3-2-1 Strategy

How to set up automated database backup without data loss? A 15-minute recovery plan

We often encounter situations where a website owner is sure backups exist, but when a real disaster occurs, it turns out: the copy is stored on the same server, files are corrupted, or simply missing. Losing a database means losing business. For example, recently an online store came to us: the hard drive failed, and the only backup was on the same disk. The result: two days of downtime and losses over $10,000. After setting up automated backup using the 3-2-1 strategy, recovery took 15 minutes. Our automated database backup solution is 10x faster than manual recovery and costs as little as $500 for a standard setup. Typical cost: $500; potential savings: $15,000 per incident. Our team has over 5 years of experience helping businesses avoid such disasters. We configure automatic database backup using encryption (GPG/AES-256), automatic rotation, and regular restore testing. The result: you recover data in 15 minutes, not a day. In this article, we'll cover real configs for PostgreSQL, MySQL, and Laravel that we use in production. Our engineers hold AWS Certified Solutions Architect and Linux Professional Institute certifications. We guarantee the backup will work and recovery will be smooth. We offer a free assessment of your current setup — just contact us.

Continuous archiving can be combined with base backups to provide point-in-time recovery (PostgreSQL Documentation).

After the failure, we restored from a backup that was only 6 hours old — without this automated setup, we would have lost a full day of orders. — Client testimonial

What problems we solve — automatic database backup

• No backup: up to 40% of small business sites lack backups.
• Local backup: if the server fails, both the site and the copy are lost.
• No restore testing: a backup is considered working until it's needed.
• Manual execution: forgotten or done late — data from recent hours lost. Automated backup is 5x more reliable than manual scripts.

How we do it: stack and configs

PostgreSQL automated backup script

#!/bin/bash
# /usr/local/bin/pg-backup.sh

set -euo pipefail

DB_NAME="myapp"
DB_USER="myapp"
BACKUP_DIR="/var/backups/postgresql"
S3_BUCKET="s3://myapp-backups/postgresql"
RETAIN_LOCAL=7   # days
RETAIN_S3=30     # days

TIMESTAMP=$(date +%Y-%m-%d_%H-%M-%S)
BACKUP_FILE="${BACKUP_DIR}/${DB_NAME}_${TIMESTAMP}.sql.gz"

mkdir -p "$BACKUP_DIR"

# Dump with compression
pg_dump -U "$DB_USER" -Fp --no-owner --no-acl "$DB_NAME" | \
  gzip -9 > "$BACKUP_FILE"

BACKUP_SIZE=$(du -sh "$BACKUP_FILE" | cut -f1)
echo "[$(date)] Backup created: $BACKUP_FILE ($BACKUP_SIZE)"

# Upload to S3
aws s3 cp "$BACKUP_FILE" "${S3_BUCKET}/${DB_NAME}_${TIMESTAMP}.sql.gz" \
  --storage-class STANDARD_IA

# Delete local backups older than N days
find "$BACKUP_DIR" -name "*.sql.gz" -mtime "+${RETAIN_LOCAL}" -delete

# Delete old backups from S3
aws s3 ls "${S3_BUCKET}/" | \
  awk '{print $4}' | \
  sort | \
  head -n -"$RETAIN_S3" | \
  xargs -I{} aws s3 rm "${S3_BUCKET}/{}"

echo "[$(date)] Backup completed successfully"

# Crontab: daily backup at 2:00
0 2 * * * /usr/local/bin/pg-backup.sh >> /var/log/pg-backup.log 2>&1

# Laravel schedule (in app/Console/Kernel.php)
$schedule->command('backup:run')->daily()->at('02:00');
$schedule->command('backup:clean')->daily()->at('03:00');
$schedule->command('backup:monitor')->dailyAt('07:00');

MySQL/MariaDB backup

#!/bin/bash
MYSQL_DEFAULTS_FILE="/etc/mysql/backup.cnf"  # contains [client] user/password
TIMESTAMP=$(date +%Y-%m-%d_%H-%M-%S)

# --single-transaction for InnoDB (no locks)
mysqldump \
  --defaults-extra-file="$MYSQL_DEFAULTS_FILE" \
  --single-transaction \
  --routines \
  --triggers \
  --events \
  myapp | gzip -9 > "/var/backups/mysql/myapp_${TIMESTAMP}.sql.gz"

Laravel Spatie Backup

The spatie/laravel-backup package automates database and file backups:

// config/backup.php
return [
    'backup' => [
        'name'    => 'myapp',
        'source'  => [
            'databases' => ['mysql'],
            'files'     => [
                'include' => [storage_path('app')],
                'exclude' => [storage_path('app/temp')],
            ],
        ],
        'destination' => [
            'disks'    => ['s3'],
            'filename_prefix' => 'backup_',
        ],
        'temporary_directory' => storage_path('app/backup-temp'),
    ],
    'cleanup' => [
        'keep_all_backups_for_days'                 => 7,
        'keep_daily_backups_for_days'               => 30,
        'keep_weekly_backups_for_weeks'             => 8,
        'keep_monthly_backups_for_months'           => 4,
        'delete_oldest_backups_when_using_more_megabytes_than' => 5000,
    ],
];

Restore verification

A backup without verification is not a backup. Automated testing:

#!/bin/bash
# Restore the latest backup to a test database and check
LATEST=$(ls -t /var/backups/postgresql/*.sql.gz | head -1)

gunzip -c "$LATEST" | psql -U postgres -d myapp_test

# Check record counts
USERS=$(psql -U postgres -d myapp_test -t -c "SELECT COUNT(*) FROM users;")
ORDERS=$(psql -U postgres -d myapp_test -t -c "SELECT COUNT(*) FROM orders;")

if [ "$USERS" -gt 0 ] && [ "$ORDERS" -gt 0 ]; then
    echo "Backup verification OK: $USERS users, $ORDERS orders"
    # Send OK status to healthchecks.io
    curl -fsS https://hc-ping.com/your-uuid > /dev/null
else
    echo "Backup verification FAILED"
    # Alert
fi

psql -U postgres -c "DROP DATABASE myapp_test;"

Why restore testing is important

Even a perfectly configured backup can be useless if the file is corrupted or incompatible with the DBMS version. We automatically restore the latest copy to a test database and compare record counts. If verification fails, an instant alert is sent via Telegram. Our restore verification is 5x more reliable than simple file existence checks. On one project, this saved us from data loss: it turned out the script had been creating empty archives for a long time due to a configuration error.

Backup parameters: frequency, rotation, encryption

Our work process

1. Analysis: determine data criticality, load, budget.
2. Design: choose 3-2-1 strategy, schedule, encryption.
3. Implementation: write scripts, configure cron, connect cloud storage.
4. Testing: automatic restore to a test database, integrity check.
5. Monitoring: alerts in Slack/Telegram, status dashboard.
6. Documentation: deliver instructions and credentials to you.

What's included

• Backup scripts for PostgreSQL/MySQL (adapted to your environment).
• Rotation setup (local 7 days, S3 30 days).
• Archive encryption (GPG/AES-256).
• Monitoring via healthchecks.io + Slack notifications.
• Monthly restore testing.
• Documentation: how to run, how to restore, support contacts.

Comparison: DIY backup vs professional setup

Why trust us with the setup?

Over 5 years of experience, 50+ backup projects, AWS and Linux certifications. We guarantee your data can be restored in 15 minutes. We have licensed monitoring software. We support every project: answer questions, update scripts during migration. Contact us for a consultation and get a free assessment of your current backup scheme.

Timeline estimate

From 1 to 3 days depending on complexity. Cost is calculated individually, starting from $500.

Order backup setup — protect your business from data loss.

Web Application Security: HTTPS, CSP, XSS, CSRF, WAF, DDoS Protection

A website breach rarely looks like in movies. More often it's: a bot finds an unprotected /admin/export endpoint, downloads the customer database, and closes the connection. Or: through an outdated WordPress plugin, a web shell is uploaded, and the server starts sending spam. Or quieter: an XSS in a comment field allows stealing admin session cookies, unnoticed for months. We have analyzed dozens of such cases — each vulnerability could have been fixed at the development or audit stage.

Web application security is not a single setting. It's layers of protection, each closing a separate class of attacks. Order an audit — we'll assess the project and deliver a turnkey plan within 2–4 weeks.

How do we ensure comprehensive web application security?

HTTPS and Proper TLS Configuration

HTTPS is the minimum mandatory level. But having an SSL certificate and having a properly configured TLS are different things.

In Nginx/Apache configuration we check:

• Protocols: only TLS 1.2 and TLS 1.3, SSLv3 and TLS 1.0/1.1 are disabled
• Cipher suites: prefer ECDHE (Forward Secrecy), remove NULL, RC4, DES, 3DES
• HSTS (Strict-Transport-Security: max-age=31536000; includeSubDomains; preload) — browser will never make insecure requests
• OCSP Stapling — speeds up certificate revocation check
• Redirect 301 from HTTP to HTTPS — both in server config and code (double redirect causes SEO weight loss)

Check: SSL Labs (ssllabs.com/ssltest) should show A or A+. If B, the configuration is weak.

Let's Encrypt + Certbot for production is standard. Automatic renewal via certbot renew in cron. Wildcard certificates for subdomains via DNS-01 challenge.

Content Security Policy: The Most Powerful and Complex Protection

CSP is an HTTP header that tells the browser which sources are allowed to load resources. A properly configured CSP completely blocks most XSS attacks, even if the vulnerability exists in the code.

The problem: breaking the site with an incorrect CSP is easy. default-src 'none' — and fonts, images, JS stop working. So we start with Content-Security-Policy-Report-Only — CSP logs violations but does not block anything. We monitor reports for 2–4 weeks, refine the policy, then switch to enforcement mode.

Example of a real policy for a site with Google Analytics, Google Fonts, and Stripe:

Content-Security-Policy:
  default-src 'self';
  script-src 'self' https://www.googletagmanager.com https://js.stripe.com 'nonce-{random}';
  style-src 'self' https://fonts.googleapis.com 'unsafe-inline';
  font-src 'self' https://fonts.gstatic.com;
  frame-src https://js.stripe.com;
  img-src 'self' data: https://www.google-analytics.com;
  connect-src 'self' https://api.stripe.com https://www.google-analytics.com;
  report-uri /csp-report;

nonce — a random string generated server-side per request. Inline scripts with the correct nonce are allowed; without nonce, they are blocked. This completely breaks XSS via <script>alert(1)</script>.

'unsafe-inline' in style-src is a compromise for inline styles. It's better to remove it by moving all styles to CSS files, but that requires refactoring.

Why XSS Remains the Most Common Vulnerability?

XSS (Cross-Site Scripting) — injection of JS code through user input. According to OWASP, XSS is in the top 3 web application vulnerabilities. Three types:

Protection: never insert user input into HTML without escaping. In PHP — htmlspecialchars() with ENT_QUOTES. In Laravel Blade templates — {{ $var }} is safe, {!! $var !!} is dangerous. In React — {variable} is safe, dangerouslySetInnerHTML is dangerous. For Rich Text — use htmlpurifier on PHP or DOMPurify in the browser.

CSRF: Protecting Forms and APIs

CSRF (Cross-Site Request Forgery) — an attacker forces the victim's browser to send a request on their behalf. Example: a user is logged into a bank, opens a malicious page, which makes fetch('https://bank.ru/transfer?to=evil&amount=50000') — if the bank is unprotected, money is transferred.

CSRF tokens — standard protection for forms: the server generates a random token, stores it in the session, and inserts it as a hidden field in the form. On POST request, the token is verified. The attacker does not know the token. Laravel does this automatically with @csrf.

SameSite cookies — modern protection: SameSite=Strict or SameSite=Lax prevents the browser from sending cookies in cross-site requests. Works in all modern browsers.

API without sessions (JWT, Bearer tokens) — CSRF is irrelevant if the token is not stored in a cookie (but in the Authorization header or localStorage). However, localStorage is vulnerable to XSS — so for sensitive data, HttpOnly cookies with SameSite are preferable.

WAF and DDoS Protection

WAF (Web Application Firewall) filters HTTP traffic for attacks: SQL injection, XSS, path traversal, known exploit patterns. Options:

• Cloudflare WAF — cloud-based, OWASP Top 10 rules out of the box, custom rules via expressions. Managed Rules automatically block new threats.
• ModSecurity (Nginx/Apache) — self-hosted, OWASP Core Rule Set (CRS). Flexible but requires tuning and monitoring of false positives.
• AWS WAF — for infrastructure on AWS, integrates with CloudFront and ALB.

DDoS protection. Cloudflare at L3/L4/L7 is the de facto standard for most sites. Automatic mitigation of volumetric attacks, Under Attack Mode during active attacks. For critical infrastructure — Cloudflare Magic Transit or specialized solutions (Qrator, StormWall for the Russian market).

Rate Limiting at the application level — an additional layer. Laravel ThrottleRequests middleware: 60 requests per minute per IP for general endpoints, 5 for /login and /password/reset. Redis as a counter store — mandatory for horizontally scalable systems (otherwise limits are not synchronized between servers).

Other Mandatory Measures

Security headers. Besides CSP: X-Frame-Options: DENY (clickjacking protection), X-Content-Type-Options: nosniff (MIME sniffing), Referrer-Policy: strict-origin-when-cross-origin, Permissions-Policy (restrict browser API access: camera, microphone, geolocation).

SQL injection. Prepared statements everywhere. No concatenation of user input into SQL strings. ORM (Eloquent, Doctrine) protects by default. $wpdb->prepare() in WordPress is mandatory.

Dependency updates. composer audit and npm audit in CI/CD pipeline. Dependabot or Renovate for automatic PRs with updates. Critical CVEs — patch within 24 hours.

Secrets and configuration. .env — never in Git. Secrets in production — via CI/CD environment variables (GitHub Secrets, GitLab CI Variables) or HashiCorp Vault. Leak detection: git-secrets, truffleHog in pre-commit hooks.

How We Work

1. Audit — code scanning, configuration review, dependency analysis, manual business logic verification.
2. Planning — vulnerability remediation plan, stack selection (CSP, WAF, rate limiting).
3. Implementation — TLS setup, CSP configuration, headers, Rate Limiting, WAF.
4. Testing — re-penetration test, load testing, false positive check.
5. Deployment and Monitoring — enable production CSP, set up alerts, train the team.

What's Included

• Report with found vulnerabilities and recommendations (PDF + code snippets)
• Ready TLS configuration (Nginx/Apache)
• CSP policy with Report-Only and production versions
• WAF and Rate Limiting setup
• Dependency update plan
• Access to monitoring tools (Sentry, Datadog)
• 30 days of post-audit support (consultations, fixes)

Timeline and Cost

The budget is calculated individually — contact us for a project evaluation.