NetBackup Enterprise Server
Most Popular | Most Recent
Version : Environment :
During Shadow Copy Components backups, very large registry hives may be skipped without NetBackup reporting a partially successful backup (Status Code 1) after the backup completes.
Doc. ID: AL1281 | 2012-04-25
In NetBackup 7.5, tapes could be prematurely deassigned, which could lead to failed duplication of images on those tapes having an "Expire After Duplication" retention. In addition, any images placed under legal hold residing on these tapes may become unrecoverable.
Doc. ID: AL1308 | 2012-06-28
Restores or verification of a limited number of Exchange and Sharepoint images protected using NetBackup 7.1.0.x to PDDO/MSDP storage units fail with the error "invalid tar header encountered, attempting to continue"
Doc. ID: AL1409 | 2013-10-28
NetBackup image cleanup may delete valid duplicated images.
Doc. ID: AL1393 | 2012-11-30
In NetBackup 7.5, when a "Backup From Snapshot" operation is defined in a Storage Lifecycle Policy where multistreaming is also enabled, some duplications may fail with status code 156 reported.
Doc. ID: AL1304 | 2012-06-13
Restore from an incremental VMware backup fails if a VM has one or more independent disks.
Doc. ID: AL1298 | 2012-05-23
NetBackup's Sybase ASA fails to start, returning "Internal database error *** ERROR *** Assertion failed"
Doc. ID: AL1452 | 2013-05-16
There is a potential for data loss in certain NetBackup 7.5 Replication Director configurations when using NetApp SnapVault with the NetApp Plugin 1.0 for Symantec NetBackup.
Doc. ID: AL1418 | 2013-01-22
If the expiration time of a backup image copy stored on a tape is manually changed to an earlier expiration time, the expiration time of the tape may be incorrectly changed to the same earlier time.
Doc. ID: AL1453 | 2013-05-16
Under certain configurations when Windows Open File Backups are enabled, backups created under policies using NetBackup Accelerator may contain incomplete images.
Doc. ID: AL1303 | 2012-06-05
A tape holding copy 1 of a synthetic full backup may have its expiration time set incorrectly when under the control of a storage lifecycle policy.
Doc. ID: AL1361 | 2012-10-09
On an alternate client, off-host snapshots back up the local drive instead of the snapshot volume.
Doc. ID: AL1371 | 2012-10-30
A potential for data loss exists when using NetBackup 6.5.x PDDO with PureDisk 22.214.171.124 or PureDisk 126.96.36.199. This issue specficially affects Optimized Duplication.
Doc. ID: AL1086 | 2011-02-18
Under certain circumstances, NetBackup may skip a random stream during SharePoint backups, resulting in an inability to restore.
Doc. ID: AL1463 | 2013-07-12
A regression in VMware vStorage APIs for data protection can result in NetBackup erroneously reporting a successful VM backup or restore of an offline LUN when using SAN transport.
Doc. ID: AL1485 | 2013-08-30
NetBackup is reusing VM selection query results for longer than configured.
Doc. ID: AL1510 | 2013-12-03
Using nbdecommission to retire a media server with MSDP storage may result in data loss.
Doc. ID: AL1518 | 2013-12-20
OpsCenter may not collect all job data during its initial sync with a NetBackup master server, leading to inaccurate reporting.
Doc. ID: AL1509 | 2013-12-03
In NetBackup 188.8.131.52, some Exchange 2013 CU1 or CU2 backups may appear to succeed, but restore attempts fail.
Doc. ID: AL1502 | 2013-11-13
When adding new schedules to a NetBackup synthetic policy on Windows, the include file list may be incorrect for future backups.
Doc. ID: AL1556 | 2014-04-23