What DB-Backup Manager offers and how it protects business databases.

Product Overview

DB-Backup Manager is a database backup management application for administrators who need a reliable way to protect business databases. It replaces fragile scripts, manual exports, and scattered backup folders with a clear backup-console workflow.

The application helps IT teams connect to database servers, select databases, create backup jobs, schedule automatic runs, copy backups to storage destinations, send email alerts, review history, and restore safely when needed.

Core Capabilities

Supported Database Engines

Backup tools are important because they are the proven database-native tools that create consistent backups and reliable restores. The application provides scheduling, UI, security, history, destinations, and automation around those tools.

Storage Destination Guides

Open Destinations, add or select a destination, configure it, run the available connection and write tests, enable it, and save. Then edit the backup job and select that destination.

Local Folder or External Drive

Select Local and enter an absolute Windows folder such as D:\DatabaseBackups. The application account and Windows service account need create, write, read, and delete permissions. Use Test Write Permission before assigning the destination to a job.

NAS or Network Share

Select NAS / Share and enter a UNC path such as \\SERVER\Backups\Database. Enter a dedicated network-share account when the Windows service account does not already have access. Confirm that both the desktop application and service can reach the share, then run the write test.

SFTP Server

Select SFTP, enter the server, SSH port, username, password, and remote folder. Use a restricted account that can write only to the required backup folder. Test the connection and write permission before enabling the destination.

OneDrive Personal

Select OneDrive Personal, enter a folder such as DatabaseBackups/MySQL, and click Connect OneDrive. Complete Microsoft sign-in in the system browser, return to the application, test the connection, enable the destination, and save it.

OneDrive for Business

Select OneDrive Business, choose the backup folder, and click Connect Microsoft 365. Sign in with a work or school account. The product owner must configure the official Microsoft public-client Application ID; enterprise administrators can optionally use their own tenant and application registration.

Google Drive

Configure the Google Drive desktop OAuth client ID and secret in Settings > Cloud Destinations. Then select Google Drive, choose a backup folder, click Connect Google, complete browser sign-in, test the connection, enable the destination, and save it. The application requests the limited drive.file scope.

Backup Workflow

1. Connect to the database server. Enter host, port, user, password, database type, and optional SSL/TLS settings.
2. Select databases. Fetch available databases and choose what should be protected.
3. Select destinations. Choose local folders, NAS/network shares, SFTP, or cloud destinations according to plan support.
4. Configure schedule and retention. Decide when backups run and how long old backup files are kept.
5. Enable notifications. Send backup result emails to success and failure recipients.
6. Run and verify. The application creates, compresses, optionally encrypts, verifies, copies, logs, and cleans up the backup.

Backup Tools Page

The Backup Tools page configures paths to command-line tools such as mysqldump, mariadb-dump, mysql, pg_dump, and psql.

If these tools are available in the Windows PATH, the simple command name is enough. Otherwise, administrators can enter the full path, for example C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqldump.exe.

This page is important because the backup engine depends on these tools to create and restore database backups correctly.

Restore and Safety

Restore is designed as a controlled administrator action. The application requires explicit confirmation before running a restore and can require the user to type RESTORE before destructive restore operations.

• Encrypted backups are validated before touching the target database.
• Incremental chains are checked for missing files or broken steps before restore.
• Restore logs are stored for later review.
• Production overwrite should never happen without explicit administrator confirmation.

Deployment Modes

Security and Reliability

• Encrypted database passwords.
• Encrypted SMTP passwords.
• Encrypted backup files when enabled.
• No clear-text password display after saving.
• Audit logs for important actions.
• User-friendly error messages.
• ProgramData storage for writable app data.
• Internal-network deployment by default.
• HTTPS-only license API configuration.
• No database contents sent to the licensing website.

Licensing and Subscription Model

DB-Backup Manager supports free, trial, monthly, yearly, and custom license plans. The customer-facing software shows license activation, current plan, subscription status, protected database limit, current usage, upgrade, and customer portal actions.

Admin license generation tools should not be included inside the customer desktop or web software. License creation, revocation, subscriptions, trial keys, and Stripe/webhook integration belong in the website/admin portal.

GDPR / DSGVO and German Market Compliance

The product is designed with data minimization in mind. The application should not upload backup files, database contents, database credentials, SMTP passwords, cloud tokens, internal paths, or internal database names to the licensing website.

The website should provide a privacy policy, terms, Impressum, cookie notice if needed, and DPA/AVV option for business customers. These documents must be reviewed by a qualified legal professional before commercial launch.

Website and Advertisement Copy