Data Domain: Troubleshooting BoostFS Connectivity, Mount, and Performance Issues

Overview

This article helps users diagnose and resolve common BoostFS issues involving connectivity, mounting, lockbox configuration, performance, backup application integration, and operational failures.

Before troubleshooting, determine whether the issue involves a standalone BoostFS installation or a BoostFS implementation integrated with a backup application.

Identify the BoostFS Implementation

The following methods can help identify the BoostFS implementation in use:

Determine the backup application being used.
Identify the hostname of the client using BoostFS.
Review Data Domain connection information to identify DD Boost clients and associated hosts.

Identifying the implementation early helps ensure troubleshooting is focused on the correct component.

Common BoostFS Validation Checks
Verify Storage Unit Configuration

Ensure:

The correct DD Boost storage unit is being used.
The storage unit has appropriate Read/Write (RW) permissions.
The correct DD Boost user is assigned to the storage unit.

Verify Connectivity

Confirm:

The correct hostname and IP address are being used.
DDPCONNCHK completes successfully.
Required firewall ports are open between the client and Data Domain system.
DNS resolution is functioning correctly if hostnames are used.

Related articles:

Data Domain: DDPCONNCHK How to Troubleshoot DD Boost Connectivity and Performance
Data Domain: Port requirements for allowing access to a Data Domain through firewalls

Verify DD Boost User Access

Confirm that:

The DD Boost user account exists.
The account is not locked.
The user can successfully authenticate.
Mount and Lockbox Troubleshooting

If users experience mount failures, lockbox errors, or connection issues, verify the following:

The correct mount command and options are being used.
NFS is enabled on the Data Domain system.
DD Boost is enabled.
A DD Boost storage unit has been created.
A DD Boost user has been created and assigned appropriate permissions.
Required network ports are open.
DDPCONNCHK completes successfully.

Related article:

Data Domain: How to troubleshoot Boostfs Installation, configuration and mount issues

Linux

For persistent mounts on Linux systems, use the documented fstab configuration method.

Related article:

Data Domain - BoostFS for Linux using fstab to make mounts persistent.

For Windows environments:

Verify scheduled tasks used for persistent mounts are configured correctly.
Verify all required storage units are included in the scheduled task configuration.
Verify each mount action is configured correctly.
Windows Installation and Upgrade Prerequisites

Data Domain: BoostFS for Windows - Windows start-up script to make BoostFS mount persistent across reboots and user-logoff

When installing or upgrading BoostFS for Windows:

Use an account with administrator privileges.
Ensure sufficient disk space is available (approximately 7 MB minimum).
Deactivate all active BoostFS mount points before installation, upgrade, or removal.

Additional requirements:

The BoostFS configuration file entry must exactly match the Data Domain hostname.
Hostname capitalization must remain unchanged from the hostname displayed by the Data Domain system.
Shared lockboxes can be used to mount BoostFS on secondary hosts when appropriate.

Lockbox Migration Issues

If the BoostFS log contains:

bfs_is_lockbox_migration_needed

Perform the following checks:

Verify the BoostFS Version
Determine which BoostFS version is installed.
Upgrade older releases to a supported BoostFS version when appropriate.
Validate the Lockbox
Confirm the lockbox file exists.
Recreate the lockbox if it is missing or outdated.
Verify the lockbox matches the installed BoostFS version.
Validate Persistent Mount Configuration
Confirm all required storage units are included in the mount configuration.
Verify mount commands reference the correct storage units.
Test mounts manually to confirm functionality.
Verify Operation After Restart

After configuration changes:

Restart the host if appropriate.
Verify mount points initialize correctly after startup.
Confirm mounts remain stable and available.

Resolution of similar issues has included:

Upgrading BoostFS.
Recreating the lockbox.
Correcting persistent mount configurations.
Adding missing storage units to mount configurations.
Backup Application Validation

Gather the following information:

Backup application name.
Backup application version.
Client hostname.
Client IP address.
DD Boost storage unit.
DD Boost user.

Examples of applications that may use BoostFS include:

Oracle RMAN
NetWorker
PowerProtect
CommVault
MongoDB
MySQL
SQL Server

Verify compatibility between:

Data Domain OS (DDOS)
BoostFS version
Backup application version

