Interactive preview: sample records and simulated states are illustrative. The preview controls do not connect to live databases, run backups, or verify a deployment.
Database Backup Operations

Secure every database backup from one platform.

Configure database profiles, manage backup destinations and schedules, review run history, and connect backup work to project tasks.

Batch workflow preview
Hostinger Bridge API
Credential handling
interactive_workflow_preview
PREVIEW
Example database profile Example
Example configured backup destination Example
$ Ready to preview interface states...
End-to-End Delivery & Maintenance

Connect project delivery directly to database protection.

Use one workspace to organize project tasks, database profiles, scheduled work, and backup history.

AC

Example project workspace

Example priority
Illustrative record · Deployment: configured per project
Example project state
Project Allotment Date Set per project Example planning field
Target Completion Date Set per project Example planning field
Project Health Score Example status Verify deployment configuration
Example work areas
DB
Database operations Profiles and backup targets
SC
Schedule coordination Timing and run review
PM
Project coordination Tasks and ownership
Project status: Example • Transport security: Deployment-specific • Credentials: Not shown
Sign In to Access Projects
Infrastructure Connectivity

Choose a database connection approach for your environment

Connection options depend on hosting restrictions, supported drivers, network access, and the settings available in your environment.

Alternative for some shared-hosting setups

The Deployable Hostinger Bridge

Some shared-hosting environments restrict external MySQL connections. The Hostinger backup package provides an alternative integration path; review its deployment instructions and storage locations before use.

  • • Confirm which host and database endpoint the package will access.
  • • Verify that backup storage is outside public access and protected by host permissions.
  • • Review the package authentication and token configuration before deployment.
// Server Directory Tree
/home/user/
├── private_backups/ (Outside web root)
├── backupApi.php
└── dumps/ (.sql.gz)
└── public_html/ (Website files)
Interactive example

See how a batch workflow can be presented.

This browser-only example simulates a queue and an isolated failure state. It does not start backup jobs or confirm batch behavior in a live deployment.

BATCH QUEUE: Example backup queue
Example only: preview the sample queue state. No backup will run.
Concurrency Protection

Plan scheduled work with clear run visibility.

The application includes schedule management and backup history. Actual overlap protection and job-claim behavior depend on the scheduling implementation and configuration in your deployed environment.

Schedule coordination: Review how the deployed worker claims a job
Overlap behavior: Confirm how concurrent runs are handled
Next-run timing: Governed by schedule and scheduler settings
// ILLUSTRATIVE SCHEDULING TIMELINE
02:00:00
Worker Polls Schedule Queue
Schedule due: Example backup schedule
02:00:01
Lock Acquired: status = 'processing'
Example timeline state; verify lock behavior in deployment.
02:00:14
Target API Acknowledges Dump
Archive handling and encryption depend on configured settings.
02:00:15
Lock Released & Next Run Calculated
Next-run time is determined by schedule configuration.
Sensitive by Design

Credentials require deliberate protection.
Treat them as sensitive infrastructure.

The database-profile interface states that stored database passwords are encrypted. Protected application actions also use role and permission checks. Security depends on deployment configuration and access practices.

Stored database passwords are encrypted by the configured application service
Role and permission checks on protected actions
Controlled reveal action with role permission check
CREDENTIAL VAULT MOCKUP EXAMPLE
Credential Name
Example credential record
Masked example value
••••••••••••••••••••
Auditability

Every run leaves an operational trace

Example rows show how run history can be presented; these are not live records.

Illustrative sample rows — not live backup history.
Run Identifier Database Profile Mode Duration Status Timestamp
sample-run-01 Example profile A Daily Sample only Example success state Example timestamp
sample-run-02 Example profile B Manual Sample only Example failure state Example timestamp
sample-run-03 Example profile C Weekly Sample only Example success state Example timestamp
Operations Workspace

Make backup operations easier to trust.

Manage database profiles, backup destinations, schedules, backup history, and related project work from one workspace.