Previous EEBs now resolved in NetBackup 11.2.0.1
The following table contains a listing of known issues with NetBackup that were identified, fixed, and made available to customers in the form of an emergency engineering binary (EEB). NetBackup 11.2.0.1 resolves the issues that were fixed with each of these EEBs.
More information on the Etracks that are listed in this topic (and any other service request Etrack) can be found on the Cohesity Services and Operations Readiness Tools (SORT) website.
Table: Previous EEBs now resolved in NetBackup 11.2.0.1
Etrack number | EEB description |
|---|---|
4229261 | Expired images were not removed from the deduplication pool or catalog, which prevented space reclamation and reduced storage efficiency. |
4230389 | After a bare metal restore, localized known folders were recovered with English names instead of the local language. |
4233468 | When the most recent backup image for a client did not contain any of the selected files, the warming operation was skipped during restore. |
4234557 | A full NDMP backup of a single volume failed. |
4233984 | Optimized duplication did not work for checkpoint restart backup images, and duplication failed with a media open error. |
4232237 | Duplication to storage failed with a media open error and an image open failure. |
4232120 | Cloud object store backups experienced a performance problem during suspend and resume operations. |
4233057 | Upgraded Spring to 6.2.19 and log4j to 2.25.4. |
4232807 | Upgraded Apache Tomcat to 10.1.57 |
4230373 | After an upgrade, restores failed on one snapshot manager because of the number of free-form tags on the instance. |
4222287 | A cross-account restore from a snapshot failed a prerecovery check because the disk encryption key did not exist or was disabled for the source disk. |
4224069 | Backup from snapshot and snapshot manager jobs queued because a resource limit was reached. |
4226797 | In NetBackup Snapshot Manager, when a virtual machine was restored, the volume type was not restored correctly. |
4230086 | Upgraded VRTSPostgres to version 14.23.1.0 to address PostgreSQL vulnerabilities. |
4233527 | A security vulnerability was resolved in NetBackup. |
4233259 | Upgrade OpenSSL 3 to 3.0.21 and OpenSSL legacy to 1.0.2zq for clients. |
4234178 | A security vulnerability was present in a core platform component. |
4233619 | Resolved an Azure credentials mapping problem affecting restore operations in NetBackup. |
4230045 | A Janus primary server package was required to apply a patch. |
4225527 | Upgrade OpenSSL to 1.0.2zp for NetBackup 10.3.0.1. |
4230893 | Security updates were required for the NetBackup 11.2 server. |
4233880 | A security vulnerability affected the PostgreSQL and MySQL database agents. |
4230453 | Updated VDDK to 9.1.0.0 |
4234243 | A security vulnerability affected catalog binaries. |
4230513 | Upgrade PostgreSQL to 16.14.1.0 to address PostgreSQL vulnerabilities. |
4229219 | Malware scanning failed when back-level media was used. |
4228903 | NAS backup policy failed with status 84 because checksum verification failed for an accelerator job. |
4229222 | A special build for S3 import functionality was required to validate ongoing feature development for import operations. |
4225218 | A malware scan hung in the activity monitor when all scan hosts were deactivated and an automatic scan job started. |
4230097 | vCenter discovery failed after an upgrade to NetBackup 10.5.0.1. |
4229749 | Replication jobs that used the storage plug-in hung when multiple threads wrote job detail messages at the same time. |
4218396 | In the web UI, VMware discovery reported a failed status for a vCenter server. |
4221772 | During restore of an Azure virtual machine, the web UI did not list all available subscriptions. |
4229457 | Because of database slowness, some catalog backup streams failed. |
4227160 | In the web UI, the primary server failed to load jobs in the activity monitor because the jobs cache database did not initialize. |
4231043 | A test build was required to validate packaging changes. |
4229395 | A NetBackup media server process (bpdm) crashed with a segmentation fault (SIGSEGV) during an optimized duplication or AIR operation using the SpanFS (DirectIO) OST plug-in. |
4234063 | During restore in the web UI, some UNC backup images were not found and recovery could not be performed. |
4228382 | After the Japanese language pack was applied, the Backup, Archive, and Restore interface hung on startup at the splash screen. |
4231385 | SharePoint granular restore failed with a policy restore error after SharePoint updates were installed. |
4226081 | On passive cluster nodes, the resource state was reported incorrectly, which caused a false indication that the application was active on multiple nodes. |
4229256 | There was no option to force proxy socket pairs to use ports within the configured client port window range. |
4228915 | During differential incremental backup of MongoDB, some files were missed and lost on restore even though the operation reported success. |
4228454 | Non-granular Microsoft Exchange full backups failed with a status 130, while cumulative incremental backups succeeded. |
4226862 | Temporary batch files were not deleted when parallel SQL backup operations were enabled. |
4233967 | After an upgrade, manually started SQL intelligent policy backups failed with a status 200 error and could not connect to the agent service. |
4229303 | Unable to extract a PostgreSQL backup after restoring it. |
4231756 | Full and differential backups of SQL Server 2025 secondary replicas ran as copy-only backups even when the copy-only option was disabled. |
4219906 | Because of a large number of snapshots, discovery took too long and blocked the restore operation during validation. |
4231602 | A multi-tenant access zone configuration prevented the backup host from connecting to snapshot exports, which caused backup from snapshot to fail. |
4212674 | After an upgrade, the snapshot manager frequently became unresponsive because the listener component became unhealthy. |
4226217 | Backup from snapshot failed with a status 6 error because no resources were available to launch the data mover before it timed out. |
4229701 | Backups of large AWS RDS Oracle databases failed because the session and renewal timeout values were fixed and could not be adjusted. |
4232506 | The snapshot manager listener became unhealthy when transient message failures could not be retried. |
4229809 | Policy creation with a WORM storage unit failed because the application log backup schedule used a default retention that could not be changed. |
4226075 | In the Java console, virtual machine restore reported that only administrators were allowed to use the option when single sign-on was used. |
4231138 | Snapshot backup of multiple KVMs failed because they tried to write to the same overlay file. |
4230835 | Backup and restore functionality for the virtualization platform, including automated recovery and storage support, was not available. |
4232812 | In Flex, backup jobs intermittently hung and showed no progress, and manual jobs could not be started during the problem. |
4232490 | The nbpas process crashed during NetBackup startup on the Janus V2 platform. |
4225533 | The device and library management processes hung when the robotic library was restarted. |
4232242 | After upgrade to NetBackup 10.4, some VMware policies that used the query operator could not be run, saved, edited, or copied. |
4233298 | The command to cancel a backup image failed with a status 220 error in D-NAS backups. |
4232622 | The NBSL service crashed after a Hyper-V policy was edited in the NetBackup web UI. |
4233465 | NetBackup 11.1.0.2 clients could not run on SLES 16 because of an unsupported system call. |
4228467 | The image expiration job hung, which caused snapshots to accumulate. |
4230987 | Idle workflow containers were not removed. |
4230327 | The parent backup job attempted to export indefinitely and did not complete. |
4233706 | Accelerator-enabled backups failed with a status 14 error because of a checksum mismatch. |
4229097 | As Azure changed to partitioned CRLs, NetBackup's certificate validation broke due to cache collisions. |
4229315 | Backup from snapshot jobs became stuck and did not write any data. |
4224304 | Cloud discovery only partially succeeded because a stale disk appeared on the volume. |
4225543 | The cloud extension did not trigger the expected number of backup from snapshot jobs. |
4231589 | The backup policies probe failed on primary servers because the policy list command returned an unsupported command error. |
4225401 | The image list command reported a negative fragment size for a cloud disk snapshot. |
4233826 | After an upgrade to NetBackup 11.1, the outbound network service leaked memory on AIX clients. |