Portal 9.50

Release Notes, January 13, 2026

1 Overview

Portal is a web-based interface for centrally managing server backups and restores.

Portal is intended for use with:

• Windows Agent and Plug-ins version 6.7 and later

• Hyper-V Agent version 7.30 and later

• vSphere Recovery Agent version 8.40 and later

• AIX Agent version 6.00 and later

• HP-UX version 6.72 and later

• Solaris version 6.73 and later

• Linux Agent version 6 and later

IMPORTANT: Beginning with Windows Agent 8.71, Linux Agent 8.63, vSphere Recovery Agent 8.80, AIX Agent 9.00 and Hyper-V Agent 9.10, when an agent tries to connect to Portal, it checks whether the public key of the Portal AMP Proxy certificate is different than when the agent first connected to Portal. We recommend updating the Portal certificate before new agents are registered to Portal or existing agents are upgraded to these versions.

1.1  Release History

Version 9.50.0166, January 13, 2026

1.2  Compatibility

API – Monitoring	Portal 9.50 is compatible with API – Monitoring 1.50 or later.
Vault	For computer and job data deletion, data must be stored in a version 8.56 or later vault that is registered to the same API – Monitoring instance as Portal. For intra-daily backup schedules, Windows Agent 8.90 or later, Linux Agent 8.90 or later, AIX Agent 9.00 or later or vSphere Recovery Agent 9.11 must back up data to a version 8.60 or later vault.
Reports	Portal is compatible with Reports version 2.74 or later.
Web browsers	Portal is compatible with the latest version of Google Chrome, Mozilla Firefox and Microsoft Edge. Note: Portal is no longer supported with Microsoft Internet Explorer.

1.3  Supported Platforms

Portal components are supported on the following 64-bit operating systems:

• Windows Server 2025

• Windows Server 2022

• Windows Server 2019 Standard

• Windows Server 2016 Standard

Portal is only supported on English versions of the supported operating systems. Portal servers should be kept up to date with the latest Windows updates.

2 New Features

Registration-Only Users For Child Sites:

A registration-only user is now created automatically for each child site in Portal. Registration-only user credentials can be used to register agents to a site, but cannot be used to sign in to Portal.

Super users and Admin users can:

• View the registration-only user for a child site on the site's Users tab on the Sites page. Registration-only users do not appear on the Users page in Portal.

• Change the password for a registration-only user.

• Disable a registration-only user so that it cannot be used for registering agents to Portal, or enable a registration-only user that has been disabled.

Create a Child Site with a User and Other Components

In parent sites where Admin users can manage child sites, Admin users can now use a wizard to create child sites with the following components needed for backing up servers:

• A registration-only user

• (Optional) An Admin user

• A vault profile

• (Optional) Agent auto-configuration settings.

By default, the Create New Site wizard is disabled. When this feature is disabled, the wizard does not appear when an Admin user clicks the “Create New Site” button on the Sites page, and the Admin user must create child sites and other components separately.

To enable the site creation wizard feature, see the Portal 9.5 Installation and Configuration Guide.

Agents with New Backup Jobs Appear as "OK"

If an agent has a new backup job that has not run, the agent status is now "OK" for 24 hours. If the new job does not run within 24 hours, the agent status then changes then to "OK with warnings".

In previous Portal versions, an agent's status was "OK with warnings" as soon as it had a new job that had not run yet.

UI Improvements

Improvements have been made throughout the Portal UI, including the following:

• Sites are sorted alphabetically in site lists throughout Portal. For example, site lists are sorted alphabetically when assigning users to sites, adding dashboard messages, and automatically configuring computers.

• On the Computers page, you can scroll through available groups in the filter row.

• When assigning users to child sites, a horizontal scroll bar allows you to view long site names.

• When entering site information, field values are validated to ensure that they do not exceed the maximum number of characters.

Additional Checks Before Deleting Online Computer Data:

If your Portal instance supports vault data deletion, additional validation is performed when you attempt to delete an online computer. This validation ensures that the correct data would be deleted if you fully delete the computer. If the validation fails, Portal marks the computer as ineligible for data deletion. In earlier Portal versions, these checks were only applied when deleting offline computers.

Localization

Portal text for recently-added features has been updated in non-English languages.

Security Improvements

Security improvements have been made throughout Portal.

3 Installation Notes

3.1  Installation Requirements

Portal components can be installed as a distributed system (recommended) or on a single server.

3.1.1  Hardware Requirements: Distributed System

The following table shows hardware requirements and recommendations when Portal is installed as a distributed system (recommended):

System	Hardware	Minimum	Recommended
Web Server	Processor	Xeon/Opteron 1.4 GHz	Xeon/Opteron 2+ GHz quad core
	Memory	4 GB	8+ GB
	HDD	20 GB	40+ GB
