magepsycho / magento2-db-code-backup-bash-script

Bash Script: Backup Magento2 Code + Database

Hi, I am Raj KB 👋

A passionate full-stack developer & indie hacker

• 🔭 I’m currently working on SEO for my Plugins

• 🌱 I’m currently learning Rust

• 👨‍💻 All of my projects are available at https://www.magepsycho.com/

• 📝 I regularly write articles on https://blog.magepsycho.com

• 💬 Ask me about PHP, Magento, Linux, DBA, DevOps, SaaS

• 📫 Drop your queries at https://www.magepsycho.com/contact

• 📄 Know about my experiences https://www.magepsycho.com/about-us

Adobe Magento Extensions

Premium Extensions

• Magento 2 Region & City Dropdown Manager
• Magento 2 Store Restriction Pro
• Magento 2 Custom Redirect Pro
• Magento 2 Group Selector / Switcher
• Magento 2 Regular, Special & Tier Price Importer
• Magento 2 Sales Promotion Pro
• Magento 2 E-Path Credit Card Payment Gateway

FREE Extensions

• Magento 2 Custom Shipping
• Magento 2 Easy Template Path Hints
• Magento 2 Preview/Visit Catalog
• Magento 2 Product Attachment
• Magento 2 Discount Limiter
• Magento 2 Product Discount Label
• Magento 2 Store View Pricing
• Magento 2 Disable Registration

Connect with me:

Languages and Tools:

Support:

 

magento2-db-code-backup-bash-script's Issues

re: Restore

Any chance you can share a restore script based on this backup script?

Issue with redis

When redis is enabled for sessions a variable called 'host' exists within this part of the config.
When the script runs the following command
grep host "app/etc/env.php" | cut -d "'" -f 4

It returns 2 lines. In my case it returns the following
localhost (from the db config)
127.0.0.1 (from the session config)

This breaks the mysqldump command.
For now I have manually entered localhost into the script instead of letting it look it up in env.php, but the script needs a means of differentiating between multiple 'host' variables in env.php

Below is my session config for reference.
'session' => [
'save' => 'redis',
'redis' => [
'host' => '127.0.0.1',
'port' => '6379',
'password' => '',
'timeout' => '2.5',
'persistent_identifier' => '',
'database' => '2',
'compression_threshold' => '2048',
'compression_library' => 'gzip',
'log_level' => '1',
'max_concurrency' => '6',
'break_after_frontend' => '5',
'break_after_adminhtml' => '30',
'first_lifetime' => '600',
'bot_first_lifetime' => '60',
'bot_lifetime' => '7200',
'disable_locking' => '0',
'min_lifetime' => '60',
'max_lifetime' => '2592000'
]
],

tput: No value for $TERM and no -T specified

Hi
Firstly thanks for creating this tool, I find it really useful.

I am running the following command as a nightly cronjob on my Ubuntu 20.04 box and I get the following output

/usr/local/bin/mage2-backup --backup-code --skip-media --use-mysql-config --src-dir=/var/www/html --dest-dir=/S3/backups/LIVE/CODE/

tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified

Cheers
Rob

incorporate GDPR-dump as an alternate for anonymised backups

Hi, more of a feature request than a bug, but it would massively streamline operations if you could incorporate the drop-in replacement for mysqldump, GDPR-dump that can be called by an --anonymous flag in the command:

https://github.com/machbarmacher/gdpr-dump

example usage: ./mage2-backup.sh --backup-code --skip-media --anonymous --src-dir=/path/to/magento2/root --dest-dir=/path/to/destination

the drop in version of gdpr-dump needs parameters added to a [mysqldump] section in the user's my.cnf file but would certainly smooth things in terms of dev environments considerably.

(there is a non-drop in version by https://github.com/Smile-SA/gdpr-dump that has more configurable options through a .yaml but i imagine that would be more hassle to incorporate, it is however more actively developed)

app/etc/env.php missing

What is the reason for excluding app/etc/env.php when creating the codebase archive? We just tried to perform a restore and realised the file is missing which prevents the restored site from working.