Backup tools and the storage each one needs

Each backup program writes to a bucket in its own way: how big its files are, how often it lists and reads them, whether it can lock them. That decides which vendor's requests, minimums and downloads it runs into. Pick yours: each page prices every vendor on what that tool does.

• rcloneA nightly rclone sync of 1 TB priced on every vendor, with the flags that cut its requests, each vendor's rclone setting, a sync that cannot empty the bucket and a restore test.
• DuplicacyA 1 TB Duplicacy storage backed up daily and pruned weekly, priced on every vendor with what pruning's renames cost, each vendor's storage URL and a restore test.
• DuplicatiA 1 TB Duplicati backup run every night, priced on every vendor with the check that downloads part of it after each run, each vendor's storage address and a restore test.
• MSP360 BackupA 1 TB computer backed up nightly with MSP360, priced on every vendor for the full copies its generations keep, against Forever Forward Incremental's one, and a restore on another computer.
• SQL ServerSQL Server's own BACKUP TO URL: a 200 GB nightly full and 15-minute log backups priced on every vendor, how many URLs a backup needs, and why the bucket cannot be locked.
• resticA 2 TB restic repository at every vendor, with a monthly check of a twelfth of the packs, and what pruning adds.
• KopiaA 2 TB Kopia repository at every vendor, with a monthly verify, and where Kopia can lock its packs.
• Veeam Backup & ReplicationWhich vendors Veeam can make immutable, ranked on a year with one full restore.
• CommvaultThe vendors on Commvault's WORM list, with the extra copy its lock makes you keep counted.
• VeleroKubernetes backups kept 30 days, and what a class's minimum storage period does to them.
• Proxmox Backup ServerA Proxmox Backup Server datastore on S3, with the monthly verify job that downloads it.

Windows, a Mac or Linux: the bill is the same on each. Every tool page says where the tool runs and how it backs up files another program holds open.

By what you back up

• A SQL Server databaseSQL Server's own BACKUP TO URL to a bucket: full and log backups priced, and how many URLs a big backup needs.
• Another database's nightly backupsA backup file each night kept 30 days, where each class's minimum storage period decides the bill.
• Proxmox virtual machinesProxmox Backup Server writing to S3, with the verify job that downloads what it checks.
• VMware or Hyper-V virtual machinesVeeam Backup & Replication writing their backups to a bucket it can lock, with its objects and lock periods priced.
• A Kubernetes clusterVelero's backups kept 30 days, and what a minimum storage period adds.
• A photo libraryPriced from the size of your shoots and how long you keep them, with one shoot or the whole library restored.
• A video archive50 TB of finished footage kept for years, with one 2 TB project brought back.
• Records kept for yearsSeven years under a lock nobody can lift, with one audit retrieval a year.

Using something else? What uploads, listings and reads cost at each vendor and what file size does to the bill answer it for any tool.