{"id":1798,"date":"2026-03-02T23:36:43","date_gmt":"2026-03-03T05:36:43","guid":{"rendered":"https:\/\/zewwy.ca\/?p=1798"},"modified":"2026-03-09T13:40:56","modified_gmt":"2026-03-09T18:40:56","slug":"veeam-13","status":"publish","type":"post","link":"https:\/\/zewwy.ca\/index.php\/2026\/03\/02\/veeam-13\/","title":{"rendered":"Veeam 13"},"content":{"rendered":"

<\/span>Veeam 13<\/span><\/h1>\n

It’s out now, but seem many admins are not pleased with how things are going. Due to how bloaty the software has become. See here for the thread which discuses a feature request to select which components should be installed with the application.<\/p>\n

Feature Request: Select Components to Install\/Upgrade – R&D Forums<\/a><\/p>\n

I have to agree with the sentiment here, V8 was literally only 800 MBs in size, compact and efficient. V13 has now balloon to over 18 Gigs, which is absolutely mind boggling. Now with components you can’t choose to install or not leaves a larger attack surface that you have to audit and compare against. Along with additional storage space requirements, memory requirements, all for features or services in which you may not even need. I recommend you read the thread, and if you, yourself are a sysadmin having to install and manage Veeam server instance, leave a like in hopes we can bring back some sanity to an otherwise great product.<\/p>\n

In this post I’ll be upgrading my home lab instance from Veeam12 to 13, and I guess we’ll see the lack of component selection along the way.<\/p>\n

<\/span>Step 1: Source Software Acquisition<\/span><\/h2>\n

I got Veeam 13 from here: Veeam Software for Enterprise<\/a> however, note this is a regwalled link and they want your email and phone number for some odd reason… so use whatever tactics you have to, to keep your information private and secure.<\/p>\n

\"\"<\/a><\/p>\n

<\/span>Step 2: Mount and Install<\/span><\/h2>\n

How you mount is up to your system, in my case I attached the ISO to my Veeam VM using VMRC, then ran setup.exe<\/p>\n

\"\"<\/a><\/p>\n

and thennnnn….<\/p>\n

\"\"<\/a><\/p>\n

and then….<\/p>\n

\"\"<\/a><\/p>\n

and then…..<\/p>\n

\"\"<\/a><\/p>\n

no choice, and then….<\/p>\n

\"\"<\/a><\/p>\n

and thenn….<\/p>\n

\"\"<\/a><\/p>\n

so dumb… ok.. check off both and then…<\/p>\n

\"\"<\/a><\/p>\n

and thennnnn….<\/p>\n

\"\"<\/a><\/p>\n

Let’s get the first one out of the way, it needs over 50 Gigs of free space, I know insane, so lets see if we can get it that… expand the HDD and bam…<\/p>\n

\"\"<\/a><\/p>\n

Veeam v13 introduces stricter OS\u2011level requirements<\/strong> and drops support for older Windows versions<\/strong> for any<\/em> feature that could<\/em> use AAP\u2014even if you don\u2019t currently use it.<\/p>\n

From the v13 system\u2011requirements updates, Veeam is removing or deprecating support for older platforms to simplify code and improve security. This includes Windows 10\/11 builds that no longer meet the updated criteria.<\/p>\n

Because AAP interacts deeply with the guest OS (VSS, credentials, application services), Veeam checks all protected VMs<\/strong> for compatibility during the upgrade, not just those with AAP enabled. If any VM is running a Windows build that falls into the \u201cdeprecated or limited support\u201d category, Veeam surfaces a warning.<\/p>\n

After I removed all Backup jobs pointing to older target VMs (even though non of the had AAP enabled), That warning disappeared. Even with all jobs removed, the last two remained.<\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

On Veeam Backup Servers where Veeam Backup & Replication was initially installed with an older version and has been upgraded over the years, the initial Veeam Backup Server Certificate may lack the “Basic Constraints” extension, which can cause issues with Platform Plug-Ins.<\/p>\n

\n
\n
\n

Issue Validation<\/b><\/p>\n

You can view the current Backup server certificate in Main Menu > Options > Security:<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n
<\/picture>\"The<\/a><\/div>\n
<\/div>\n<\/div>\n<\/div>\n
\n
\n
<\/picture>\"The<\/a><\/div>\n
<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n<\/picture>\"Screenshot<\/a><\/p>\n
Basic Constraint Missing<\/i><\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n<\/picture>\"Screenshot<\/a><\/p>\n
Basic Constraint Present<\/i><\/div>\n
<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n

Resolution<\/b><\/p>\n

\n
\n
\n

Note:<\/b>\u00a0If your environment does\u00a0not<\/b>\u00a0use the default self-signed certificate, you must ensure that the CA-signed certificate you provide to Veeam Backup & Replication contains the\u00a0Basic Constraints<\/b><\/code>\u00a0extension, and\u00a0Subject Type = CA<\/b><\/code>\u00a0must be set within that extension.<\/p>\n

 <\/p>\n

For deployments using the self-signed Veeam Backup Service Certificate, a new one must be generated:<\/p>\n

    \n
  1. From the Main Menu, click Options<\/li>\n<\/ol>\n<\/div>\n<\/div>\n<\/div>\n
    \n
    \n
    <\/picture>\"The<\/a><\/div>\n<\/div>\n<\/div>\n
    \n
    \n
    \n
      \n
    1. In the Options dialog box, select the Security tab.<\/li>\n
    2. On the Security tab, click\u00a0“Install…<\/strong>“in the “Backup server certificate”\u00a0section.<\/li>\n<\/ol>\n<\/div>\n<\/div>\n<\/div>\n
      \n
      \n
      <\/picture>\"The<\/a><\/div>\n<\/div>\n<\/div>\n
      \n
      \n
      \n
        \n
      1. In the Certificate creation wizard, select the option for\u00a0Generate a new certificate<\/b>, and click\u00a0Next.<\/b><\/li>\n<\/ol>\n<\/div>\n<\/div>\n<\/div>\n
        \n
        \n
        <\/picture>\"The<\/a><\/div>\n<\/div>\n<\/div>\n
        \n
        \n
        \n
          \n
        1. On the Generate Certificate step, leave the friendly name as\u00a0Veeam Backup Server Certificate<\/b>, and click\u00a0Next<\/b>.<\/li>\n<\/ol>\n<\/div>\n<\/div>\n<\/div>\n
          \n
          \n
          <\/picture>\"The<\/a><\/div>\n<\/div>\n<\/div>\n
          \n
          \n
          \n
            \n
          1. On the Summary steps, click\u00a0Finish.<\/b><\/li>\n<\/ol>\n<\/div>\n<\/div>\n<\/div>\n
            \n
            \n
            <\/picture>\"The<\/a><\/div>\n
            <\/div>\n
            Retry and.. oh look it’s gone now…<\/div>\n
            \n

            Option A \u2014 Remove old plug\u2011ins from \u201cBackup Infrastructure \u2192 Plug\u2011ins\u201d<\/strong><\/p>\n

            If any plug\u2011ins appear there, remove them.<\/p>\n

            Option B \u2014 Clean stale entries from the configuration database<\/strong><\/p>\n

            This requires Veeam Support. They run a script to remove:<\/p>\n