Object, object, object! The big thing from VeeamON was that Object is going to become a first-class citizen. What all does that mean?
Primary backups: You can now use object as the primary backup destination. If you immediately thought “wow, that sounds like a situation to get yourself in trouble,” it could be. But remember, object doesn’t only mean cloud. Yes, you could do primary backups directly to object storage in the cloud, but there are dozens of onsite object storage vendors that could also provide local, low latency, high bandwidth object storage. What major benefit would we get with that? Yes, you’ll be able to now have your primary backups immutable with object storage for extra protection. Rather than your only surviving non-encrypted copy being in the cloud, behind latency, bandwidth limitations and egress charges, you can now have a surviving copy onsite. This does NOT preclude you from following the 3-2-1 rule of 3 copies of your backups on 2 different media with at least one offsite.
Instant-On from object: You can now do instant-On restores from object storage. Again, if you think of object only as a cloud-based thing, this might not make sense… unless you’re booting into the cloud itself. However, if you have onsite object storage for primary backups, being able to instant-on those backups to your production environment is very important.
SoBR Object Storage: You can now have multiple Object Storage buckets in a single SoBR, allowing for wider as well as deeper scaling, with performance backups being on object, moving copies off to scale-out
File backups to storage: Directly backup to object storage for files.
Agent backups to storage: Directly backup agents to object storage. This is a place where the cloud as the primary/initial repo might make a lot of sense, allowing a mobile laptop to backup straight to the cloud wherever it goes? Sounds like a winner.