Veeam Backup & Replication v12 – My Top v12 Features


Userlevel 7
Badge +19

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)


48 comments

Userlevel 7
Badge +8

I just had a situation where the vmover saved my bacon. Had to free up some SAN space, and had to data I didn’t want to delete, but didn’t REALLY need to keep around. I moved it off quickly and we are back in business.!

I’ve also bee moving jobs around and it’s been so convenient!

 

Userlevel 4
Badge +1

I wonder if v12 will support ESXi 8?

https://helpcenter.veeam.com/docs/backup/vsphere/platform_support.html?ver=120

It’s supported.

I can confirm it works as well using ESXi 8 in my homelab for a while now. 😎

Amazing Chris, good to know it.

Userlevel 7
Badge +21

I wonder if v12 will support ESXi 8?

https://helpcenter.veeam.com/docs/backup/vsphere/platform_support.html?ver=120

It’s supported.

I can confirm it works as well using ESXi 8 in my homelab for a while now. 😎

Userlevel 4
Badge +1

I wonder if v12 will support ESXi 8?

https://helpcenter.veeam.com/docs/backup/vsphere/platform_support.html?ver=120

It’s supported.

Userlevel 7
Badge +10

Good shout, @coolsport00 that is exactly what Veeamover was born to do @ShrikrushnaBhutekar 
 

 

Userlevel 7
Badge +19

@ShrikrushnaBhutekar - read the post @Rick Vanover shared last week and see if this is what you’re wanting. He talks about VeeamMover, but also changing Repositories.

Can we change backup repository in Veeam console.   version 12

Userlevel 7
Badge +21

Great job @coolsport00!  

 

My favorite is the Vmover.  It’s nice being able to move backups between object storage buckets, or between on prep repos with RefS /XFS without having to rehydrate data.  And it’s great being able to move from an on-prem repo to a object repo and have the repo changed in the job as well!

I think this has been one of the best enhancements for this release.  So many possibilities.

Userlevel 7
Badge +19

Appreciate it @vmJoe 😊

Userlevel 7
Badge +7

Great job @coolsport00!  

 

My favorite is the Vmover.  It’s nice being able to move backups between object storage buckets, or between on prep repos with RefS /XFS without having to rehydrate data.  And it’s great being able to move from an on-prem repo to a object repo and have the repo changed in the job as well!

Userlevel 7
Badge +21

I’m hoping that Per-VM backup chains isn’t becoming a requirement.  The reason for not doing per-VM is to take advantage of dedupe.  If you consider a typical enterprise environment with Prod, Test, and Dev VMs running a largely duplicate dataset being backed-up to disk, the ability to group these into a single backup file that dedupes this data results in huge space savings.

Based on it being configurable as per documentation here:https://helpcenter.veeam.com/docs/backup/vsphere/repository_repository.html?ver=120

 

and  the note about object storage located here: https://helpcenter.veeam.com/docs/backup/vsphere/sobr_add_extents.html?zoom_highlight=Per+machine&ver=120

 

“For object storage repositories that you add as performance extents, this option is selected by default and you cannot disable it.”


looks like it only impacts object storage currently!

Userlevel 7
Badge +21

I’m hoping that Per-VM backup chains isn’t becoming a requirement.  The reason for not doing per-VM is to take advantage of dedupe.  If you consider a typical enterprise environment with Prod, Test, and Dev VMs running a largely duplicate dataset being backed-up to disk, the ability to group these into a single backup file that dedupes this data results in huge space savings.

As far as I can see it is turned on for any repository you add but you can turn it off as well.  So, it is not a hard requirement.

I’m hoping that Per-VM backup chains isn’t becoming a requirement.  The reason for not doing per-VM is to take advantage of dedupe.  If you consider a typical enterprise environment with Prod, Test, and Dev VMs running a largely duplicate dataset being backed-up to disk, the ability to group these into a single backup file that dedupes this data results in huge space savings.

Userlevel 7
Badge +17

Does V12 also supports the OnPremise backup Repository that is Immutable?

AFAIK, Azure Storage account does not support Immutability yet as of this time I write the reply.

Yes, you can have an on-premise object storage repository with immutablility.

Userlevel 7
Badge +7

Hello!

Any cloud provider features at v12?

Especially Veeam Self-Service Backup Portal (VBEM).

CDP replica for sure!

Userlevel 7
Badge +2

Does V12 also supports the OnPremise backup Repository that is Immutable?

AFAIK, Azure Storage account does not support Immutability yet as of this time I write the reply.

Userlevel 7
Badge +21

Hello!

Any cloud provider features at v12?

Especially Veeam Self-Service Backup Portal (VBEM).

There are many features that help improve for Cloud Providers for sure but not sure about this. We are looking forward to many new features ourselves.

Hello!

Any cloud provider features at v12?

Especially Veeam Self-Service Backup Portal (VBEM).

Userlevel 7
Badge +17

Is it still possible to easily extract the veeam accounts with a simple powershell script or is it finally fixed?

 

If you have direct access to the backup server you can extract anything you want from the database. This is the reason why the backup server should be hardened as much as you can.

Userlevel 1

Is it still possible to easily extract the veeam accounts with a simple powershell script or is it finally fixed?

 

Userlevel 7
Badge +21

I wonder if v12 will support ESXi 8?

It will eventually but not right out of the box.  Typically, 2-3 months after release from VMware then Veeam works to support it.

This topic was discussed on the a forum thread too: https://forums.veeam.com/vmware-vsphere-f24/vsphere-8-0-support-t83085.html

Yeah that is where I watch these kind of things when they are asked. 👍

Userlevel 1
Badge +3

I wonder if v12 will support ESXi 8?

It will eventually but not right out of the box.  Typically, 2-3 months after release from VMware then Veeam works to support it.

This topic was discussed on the a forum thread too: https://forums.veeam.com/vmware-vsphere-f24/vsphere-8-0-support-t83085.html

Userlevel 7
Badge +21

I wonder if v12 will support ESXi 8?

It will eventually but not right out of the box.  Typically, 2-3 months after release from VMware then Veeam works to support it.

Badge +1

I wonder if v12 will support ESXi 8?

Userlevel 5
Badge

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.. 

Comment