Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $249.00 USD
- ERPNext versions
- —
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
एक बार की खरीदारी
Cloud Backup Manager (S3/Drive/Dropbox/RClone)
A build-to-order Frappe/ERPNext app that runs scheduled, client-side-encrypted backups of your database and files to S3, Google Drive, Dropbox, Backblaze B2 or any RClone remote — with retention policies, one-click restore and automated restore-testing drills. ECOSIRE builds, installs and supports it for your bench.
$249.00USD
अभी कोई भुगतान नहीं। यह हमारी टीम को एक कोटेशन अनुरोध भेजता है — हम कीमत और अगले चरणों के साथ ईमेल द्वारा संपर्क करेंगे।
प्रमुख सुविधाएँ
`Backup Destination` DocType per target with credentials encrypted at rest via Frappe's `Password` fieldtype (S3, Google Drive, Dropbox, Backblaze B2, any `rclone` remote)
`Backup Policy` DocType defining scope (DB, public files, private files, or all), schedule, retention window and destination fan-out
Scheduled runs wired to Frappe `scheduler_events` (hourly/daily/weekly/cron) executed in background workers via `frappe.enqueue` so uploads never block web workers
Client-side symmetric encryption of backup artifacts before upload — you hold the key; only ciphertext reaches the cloud (optional SSE-KMS mode where preferred)
Multi-destination fan-out: a single run pushes to several targets in parallel with independent success/failure tracking
Retention and rotation policies enforced per destination (e.g. keep 7 daily / 4 weekly / 12 monthly), pruning old objects automatically
`Backup Run` log DocType recording start/end time, byte size, SHA-256 checksum, per-destination status and error traceback for a full audit trail
One-click restore: pull a selected `Backup Run` from any destination, decrypt, verify checksum and restore into a target site
Scheduled restore drills that restore the latest backup into a throwaway staging site, run a health check and record pass/fail
Post-upload integrity verification and multipart/resumable transfer (`boto3` for S3-compatible targets, `rclone` for the rest)
Dedicated `Backup Manager` role profile plus DocType permissions so destinations, keys and restore actions are locked down
Whitelisted REST API methods (`@frappe.whitelist()`) to query backup status, list runs and trigger a manual run from monitoring/CI
Failure alerting via `hooks.py` doc events — email/webhook notification to admins when a run or a destination upload fails
Optional client script on the `Backup Policy` form to preview the effective retention schedule and next run time before saving
इस उत्पाद के बारे में
Self-hosted ERPNext gives you a bench backup command and a basic scheduled backup that drops .sql.gz and files tarballs into sites/<site>/private/backups/ — on the same server that holds your production data. If that disk fails, the instance is compromised, or someone fat-fingers a bench drop-site, your "backups" die with the box. ERPNext core has no built-in off-site push, no client-side encryption, no per-destination retention, and crucially no way to prove a backup can actually be restored. For any business running ERPNext in production, that is the gap between "we take backups" and "we have disaster recovery."
Cloud Backup Manager (S3/Drive/Dropbox/RClone) क्यों चुनें
`Backup Destination` DocType per target with credentials encrypted at rest via Frappe's `Password` fieldtype (S3, Google Drive, Dropbox, Backblaze B2, any `rclone` remote)
`Backup Policy` DocType defining scope (DB, public files, private files, or all), schedule, retention window and destination fan-out
Scheduled runs wired to Frappe `scheduler_events` (hourly/daily/weekly/cron) executed in background workers via `frappe.enqueue` so uploads never block web workers
Client-side symmetric encryption of backup artifacts before upload — you hold the key; only ciphertext reaches the cloud (optional SSE-KMS mode where preferred)
Multi-destination fan-out: a single run pushes to several targets in parallel with independent success/failure tracking
Retention and rotation policies enforced per destination (e.g. keep 7 daily / 4 weekly / 12 monthly), pruning old objects automatically
Cloud Backup Manager is a proper Frappe app (its own module, hooks.py, DocTypes and scheduler events) that we build for your bench to close that gap. A Backup Destination DocType stores each target (S3, Google Drive, Dropbox, Backblaze B2, or any rclone remote), with credentials encrypted at rest using Frappe's Password fieldtype. A Backup Policy DocType defines what to back up (database, public files, private files, or all), the schedule, the retention/rotation rules (e.g. keep 7 daily, 4 weekly, 12 monthly), and which destinations to fan out to. Jobs run on Frappe scheduler_events (hourly/daily/cron) and execute inside background workers via frappe.enqueue, so long uploads never block the web workers. Every run writes a Backup Run log DocType — start/end, byte size, checksum, destination status and errors — giving you an auditable history right inside ERPNext.
Backups are encrypted client-side before they leave your server. The app streams the bench backup artifacts through age/GPG-style symmetric encryption (or SSE-KMS where you prefer server-side), so what lands in S3 or Dropbox is ciphertext you hold the key to — not a plaintext dump sitting in someone else's cloud. Uploads use boto3 for S3-compatible targets and rclone for the rest, with multipart/resumable transfer and integrity checksums verified after upload. Retention enforcement prunes old objects per policy on each destination independently, so a cheap Dropbox tier and a compliance-grade S3 bucket can hold different windows.
The part most tools skip is restore confidence. Cloud Backup Manager includes one-click restore (pull a chosen Backup Run from any destination, decrypt, and restore into a target site) plus scheduled restore drills: on a cadence you set, the app restores the latest backup into a throwaway staging site, runs a health check, and records a pass/fail on the Backup Run — so you find out your backups are broken during a drill, not during an outage. Role-based permissions (a dedicated Backup Manager role profile) keep destinations and restore actions out of ordinary users' hands, and whitelisted REST methods let your monitoring stack query backup status and trigger runs. Everything supports Frappe/ERPNext v15 and v16.
Because this is build-to-order, nothing is a shrink-wrapped download. After a short scoping call we confirm your destinations, encryption approach, retention windows and restore-drill cadence, then build the app to that spec, test it on a staging bench with a real restore, and hand over the git repository. Typical delivery is 2–4 weeks from confirmed scope depending on how many destinations and compliance requirements are in play. You get the source, install and configuration on your bench, documentation, a training session, and a post-go-live support window.
What you get
- Installable source code for your version of the app, built for your Frappe/ERPNext v15 or v16 bench
- Installation and configuration on your bench — destinations connected, encryption keys set up, policies and schedules configured
- Technical documentation covering DocTypes, scheduler events, hooks, whitelisted REST methods and the encryption/key-management model
- User guide plus a live training session for your backup administrators
- UAT on a staging bench including a real end-to-end restore drill, with a documented rollback plan
- Post-go-live support window for fixes and configuration adjustments
- Git repository handover with full commit history and README
- Runbook for disaster recovery — how to restore from a chosen destination when the primary server is gone
Who this is for
Self-hosted ERPNext system administrator
Runs one or more production benches on their own VPS/on-prem servers and needs real off-site disaster recovery, not just local `bench backup` files sitting on the same disk as the data they are meant to protect.
MSP / Frappe hosting partner
Manages ERPNext for multiple clients and needs consistent, auditable, multi-destination backup policies with restore drills they can point to during audits and SLA reviews.
Compliance-driven finance or healthcare operator
Must demonstrate encrypted, retained, recoverable backups with a documented restore-test history — and wants the evidence stored inside ERPNext as `Backup Run` records rather than in ad-hoc scripts.
Technical founder / IT lead on a lean team
Has no dedicated DBA, wants set-and-forget scheduled encrypted backups to their existing S3 or Dropbox account, and wants to be alerted the moment a backup or a restore drill fails.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Cloud Backup Manager (S3/Drive/Dropbox/RClone) app ZIP from your account dashboard.
Add the app to your bench
Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.
Install on your site
Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install Cloud Backup Manager (S3/Drive/Dropbox/RClone) and apply its schema.
Activate your license
Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.
How Cloud Backup Manager (S3/Drive/Dropbox/RClone) Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Off-site storage | S3, Drive, Dropbox, B2 or any RClone remote, multi-destination fan-out | Whatever you script; usually one destination | Often a single provider (e.g. S3 only) | |
| Client-side encryption | Yes, you hold the key; SSE-KMS optional | Only if you build and maintain it | Rarely; often plaintext upload | |
| Restore testing / drills | Scheduled drills restore to staging + pass/fail log | Almost never built | Typically not included | |
| Retention & rotation | Per-destination policies (daily/weekly/monthly) | Hand-rolled cron and cleanup scripts | Basic single retention window | |
| Audit trail | `Backup Run` DocType with size, checksum, status | Log files if you remember to keep them | Limited or vendor dashboard only | |
| ERPNext integration | Native DocTypes, roles, REST API, scheduler events | Depends on the developer | Varies; may be a bolt-on | |
| Failure alerting | Email/webhook via `hooks.py` doc events | Only if you wire it up | Sometimes, provider-dependent | |
| Ownership & support | Full source + git handover + support window | You own it and maintain it | Vendor-locked, subscription |
Frequently Asked Questions about Cloud Backup Manager (S3/Drive/Dropbox/RClone)
+Is this a download I can install from the Frappe Cloud Marketplace right now?
No. Cloud Backup Manager is build-to-order — ECOSIRE builds, installs and supports it for your specific bench after we confirm scope. There is no instant download. You receive the full source and git repository as part of the handover.
+How long does delivery take?
Typically 2–4 weeks from confirmed scope. The exact timeline depends on how many destinations you need, your encryption and compliance requirements, and how much restore-drill automation you want. We agree the timeline in writing on the scoping call before any build starts.
+How are updates and support handled after go-live?
Every engagement includes a post-go-live support window for fixes and configuration adjustments. Because you receive the git repository, your own team can also extend it. Beyond the included window we offer ongoing support and compatibility updates (for example moving from ERPNext v15 to v16) as a separate arrangement.
+Which destinations and ERPNext versions are supported?
Amazon S3 and any S3-compatible store, Google Drive, Dropbox, Backblaze B2, and any target `rclone` supports (Wasabi, OneDrive, SFTP, etc.). It is built for Frappe/ERPNext v15 and v16. We confirm your exact destinations during scoping.
+How is my data protected in transit and at rest in the cloud?
Backups are encrypted client-side before they leave your server, so only ciphertext reaches the destination and you hold the key. Destination credentials are stored using Frappe's encrypted `Password` fieldtype, transfers use TLS, and each upload is checksum-verified. We can also use server-side SSE-KMS where you prefer that model.
+Can it actually prove my backups are restorable?
Yes — that is the core differentiator. The app runs scheduled restore drills that restore the latest backup into a throwaway staging site, run a health check, and record a pass/fail on the `Backup Run` log. You find out a backup is broken during a drill, not during an outage.
+Will scheduled backups slow down my live ERPNext instance?
No. Backup and upload jobs run in Frappe background workers via `frappe.enqueue` on scheduler events, so they never block the web workers serving your users. You can also schedule heavy runs for off-peak hours per policy.
कोटेशन का अनुरोध करें
Cloud Backup Manager (S3/Drive/Dropbox/RClone)
A build-to-order Frappe/ERPNext app that runs scheduled, client-side-encrypted backups of your database and files to S3, Google Drive, Dropbox, Backblaze B2 or any RClone remote — with retention policies, one-click restore and automated restore-testing drills. ECOSIRE builds, installs and supports it for your bench.
- `Backup Destination` DocType per target with credentials encrypted at rest via Frappe's `Password` fieldtype (S3, Google Drive, Dropbox, Backblaze B2, any `rclone` remote)
- `Backup Policy` DocType defining scope (DB, public files, private files, or all), schedule, retention window and destination fan-out
- Scheduled runs wired to Frappe `scheduler_events` (hourly/daily/weekly/cron) executed in background workers via `frappe.enqueue` so uploads never block web workers
- Client-side symmetric encryption of backup artifacts before upload — you hold the key; only ciphertext reaches the cloud (optional SSE-KMS mode where preferred)