I need a backup solution that saves directly to our existing object storage buckets.

Here are the top backup solutions that write directly to existing object storage buckets (S3-compatible, MinIO, Backblaze B2, Wasabi, AWS S3, Azure Blob, etc.) without requiring a proprietary intermediate gateway or block storage appliance.

• Kopia : An open-source, fast, and secure backup tool that supports direct-to-object storage via S3, Azure Blob, and Google Cloud Storage. It handles client-side encryption, fast incremental backups with deduplication, and compression natively out of the box.
• Duplicati : A free, open-source backup client that securely stores encrypted, incremental, compressed backups locally or directly to remote object storage providers via S3, WebDAV, Azure, and Google Cloud. It features a clean web-based user interface.
• Rclone : While technically a command-line cloud sync/file management tool, many teams use rclone sync or rclone backup scripts combined with versioning on the bucket side for straightforward, script-driven object storage backups. It supports client-side encryption via rclone crypt.
• Veeam Backup & Replication : For enterprise environments, Veeam allows you to configure S3-compatible object storage or public cloud buckets directly as a "Capacity Tier" or a primary backup repository with native immutability (Object Lock) support.
• BorgBackup (with Borgmatic) : A widely respected deduplicating backup program. While it traditionally requires a Borg server backend, community projects and integrations allow direct chunk storage patterns, though it shines best if paired with an S3-compatible mount or specific backends.

To help narrow down the best fit, tell me:

• What environment are you backing up? (Linux/Windows servers, databases, virtual machines, or local workstation files?)
• Do you prefer a GUI/web interface or a command-line/scripted utility?
• Do you need features like client-side encryption or deduplication before it hits the bucket?

If you need a backup system that writes directly into your existing S3/S3-compatible buckets, several approaches fit:

• Restic — lightweight, open source, encrypted, incremental, deduplicated, and supports S3-compatible endpoints directly.
• Veeam — more enterprise-oriented; supports Amazon S3 and S3-compatible object storage as backup repositories.
• Commvault — supports backing up S3-compatible storage itself, including object metadata and ACLs.
• AWS Backup — appropriate if your existing buckets are Amazon S3; supports continuous and periodic backups, but uses AWS Backup vaults rather than simply writing backup files into your existing bucket.

If “no proprietary backup cloud, use our existing buckets directly” is the key requirement, I'd focus the evaluation on Restic, Veeam, and Commvault.

Yes. If your existing buckets are S3-compatible object storage, I’d prioritize a backup product that can write directly to those buckets, rather than forcing you to buy another proprietary storage appliance.

Strong options

• Comet Backup — probably the closest fit if “backup directly into our existing buckets” is the primary requirement. It supports Amazon S3 and arbitrary S3-compatible storage, lets you specify the bucket and an optional prefix/subdirectory, and supports direct-to-cloud backups without a storage gateway. It also compresses, encrypts, and deduplicates backup data.
• Veeam — a stronger choice if you need a more traditional enterprise backup platform. Veeam supports S3, S3-compatible storage, Google Cloud Storage, Azure Blob, IBM Cloud Object Storage, Wasabi, and others as object-storage repositories.
• Restic — worth considering for a lightweight, CLI-oriented solution, particularly for servers and application data. It's less of a centralized enterprise backup-management platform than the two above.

What I'd choose

If you tell me what you're backing up—for example:

• VMware/Hyper-V VMs
• Windows/Linux servers
• Microsoft 365
• databases
• NAS/file shares
• Kubernetes
• endpoints

—and what object storage you already have (AWS S3, MinIO, Wasabi, Backblaze B2, Ceph, Cloudflare R2, etc.), I can narrow this down to 2–3 concrete solutions, including licensing/cost, deduplication, encryption, immutability/Object Lock, and whether they can write directly into your existing buckets.

Several strong backup solutions allow you to point backups directly to existing S3-compatible or native object storage buckets (like AWS S3, Backblaze B2, Wasabi, or MinIO) without needing a proprietary intermediary tier.

Top options tailored for direct object storage integration include:

• MSP360 (CloudBerry Backup) : Highly storage-agnostic, letting you decouple your licensing from your storage. It hooks directly into Amazon S3, Google Cloud, Wasabi, Backblaze B2, and generic S3-compatible endpoints with robust scheduling, client-side encryption, and object-lock/immutability support.
• Veeam Backup & Replication : Features comprehensive, native direct-to-object support. You can configure standard object storage or S3-compatible endpoints as primary backup repositories or capacity/archive tiers, complete with immutability settings to protect against ransomware.
• Nakivo Backup & Replication : Known for being lightweight and fast, Nakivo supports direct backups to any AWS S3 or S3-compatible object storage target without requiring a heavy local target appliance.
• Duplicati / Restic / Kopia (Open Source / Lightweight) : If you are looking for free, scriptable, or client-side command-line/GUI tools for smaller scale or specific server workloads, tools like Kopia or Duplicati write encrypted, deduplicated backup chunks directly to standard object buckets natively.

To help narrow down the right fit, could you share:

