NetBackup Enterprise Server
Most Popular | Most Recent
Version : Environment :
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
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
In NetBackup 7.5, if 'bpexpdate -recalculate' is invoked from the command line without the '-d' or '-ret' option, incorrect expiration dates for images may be recalculated, which may lead to early expiration of those images.
Doc. ID: AL1299 | 2012-05-24
Restore from an incremental VMware backup fails if a VM has one or more independent disks.
Doc. ID: AL1298 | 2012-05-23
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
Data loss can occur on PDDO storage servers for images replicated from an MSDP storage server.
Doc. ID: AL1205 | 2011-11-03
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 | 2011-10-05
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 | 2011-08-11
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 | 2011-06-24
After duplicating full VMware images, block-level incremental backups based on full backups may expire earlier than expected when Copy 1 of the full backup expires.
Doc. ID: AL1136 | 2011-06-23
If an OpsCenter upgrade to 7.1 fails on UNIX or Linux when the database backup process times out, corrective action must be taken or the database will be corrupted.
Doc. ID: AL1120 | 2011-04-29
On Windows systems running NetBackup 7.x Media Server Deduplication, queue processing may fail if the sorted tmp file reaches 4 GB in size.
Doc. ID: AL1101 | 2011-03-18
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 | 2011-03-07
Under NetBackup 7.0.1, VMware Virtual Machines cannot be restored if any of the virtual disks (VMDKs) are larger than one Terabyte.
Doc. ID: AL1079 | 2011-02-23
A potential for data loss exists when using NetBackup 6.5.x PDDO with PureDisk 184.108.40.206 or PureDisk 220.127.116.11. This issue specficially affects Optimized Duplication.
Doc. ID: AL1086 | 2011-02-18
NetBackup Enterprise Server Software Alerts (July 31, 2010 and prior)
Doc. ID: AL1005 | 2011-01-07
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 | 2010-11-10
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 | 2010-11-01
Exclude and include lists are being recognized by user and catalog backups. This may lead to unintended exclusions during backup.
Doc. ID: AL1020 | 2010-09-21