OpenText Server Backup
Portal 9.60.0291
Release Notes, June 16, 2026
1 Overview
1.1  Release History
1.2  Compatibility
1.3  Supported Platforms
2 New Features
3 Installation Notes
3.1  Installation Requirements
3.1.1  Hardware Requirements: Distributed System
3.1.2  Hardware Requirements: Single System Deployment
3.1.3  Virtual Hardware: Minimum Requirements
3.1.4  Software Requirements
3.2  Conditional Requirements
3.3  Licensing
3.4  Install/Upgrade
4 Limitations, Fixes and Known Issues
4.1  Limitations
4.2  Fixes
4.3  Known Issues
5 PRODUCT SUPPORT
5.1  Technical Support
5.2  Product Updates
5.3  Documentation

© 2026 Open Text
The release notes are governed by the Terms of Service found here. The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
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.60.0291, June 16, 2026
1.2  Compatibility
API – Monitoring | Portal 9.60 is compatible with API – Monitoring 1.50 or later.

Director

For computer and job data deletion, data must be stored in a Director 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 Director 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
Multifactor authentication with authenticator apps
Portal now supports multifactor authentication (MFA) using authenticator apps such as Microsoft Authenticator or Google Authenticator, that generate time-based one-time passwords (TOTPs). Previously, MFA was only available through codes sent in SMS messages or automated voice calls using services from Twilio or TeleSign.
Super users can enable MFA with authenticator apps on the Global Settings tab in Portal. If both authenticator apps and SMS/Voice MFA are enabled in a Portal instance, a user can only use one authentication method at a time, but can switch to the other method.
Users can set up MFA using authenticator apps when prompted at sign in or in their profile settings.
Modernized Dashboard
The Dashboard has been updated with a modern layout and design. Cards and graphics on the Dashboard provide a clear overview of your agents and backups, and highlight any issues that might need attention.
Information cards on the Dashboard now show:
•	The total number of computers in your sites.
•	The number of jobs with potential ransomware threats.
•	The number of backup jobs where the last backup was successful.
•	The number of backups that need attention.
You can click a card to navigate to related information in Portal.
A Backup Job Status graph on the Dashboard shows job backup statuses for the past 28 days. Each job is counted in one of the following categories each day, based on the outcome of backups that started on that day:
•	Protected: Jobs where at least one backup completed without warnings.
•	Protected with warnings: Jobs where at least one backup completed with warnings or was deferred, but no backups completed without warnings or errors.
•	Attention required: Jobs where at least one backup completed with errors, failed, was cancelled, or had no files backed up. No backups that started that day completed with or without warnings.
•	No backup: Jobs where backups were missed, skipped, or in progress, or there was no backup activity on the day.
You can point to a specific date on the Backup Job Status graph to view a tooltip with the number of jobs in each category on that date.
Note: Hyper-V backup jobs are not included in the Backup Job Status graph.
The following charts also appear on the Dashboard:
•	Job Type chart, which shows the number of backup jobs of each type, such as Image, UNC, Exchange, Hyper-V, and vSphere.
•	Online & Offline chart, which shows the number of agents that are online, have been online in the past 7 days, and have been offline for more than 7 days.
To view notifications of recent backups, restores, and configuration changes, click the "Feed" tab in the middle of the Dashboard. To view messages from your service provider and notifications of newly-added computers, click the "News" tab. These tabs replace the "What's New" and "Status Feed" items that appeared in the Notification Center in previous Portal versions.
Backup History Graphics on the Monitor Page
On the Monitor page, Backup History graphics now show jobs' backup statuses for the past 28 days (excluding the current day). In previous Portal versions, the Monitor page only showed the last backup status for each job.
Backup History graphics appear in a new "Backup History (28 days)" column on the Monitor page. Each graphic consists of a row of rectangles, where each rectangle represents a day, and its color indicates the job's backup status for the day:
•	Completed (green): At least one backup that started that day completed successfully without warnings or errors.
•	Completed with warnings (yellow): At least one backup that started that day completed with warnings or was deferred, but no backups completed without warnings or errors.
•	Completed with errors (red): At least one backup that started that day completed with errors, failed, was cancelled, or had no files backed up. No backups that started that day completed with or without warnings.
•	No backups (gray): Backups for the job were missed or skipped, are in progress, or had no backup activity.
You can point to a specific date to view a tooltip that shows the job's backup status for that date.
Note: Backup History graphics are not available for Hyper-V backup jobs, and do not appear in exported data or emailed reports.
To accommodate the new Backup History column, columns on the Monitor page have been reordered.
Clear Information about Hyper-V Backup Retries
The Hyper-V Create New Job and Edit Job dialog boxes now indicate that failed VM backups are automatically retried until the backup job completes. This behavior has not changed; Hyper-V Agents have always retried failed VM backups. Text in the dialog boxes is intended to clarify the existing behavior.
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-60-0291.exe
You can use the Portal installation kit to install Portal 9.60, or to upgrade Portal from version 9.50 or 9.40 to version 9.60. 
In a fresh install of Portal 9.60, 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.60 from a pre-9.40 version, first upgrade Portal to version 9.40 and then upgrade to version 9.60. 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.31, upgrade Portal from version 9.31 to 9.50, and then 9.50 to 9.60.
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
•	An issue has been fixed where expanding an agent to view its jobs could, in rare cases, result in an "Index was outside the bounds of the array" error. (5078925)
•	An issue in Portal 9.50 has been resolved so that an internal server error no longer occurs in some cases when a site is deleted. (5208660, 5185580)
•	When agents try to register to Portal, NullReferenceException errors no longer appear in AMP Redirector logs. (4459936, 4662145)
•	Portal no longer generates registration-only usernames that include special characters such as umlauts. In Portal 9.50, if a site’s registration-only username contained an umlaut, you could not manage users on the site’s Users tab, and the registration-only user could not be used to register agents to Portal. (5151021, 5145789)
4.3  Known Issues
•	In a Portal instance where the Login page is customized and multifactor 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 multifactor account verification is enabled in a Portal instance where single sign-on is configured, users who set up multifactor account verification cannot move past account verification screens when they try to sign in to Portal. 
WORKAROUND: Do not enable multifactor 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)
5 PRODUCT SUPPORT
5.1  Technical Support
Contact information for your provider is available through the Need Help button in Portal.
5.2  Product Updates
Product updates are available through your provider.
5.3  Documentation
The following documentation is available for this product: 
•	Server Backup online help and knowledge base
•	Release notes (this document)
•	User Guide
•	Admin Guide
•	Installation and Configuration Guide