Solved

DDB Verification Operation failed

  • 22 March 2023
  • 5 replies
  • 626 views

Userlevel 2
Badge +6

Hi,

We have the following environment:

  • Commserve 11.28 on W2K22
  • 3 Physical Media Agents (MA) on W2K22
  • Each physical MA has its own DDB partition disk (D:\) and its own Disk library volume (G:\) → there is no sharing of the disks between the physical MA
  • The DDB has 3 partitions: one on each physical MA
  • One disk library with 3 mounth paths (one per MA) but each MA has its own disk library volume not shared

Backups are going well but we have issues with “DDB Verification” operation.

The error messages are the following:

Error Code: [62:2687] Description: Export / Mount failed for mount path [G:/dl_ssd_aalst/CV_MAGNETIC], 
please check if the mount path is accessible on Data Server [appwbck003]. 
Check the logs for detailed error. 
Source: appwbck002, Process: ScalableDDBVerf
 

Library [dl_ssd_aalst], MediaAgent [appwbck002], 
Drive Pool [], MountPath[\dl_ssd_aalst]: Mount failed for mount path, please check if the mount path is accessible on Data Server. 
Check the Media Agent logs for detailed error. 
Advice: If the issue persists, please upload log files from CommServe, MediaAgent and Client and cont”

 

Any advice?

Thanks

 

icon

Best answer by Jos Meijer 23 March 2023, 19:51

View original

5 replies

Badge

Hi,

have you tried running DDB verification without Using Scalable Resource Allocation option?

Regards

 

Userlevel 2
Badge +6

Hi,

Thanks what is the impact of doing that type of DDB verification and how to setup this?

Any links is welcome.

Thanks

Badge

Here the link.

 

Verification of Deduplicated Data (commvault.com)

Performing a Data Verification Operation on Deduplicated Data (commvault.com)

https://documentation.commvault.com/2022e/expert/12398_data_verification_online_help.html

  • Use Scalable Resource Allocation

    To enhance the scalability of the data verification operation and to optimize the processes of scaling the resources, select this option. For more information, see Scalable Resource Allocation.

    This option is enabled by default.

Userlevel 2
Badge +6

Thanks for your answer.

However, after analyzing documentation, log files it seems that the issue could come from the fact that the firewall ports are not opened between the DataServer-IP and the media agents.

See under:

Sharing a Mount Path Using DataServer-IP (commvault.com)

Entering Required Firewall Settings to Configure DataServer-IP (commvault.com)

Ports 2049 & 111 needs to be opened from Dataserver-IP and Media Agents.

What do you think?

Thanks.

Userlevel 7
Badge +16

Hi @brucquat 

The reason @Nicola Bonugli is referring to Scalable Resources is due to the fact that this option load balances activities over all the media agents thus expecting a shared mount path between them.

When disabling this option it would prevent this load balancing and could prevent the need for the shared mount path.

If you do however decide to share the mount path, use type regular for Windows Media agents and enter a UNC path. This is the optimal protocol for Windows Media agents. Data server IP is optimal for Linux media agents.

Reply