How to Download a Backup File (.sql)

After creating a backup on the Nobregas MySQL Panel, you can download the .sql file to your local machine. Downloaded backups serve as offline copies you can store, share, or use to restore your database on any MySQL server.

Step-by-Step: Downloading a Backup

1. Log in at mysql.nobregas.org.
2. Click Backups in the top navigation bar.
3. Find the backup you want to download in the backup list.
4. Click the Download button on that backup's row.
5. Your browser downloads the .sql file to your default downloads folder.

Understanding the .sql File

The downloaded file is a plain-text SQL dump containing:

-- Table structure and data
CREATE TABLE `users` (...);
INSERT INTO `users` VALUES (...);

-- Views, triggers, procedures
CREATE VIEW `active_users` AS ...;

You can open it with any text editor (VS Code, Notepad++, Sublime Text) to inspect its contents.

File Naming Convention

Backup files are named with the database name and timestamp, making it easy to identify which backup is which:

databasename_2026-03-15_14-30-00.sql

What to Do with Downloaded Backups

Local Storage

Keep a copy on your local machine, external drive, or cloud storage (Google Drive, Dropbox) as an additional safety layer.

Restore on Another Server

Import the .sql file into any MySQL server using:

• phpMyAdmin — Use the Import tab.
• MySQL CLI — Run mysql -u user -p database < backup.sql.
• Nobregas Panel — Use the Restore feature on the Backups page.

Share with a Developer

Send the .sql file to a developer who needs a copy of the database for development or debugging. Remove sensitive data first if necessary.

Version Control

Store backups alongside your code releases to maintain database snapshots that correspond to specific application versions.

Download Tips

• Download before deleting — If you plan to delete old backups from the panel to free quota, download them first.
• Verify the file — Open the downloaded .sql file briefly to confirm it contains data (not an empty or corrupted file).
• Compress large files — For databases over 100 MB, compress the .sql file with ZIP or GZIP to save local storage space.
• Automate offsite backups — Download backups regularly and store them in a separate location from your server.