Quick Start
Create your first backup in 5 minutes
Quick Start
Get up and running with your first database backup in just a few minutes.
This guide assumes you've already installed Velld. If not, start there first.
Your First Backup
Access the Dashboard
Open http://localhost:3000 and create your account.
The dashboard gives you an overview of all your backups, success rates, and storage usage.
Add a Database Connection
- Navigate to Connections in the sidebar
- Click Add Connection
- Fill in your database details:
Name: My Production DB
Type: PostgreSQL
Host: host.docker.internal
Port: 5432
Database: myapp_production
Username: postgres
Password: ••••••••
Use host.docker.internal
instead of localhost
to connect to databases running on your host machine.
For remote databases behind a firewall:
Expand the SSH Tunnel section and enable it:
SSH Enabled: ✅
SSH Host: bastion.example.com
SSH Port: 22
SSH Username: deploy
SSH Auth Method: Private Key or Password
SSH tunnels provide secure access to databases that don't allow direct external connections. See Database Configuration for details.
- Click Test Connection to verify it works
- Click Save Connection
Run Your First Backup
From the Connections page:
- Find your newly created connection
- Click Backup Now
- Watch the backup progress in real-time
Your backup will appear in the History page once complete!
Schedule Automatic Backups
Never miss a backup again:
- Go to Connections
- Click the Schedule icon on your connection
- Choose your backup frequency:
- Hourly - Every hour
- Daily - Once per day at a specific time
- Weekly - Once per week
- Monthly - Once per month
- Custom - Use a cron expression
Example schedules:
# Every day at 2 AM
0 2 * * *
# Every 6 hours
0 */6 * * *
# Every Sunday at midnight
0 0 * * 0
-
Set retention policy (optional):
- Keep backups for 7, 14, 30, or 90 days
- Older backups are automatically deleted
-
Click Save Schedule
Your backups will now run automatically! You'll receive notifications for each backup.
Download or Compare Backups
From the History page:
Download a backup:
- Click the download icon next to any backup
- The backup file will download to your computer
Compare two backups:
- Click Compare Backups or click the compare icon on any backup
- Select two backups to compare
- View a detailed diff showing what changed between them
The compare feature is perfect for tracking schema changes or data migrations!
Common Use Cases
Production Database Backups
Schedule daily backups with 30-day retention:
Connection: production-db
Schedule: 0 2 * * * (Daily at 2 AM)
Retention: 30 days
Notifications: ✓ Email on failure
Development Database Snapshots
Run on-demand backups before migrations:
Connection: dev-db
Schedule: Manual only
Retention: 7 days
Notifications: None
Multi-Database Setup
Backup all your databases with different schedules:
PostgreSQL (Main DB):
Schedule: 0 */6 * * * (Every 6 hours)
Retention: 14 days
MySQL (Analytics):
Schedule: 0 3 * * * (Daily at 3 AM)
Retention: 30 days
MongoDB (Sessions):
Schedule: 0 */12 * * * (Every 12 hours)
Retention: 7 days
Pro Tips
1. Test Your Backups
Don't just create backups—test them! Download a backup and try restoring it to a test database.
2. Use Descriptive Names
Name your connections clearly:
- ✅
production-postgres-main
- ✅
staging-mysql-analytics
- ❌
database1
- ❌
db
3. Set Up Email Notifications
Get alerted when backups fail:
- Go to Settings → Notifications
- Enable email notifications
- Configure your SMTP settings
- Choose notification preferences (failures only, all backups, etc.)
4. Monitor Your Storage
Keep an eye on the Storage Used metric on the dashboard. Set up retention policies to automatically clean up old backups.
5. Use Connection Groups
If you have many databases, organize them by environment:
prod-*
for productionstaging-*
for stagingdev-*
for development
Restoring a Backup
Always restore to an empty database. See Restore Best Practices.
Using Velld UI
- Go to History page
- Click Restore on your backup
- Select target database (must be empty)
- Confirm
For production: Create new database → Restore → Test → Switch app connection.
Manual Restoration
PostgreSQL
createdb myapp_new
psql -U postgres -d myapp_new < backup.sql
MySQL
mysql -u root -p -e "CREATE DATABASE myapp_new;"
mysql -u root -p myapp_new < backup.sql
MongoDB
mongorestore --archive=backup.archive --gzip