Because this is build-to-order, typical delivery is about one working week from when we have your Magento edition/version, hosting details and a staging environment. The first milestone is a working install on staging with scheduled cron backups landing in your chosen off-site destination; we then run a witnessed dry-run restore before any production cutover. Complex setups (Adobe Commerce Cloud, very large media catalogs, custom storage targets) may add a few days, and we confirm the exact timeline in writing before starting.

Every build includes a post-deployment support window for bug fixes and minor adjustments, plus verification that the module stays compatible across your Magento 2 / Adobe Commerce security patches and minor upgrades. Because this is not a Marketplace product with anonymous auto-updates, you get the source code and a named point of contact at ECOSIRE; we can also arrange an ongoing maintenance retainer to keep the module patch-tested and to add destinations or features as your infrastructure changes.

Yes. The core setup:backup command is deprecated, runs synchronously (blocking the storefront), writes only to local var/backups on the same disk, and has no scheduling, off-site copy or restore UI. This module runs backups as background cron jobs, streams compressed archives off-site to S3/FTP/Google Drive, enforces retention, and provides one-click restore from the Admin behind ACL — the disaster-recovery layer Magento core never shipped.

It runs on Adobe Commerce Open Source and Adobe Commerce (including Cloud) and on self-managed or managed hosting. For large media catalogs we use incremental media detection and streamed, compressed uploads so nightly runs stay fast and do not exhaust local disk. On Adobe Commerce Cloud we adapt to the platform's read-only filesystem and cron model during the build, which is exactly why we tailor and test each deployment rather than shipping a generic package.

Credentials for S3, FTP/SFTP or Google Drive are stored in env.php or Magento's encrypted configuration, never hard-coded in source or committed to your repository. Access to create, download and restore backups is gated by dedicated Magento ACL resources so only authorized admin roles can act, and every restore is written to an audit log. Optional archive encryption can be enabled so the off-site copies are protected at rest, and we verify each backup with a checksum and read-back to confirm it is recoverable.