NetBackup Enterprise Server
Most Popular | Most Recent
Version : Environment :
NetBackup restores of SharePoint objects may fail to restore lookup column values.
Doc. ID: AL1615 | 2014-11-13
After resizing the virtual disk, there is a potential for data loss when backing up VMware clients with NetBackup using Changed Block Tracking (CBT).
Doc. ID: AL1613 | 2014-11-07
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 | 2014-11-04
In rare cases, specifying more than nine paths of differing drive letters in a Windows policy can lead to skipped backups of the tenth and later paths.
Doc. ID: AL1049 | 2014-11-04
NetBackup Enterprise Server Software Alerts (July 31, 2010 and prior)
Doc. ID: AL1005 | 2014-11-04
Under certain conditions, NetBackup for VMware backups may appear to succeed, but backups are incomplete leading to unexpected results such as unrestorable files or a failure of the Virtual Machine to boot.
Doc. ID: AL1126 | 2014-11-04
If a retention level is set such that expiration dates of images is set after January 2038, after successful backups or duplications to tape using this custom retention period, the tape media (but not the image) is expired. Media may then be overwritten. This condition does not occur with "infinity" retention levels.
Doc. ID: AL1161 | 2014-11-04
In NetBackup 7.6, a catalog backup will skip the contents of the db\images directory when it is set as a volume mount point or directory junction.
Doc. ID: AL1544 | 2014-11-04
NetBackup restores of SQL Server databases fail when the database name contains special characters.
Doc. ID: AL1558 | 2014-11-04
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 | 2014-11-04
Duplicated copies managed by a Storage Lifecycle Policy created with expiration dates beyond the UNIX epoch (January 19, 2038 03:14:07 UTC) are prematurely expired. This condition does not occur when a retention level set to "infinity" is used.
Doc. ID: AL1407 | 2014-11-04
In NetBackup 7.0.1, when SIZE_DATA_BUFFERS_NDMP is set to a different value than SIZE_DATA_BUFFERS, backups may fail due to coredumps from bptm and ndmpagent, while backups which succeed may not be restorable under certain conditions.
Doc. ID: AL1039 | 2014-11-04
When /usr/openv is in the exclude list of a Linux backup hosts, VMware backups will appear to complete successfully but will not contain any data.
Doc. ID: AL1550 | 2014-11-04
OpsCenter may not collect all job data during its initial sync with a NetBackup master server, leading to inaccurate reporting.
Doc. ID: AL1509 | 2014-11-04
Using nbdecommission to retire a media server with MSDP storage may result in data loss.
Doc. ID: AL1518 | 2014-11-04
Backups of vCloud Director generated virtual machines may complete successfully but back up a different VMDK than expected when duplicate BIOS UUIDs have been generated.
Doc. ID: AL1178 | 2014-11-04
After Disaster Recovery, NetBackup jobID values are reset. This can cause irregularities in reporting in NOM, VBR and OpsCenter if "duplicate" job IDs are encountered.
Doc. ID: AL1098 | 2014-11-04
When the STANDBYPATH batch parameter is commented out in the MOVE script, the NetBackup for SQL agent doesn't fail the restore and reports a successful parent job even though the restore has failed.
Doc. ID: AL1603 | 2014-11-04
In NetBackup 126.96.36.199, some Exchange 2013 CU1 or CU2 backups may appear to succeed, but restore attempts fail.
Doc. ID: AL1502 | 2014-11-04
NetBackup is reusing VM selection query results for longer than configured.
Doc. ID: AL1510 | 2014-11-04