Veeam Backup & Replication v12 released

[Arthur]

Website / What's New (PDF)

 

Veeam Backup & Replication v12, the foundational product component of Veeam Data Platform, advances enterprise-grade recovery capabilities that ensure confidence in the face of disaster or cyber-attacks across the hybrid cloud. The following is a list of the major new features and enhancements added in V12.

 

Direct backup to object storage

Take full advantage of the unlimited scalability, built-in reliability and resiliency of on-premises and cloud object storage without having to sacrifice backup and restore performance. With V12, you can leverage object storage both as a regular backup repository and as ANY Scale-out Backup Repository (SOBR) tier. Object storage repositories can also be a target for both primary (i.e., backup) and secondary (i.e., backup copy) jobs.

 

The unique benefits of object storage integration in V12 include:

 

• Direct-to-Object — Whenever possible, protected data will be transferred from backup proxies and agents directly to object storage, avoiding intermediary hops that could potentially affect performance and reliability. Plus, in scenarios when a direct network connection to object storage is not available, you can route the traffic through a redundant gateway servers pool.
   
   
  
• Direct-to-Cloud — Reduce the overall cost and complexity of managing backups at the edge, such as in Remote Office Branch Office (ROBO) environments, with direct backups to cloud object storage. Please note that we continue recommending local backups as the first step for data center environments due to the performance implications and extra cost of achieving the 3-2-1 Rule when backing up directly to cloud object storage.
   
   
  
• Immutable backups — Keep your backups safe in object storage with support for native immutability technologies provided by on-premises and cloud object storage vendors. Malicious actors will not be able to tamper with, encrypt or delete your recent backups for the specified number of days following their creation. GFS backups are automatically protected for the entire duration of the retention policy to satisfy compliance requirements.
   
   
  
• Spaceless full backups — The spaceless full backup technology of ReFS and XFS-based Veeam backup repositories is also available when you backup directly to object storage. Remain flexible with your retention policies with the knowledge that your GFS full backups will not consume additional object storage space.
   
   
  
• Improved storage format — Using our learnings from years of observing our customers storing their real-world workloads on object storage, we were able to significantly simplify our storage format without impacting performance or increasing object storage costs. As a result of removing the local index and the need to synchronize it between local and object storage, this new format brings significantly improved reliability.
   
   
  
• Health check light — Managed-by-Agent backup jobs that use an object storage repository as a target will perform light storage-level data corruption guard scans that will only check if all required objects exist. This provides some balance considering the performance implications and cloud egress costs of full content verification. All backup jobs managed by a backup server avoid these issues with the help of automatically provisioned, in-cloud helper appliances that allow users to perform full health checks.
   
   
  
• Wasabi integration — As one of the most popular object storage options among Veeam users, Wasabi now joins other directly integrated cloud object storage partners with a new, dedicated UI for registering a Wasabi Hot Cloud Storage repository.
   
   
  
• Smart Object Storage API — This newly introduced Smart Object Storage API (SOSAPI) allows object storage vendors to integrate with Veeam Backup & Replication more deeply and improve performance and user experience. Its first version enables vendors to report remaining physical disk space in a bucket and gives them machine-level control over Veeam backup streams. For example, they can instruct Veeam to write backup data of a particular machine directly to the specific cluster node for faster performance. The launch partners for SOSAPI integrations are Scality (software defined storage) and Object First (hardware appliance), with other object storage vendors planning to release their integrations soon.
  

Continues...

[kennysarmy]

Veeam recently announced the release of Veeam Backup & Replication v12, and have made it available for download and installation as of today, Tuesday 14th February 2023.

 

 

Veeam has classified this update as a breaking release, meaning if you upgrade your local Veeam installation to this release before 11:11 Systems (formerly iland) upgrades its Veeam Cloud Connect environment, you will be unable to access your cloud repositories and hosts.

[Arthur]

Veeam recently announced the release of Veeam Backup & Replication v12, and have made it available for download and installation as of today, Tuesday 14th February 2023.

I should have elaborated further at the time, but v12 was available to download last night when I created this thread.

[Jaan]

We've updated here.

 

Only warning we got as part of the update was the 'Backup copy Jobs' have been improved. Not sure why i need to change anything if they continue to work as expected.

 

 

We basically have a backup copy job that 'Copies' the Hyper-v VMs from our San storage to a 'offsite' NAS device.

 

Veeam displays these jobs as legacy.

 

 

I can't seem to find any real answer via the link provided.

 

Anybody else had this?

 

Cheers

[Steve21]

They’ll carry on but won’t have the per VM split/new items etc

 

If you want to update it you need to make a new job but then map it to the old backup so it’ll upgrade it

 

Steve

[Jaan]

They’ll carry on but won’t have the per VM split/new items etc

 

If you want to update it you need to make a new job but then map it to the old backup so it’ll upgrade it

 

Steve

 

Thanks for this.

 

I think this is where i'm confused. I can't seem to find any documentation on the process of change from the Legacy "copy back-up" to the new ones.

[Steve21]

Thanks for this.

 

I think this is where i'm confused. I can't seem to find any documentation on the process of change from the Legacy "copy back-up" to the new ones.

 

You can’t change it as such

 

You create a new job, and in the job settings you can map it to the old backup location/files

 

Similar to if you were mapping a normal job to a new storage location etc

 

Steve

[Jaan]

so do i delete the old copy job first or after i've created the new one? Or doesn't that matter?