Database, Notification, Registration and Status Server	Processor	Xeon/Opteron 1.4 GHz	Xeon/Opteron 2+ GHz quad core
	Memory	8 GB	12+ GB
	HDD	120 GB	140+ GB
AMP Proxy and Redirector	Processor	Xeon/Opteron 1.4 GHz	Xeon/Opteron 2+ GHz quad core
	Memory	4 GB	16 GB
	HDD	20 GB	60+ GB

3.1.2  Hardware Requirements: Single System Deployment

The following table shows hardware requirements and recommendations when Portal is installed on a single system. The single system configuration is not recommended, but can be used for environments with fewer than 500 Agents.

Hardware	Minimum	Recommended
Processor	Xeon/Opteron 1.4 GHz	Xeon/Opteron 2+ GHz quad core
Memory	8 GB	16+ GB
HDD	120 GB	120+ GB

3.1.3  Virtual Hardware: Minimum Requirements

In a virtualized environment with fewer than 500 Agents, the Portal Web Server should be installed on a virtual machine with a minimum of 2 CPUs (logical processors) and 4 GB of memory (RAM).

This recommendation is provided as a guideline for small environments. For larger environments and improved performance, additional virtual machine resources are recommended.

3.1.4  Software Requirements

The following software must be installed before you can install Portal:

• Web Server (IIS) 8.0 or later, including all role services that are installed by default, plus the following role services and features:

  • Under Common HTTP Features:

    • Static Content

    • HTTP Errors

    • HTTP Redirection

  • Under Application Development:

    • .NET Extensibility 4.x

    • ASP.NET 4.x

    • ISAPI Extensions

    • ISAPI Filters

      Note: Make sure that ASP.NET and .NET Extensibility are turned on in Windows features, particularly if IIS is installed before ASP.NET.

  • Under Security:

    • Windows Authentication

  • Under .NET Framework 4.x Features:

    • .NET Framework 4.x

    • ASP.NET 4.x

    • HTTP Activation

• SQL Server or SQL Server Express 2022, 2019, 2017, 2016 or 2014 (64-bit) installed with mixed mode authentication and case-insensitive collation and running. The latest SQL Server service packs and updates are recommended.

Note: Anti-virus software can have a negative impact on the performance of some Portal system components. The effect of anti-virus software on SQL Server should be minimal.

3.2  Conditional Requirements

If you install Portal as a distributed system (recommended), the software required on each system depends on the Portal components installed. For more information, see the Portal Installation and Configuration Guide.

For increased security, we recommend that you:

• Enable TLS in the SQL Server instance, to ensure secure communications between SQL Server and Portal.

• Disable some older cipher suites on Portal systems which are exposed to the Internet. This could cause older Agents to lose connection with Portal, but newer agent versions will continue to work.

• Configure IIS to enforce HSTS for the Portal website.

• Prohibit unprivileged access to Portal front-end servers. Bind the Portal Services Website only to 127.0.0.1 (localhost) and do not expose it on the Internet.

• Disable the default website and enable the request smuggling filter on Portal UI servers.

For more information about these security recommendations, see the Portal Installation and Configuration Guide.

We recommend using Window authentication for Portal database access. To use Windows authentication for Portal database access in a distributed system, all systems where Portal components are installed must be members of the same domain. For more information, see the Portal Installation and Configuration Guide.

To install Portal with a remote SQL Server, install the sqlcmd utility from Microsoft on the machine where you are installing Portal. See https://docs.microsoft.com/en-us/sql/tools/sqlcmd-utility?view=sql-server-ver15. Otherwise, a “failure to create database” error might occur during the installation.

We recommend turning off macros in Microsoft Excel when using Portal, particularly if you export reports in XLS or CSV format and open these reports in Excel.

3.3  Licensing

You do not require a license to use Portal. You do require licenses from the vault for agents and features such as plug-ins.

3.4  Install/Upgrade

The Portal installation kit name is: OpenTextServerBackupPortal-9-50-0166.exe

You can use the Portal installation kit to install Portal 9.50, or to upgrade Portal from version 9.40 or 9.31 to version 9.50.

In a fresh install of Portal 9.50, Portal files are installed in C:\Program Files\OpenText Server Backup. If you upgrade a Portal instance that was installed in C:\Program Files\Carbonite Server Backup, Portal files remain in C:\Program Files\Carbonite Server Backup.

To upgrade Portal to version 9.50 from a pre-9.31 version, first upgrade Portal to version 9.31 and then upgrade to version 9.50. When upgrading Portal from an earlier Portal version, we recommend skipping only one Portal version at a time. For example, to upgrade Portal from version 9.20, upgrade Portal from version 9.20 to 9.31, and then 9.31 to 9.50.

Before upgrading Portal, make sure that there is enough free space on the system for backing up the Portal databases. Portal databases are backed up automatically during an upgrade.

