Clear, authoritative answers for Backup Manager.

Backup Manager is a centralized application for managing database backup operations, automated schedules, and run history alongside operational project records. It replaces disjointed, unmonitored cron scripts with structured database profiles, verified target destinations, and unified execution logs so technical teams maintain visibility over critical data protection.

Compatibility depends on the database drivers and tools installed in your deployment environment. Because Backup Manager runs on your infrastructure or hosted stack, database engines and versions should be confirmed against your deployment configuration before connecting production databases. A fixed global matrix is not hardcoded, allowing deployment flexibility.

Stored database passwords are encrypted within the application's configuration store. In addition, the database profile workflow supports configuring an encryption passphrase for generated backup archives. Overall security also relies on your host key-management and TLS configurations. Never submit credentials or encryption keys through public contact forms.

No. A completed backup record indicates that the dump process and target storage transfer finished without reported errors. However, true disaster recovery requires regular, verified restoration testing in an isolated staging environment. We strongly recommend routinely restoring test archives to validate data consistency and schema integrity.

Backup Manager includes a Schedules area where you configure recurring backup intervals. Actual execution relies on your underlying server scheduler (such as system cron or task scheduler) invoking the application runner, valid network connectivity to database servers, and sufficient storage on configured target destinations.

Backup targets define where generated backup archives are stored. You can configure target destinations within the application, including local directories and supported remote storage destinations. Confirm that destination account credentials, write permissions, and disk quotas are verified prior to scheduling critical jobs.

Use the Backup History section to review previous execution records. Each record details execution start times, duration, completion status, and available diagnostic output. If a job fails due to connection timeouts or disk limits, reviewing history logs provides the diagnostic context needed to resolve the issue.

Yes. You can initiate manual, on-demand backup runs directly from the application console at any time. This is standard procedure prior to software deployments, major database schema migrations, or server maintenance windows.

The Hostinger backup-package workflow is a specialized integration within Backup Manager designed to handle Hostinger-specific backup packages and archive formats. While standard database profiles connect directly to database servers via standard connection parameters, the Hostinger workflow is tailored specifically for organizations managing Hostinger-hosted backup archives.

Backup Manager provides multi-user management with role-based permission checks across protected areas. Administrators can restrict sensitive actions—such as modifying database connection profiles, managing target storage, or initiating manual runs—to authorized personnel. Accounts should never be shared among team members.

Operational teams frequently execute backups in conjunction with release milestones, infrastructure migrations, and maintenance sprints. Backup Manager integrates project records and task tracking in the same workspace, allowing teams to coordinate operational tasks and document verification steps alongside backup execution history.

All pricing on the Pricing page is quoted in US dollars (USD) on a monthly basis. Because technical environments and onboarding requirements vary across organizations, our team confirms commercial terms directly prior to finalizing purchase arrangements.

Database backup software is infrastructure-critical. To ensure that our platform aligns with your database engines, storage targets, and operational expectations, plan selection initiates a direct inquiry with our technical team rather than an unassisted payment checkout.

Open our Contact page and toggle the form to Customer Support. Enter your account email, select the issue category, provide a non-sensitive reference (such as a profile or run record ID), and describe the problem. To protect your systems, never paste database passwords, encryption passphrases, API tokens, or private keys.