Problem

A Windows client backup does not cross a mount point volume.

Error

2:21:01.898 PM: [4724.5740] <4> dos_backup::tfs_startdir: INF - Stopping scan for Directory Junction: C:\mount\mount_name

Solution

Overview: A MS-Windows-NT backup policy is configured to use the Cross mount points feature and the backup selection contains a mount point volume, i.e. C:\mount\mount_name. 

 Result: The backup will complete successfully but reports the backup of 1 file, the folder itself. This is evidence that the backup did not follow the mount point. 

 Verification: Examine the bpbkar log for the Stopping scan message. Below is an example bpbkar.log snippet showing how the mismatched GUID is forcing the backup process (bpbkar) to stop scan on the mount point volume. Because of the GUID mismatch, NetBackup bpbkar treats the volume as invalid. 

 Example: bpbkar.log: \install_path\netbackup\logs\bpbkar\mmddyy.log 

 2:21:01.882 PM: [4724.5740] <4> dos_backup::tfs_startdir: INF - Volume GUID: \\?\Volume{aa1ec8f5-a7ce-11d9-866b-505054503030}\ 2:21:01.882 PM: [4724.5740] <4> dos_backup::tfs_startdir: INF - Volume Mount Point: C:\mount\mount_name\ 2:21:01.898 PM: [4724.5740] <4> dos_backup::tfs_startdir: INF - Stopping scan for Directory Junction: C:\mount\mount_name\ 2:21:01.898 PM: [4724.5740] <2> tar_base::backup_finish: TAR - backup:                              1 files 2:21:01.898 PM: [4724.5740] <2> tar_base::backup_finish: TAR - backup:          file data:         0 bytes 2:21:01.913 PM: [4724.5740] <2> tar_base::V_vTarMsgW: INF - Total Size:0 2:21:01.913 PM: [4724.5740] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 0: the requested operation was successfully completed 2:21:16.913 PM: [4724.5740] <4> OVStopCmd: INF - EXIT - status = 0 

 Troubleshooting: Use the Windows mountvol command to determine the Globally Unique Identifier or GUID. The mountvol command as shown below lists two GUID's for the same mount point volume. This indicates a potential problem in the operating system or logical disk manager or volume manager but not in NetBackup. The Windows mountvol command without any options lists a different volume GUID than mountvol with a /L option. 

 Example syntax: 

C:\>mountvol Creates, deletes, or lists a volume mount point. MOUNTVOL [drive:]path /L /L   Lists the mounted volume name for the specified directory. 

 Example of the mismatch: C:\>mountvol    \\?\Volume{c4e88244-153c-413c-a82f-1c29b2257b9a}\         C:\mount\mount_name\ C:\>mountvol C:\mount\mount_name\ /L    \\?\Volume{aa1ec8f5-a7ce-11d9-866b-505054503030}\ 

 Also note that the application event log may record an error if the mismatched volume is using Microsoft Shadow Copies. 20080724 17:03:11 VSS W12290 NA Volume Shadow Copy Service warning: GetVolumeInformationW(\\?\Volume{c4e88244-153c-413c-a82f-1c29b2257b9a}\,NULL,0,NULL,NULL,[0x00000000], , 260) == 0x00000005. hr = 0x00000000. 

 Work Around: In the MS-Windows-NT policy, specify a wild card for the mount point. Example file list: C:\mount\mount_name\* This will backup all the data in the mount point volume.