How do I back up a Node.js site?

Why Node.js Backups Matter

At HostingDuty, we treat backups as a non-negotiable part of our hosting infrastructure. A Node.js application relies on three critical components: the application code, the runtime environment, and the persistent data layer. If any of these are lost, your site goes down. Unlike static sites, dynamic Node.js apps require a multi-layered backup strategy.

1. Backing Up the Codebase

The first step is version control. We never store code directly on the server as the primary source of truth. Instead, we use Git repositories (GitHub, GitLab, or Bitbucket). This ensures that every change is tracked, and you can revert to a previous state instantly. For HostingDuty customers, we recommend enabling automatic pushes to your remote repository after every successful deployment.

To automate this, we often use CI/CD pipelines. If you are setting up your own pipeline, check our guide on CI/CD pipelines for Node.js for detailed steps. This ensures that your code is never lost due to server hardware failure.

2. Database Backups

The most critical data in a Node.js app is usually stored in a database. Whether you use PostgreSQL, MongoDB, MySQL, or Redis, the backup method depends on the engine.

PostgreSQL

For PostgreSQL, we use the pg_dump utility. This creates a logical backup of the database. You can schedule this using a cron job:

``bash 0 2 * * * pg_dump -U username dbname > backup_$(date +\%F).sql `

This script runs daily at 2 AM. We recommend storing these backups in an off-site location like AWS S3 or a secure cloud storage bucket. Learn more about database security in our PostgreSQL security best practices.

MongoDB

For MongoDB, the mongodump tool is the standard. It creates a binary backup of your data.

`bash mongodump --uri="mongodb://username:password@host:port/dbname" --out=/backup/path `

Just like PostgreSQL, we automate this and move the files to cold storage. For more details on managing MongoDB backups, see our MongoDB backup guide.

3. Environment Variables and Configuration

Node.js apps rely heavily on environment variables stored in .env files. These contain API keys, database credentials, and secrets. Never commit these to Git. Instead, we back up the .env` file manually or via a secure secret management tool like HashiCorp Vault. At HostingDuty, we encrypt these files at rest and rotate keys regularly.

4. Scheduling and Automation

Manual backups are prone to human error. We use cron jobs on Linux servers or task schedulers in cloud environments to automate the process. For example, a daily backup ensures you lose at most one day's worth of data. For more on scheduling tasks, read our Cron job basics.

5. Testing Restores

A backup is only useful if you can restore from it. We test restores monthly to ensure the backup files are not corrupted. This involves spinning up a temporary instance, restoring the database, and verifying the application functions correctly. For a step-by-step on restoring databases, see our Database restore procedures.

6. Off-Site Storage

Local backups are vulnerable to physical disasters. We recommend using cloud storage for off-site backups. AWS S3, Google Cloud Storage, or Azure Blob Storage are excellent choices. HostingDuty integrates with these services for seamless backup storage. For more on cloud storage options, see our Cloud storage comparison.

7. Incremental vs. Full Backups

Full backups are comprehensive but time-consuming. Incremental backups only save changes since the last backup, making them faster and less storage-intensive. For large databases, we prefer incremental backups combined with periodic full backups. Learn more about backup strategies in our Backup strategies glossary.

8. Security Considerations

Backups contain sensitive data. We encrypt all backup files before storage. At HostingDuty, we use AES-256 encryption for all stored backups. For more on encryption, see our Encryption at rest guide.

Conclusion

Backing up a Node.js site requires a systematic approach covering code, data, and configuration. By automating these processes and testing restores regularly, we ensure your site remains resilient. For more on Node.js hosting, check out our Node.js hosting overview.

External Resources

For additional insights on backup strategies, we recommend reading How to Back Up Your Website from PCMag.