{"id":59945,"date":"2023-12-12T09:00:07","date_gmt":"2023-12-12T08:00:07","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=59945"},"modified":"2023-12-09T14:49:06","modified_gmt":"2023-12-09T13:49:06","slug":"upgrade-veeam-backup-replication-to-v12-1","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/upgrade-veeam-backup-replication-to-v12-1\/","title":{"rendered":"Upgrade Veeam Backup &#038; Replication to v12.1"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-59963 size-full\" title=\"upgrade-veeam-backup-and-replication-to-version-12-1-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-01.jpg\" alt=\"upgrade-veeam-backup-and-replication-to-version-12-1-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>The procedure to upgrade <a href=\"https:\/\/nolabnoparty.com\/en\/veeam-v12-1-whats-new-pt-1\/\">Veeam Backup &amp; Replication<\/a> to v12.1\u00a0 is pretty simple but you need to follow the correct steps to do to <strong>avoid service disruption<\/strong>.<\/p>\n<p>An <strong>in-place upgrade<\/strong> is supported but the installed version must be <strong>at least version 10a (build 10.0.1.4854)<\/strong>.<!--more--><\/p>\n<p>&nbsp;<\/p>\n<h2>Before upgrading<\/h2>\n<p>Before upgrading, make sure your infrastructure <strong>meets the prerequisites<\/strong>.<\/p>\n<ul>\n<li>Veeam 12.1 requires the <strong>same license format<\/strong> introduced for version 10.<\/li>\n<li>Make sure the <strong>OS where Veeam is installed<\/strong> is still supported.<\/li>\n<li>Make sure the environment and server used <a href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/hyperv\/system_requirements.html\" target=\"_blank\" rel=\"noopener\">meet the requirements<\/a> for Veeam v12.1.<\/li>\n<li><span class=\"List_L1\">If you use <strong>File to Tape jobs<\/strong> they are no longer free with <\/span><span class=\"List_L1\">Veeam\u00a0Backup\u00a0&amp;\u00a0Replication<\/span><span class=\"List_L1\"> 12.1.<\/span><\/li>\n<li><span class=\"List_L1\">If <\/span><span class=\"List_L1\">Veeam <strong>Backup for Microsoft 365<\/strong> is installed on the same machine, upgrade Veeam Backup for Microsoft 365 first.<\/span><\/li>\n<li>If Veeam uses Windows 2019 Backup Repositories <strong>formatted with ReFS<\/strong>, avoid upgrading them to Server 2022. You need to apply a fix first.<\/li>\n<li>If you have some <strong>Scale-Out Backup Repositories<\/strong> configured with immutable performance tier extents make sure all extents have the same immutability settings.<\/li>\n<li>If you use Veeam ONE, <strong>upgrade Veeam ONE first<\/strong>.<\/li>\n<li>If you use <strong>Veeam Backup Enterprise Manager<\/strong>, upgrade this component first then Veeam Backup &amp; replication.<\/li>\n<li><span class=\"List_L1\">If you use <\/span><strong><span class=\"T_Controls\">Veeam Backup Enterprise Manager<\/span><\/strong><span class=\"List_L1\">\u00a0server added to\u00a0<\/span><span class=\"T_Controls\"><strong>Veeam ONE<\/strong>, upgrade Veeam ONE first, then Veeam Backup Enterprise Manager and last Veeam Backup &amp; Replication.<\/span><\/li>\n<li>If you use <strong>Veeam Agents<\/strong>, make sure to upgrade them accordingly. Version 4.0 is no longer supported.<\/li>\n<li>If you use plug-ins for <strong>SAP HANA, Oracle RMAN, SAP on Oracle and Microsoft SQL Server<\/strong>, upgrade<span class=\"List_L1\"> Veeam Backup &amp; Replication first then the plug-ins.<\/span><\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>Upgrade Veeam Backup &amp; Replication to version 12.1<\/h2>\n<p>Download the <strong>.ISO file<\/strong> from Veeam website and run the installer. The <strong>installer detects a previous installed version<\/strong> and display the upgrade option. Click <strong>Upgrade<\/strong> to proceed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59965\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-02-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p>Click <strong>Upgrade Veeam Backup &amp; Replication<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59967\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-03-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p>Click <strong>I Accept<\/strong> to accept the EULA.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59969\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-04-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p>The wizard displays the <strong>Version<\/strong> to upgrade. Since the wizard upgrades the Veeam Server only, select <strong>Update remote components automatically<\/strong> option to also upgrade other Veeam components such as Proxy Servers, Mount Servers, Hardened Repositories and so on. Click <strong>Next<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59971\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-05-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p>If you have an NFR license installed in your system for example, you need to enable the <strong>Update license automatically<\/strong> option. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59973\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-06-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p>The installer wizard checks the System for potential installation issues.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59975\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-07-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p>Select the <strong>Service account<\/strong> to use (LOCAL SYSTEM in the example) and click <strong>Next<\/strong>. As best practice, Veeam Server should <strong>not be joined to any domain<\/strong> or joined to a dedicated management domain with a <strong>one-way trust relation<\/strong> from the production domain.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59977\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-08-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p>In this example Veeam uses a <strong>SQL database<\/strong> to store the configuration DB. Keep in mind that from version 12 the Veeam DB can be stored also to a <a href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/vsphere\/vbr_config_migrate_to_postgresql.html?ver=120\" target=\"_blank\" rel=\"noopener\">PostgreSQL database<\/a>\u00a0and it's the <strong>default option for fresh installation<\/strong>. Click\u00a0<strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59979\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-09-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p>Click <strong>Yes<\/strong> to upgrade the Veeam database.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-59981\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-10.jpg\" alt=\"\" width=\"499\" height=\"181\" title=\"\"><\/p>\n<p>When you are ready, click <strong>Upgrade<\/strong> to begin the upgrade process.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59983\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-11-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p>The procedure to upgrade Veeam Backup &amp; Replication to version 12.1 is composed by six steps:<\/p>\n<p><strong>1. Upgrading Veeam Backup &amp; Replication Server<\/strong><\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59985\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-12-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p><strong>2. Upgrading Veeam Backup &amp; Replication Console\u00a0<\/strong><\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59987\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-13-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p><strong>3. Upgrading Veeam Explorers<\/strong><\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59989\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-14-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p><strong>4. Upgrading Veeam Agent Redistributables<\/strong><\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59991\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-15-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p><strong>5. Upgrading Plug-ins for Veeam Backup &amp; Replication<\/strong><\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59993\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-16-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p><strong>6. Finalizing installation and starting services<\/strong><\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59995\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-17-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p>Click <strong>Finish<\/strong> when the upgrade has been completed successfully.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-59997\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-18-600x467.jpg\" alt=\"\" width=\"600\" height=\"467\" title=\"\"><\/p>\n<p>&nbsp;<\/p>\n<h2>Post upgrade<\/h2>\n<p>After completing the procedure to upgrade <a href=\"https:\/\/nolabnoparty.com\/en\/veeamover-move-and-copy-backups-in-veeam-v12\/\">Veeam Backup &amp; Replication<\/a>, login to Veeam Server.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-59999\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-19.jpg\" alt=\"\" width=\"436\" height=\"351\" title=\"\"><\/p>\n<p>When you first login after the upgrade, the system attempts to <strong>upgrade remote components<\/strong>. Since the system detects that <a href=\"https:\/\/nolabnoparty.com\/en\/veeam-v11-hardened-repository-immutability-pt-1\/\">Hardened Repositories<\/a> are configured in this backup infrastructure, <strong>single-use credentials<\/strong> must be entered once again to allow the upgrade.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-60001\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-20.jpg\" alt=\"\" width=\"522\" height=\"392\" title=\"\"><\/p>\n<p>Select <strong>Set User &gt; Single-use credentials for hardened repository<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-60003\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-21-600x421.jpg\" alt=\"\" width=\"600\" height=\"421\" title=\"\"><\/p>\n<p>Enter the <strong>Username<\/strong> and <strong>Password<\/strong> for the Veeam user used to connect the Hardened Repository. Click <strong>OK<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-60005\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-22.jpg\" alt=\"\" width=\"419\" height=\"400\" title=\"\"><\/p>\n<p>After upgrading the remote components, it may happen the <strong>Hardened Repositories fail to upgrade<\/strong>. Click <strong>Finish<\/strong> to exit the wizard.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-60009\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-24-600x427.jpg\" alt=\"\" width=\"600\" height=\"427\" title=\"\"><\/p>\n<p>&nbsp;<\/p>\n<h4>Hardened Repository issue<\/h4>\n<p>Starting from version 12, Hardened Repositories should be updated automatically with <strong>no need to enable SSH<\/strong> and configure the veeam user as a <strong>member of <em>sudo<\/em> group<\/strong>.\u00a0Unfortunately the <a href=\"https:\/\/www.veeam.com\/veeam_backup_12_1_release_notes_rn.pdf\" target=\"_blank\" rel=\"noopener\">Release Notes<\/a> of v12.1<strong>\u00a0on page 39<\/strong> state that it is once again necessary to <strong>enable SSH<\/strong> and <strong>give <em>sudo<\/em> rights<\/strong> to the Veeam user.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-60011\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-25-600x101.jpg\" alt=\"\" width=\"600\" height=\"101\" title=\"\"><\/p>\n<p>Enable SSH and give <em>sudo<\/em> rights to the Veeam user in the configured Hardened Repositories with the following commands:<\/p>\n<p><span style=\"color: #0000ff;\"># sudo systemctl start ssh.service<\/span><br \/>\n<span style=\"color: #0000ff;\"># sudo usermod -a -G sudo locveeam<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-60013\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-26-600x110.jpg\" alt=\"\" width=\"600\" height=\"110\" title=\"\"><\/p>\n<p>Try again to upgrade the Hardened Repository components. This time the <strong>upgrade succeeded<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-60021\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-27-600x427.jpg\" alt=\"\" width=\"600\" height=\"427\" title=\"\"><\/p>\n<p>Checking the installed version, the <strong>reported build number is 12.1.0.2131<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-60023\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/12\/upgrade-veeam-backup-and-replication-to-version-12-1-28.jpg\" alt=\"\" width=\"450\" height=\"307\" title=\"\"><\/p>\n<p>Remember to <strong>disable SSH<\/strong> and <strong>remove the Veeam user from <em>sudo<\/em> group<\/strong>\u00a0in the Hardened Repository. The procedure to upgrade Veeam to version 12.1 is now complete.<\/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>The procedure to upgrade Veeam Backup &amp; Replication to v12.1\u00a0 is pretty simple but you need to follow the correct steps to do to avoid service disruption. An in-place upgrade is supported but the installed version must be at least version 10a (build 10.0.1.4854).<\/p>\n","protected":false},"author":3,"featured_media":59963,"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,876,584],"class_list":["post-59945","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-veeam-en","tag-backup-en","tag-upgrade-en","tag-veeam-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/59945","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=59945"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/59945\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/59963"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=59945"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=59945"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=59945"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}