🔵 QuantumLinx · Bakyru · Windows

Bakyru: smart station backup — mirror mode, profiles and monitoring

Bakyru is QuantumLinx’s answer for data protection on Microsoft Windows: structured sync between local folders, external drives, and network storage. You define profiles (source, destination, and 24-hour schedule slots), watch status in a dashboard, and can get alerts via WhatsApp or email. The modern UI supports visual scaling and multiple interface languages.

Goal: reduce the risk of data loss when a disk or device fails — keeping a faithful replica of what you included in policy, at the destination you chose. Not a full Windows image; it is the set of files and folders you configured. Licensed per machine, in trial or active states; catalog plans cover 1 to 25 stations.

🪞 Mirror mode source → destination parity ⏱️ 24h scheduling automatic or run now 📊 Dashboard progress and metrics 🔔 Alerts WhatsApp and SMTP 💾 UNC / network external drive or server 📋 License per station Start a Scale

Long-form walkthrough — Bakyru

Full product explanation in English — mirror mode, profiles, dashboard, and alerts.

In three ideas

From IT to the end user: what to copy, where, and when — with integrity checks, network retries, and clear visibility in the dashboard.

Profiles and schedules

Each profile has a name, source path, destination path, and a scheduling matrix (24-hour format). You can combine automatic scheduling with a manual run (“Run now”) after paths and license checks pass.

Network and permissions

It supports UNC paths (e.g. \\server\share) and mapped drives (e.g. Z:\). On servers, UNC tends to be more stable. The account needs read access at the source and write access at the destination.

Mirror mode

The engine syncs in mirror mode: it compares modification time and size, copies changes, and aligns the destination tree with the source. At the source the flow is read/copy; at the destination, files with no matching source may be removed to keep parity — validate with Run now before you automate.

Copy Engine and Resilience

Bakyru reads metadata at the source, sends new or changed items, and applies retries for transient network failures, respecting configured time limits. Internal folders such as config/ (notification profiles and credentials), logs/ (audit, e.g. backup_log.txt), and assets/ (application resources) ship with the install — back up config/ before migrations.

Recommended security: SMTP credentials and API keys are on local disk — use BitLocker and permissions NTFS restricted to the program folder when it makes sense in your policy.

Validations and integrity

To avoid cycles and corruption, the product enforces, among others: source and destination cannot be identical; the destination cannot be inside the source; the source cannot be inside the destination. Profiles are stored in a structured model (name, source, destination, and schedule fields).

Dashboard and notifications

The dashboard shows active profiles, schedules, task status, and the file in progress, with a 0–100% bar and a completion message. The run summary includes total scanned, copied, removed at destination (mirror alignment), and skipped (no change detected).

Under notifications you can configure WhatsApp (e.g. CallMeBot, with international number and API key) and SMTP email (host, port, TLS, sender, and recipients). Choose alerts on error only, success only, or both. Use Submit test to validate integrations.

Operation and license security

Sensitive changes to profiles and notifications require an admin session with password; the session expires after 15 minutes of inactivity. Store the recovery token the system provides in a secure, off-site location in case credentials are lost.

The license is validated with QuantumLinx servers in trial (evaluation) or active states. The Machine ID identifies hardware for support and renewals via QuantumLinx.tech.

For reliable scheduling, enable Start with Windows and keep the tray agent running when you close the window, so background jobs keep firing on schedule.

Quick troubleshooting

Frequent symptoms and initial checks (v1.0 technical guide summary):

SituationWhat to check
Backup does not startLicense in the corresponding area; assembled destination; another copy already running.
Schedule fails to runStart with Windows enabled; time in HH:MM (24h).
Notification does not arriveUse Submit test; HTTP 200 means the send path responded — then confirm firewall and the receiving endpoint.
Error in network pathTest UNC in Explorer; write permissions of the user running Bakyru.

Good practices

  • Before automating, use Run now and confirm that removals at the destination (mirror mode) are acceptable.
  • Use a strong password in the admin area and store the recovery token outside the backup machine.
  • Prefer two separate destinations (e.g. USB + NAS) with separate profiles for physical redundancy.
  • Review logs periodically to catch file locks or network bottlenecks.

How it works in practice

Picture a PC with important files. If the main disk fails or there is physical damage, anything that only lived on that disk can be lost. With Bakyru copying to external storage or a network path, the files in your profiles also exist in that second location — as long as scheduled runs completed as expected.

At the source, Bakyru does not rewrite your working data “because of backup”: it reads and writes the copy to the destination. At the destination, in mirror mode, the tree stays aligned with the source — including removing files that no longer exist at the source. Use a dedicated backup target, not random working folders without a clear policy.

For volumes above the catalog or special conditions, use the Sarah on the page Bakyru plans.

Plans in one line

On the plans page you compare Start, Pro, Business, and Scale with pricing for monthly, quarterly, semi-annual, and annual billing.

Start

1 station with dedicated backup policy.

Pro · Business · Scale

Up to 5, 10 or 25 machines in the standard catalog — choose the ceiling that covers the park today with room for controlled growth.

Common Bakyru Questions

Straight answers about what the product does and how to buy. QuantumLinx ships other product lines on this site; each has its own page and plans.

Does Bakyru change or delete something in my working folder (source)?

At the source: Bakyru uses read operations and copies to the configured destination — it does not rewrite your working files “because of backup.”

At the destination (mirror mode): files that existed in a previous run but no longer exist at the source may be removed at the destination so the replica stays faithful. Use Run now and a dedicated destination before you automate production schedules.

Does this copy all of Windows?

No. You choose folders and files via profiles. It is not a full OS clone — only what you mark for protection.

What if I change, delete, or create files at the source?

On the next run (scheduled or manual), the mirror-mode destination reflects the current source: new and changed files are copied; items that no longer exist at the source can be removed at the destination to keep parity. See the product documentation for full policy details.

Does Bakyru send alerts when a backup finishes or fails?

Yes. Under notifications you can set up WhatsApp and SMTP email, and choose alerts for errors, success, or both. A test action validates credentials and connectivity.

Where do I see prices and periods?

On the page Bakyru Plans, with period selector and Start a Scale cards.

How do I talk to QuantumLinx about Bakyru?

Use a Sarah on this website or open the page Bakyru Plans for hiring and values.

Next step

Compare plans calmly. If the scenario is non-standard, send by Sarah the number of machines and the country.