I was comparing Veeam to backing up VM's with SAN Snapshots. If I have a 1TB backup job that I have to store for 28 days, I will have to create 4 synthetic fulls within 28 days equaling 4TB worth of fulls using Veeam. With SAN snapshots, some vendors offer pointer based snapshots that are Hyper-v aware. Each snapshot is a point in time. So to store 28 days of SAN Snapshots, I don't have to store the 4TB of fulls, but only the changes.
Yes, you would need to replicate these snapshots to a secondary array to be safe. But even after replicating, you are still storing less data for backups overall. You are tied to a SAN vendor, which is bad. The cost of storage per TB is more on a SAN then commodity storage that would be used for a Veeam Repository. But when you look at it overall, the 4TB of synthetic full's in a month can be costly. Therefore, I am asking, would it be possible to have the best of both worlds and use Veeam to create synthetic fulls every 2 weeks?
In terms of Reverse incrementals, we only have a single datacenter and AWS/tape are our offsite options. So I meant that reverse incrementals aren't tape (at this point) or AWS friendly to my knowledge. But now that I think of it, you are right, Reverse Incrementals would work well with SAN replication because only the changed blocks would replicate and not the entire Reverse Incremental Full. Is there a good product that can be used to replicate between sites if you are storing your backups on commodity storage (not a san with snapshot technology)?