For installation, upgrade and configuration instructions, see the Portal Installation and Configuration Guide.

4 Limitations, Fixes and Known Issues

4.1  Limitations

• Agents can only register to Portal using IPV4 addresses. IPV6 addresses are not supported.

• When you restore a job from another computer, the target computer must have the correct plug-in installed. For example, you can only restore a SQL job to a computer where the SQL Server Plug-in is installed.

• Issues can arise if you manage an agent using both Portal and the legacy Windows CentralControl. Do not manage the same agent using both Portal and Windows CentralControl.

4.2  Fixes

• In the Daily Status Report, a duplicate entry dated "01.01.1900" no longer appears for an unscheduled backup job that ran recently but where the agent is offline. (2454648)

• An issue has been resolved where, when an agent was re-registered to a vault, its jobs were sometimes associated with the wrong vault registration. A script provided with Portal 9.50 can fix any instances of the problem that occurred previously. (2453512)

• When entering contact information for a site, if you enter a value that exceeds the maximum allowed number of characters for a field, a validation message now appears instead of an "unknown exception" message. (2452775)

• A stored procedure for addressing possible database deadlocks has been added to the WebCC database. This "DeleteAgentPresence" stored procedure can be run daily or weekly to clean up database records. (EV-97552, 4830761)

4.3  Known Issues

• In a Portal instance where the Login page is customized and two-factor authentication is enabled, an error message can appear when users click the Take Me To Portal button after resetting their Portal passwords. This problem can occur if special characters are encoded in custom CSS for the login page.
  WORKAROUND: Paste custom CSS for the Portal login page into an HTML encoding tool. If the tool encodes any special characters in the CSS, modify the CSS so that it does not include encoded special characters. You can then use the CSS to customize the Portal login page. (4409360)

• When a Super user tries to upload a Windows Agent version 9.30 or later installer to Portal version 9.30 or earlier for automatic agent upgrades, an error message states that the installation kit is not a valid agent installer.
  WORKAROUND: When signed in to Portal as a Super user, on the Agent Upgrades tab on the Global Settings tab, select "I acknowledge that this option is not recommended" and turn on the "Allow agent installers that are not signed by Carbonite or OpenText" toggle. A Super user can then upload the Windows Agent installation kit. (EV-97091)

• Vault data deletion requests fail if TLS 1.0 and 1.1 are not enabled on a Portal server.
  WORKAROUND: Configure Portal to use TLS 1.2 for vault data deletion requests. For more information, see the Portal Installation and Configuration Guide. (EV-90610, EV-80448)

• If two-factor account verification is enabled in a Portal instance where single sign-on is configured, users who set up two-factor account verification cannot move past account verification screens when they try to sign in to Portal.
  WORKAROUND: Do not enable two-factor account verification in a Portal instance where single sign-on is configured. (EV-88598)

• If you try to edit a Hyper-V job where credentials are entered for specific VMs in the job, but one of the VMs is no longer available in the Hyper-V environment, an "Oops! Server Error" message appears in Portal.
  WORKAROUND: Delete the Hyper-V job and add the remaining VMs to a new job. To prevent this issue, if you plan to delete VMs from a Hyper-V environment, remove the VMs from the Hyper-V backup job before deleting them from the Hyper-V environment. (EV-84450)

• When a computer has been re-registered to a vault, the Monitor page does not indicate whether Local System and Image jobs on the computer protect the entire server.
  WORKAROUND: For each Local System and Image job on the computer, select "Edit Job" and then click Cancel or Save in the Edit Job dialog box. (EV-63557)

• When you try to recover jobs and settings from an offline Hyper-V Agent in a large Hyper-V environment, Portal sometimes times out and the recovery cannot be completed.
  WORKAROUND: A configuration change in Portal can allow the Hyper-V Agent recovery to succeed. For more information, please contact Support. (EV-47193, EV-47032)

• After upgrading Portal to version 8.84 or later, custom CSS specified for the Portal login page does not work correctly.
  WORKAROUND: On the Default Visual Customizations tab on the Global Settings page, remove any line breaks from selector lists in the Login Page Custom CSS. (EV-42186)

• In the Usage Summary report, job names may be missing if a job was moved from one vault to another. 
  WORKAROUND: Run a hotfix for DTS-28838 on the EVault Reports database. This hotfix is available from your service provider.

• Portal time zone handling can result in confusing process dates and times. Some dates are shown in the Agent time zone and some dates are shown in the browser time zone. For example, Portal shows backup dates and times in the user's time zone, but log information appears in the Agent's time zone. (31881, 31107)

• If you try to restore a vSphere VM from an alternate location, an error states that the safeset is offline and the restore cannot be completed.
  WORKAROUND: Manually synchronize a vSphere Agent job before trying to restore a VM from an alternate location. (27833)