Read/write capability for NAS recovery is currently being researched, said Cade. It has also added recovery of NAS shares, but these are via SMB connections and read-only for now. Veeam customers should contact their Veeam account team for details on this.

This native S3 interface will allow Veeam customers to use S3-compatible storage such as Wasabi as a Capacity Tier.

Veeam has also added instant recovery of Veeam backups to Microsoft Hyper-V and SQL and Oracle databases to a production environment. Native S3 interface: Veeam v11 release has continued its native support for S3 interface for Veeams Backup & Replication product. That allows data to be optimised for cost-effective ingress and egress.” “That means we can send much bigger chunks into the cloud archive but still recover at the level of an individual file, virtual machine, and so on. We turn it into an object-oriented chunk so that it’s possible to understand what data is contained,” said Cade. “The key thing is that we don’t just take the backup file and put it in object storage. It is already possible to use cloud performance and capacity tiers as targets, but this allows for policy-driven movement of backups to cloud archive services. Retention periods can be set for any period, during which time the files are locked to any attempt to delete or edit them.Īnother key set of functionality added is to be able to archive to Amazon (S3 Glacier) and Azure Archive. This adds to similar capability in the cloud. It has added ransomware protection that puts backup files into an immutable state on-premise, in any customer hardware. Meanwhile, Veeam has added a few more notable enhancements in v11 (out of around 150 in total).

Everything else can use vSphere replication or storage replication,” said Cade. “We’re aiming CDP at the top 5% of workloads, the mission-critical workloads, such as database servers. In theory, you could run snapshots at much higher frequency to provide much the same thing, but there would be an effect on performance as they have not been optimised to not impact I/O. CDP collects all I/O as it is written, and using only what is new, replicates that to the secondary site.ĬDP is intended to run constantly, so giving ready access to any point in time. Veeam snapshots work differently, by taking a point-in-time copy or building one using deltas. Additionally, there is no physical distance limit to where data can be replicated, said Veeam senior global technologist Michael Cade.