mariabackup failed on Windows 10

mariabackup --backup --target-dir="C:/Program Files/MariaDB 10.6/data" --user=root --password=########

[00] 2021-08-18 15:39:15 Connecting to MariaDB server host: localhost, user: root, password: set, port: 3306, socket: not set

[00] 2021-08-18 15:39:15 Using server version 10.6.4-MariaDB

[00] 2021-08-18 15:39:15 Warning: option 'datadir' has different values:

  'C:/Program Files/MariaDB 10.6/data' in defaults file

  'C:\Program Files\MariaDB 10.6\data\' in SHOW VARIABLES

mariabackup based on MariaDB server 10.6.4-MariaDB Win64 (AMD64)

[00] 2021-08-18 15:39:15 cd to C:\Program Files\MariaDB 10.6\data\

[00] 2021-08-18 15:39:15 open files limit requested 0, set to 0

[00] 2021-08-18 15:39:15 mariabackup: using the following InnoDB configuration:

[00] 2021-08-18 15:39:15 innodb_data_home_dir =

[00] 2021-08-18 15:39:15 innodb_data_file_path = ibdata1:12M:autoextend

[00] 2021-08-18 15:39:15 innodb_log_group_home_dir = ./

2021-08-18 15:39:15 0 [Note] InnoDB: Number of pools: 1

2021-08-18 15:39:15 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.

2021-08-18 15:39:15 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/

2021-08-18 15:39:15 0 [ERROR] InnoDB: File ./ib_logfile0: 'open' returned OS error 71.

2021-08-18 15:39:15 0 [ERROR] [FATAL] InnoDB: open(./ib_logfile0) returned Generic error

210818 15:39:15 [ERROR] mysqld got exception 0x80000003 ;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed,

something is definitely wrong and this may fail.

Server version: 10.6.4-MariaDB

key_buffer_size=0

read_buffer_size=131072

max_used_connections=0

max_threads=1

thread_count=0

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5473 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

mariabackup.exe!???

ucrtbase.dll!raise()

ucrtbase.dll!abort()

mariabackup.exe!???

mariabackup.exe!???

mariabackup.exe!???

mariabackup.exe!???

mariabackup.exe!???

mariabackup.exe!???

KERNEL32.DLL!BaseThreadInitThunk()

ntdll.dll!RtlUserThreadStart()

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains

information that should help you find out what is causing the crash.

Writing a core file at C:\Program Files\MariaDB 10.6\data\

Minidump written to C:\Program Files\MariaDB 10.6\data\mariabackup.dmp