{"id":53568,"date":"2022-05-31T09:00:37","date_gmt":"2022-05-31T07:00:37","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=53568"},"modified":"2022-05-30T08:20:00","modified_gmt":"2022-05-30T06:20:00","slug":"veeam-v12-sneak-peek-whats-new","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/veeam-v12-sneak-peek-whats-new\/","title":{"rendered":"Veeam v12 Sneak Peek: what's new"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-53589 size-full\" title=\"veeam-backup-replication-v12-announced-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-01.jpg\" alt=\"veeam-backup-replication-v12-announced-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>During the last VeeamON 2022 in Las Vegas, Veeam announced the forthcoming new <strong>Veeam v12<\/strong> that provides new enhancements and some new features.<\/p>\n<p>Still in beta version, the new Veeam v12 contains lots of improvements and simplified procedures to <strong>make the backup administration easier<\/strong>.<!--more--><\/p>\n<p>&nbsp;<\/p>\n<h2>What's new in Veeam v12<\/h2>\n<p>Several enhancements and improvements have been introduced in version 12. Here as follows some of the added features.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53591 size-large\" title=\"veeam-backup-replication-v12-announced-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-02-600x420.jpg\" alt=\"veeam-backup-replication-v12-announced-02\" width=\"600\" height=\"420\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Configuration DB PostgreSQL support<\/h4>\n<p>One of the biggest news of this version is the option to <strong>save the Veeam configuration DB<\/strong> to the free PostgreSQL platform. The use of this platform not only <strong>improves performance<\/strong> but <strong>removes the constraints<\/strong> imposed by the SQL Express that limits the DB size to 10 GB and the use of 4 cores maximum.<\/p>\n<p>Veeam configuration DB can still be saved to the <strong>SQL Express or migrated to PostgreSQL<\/strong>. If the Enterprise Manager is used in the backup infrastructure, both solutions (EM and VBR) must run on the <strong>same DB platform<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53593 size-full\" title=\"veeam-backup-replication-v12-announced-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-03.jpg\" alt=\"veeam-backup-replication-v12-announced-03\" width=\"551\" height=\"386\" \/><\/p>\n<p>Veeam v12 <strong>includes PostgreSQL v14<\/strong> that can be embedded on the same server during the installation of Veeam or to an external server.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53595 size-large\" title=\"veeam-backup-replication-v12-announced-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-04-600x207.jpg\" alt=\"veeam-backup-replication-v12-announced-04\" width=\"600\" height=\"207\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Direct backup to Object Storage<\/h4>\n<p>Veeam v12 now supports the <strong>direct backup to object storage<\/strong>\u00a0without Scale-Out configuration requirement.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53597 size-large\" title=\"veeam-backup-replication-v12-announced-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-05-600x490.jpg\" alt=\"veeam-backup-replication-v12-announced-05\" width=\"600\" height=\"490\" \/><\/p>\n<p>The Object Storage repository can also be configured as <a href=\"https:\/\/nolabnoparty.com\/en\/veeam-v11-hardened-repository-immutability-pt-1\/\">Hardened Repository<\/a>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53599 size-large\" title=\"veeam-backup-replication-v12-announced-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-06-600x427.jpg\" alt=\"veeam-backup-replication-v12-announced-06\" width=\"600\" height=\"427\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><strong>Scale-out Repository<\/strong><\/p>\n<p>Some improvements have been introduced for <a href=\"https:\/\/nolabnoparty.com\/en\/veeam-9-scale-out-backup-repository-setup\/\">Scale-Out repository<\/a>:<\/p>\n<ul>\n<li>Two Object Storage repositories can be used as <strong>performance tier<\/strong> but they must belong to the <strong>same platform<\/strong> (AWS, Azure, S3, etc.).<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53601 size-large\" title=\"veeam-backup-replication-v12-announced-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-07-600x427.jpg\" alt=\"veeam-backup-replication-v12-announced-07\" width=\"600\" height=\"427\" \/><\/p>\n<ul>\n<li><strong>Multiple buckets<\/strong> can be configurated for <strong>Capacity extent<\/strong> but they must be the same type.<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53605 size-large\" title=\"veeam-backup-replication-v12-announced-08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-08-600x480.jpg\" alt=\"veeam-backup-replication-v12-announced-08\" width=\"600\" height=\"480\" \/><\/p>\n<ul>\n<li>Archive tiers can be used for Amazon and Azure.<\/li>\n<li>It's now supported the <strong>export of backups<\/strong> from Capacity or Archive tier.<\/li>\n<li>Now you can <strong>manually rebalance<\/strong> Scale-out.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h4>Per-machine backup chains<\/h4>\n<p>Depending on the installed license, Veeam backup jobs can be run to store data backup in a <strong>single file per job or per VM-based files<\/strong>.<\/p>\n<p>In version 12, the <strong>per-machine backup chain<\/strong> is the default option and <strong>VMs can be moved between backup jobs<\/strong>. Previously this capability was not available and the only way to change the backup chain type was to re-create a new backup chain. <strong>Existing backup chains<\/strong> can be upgraded to per-VM model with a <strong>manual task<\/strong> (one <em>.vbm<\/em> file per VM).<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53607 size-large\" title=\"veeam-backup-replication-v12-announced-09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-09-600x427.jpg\" alt=\"veeam-backup-replication-v12-announced-09\" width=\"600\" height=\"427\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Backup Job<\/h4>\n<p>The Backup job has been improved by introducing some new capabilities.<\/p>\n<ul>\n<li><strong>Health check<\/strong> is now separated and can be run regardless the job schedule.<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53615 size-large\" title=\"veeam-backup-replication-v12-announced-10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-10-600x584.jpg\" alt=\"veeam-backup-replication-v12-announced-10\" width=\"600\" height=\"584\" \/><\/p>\n<ul>\n<li>The <strong>Active Full<\/strong> operation can now be <strong>triggered for a single VM<\/strong> instead of the whole job.<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53617 size-large\" title=\"veeam-backup-replication-v12-announced-11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-11-600x426.jpg\" alt=\"veeam-backup-replication-v12-announced-11\" width=\"600\" height=\"426\" \/><\/p>\n<ul>\n<li>Also the <strong>Retry<\/strong> operation can now be <strong>run per single VM<\/strong> instead of the entire job.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h4>Backup Copy Job<\/h4>\n<p>Version 12 uses option <strong>Periodic copy (pruning)<\/strong> as <strong>Copy mode<\/strong> to optimize the performance by processing the <strong>latest available restore points<\/strong> only (no schedule option available). You can now <strong>switch between Mirror and Periodic copy mode<\/strong> but you must <strong>upgrade to v12 first<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53628 size-large\" title=\"veeam-backup-replication-v12-announced-12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-12-600x427.jpg\" alt=\"veeam-backup-replication-v12-announced-12\" width=\"600\" height=\"427\" \/><\/p>\n<p>In Veeam v12, Backup Copy jobs shares <strong>same engine<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<h4>Copy or move backups<\/h4>\n<p>One of the new capabilities provided in this new version is the capability to copy or move backups across different repositories.<\/p>\n<ul>\n<li>Backups can be moved to <strong>different Repositories<\/strong>.<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53621 size-large\" title=\"veeam-backup-replication-v12-announced-13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-13-600x389.jpg\" alt=\"veeam-backup-replication-v12-announced-13\" width=\"600\" height=\"389\" \/><\/p>\n<ul>\n<li>Backups can be copied to <strong>another repository or location<\/strong>.\u00a0The copy will <strong>preserve the compression<\/strong> of the VM backup when moved to another job.<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53623 size-large\" title=\"veeam-backup-replication-v12-announced-14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-14-600x516.jpg\" alt=\"veeam-backup-replication-v12-announced-14\" width=\"600\" height=\"516\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Exclude VMs from backup<\/h4>\n<p>Specific VMs can now be excluded from backup. VMs added to the <strong>VM Exclusions<\/strong> list <strong>won't be processed<\/strong> by any task (backup, backup copy, replica, etc.).<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53625 size-full\" title=\"veeam-backup-replication-v12-announced-15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-15.jpg\" alt=\"veeam-backup-replication-v12-announced-15\" width=\"471\" height=\"546\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Manually apply retention<\/h4>\n<p>Normally the retention is applied at the\u00a0<strong>end of the backup<\/strong>. In version 12 you can now\u00a0<strong>manually apply<\/strong>\u00a0the retention.<\/p>\n<p>&nbsp;<\/p>\n<h4>MFA<\/h4>\n<p>To <strong>increase security<\/strong>, it is now available the MFA capability to protect the login but it is good for any <strong>single user, no groups<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53630 size-full\" title=\"veeam-backup-replication-v12-announced-16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-16.jpg\" alt=\"veeam-backup-replication-v12-announced-16\" width=\"501\" height=\"413\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Veeam CDP enhancements<\/h4>\n<p>Introduced in v11, <a href=\"https:\/\/nolabnoparty.com\/en\/veeam-v11-continuous-data-protection-cdp\/\">Veeam CDP<\/a> was designed to protect mission critical VMs that require a very low RPO and RTO.<\/p>\n<p>Version 12 extends the CDP capability introducing new enhancements:<\/p>\n<ul>\n<li><strong>Linux Backup Proxy<\/strong> can now be used for CDP<\/li>\n<li>Service Providers can now use CDP for VMware Cloud Director and Veeam Cloud Connect.\n<ul>\n<li>vApp-based failover<\/li>\n<li>Failover is possible also if VMs failed<\/li>\n<li>CDP Filter Driver is enabled per vDC<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53632 size-full\" title=\"veeam-backup-replication-v12-announced-17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-17.jpg\" alt=\"veeam-backup-replication-v12-announced-17\" width=\"553\" height=\"383\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Best Practices Analyzer<\/h4>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/veeam-v11-configure-double-immutable-backups-on-prem-and-cloud-pt-1\/\">Veeam Backup &amp; Replication<\/a> v12 introduces the Best Practices Analyzer that provides <strong>guidelines for an optimium configuration<\/strong> based on experts' recommendations.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-53634 size-large\" title=\"veeam-backup-replication-v12-announced-18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2022\/05\/veeam-backup-replication-v12-announced-18-600x371.jpg\" alt=\"veeam-backup-replication-v12-announced-18\" width=\"600\" height=\"371\" \/><\/p>\n<p>Veeam v12 comes with significant improvements but <strong>doesn't introduce specific new functions<\/strong>. Existing capabilities have been improved with the introduction of those changes claimed by administrators to perform specific tasks or specific business requirements without the hassle to apply <strong>workarounds or tricky solutions<\/strong>.<\/p>\n<p>Bear in mind that <a href=\"https:\/\/www.veeam.com\/\" target=\"_blank\" rel=\"noopener\">Veeam Backup &amp; Replication<\/a> v12 is still in beta version and <strong>some features may change in the GA version<\/strong>.<\/p>\n<p>Veeam v12 should be released <strong>within the end of the year<\/strong>.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>During the last VeeamON 2022 in Las Vegas, Veeam announced the forthcoming new Veeam v12 that provides new enhancements and some new features. Still in beta version, the new Veeam v12 contains lots of improvements and simplified procedures to make the backup administration easier.<\/p>\n","protected":false},"author":3,"featured_media":53589,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[2138,933],"tags":[579,1782,2106,2466],"class_list":["post-53568","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-veeam-en","tag-backup-en","tag-cdp","tag-object-storage","tag-postgresql-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/53568","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=53568"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/53568\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/53589"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=53568"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=53568"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=53568"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}