Skip to main content
  • EN

While attending the VeeamON conference in Las Vegas back in May, Veeam announced they will be releasing Veeam Backup & Replication (VBR) v12 later in the year, and gave several sessions presenting what some of those features will be in the new release. I thought I’d do a write-up of what v12 features I’m looking forward to most, as well as provide a few extra lines of other notable features coming.

Security

-Veeam is upping its security game by implementing Multi-Factor Authentication (MFA) and Group Managed Service Accounts (gMSA). MFA is self-explanatory. From the VBR Menu > Users and Roles option, a Security window opens for you to select MFA for your Veeam user accounts (see figure below). But what about the gMSA? gMSA is a fantastic concept as it allows Veeam to use Active Directory service accounts while not storing the password locally on the Veeam server (i.e. when using for AAIP). Instead, VBR retrieves gMSA passwords on-demand from organization domain controllers.

 


Platform

-Veeam is introducing a new database platform - PostgreSQL v14. Some of the reasons for doing so is first and foremost, like SQL Express, it’s free. But, from a use and scalability perspective, it has no size limit or compute restrictions, and has improved performance over SQL Express. SQL Express will still be an usable option if it’s your preference. PostgreSQL is only going to be in VBR and Enterprise Manager (EM) initially. I would look for it to be part of VeeamONE (VONE) in subsequent VONE releases; nothing definitve shared by Veeam...just my opinion, as it would seem logical for Veeam to do so.

Backup Infrastructure

-Probably one of the most important features upcoming in v12 is the VM Move or Copy feature. Veeam has designed a new VeeaMover technology around Block Cloning with ReFS (Windows) and XFS (Linux). Why is this so important? Customers who deploy Repositories which use some form of Block Cloning can now move their backup data around without worrying about losing space savings with Block Cloning (i.e. rehydrating). You can move a Backup Job from one Repository to another and the Block Cloning is maintained! You can also move individual VMs from one Backup Job to another without losing previous Backup chain data
 


-There’s another somewhat hidden feature coming which customers may find useful – Apply Retention Now. This feature applies only to GFS policies which have Retentions configured in DAYS, not in Restore Points. This feature runs on Repositories and applies to all orphaned backups with time-based (days) retention to free up space from the orphaned backups.

-Per-VM backup chains is now going to be the default. Honestly, from a performance standpoint, I’m not sure why VBR users aren’t configuring their jobs to use this if they aren’t already. Aside from increased performance, you utilize all available streams to your underlying storage (i.e. more ‘bang for your buck’ as it were). Veeam also redesigned Per-VM technology to run a bit differently than in the past by creating a .vbm (metadata) file for every VM instead just one for the whole job. And with this, it is important to note – Backup Copy jobs will only use the Per-VM technology. You will not be able to configure Copy Jobs otherwise. There are a couple exceptions – when using Failover Clusters and Veeam Agents

-A couple other small, but probably welcome features – you will be able to run an Active Full on individual VMs, or Retry individual VMs which failed in a Backup Job, both of which can be run in the Job History view
 


 

-In v12 Veeam will now allow you to have Object Storage in the Performance Tier as well as have multiple buckets in the Capacity Tier. But, the Object Storage must be of the same Platform. You can also do an Extent Rebalance operation to disperse files among the Extents more evenly, but keep in mind all Extents are put in Maintenance Mode when the task runs (i.e. there is downtime for your jobs)

-Health Checks can be done outside a job schedule/backup window, & is the recommended way to do so by Veeam. The cool thing about this is now, depending on when you previously configured this to run, your Job won’t take an exorbitant amount of time to run. The Health Check can be configured to run whenever, outside the Job window. NOTE: Backup & Restore tasks have priority over this task
 


-Lastly, one for all you Cloud-use folks out there, you will now be able to directly backup your data to Object Storage, and have Immutability! Some caveats to note, which makes sense – you can not mix/match Object Storage Platforms (AWS, Azure Google GCS, etc), and you cannot mix non-Object with Object Storage. Another Object Storage change coming is you’ll be able to go from Peformance to Archive Tiers if you like, instead of the need to use the ‘middle-man’ Capacity Tier

Other Noteworthy Features

-Backup Copy Job changes
> Menu options have been consolidated to just the following: Image-level, Application, HPE StoreOnce
> Job Modes engine was changed so are now changeable; and Copy Jobs no longer run continuously

-Global Exclude VM (in VBR’s Main Menu) – can be based on individual VMs or container (i.e. Datastores or Tags)

-Redundant Gateway Servers  Support – anything requiring Gateways - Object Storage, Dedup, etc -  you can now have more than 1 Gateway Server for scalability and redundancy

-IPv6 Support – IPv4 is default when upgrading but IPv6 is preferred when doing a fresh install
> Not supported in: Cloud (AWS, Azure, Google), Nutanix/RHEV, or Unmanaged Agents

-Enhanced Network Internet Traffic Management – this is actually cool for Enterprise environments with multiple Internet traffic speed links. You will now have the ability to configure multiple Internet links, instead of just one
 