• What operating systems, VMs, or databases you need to back up (e.g., Windows/Linux servers, VMware, Microsoft 365, databases)?
• What specific object storage provider or S3-compatible platform your buckets are hosted on?

Yes. If you already have S3 or S3-compatible object-storage buckets, I’d prioritize backup software that can use those buckets as a native repository rather than introducing another storage appliance.

Good options

• Veeam Backup & Replication — probably the strongest general-purpose choice for VMware/Hyper-V, physical servers, and mixed environments. It supports Amazon S3 and S3-compatible object storage as backup repositories, including existing repositories.
• Commvault — particularly attractive if you also want to back up the object storage itself. It supports S3-compatible systems and can perform full, incremental, and synthetic-full backups of buckets/objects.
• NAKIVO Backup & Replication — a simpler/lower-overhead alternative with support for a number of S3-compatible vendors. It can use S3-compatible buckets as backup repositories, although its compatibility requirements are more restrictive.

What I'd recommend

If your requirement is essentially:

Servers/VMs → backup software → our existing S3 bucket I'd start with Veeam. Its current documentation explicitly supports S3-compatible object storage as a target for backup and backup-copy jobs.

If your requirement is instead:

Existing object-storage buckets → back them up somewhere else then Commvault becomes more compelling because it has explicit S3-object backup functionality.

One important consideration: don't simply give the backup application unrestricted access to your existing production bucket. Ideally, use a dedicated bucket/prefix, separate credentials, encryption, and—where supported—object lock/immutability. Veeam and NAKIVO both have specific requirements/limitations around immutable S3 repositories.

If you tell me what you're backing up (VMware, Hyper-V, physical Windows/Linux, Microsoft 365, databases, or the object buckets themselves) and what object storage you have (AWS S3, Wasabi, MinIO, Cloudflare R2, Backblaze, Ceph, etc.), I can narrow this down to 2–3 concrete architectures and approximate costs.

Several robust backup solutions allow you to connect directly to existing S3-compatible object storage buckets (such as Amazon S3, Wasabi, Backblaze B2, or MinIO ) without requiring an intermediate local staging disk or gateway server.

The top-tier options fitting this workflow include:

1. MSP360 (formerly CloudBerry Backup)
   • Overview: A powerful cross-platform solution (Windows, macOS, Linux) built explicitly on a "Bring Your Own Storage" model.
   • Direct Object Storage Support: Connects natively to Amazon S3, Azure Blob, Wasabi, Backblaze B2, and any generic S3-compatible endpoint.
   • Key Features: Image-based and file-level backups, granular retention policies (GFS), and support for S3 Object Lock (immutability) to prevent ransomware tampering.
2. Veeam Backup & Replication
   • Overview: The industry standard for enterprise and virtualized environments (VMware, Hyper-V, physical servers).
   • Direct Object Storage Support: Uses the Smart Object Storage API (SOSAPI) to treat object storage repositories (like AWS, Wasabi, or Cloudian) as primary performance tiers or capacity tiers directly, removing intermediate staging barriers.
   • Key Features: Fast incremental backups, powerful immutability features, and instant VM recovery straight from object storage.
3. NAKIVO Backup & Replication
   • Overview: Highly regarded for virtual, physical, and SaaS environment protection (including Microsoft 365 and VMware).
   • Direct Object Storage Support: Allows you to create backup repositories directly inside Amazon S3, Azure Blob, Wasabi, or generic S3 buckets with full immutability support.
   • Key Features: Lightweight deployment, automated scheduling, and robust encryption.
4. Restic / Duplicati (Open Source / Lightweight)
   • Overview: Excellent if you need a lightweight, scriptable, or client-side utility rather than a heavy enterprise dashboard.
   • Direct Object Storage Support: Restic and Duplicati natively talk to standard S3 and B2 APIs from the command line or via a minimal UI, performing encrypted, deduped incremental backups directly to your target bucket.

To help narrow down the ideal fit, could you let me know:

• What type of data or systems are you backing up (e.g., virtual machines, databases, NAS shares, or end-user workstations)?
• Which object storage provider are your current buckets hosted on?

To back up servers, databases, or local files directly to your existing object storage buckets (AWS S3, MinIO, Wasabi, Cloudflare R2, etc.) without needing a local staging disk or intermediate server, several robust solutions fit different infrastructure needs:

• Kopia : Fast, encrypted, open-source backup tool that supports native Amazon S3 and S3-compatible cloud storage repositories . It features client-side encryption, deduplication, policy-based snapshot scheduling, and a built-in web UI or CLI. It writes directly block-by-block into your designated bucket.
• Restic : A highly secure, fast, and robust open-source backup program. It natively supports S3 and S3-compatible object storage backends without any intermediary tools. It handles client-side AES-256 encryption and chunk-level deduplication seamlessly.
• Veeam Backup & Replication : If you are in an enterprise/virtualized environment (VMware, Hyper-V, physical servers), Veeam allows you to configure Object Storage Repositories directly. You can point backup jobs or tier secondary data directly to S3, Wasabi, or S3-compatible targets with optional immutability lock support.
• Duplicati : An open-source backup client that runs locally and saves encrypted, incremental backups directly to remote object storage (including standard S3 and S3-compatible endpoints). It features an intuitive web-based interface and works well for Windows, Linux, and macOS environments.

