Open sync-c opened 2 years ago
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
What do you have for your DB_DUMP_PATH
in your .env
? Per the documentation:
Debug mode
Describe the bug
snipeIT 6.0.9 MariaDB 10.8
php artisan snipeit:restore C:\file.whatever does not work
PS C:\inetpub\wwwroot\snipe-it> php artisan snipeit:restore C:\inetpub\wwwroot\snipe-it\storage\app\backups\snipe-it-2022-08-18-10-32-36.zip
Are you sure you wish to restore from the given backup file? This can lead to MASSIVE DATA LOSS! (yes/no) [no]:
mysql tool at: 'C:/PROGRA~1/MARIAD~1.8/bin/mysql' does not exist, cannot restore. Please edit DB_DUMP_PATH in your .env to point to a directory that contains the mysqldump and mysql binary PS C:\inetpub\wwwroot\snipe-it>
Seems to be looking for a non existent folder called mysql in the bin folder of MariaDB
The backup command worked fine
Reproduction steps
This is my DB Dump path as reference DB_DUMP_PATH='C:/PROGRA~1/MARIAD~1.8/bin'
PS C:\inetpub\wwwroot\snipe-it> php artisan snipeit:restore C:\inetpub\wwwroot\snipe-it\storage\app\backups\snipe-it-2022-08-18-10-32-36.zip
Are you sure you wish to restore from the given backup file? This can lead to MASSIVE DATA LOSS! (yes/no) [no]:
mysql tool at: 'C:/PROGRA~1/MARIAD~1.8/bin/mysql' does not exist, cannot restore. Please edit DB_DUMP_PATH in your .env to point to a directory that contains the mysqldump and mysql binary PS C:\inetpub\wwwroot\snipe-it>
Expected behavior
Was hoping for it to restore my backup.
Was able to fix it by copying all the files in the mariaDB/bin folder in a new folder called mysql in the bin folder.
The restore command was then able to see the files it needs and restore the DB
Screenshots
No response
Snipe-IT Version
6.0.9
Operating System
Windows Server 2019
Web Server
IIS
PHP Version
8.1.9
Operating System
No response
Browser
No response
Version
No response
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
No response