Most Popular | Most Recent
Version : Environment :
Data loss can occur on PDDO storage servers for images replicated from an MSDP storage server.
Doc. ID: AL1205 | 2011-11-03
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
After certain upgrades, upon restart of the Content Router, small (0-13 byte) segments are not loaded into the cache which may cause queue processing failures and data loss.
Doc. ID: AL1125 | 2011-06-24
In PureDisk 6.6.x, running the Storage Pool Configuration Wizard under certain conditions may overwrite and reinstall the PureDisk environment.
Doc. ID: AL1067 | 2011-01-11
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
The AIX PureDisk 6.6.1.x agent may report successful backups, but files larger than 2 gigabytes will have been excluded from the backup.
Doc. ID: AL1124 | 2011-05-27
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
Symantec® Proactive Support via Call Home IP Address Change Notification
Doc. ID: AL1306 | 2012-06-26
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
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 | 2012-12-18
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
Upgrading the 5000/5020 Appliance to 220.127.116.11 may fail during installation. This issue is resolved in the 18.104.22.168B release.
Doc. ID: AL1141 | 2011-07-06
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
A firmware update is available for NetBackup 5000, 5020, and 5200 Appliances which resolves an issue where the failure of a single disk could cause a cascading failure on multiple (good) drives.
Doc. ID: AL1313 | 2012-07-12
Upgrades of NetBackup 52x0 Appliances configured as master servers from version 2.0.x to version 2.5.x may experience catalog issues. These patches will be replaced.
Doc. ID: AL1367 | 2012-10-31
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
Two issues cause missing fingerprints when using PureDisk Remote Office Agent for backups. This includes NetBackup 50x0 Appliances.
Doc. ID: AL1498 | 2013-11-04