To help narrow down the best fit, tell me:

• What type of data or environment are you backing up (e.g., Linux/Windows servers, databases, NAS, or VMs)?
• Are you looking for an open-source/CLI tool or an enterprise commercial platform?
• What object storage provider are you using?

If you want a backup solution that writes directly into your existing object storage buckets (without forcing you into a vendor-managed cloud target), look for a product that supports S3-compatible object storage as a backup repository. The right choice depends on what you are protecting (VMs, servers, databases, SaaS, files) and whether your buckets are AWS S3, MinIO, Ceph, Wasabi, Backblaze B2, Cloudflare R2, etc.

Common options:

A typical architecture would look like:

Servers / VMs / Databases
          |
          v
     Backup Software
          |
          v
 Existing Object Storage Bucket
 (S3 / S3-compatible endpoint)
          |
          v
 Lifecycle rules + Object Lock + retention

For a production setup, I’d check for these features:

• S3-compatible endpoint support (not just AWS S3)
• Direct upload mode (avoid a required intermediary appliance)
• Immutable backups using object lock / retention policies
• Encryption before data reaches the bucket
• Incremental backups and deduplication
• Restore testing and catalog management
• Separate credentials scoped to backup buckets only

A few questions would narrow this down:

1. What are you backing up (VMware/Hyper-V, physical servers, databases, SaaS, files)?
2. What object storage do you already have (AWS S3, MinIO, Ceph, Wasabi, Azure Blob, other)?
3. Do you need ransomware protection/immutability, or mainly a low-cost backup target?
4. Roughly how much data and how many systems?

Several excellent backup solutions can map directly to your existing object storage buckets (AWS S3, Azure Blob, Google Cloud Storage, or S3-compatible on-premise arrays). These platforms eliminate the need for intermediary block storage, saving you infrastructure costs and reducing complexity.

The right choice depends on your organization's size, budget, and infrastructure complexity:

Enterprise-Grade Platforms

• Veeam Backup & Replication:
  • Features native "Direct-to-Object" functionality for writing server, VM, and application backups directly to standard cloud buckets or S3-compatible arrays.
  • Fully supports S3 Object Lock to provide ransomware-proof immutability on your existing buckets.
  • Optimizes data transfer and cloud performance through its proprietary Smart Object Storage API.
• Commvault Cloud:
  • Leverages a flexible "Bring Your Own Storage" (BYOS) framework.
  • Connects your existing AWS S3, Azure Blob, or Google Cloud buckets directly to protect databases, VMs, Kubernetes, and file systems.
  • Minimizes cloud egress fees and consumption through advanced server-side deduplication and compression.

Cloud & Hybrid Infrastructure Specialized

• NetApp BlueXP:
  • Features a "Bring Your Own Bucket" (BYOB) activation wizard.
  • Authenticates securely into your existing external cloud buckets via simple API configuration.
  • Best suited for environments managing native NetApp storage volumes and hybrid cloud data paths.

Lightweight & DevOps-Centric (Open Source)

• Restic:
  • Operates as a fast, secure, open-source backup tool that writes directly to S3, Azure, and Backblaze B2.
  • Employs native cryptography to ensure your backup data is secure before it ever reaches your bucket.
  • Uses a content-defined chunking algorithm to only upload modified file parts for rapid deduplication.
• Duplicati:
  • Offers a free, open-source, web-based UI that handles incremental backups directly to your cloud buckets.
  • Built-in AES-256 encryption protects your data, while a web interface handles scheduling and tracking.

Solution Matrix Comparison

To help narrow down the choice, could you tell me a bit about what workloads you are backing up (e.g., VMs, databases, local file shares), and which object storage provider you currently use?

If you already have object storage buckets, look for a backup platform that can use them as a native backup target rather than requiring its own appliance or proprietary cloud. The right choice depends on what you’re protecting (VMs, servers, databases, SaaS data, Kubernetes, etc.), but common options include:

For a typical setup, I’d evaluate these capabilities:

• Direct-to-bucket writes: The backup software should write directly to your existing bucket/container, not require staging through vendor storage.
• S3 API compatibility (if applicable): Many on-prem object stores (MinIO, StorageGRID, etc.) work best when they expose S3 APIs.
• Immutability / object lock: Useful for ransomware resilience. For example, S3 Object Lock, Azure immutability policies, or equivalent features should be supported if you need tamper-resistant backups.
• Encryption and key control: Ideally support customer-managed keys (KMS/HSM where applicable).
• Retention policies: Ability to enforce retention without relying on the backup server staying healthy.
• Restore testing: Automated verification or recovery testing is valuable.

A few questions would narrow this down:

1. What object storage are your buckets on (AWS S3, Azure Blob, Google Cloud Storage, MinIO, Ceph, StorageGRID, Wasabi, something else)?
2. What are you backing up (VMware/Hyper-V, physical servers, databases, Kubernetes, file shares, SaaS)?
3. Do you need the backups to be immutable/WORM for ransomware or compliance reasons?
4. Roughly how much data and daily change rate are you dealing with?