Known issues
Note the following issues:
The installation and upgrade screens might not display correctly on systems with lower display resolutions.
Workaround: Use a screen resolution of 1920 × 1020 or higher for the best experience.
Upgrading to version 11.1 from a fresh installation that uses an existing database is not supported. During uninstallation, version 11.1 removes files that are required for the upgrade process.
Workaround: None.
Note:
Starting with version 11.2, the uninstallation process preserves the required files. As a result, upgrading from a fresh 11.2 installation using an existing database is supported in subsequent releases.
Capacity usage calculations can vary between the Admin and Tenant pages when the Use Data Transferred Values setting is configured differently at the global and tenant levels.
Details:
When the setting is enabled globally, consumed capacity is calculated using TransferredSizeBytes and displayed on both the Admin and Tenant pages.
When the setting is configured at the tenant level, consumed capacity is calculated using TransferredSizeBytes and displayed only on the Tenant page. Different tenants can display different usage values based on their individual settings.
In some environments, usage calculations might not update all usage data correctly.
Workaround: Restart the Windows service and then perform a system synchronization.
Status: The issue is under investigation. A fix might be provided in a future patch release.
When upgrading to NetBackup Self Service 11.2, the installer copies existing database connection strings from earlier NetBackup Self Service versions. If the source NetBackup Self Service version is earlier than 10.5.0.1, the existing connection strings in appsettings.json might not include the following required attributes:
;Encrypt=false;TrustServerCertificate=true
These attributes were introduced after NetBackup Self Service 10.3.0.1 because of changes to SQL Server database encryption requirements. During the upgrade, the installer copies the existing connection strings without modifying them. As a result, the required attributes might be missing after the upgrade.
Affected Configurations:
NetBackup Self Service versions earlier than 10.5.0.1.
Upgrades to NetBackup Self Service 11.2.
Existing connection strings that do not contain: ;Encrypt=false;TrustServerCertificate=true
Workaround:
To apply the workaround
- Open the following file:
{ProgramFolder}/Config/connectionstrings.json. - Verify that the MainDB and AdapterDb connection strings contain the following attributes: ;Encrypt=false;TrustServerCertificate=true.
- If the attributes are missing, append the following string to the end of both connection strings, before the closing quotation mark: ;Encrypt=false;TrustServerCertificate=true.
- Save the file.
- Restart the Self Service Windows service and IIS.
- Verify that:
The website is accessible.
The Self Service Windows service is running.
The service does not terminate unexpectedly.
Table: Installer limitations
Limitation | Status | Workaround |
|---|---|---|
DAPI password in | Uses ChangeMe after fresh installation | Configure DAPI after installation. |
ApplicationKey rotation | Not supported after initial configuration | Restore the ApplicationKey from backup. |
Copying | Not supported because the file is DPAPI-protected | Use the same ApplicationKey value on each node. |
Partial InitData retry | Not automated | Restore the database and retry from a clean state. |