Compatibility information can be reviewed through Dell's Enterprise Compatibility Matrix (eLab Navigator).

If using CommVault, review current Dell and CommVault best practices to ensure the recommended DD Boost integration method is being used.

Verify the BoostFS Version

Older BoostFS versions may contain known issues resolved in newer releases.

Verify that:

The latest supported BoostFS plugin is installed.
DDOS is compatible with the installed plugin version.
The backup application is supported with the selected DDOS and BoostFS versions.

Using the latest supported version is strongly recommended.

Security Software Considerations

Security software running against active BoostFS mount points can interfere with backups, restores, and general BoostFS operations.

Examples include:

Microsoft Defender
CrowdStrike
Tripwire
Antivirus software
Endpoint detection and response tools
Security scanning applications

Potential symptoms include:

Backup failures
Restore failures
Performance degradation
Mount instability
Application hangs
Unexpected process termination

Related article:

Data Domain: BoostFS Issues with Security Scanner Software or Apps

Exclude active BoostFS mount points from security scanning whenever permitted by organizational policies.

BoostFS Log Locations

Linux

BoostFS logs:

/opt/emc/boostfs/log

Command logs:

/opt/emc/boostfs/log/boostfs_command.log

Windows

BoostFS logs:

C:\BoostFS\Log

Command logs:

C:\BoostFS\Log\boostfs_commands.log

Additional directories may include:

C:\BoostFS
C:\Program Files\BoostFS

Collect Backup Application Logs

The backup application using BoostFS maintains its own logs.

Review application logs alongside BoostFS logs to identify:

Authentication failures
Storage unit errors
Connection failures
Performance issues
Application-specific errors

Required Information for Troubleshooting

Collect the following information before opening a support case:

Client Information
Client hostname
Client IP address
DD Boost storage unit
DD Boost user
Time Information
Date and time of the failure
Time zone where the issue occurred
Job Information

Identify the type of workload involved:

Full backup
Incremental backup
Synthetic full backup
Restore
Auxiliary copy
Client-side deduplication
Client-side compression
Client-side encryption

Document the options used when the issue occurred.

Network and Interface Validation

Review the Data Domain network configuration:

Backup interfaces in use
Restore interfaces in use
Interface groups (ifgroups)
LACP configuration
Link speeds (1 GbE, 10 GbE, etc.)
Frame errors
Interface health and utilization

Identify the specific interfaces and IP addresses used for backup and restore traffic.

Performance Troubleshooting

If BoostFS performance is slow, perform:

DDPCONNCHK testing
MTU testing
iPerf testing
Slow Backup Operations

Perform testing from the BoostFS client toward the Data Domain system.

Slow Restore Operations

Perform testing from the Data Domain system toward the BoostFS client.

If network testing reveals errors, work with the appropriate networking team to resolve the underlying network issue before continuing application-level troubleshooting.

Support Bundle Review

Obtain a Data Domain support bundle and review information around the period when the issue occurred.

Perform the following:

Review alerts and errors near the reported timestamps.
Search for the affected hostname and IP address.
Verify general system health.
Review DD Boost-related information.

Also review BoostFS logs for indications such as:

panic
fanout
failure
bfs_is_lockbox_migration_needed
app-info
authentication errors
connection errors

A commonly observed issue is reaching the maximum BoostFS connection limit.

Advanced Logging

If the issue cannot be isolated through standard logs:

Collect BoostFS logs.
Collect backup application logs.
Collect a Data Domain support bundle.
Enable DD Boost API Precert logging if additional diagnostics are required.

Related article:

Data Domain: Enabling DD Boost API Logging | Precert Logs

Additional Research

When appropriate, review documented errors from:

BoostFS logs
Backup application logs
Data Domain logs

Application-specific error messages may provide additional guidance from the respective software vendor.

Information Recommended for Support Review

BoostFS logs
DD Boost API Precert logs (if collected)
Data Domain support bundle
Client hostname
Client IP address
DD Boost storage unit
DD Boost user
Backup application logs
Issue timestamps
Description of the failure and its impact

Data Domain: BoostFS Panics or Mount Point becomes Unresponsive

How to troubleshoot BoostFS Mount Offline issues for both Windows and Linux platforms

Data Domain - boostfs plugin: too many connections (256 limit)

Data Domain: boostfs plugin memory leak