Veeam has introduced MFA for the Veeam console. You can now simply create a new object repository and point your backup jobs and copy jobs to the new repo. In most cases this required carving out additional staging or swing space for backups to land temporarily – not an ideal option. While this method was functional, it added complexity and reduced flexibility as far as choosing which backups you wanted tiered.

Previously the only way you could store backups on object storage was to build a Scale-Out repository and choose the tiering option (capacity tier). You have the ability to directly back up or create backup copy jobs (using GFS if you would like) to store these backups directly on cloud storage. This is a feature that I have a lot of people ask about – you can now back up your workloads directly to object storage (Azure, AWS, Wasabi, etc.) and treat as if it was an on-prem repository.

Veeam Backup & Replication v12 is no exception… in fact, it has over 500 new features (which is likely a record!) and there are some great enhancements I wanted to highlight in this blog post. It filled a gap in backup products early on by backing up VMs at the machine level and not requiring agents to be installed on the guest OS to perform most of the functionality (backups, restores, etc.)Įach new release has always been carefully crafted to have new features users have been waiting for and they have continued to push the envelope on a quality backup product further with each release. Veeam Backup & Replication has been a go-to backup product for virtual environments for the past 15 years.

Veeam best practice backup job