Event ID 50000 "Sparse vmdk file not found in NameDataMap" is reported on verify or restore
Article ID: 100053826
Updated On:
Description
Error Message
Application event log:
Log Name: Application
Source: PDVFS
Event ID: 50000
Level: Error
Keywords: Classic
Description:
An error occurred in the PDVFS driver: VMDKFilter::PdCreateFile Sparse vmdk file name "\2\BEData\STHVMDK\IMG000123\vm.vmdk" not found in NameDataMap. Res = 2
Ppdvfs log:
(2760:beremote.exe, 6324) - VMDKFilter::PdCreateFile Sparse vmdk file name "\2\BEData\STHVMDK\IMG000123\vm.vmdk" not found in NameDataMap. Res = 2
(12444:PDVFSService.exe, 7820) - The previous 1 messages have repeated 156 times
By default, pdvfs log is located in the following path:
C:\Program Files\Veritas\Backup Exec\Logs\PDVFS\(PDVFS)YYYY-MM-DD-HHmm.LOG
Cause
In the case of VMDKs are more than 2 TB, Backup Exec creates split sparse disks in multiples of 2 TBs. During the used sector backup or changed block backup, it appears the PDVFS interface is unable to find/open the concerned extent map file. This could be a small technical glitch in the PDVFS code flow as Veritas Technologies does not see any side-effect on the Bbackup and Recovery part.
Resolution
The message is harmless and can be safely ignored.
Issue/Introduction
- Using VMware agent
- Backing up a vmdk file which the provisioning size is larger than 2 TB.
- Backing up to the local deduplication device.
- One of the following properties of the backup jobs is used and the backup set is saved to the IMG folder:
- Forever Incremental (FI) jobs.
- Granular Recovery Technology (GRT) is enabled.
- Instant Recovery (IR) is enabled.
- One of the following types of jobs or stages is running:
- Verify stage in the backup job.
- Separated verify job.
- Restore job.