-Best Practice Analyzer (from the main view Ribbon) – checks RDP & Remote Registry services; Windows F/W; Immutability; MFA; and credential password protection. As you can see below, my test environment needs work 🙂
 

 

Those are some of the features I’m looking forward to, and some I don’t necessarily use but feel a lot of MSPs and/or Enterprises are highly anticipating. A few recommended VeeamON session titles to review which discuss the above features I’ve shared below. Just go to the VeeamON site, log in, then click the On Demand menu link at the very top of the page.

What features are you most looking forward to?

 

v12: Core Architecture Enhancements, pt1 (Hannes Kasparick & Edwin Weijdema)
v12: Core Architecture Enhancements, pt2 (Hannes Kasparick & Tom Sightler)
v12 Object Storage Enhancements (Anthony Spiteri, Dustin Albertson)

Definitely loving these changes. 👍

I LOVE :

MFA 😍

MOVE backup😍

Another wall in front of attackers !

These are brilliant changes. The ability to backup just a VM in a backup job will come in really handy as will be the ability to run Health Checks whenever.

Hello 

great for all new featurs but for more security because you say the backup is the last bastion, whe n Veeam think to move from platform windows to Linux like all other editor like Nakivo with local or distant immutable repository. 
thanks

 

 

 

Hello 

great for all new featurs but for more security because you say the backup is the last bastion, whe n Veeam think to move from platform windows to Linux like all other editor like Nakivo with local or distant immutable repository. 
thanks

 

 

 

We’re continuing to see Veeam disconnect itself from “Windows only” to “Windows + Linux”, certainly within public cloud they’ve adopted a Linux only approach by basing those public cloud appliances on Ubuntu. In v12 we’ll see agnostic database support for both MS SQL and now PostgreSQL with both Linux & Windows OS support for hosting the database.

 

I wouldn’t want to see it become a Linux only platform however as it can be far more vulnerable if a team has no resources to manage Linux. But +1 for Linux OS support!

Any idea if Veeam will ever get rid of the  full + incremental backup chain?  So many other backup products complete 1 full and after use hash marks to count changes, therefore every backup is a “full”, with no reliance on previous backups.

thanks

 

Any idea if Veeam will ever get rid of the  full + incremental backup chain?  So many other backup products complete 1 full and after use hash marks to count changes, therefore every backup is a “full”, with no reliance on previous backups.

thanks

 

I highly doubt that will ever change but you could ask or put this suggestion on the Forums.

Nice, nice, nice summary @coolsport00 !!! I agree, those new features / changes are incredible. Looking forward to implement this version at the customers.

@Amiller are you talking about amending new data into the main “full” file? I would never want that in the Veeam product because that could easily lead to fragmentation & bloat within the file, I also wouldn’t want any manipulation of the full file because this would be incompatible with immutable backups in their present form, where the files are locked. Finally, I don’t want any unnecessary manipulation of existing files, the benefit to a full + incrementals is if the incremental backup failed due to any number of reasons such as BSOD or power failure, the pre-existing full & previous incremental points would all have a high probability of surviving the fault without any corrupted data, as they were static and only read from, whereas a manipulated file is questionable.

 

If that’s not how your other backup software works I’d love to know more and see if there’s some benefits to Veeam using this 🙂

Thank you @Nico Losschaert . Yes...some great changes ahead! 😊

MFA is the way 😍

Nice recap!

MFA is the way 😍

This is going to be a great thing for security for sure. 😎

Is immutability finally supported with Azure blob in this release?

Is immutability finally supported with Azure blob in this release?

I do not believe it will be as of yet.

Had a webinar about V12 this morning. There was no immutability for Azure on the slides….

Very nice post,thanks. Looking forward to try all these features on our environment, move backup and retry individual, I think I´ll love them 

I must admit that skipping the middle man capacity tier will be much welcomed from my point of view 🙂 We have never used it so far (beside the exercises and disaster training) and it will certainly reduce the cost for us and hopefully give us a little more margin on our services. 

Have you been able to test or let us know if we can write live to a S3 bucket. To date it is necessary to create a backup in Y with a copy on disk.Thanks for your feedback

Yes, you will be able to write your backups directly to object storage in V12.

 

Let's go even further. Could we consider creating the Veeam Server via AWS Marketplace V12, fetching the data from an on-prem server and launching a backup on AWS S3 live? The idea is to put Veeam in the cloud, before migrating the data server 100% to the cloud.

I have never done such a scenario. I think this could be possible, because you should be able to attach and use a AWS S3 bucket from a VBR server on AWS….
Just be sure not to use this bucket with two servers at the same time.

But we have some cloud experts here in the community who can tell us for sure….

will we be able to ship directly from veean agents to immutable amazon s3 buckets?

That is certainly something I hope for to protect our VM-customers in Azure.. 

I though soft-delete in Azure was a kind of protection for Ransomware attack (Microsoft claim it is). But it is not. You can actually just switch it off, and you can then also delete EXISTING backups.. 

I wonder if v12 will support ESXi 8?

Comment


Terms & Conditions