Issue

When running a Discovery workflow with Remediation against SMB storage, some files may fail with the following error:

Possible issues

By default, MetaDefender Storage Security waits up to 1 hour for a remediation task to complete. If the remediation process takes longer than the configured timeout, the file is marked as failed.

This can happen when:

• The server does not meet the recommended system requirements.

• The SMB storage configuration is not optimized for MetaDefender Storage Security.

• The storage contains a large number of files or large file sizes.

• SMB remediation takes longer than NFS remediation due to protocol or environment differences.

Resolutions

1. Verify the Server Meets System Requirements

Confirm that the server hosting MetaDefender Storage Security meets the required system specifications.

Refer to the official system requirements:

General System Requirements - MetaDefender Storage Security

2. Use the Recommended SMB Storage Approach

For SMB-compatible storage, OPSWAT highly recommends using the recommended integration approach documented below:

Recommended approach when adding SMB units on Linux deployments - MetaDefender Storage Security

This approach can help improve reliability and reduce remediation-related timeout issues when working with SMB shares.

3. Increase the Remediation Timeout

If remediation tasks require more than the default timeout of 1 hour, increase the configured remediation timeout (to 3 hours for example).

On the MetaDefender Storage Security server, edit the customer.env file and add the following value:

If this value already exists, update it to:

For instructions on modifying customer.env, refer to:

Custom configuration - MetaDefender Storage Security