One of the Arch wiki maintainers thought it was “useless bloat” to add information about which remote backends are supported by various Linux backup programs on the Arch wiki, and reverted my contribution. Well, I don’t think so, as I did the research because I needed to know. I don’t want it to be lost, I’ll post what I learned here.

P.S. This is my first negative experience in the Arch community; I guess I should be happy it has been only positives for such a long time.

• Areca Backup: Local drive, network drive, USB, FTP, FTPS, SFTP server
• BorgBackup: Local drive, remote drive via ssh
• btar: Local drive
• bup: Local drive, remote drive executing bup via ssh
• bups: See bup
• Déjà Dup: See duplicity
• Duplicati: Local drive, ftp, OpenStack Swift, sftp, Amazon Cloud Drive, Azure, B2 Cloud Storage, Box.com, Dropbox, Google Cloud Storage, Google Drive, HubiC, Yottacloud, Mega.nz, Microsoft Office 365, Microsoft OneDrive, Microsoft Sharepoint, Rackspace Cloudfiles, Rclone, Sia, Tahoae-LAFS
• Duplicity: local drive, acd_cli, Amazon S3, Backblaze B2, Copy.com, DropBox, ftp, GIO, Google Docs, Google Drive, HSI, Hubic, IMAP, Mega.co, Microsoft Azure, Microsoft Onedrive, par2, Rackspace Cloudfiles, rsync, Skylabel, ssh/scp, SwiftStack, Tahoe-LAFS, WebDAV
• Duply: See duplicity
• Kup Backup System: See rsync, bup
• restic: Local disk, sftp, REST, Amazon S3, Minio, OpenStack Swift, Backblaze B2, Microsoft Azure, Google Cloud Storage, other services via rclone
• ZBackup: Local disk