NetBackup Enterprise Server
Most Popular | Most Recent
Version : Environment :
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
Data loss can occur on PDDO storage servers for images replicated from an MSDP storage server.
Doc. ID: AL1205 | 2011-11-03
NetBackup Enterprise Server Software Alerts (July 31, 2010 and prior)
Doc. ID: AL1005 | 2011-01-07
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
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
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
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
Backups taken with the NetBackup Snapshot Client with Instant Recovery snapshots enabled are not restorable when a snapshot is taken of a mounted drive whose path includes a space character
Doc. ID: AL1078 | 2013-10-24
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
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
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
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
Duplicated images using OpenStorage technologies (OST) direct copy to tape may fail to restore the last file in the image when the SIZE_DATA_BUFFERS_DISK setting is greater than 64K.
Doc. ID: AL1291 | 2013-10-25
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
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
When duplicating images to a PDDO storage pool, if duplication fails initially but succeeds on a later attempt, it is possible that the duplicated images will be unrestorable.
Doc. ID: AL1392 | 2012-11-30
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
Differential incremental catalog backups may skip recently updated configuration information. This can result in restores which will not bring configuration state to the expected point in time.
Doc. ID: AL1310 | 2012-07-02
When using Inline Tape Copy to create multiple copies of 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: AL1412 | 2013-01-16
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