Does it make sense to use object storage for backup?

Question

Backup

I read about Veeam - a bunch of tasty things like synthetic full backups and deduplicated copying, when only the changed block is copied, and a pointer to the change is created in the storage and I have 2 whole files of different versions in the storage, but occupying only the file + the changed block. Do I understand correctly that dehydration chips work only in object storages and it makes much less sense to rent the same SMB\CIFS storages under Veeam?

Answer 1

We look at Copy-On-Write file systems like btrfs / zfs / xfs, in which creating and working with snapshots does not affect performance and is almost instant (on lvm volumes, you can also do snapshots, but at the cost of a multiple decrease in speed), thus creating a backup = creating and storing a snapshot, physical space is not wasted, more precisely, only for storing changed blocks.
Windows ntfs also has a shadow copy, I don’t know how effective the implementation is there, but I think it’s just as good