Backup failed because The dump process failed with exitcode 127

[schel4ok]

I have "Backup failed because The dump process failed with exitcode 127 : Command not found." error in the log file

[2025-10-24 10:19:33] local.ERROR: Backpack\BackupManager -- backup process failed because : The dump process failed with a none successful exitcode.
Starting backup...
Dumping database mydb...
Backup failed because: The dump process failed with a none successful exitcode.
Exitcode

in .env I have DB_CONNECTION=mariadb
then in config/database.php

    'connections' => [
        'mariadb' => [
            'driver' => 'mariadb',
            'url' => env('DB_URL'),
            'host' => env('DB_HOST', '127.0.0.1'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'laravel'),
            'username' => env('DB_USERNAME', 'root'),
            'password' => env('DB_PASSWORD', ''),
            'unix_socket' => env('DB_SOCKET', ''),
            'charset' => env('DB_CHARSET', 'utf8mb4'),
            'collation' => env('DB_COLLATION', 'utf8mb4_unicode_ci'),
            'prefix' => '',
            'prefix_indexes' => true,
            'strict' => true,
            'engine' => null,
            'dump' => [
                'dump_binary_path' => '/storage/app/private/', // only the path, without `mysqldump` or `pg_dump`
                // 'dump_binary_path' => '/Applications/MAMP/Library/bin/', // works for MAMP on Mac OS
                // 'dump_binary_path' => '/opt/homebrew/bin/', // works for Laravel Valet on Mac OS
                'use_single_transaction',
                'timeout' => 60 * 5, // 5 minute timeout
                // 'exclude_tables' => ['table1', 'table2'],
                // 'add_extra_option' => '--optionname=optionvalue',
            ],
            'options' => extension_loaded('pdo_mysql') ? array_filter([
                PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
            ]) : [],

[welcome]

Hello there! Thanks for opening your first issue on this repo!
Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.
Backpack communication mediums:

• Bug Reports, Feature Requests - Github Issues (here);
• Quick help (How do I do X) - Gitter Chatroom;
• Long questions (I have done X and Y and it won't do Z wtf) - Stackoverflow, using the backpack-for-laravel tag;

Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.
Thank you!
-- Justin Case The Backpack Robot

[backpack-ai-bot]

The error message “The dump process failed with exitcode 127 : Command not found.” indicates that the backup process cannot find the required database dump command (such as mysqldump) in the specified path.

Based on the knowledge sources, this is a common configuration issue, not a bug in Backpack. The Backpack BackupManager package is just an interface for triggering the spatie/laravel-backup package, which relies on external tools like mysqldump to perform database backups. If mysqldump is not installed or not found in the path specified in your configuration, you will get this error.

How to fix:

1. Check the dump_binary_path:
   In your config/database.php, you have:

   'dump_binary_path' => '/storage/app/private/', // only the path, without `mysqldump` or `pg_dump`

   This path should point to the directory where the mysqldump binary is located, not a storage directory. For example, on many systems, it might be /usr/bin/ or /usr/local/bin/. On Windows with XAMPP, it might be something like C:\xampp\mysql\bin\.

2. Example for MAMP on Mac OS:

   'dump_binary_path' => '/Applications/MAMP/Library/bin/', // works for MAMP on Mac OS

   Make sure the path is correct for your environment. You can find the correct path by running which mysqldump in your terminal.

3. Restart your server after making changes to the configuration.

4. Try running the backup again.

This issue and its solution are described in the Backpack documentation and community discussions. If you’re on Windows, you may need to set an environment variable or specify the path directly in your config as shown above. The key is that the path must contain the mysqldump executable, not just any directory or storage path see this discussion for a similar issue and solution.

If you continue to have issues, double-check that mysqldump is installed and accessible from the command line, and that your web server user has permission to execute it.

Summary:
Update your dump_binary_path to the correct directory containing mysqldump, not a storage directory. This should resolve the exitcode 127 error.

If you need more help, refer to the spatie/laravel-backup documentation as well, since Backpack BackupManager is just a UI for that package.

ℹ️ Please note our AI Bot does not reply to follow-ups, this will be the only AI answer in this thread. If the AI helped you find the answer, please mark it as answered or write details below so it can learn. Then close the conversation. If not, please give more information for when a human reads this. ℹ️

Relevant sources:

Github Issue (closed): [Bug] backpack:install command crashes while installing backpack generators
Github Issue (closed): [Bug]
Having trouble using Backpack?|Having trouble using Backpack?
DevTools|Requirements
Installation|Frequently Asked Questions
Updating raw DB queries to include DB prefix.
Github Issue (closed): SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111 "Connection refused")
Official Add-ons|Official Add-ons Part 2
Installation error
Updated the database configuration for unit tests to work with a MySQ…
DevTools|Requirements
Github Issue (closed): [Bug] Search is not working correctly
Github Issue (closed): [Bug] Checking column exists in database doesn't work with MariaDB
Install Optional Packages|Install Optional Packages
Github Issue (closed): backup manager backup does not work

[schel4ok]

it works like that 'dump_binary_path' => 'd:/ospanel/modules/MariaDB-11.8/bin'