Backup script example

[cod3rshotout]

Hi, I would like to use the server-automation to automatize the database backup of all my containers (wordpress and other apps).

I have cloned the repository and then within the cloned directory I changed the .env file setting the home path.
When I execute this command: ./backup.sh I get:

 Start execution '/home/john/docker/server-automation/backup/backup.sh ':
 ✔ success Function 'check_docker'
 ✔ success Function 'check_running_script'
 ✔ success Function 'starts_initial_check'
 ✔ success Function 'check_server_automation_env_file_exists'
 ✘ ERROR   Folder '/home/john/server-automation/sites' does not exist

I also noticed that the youtube video is outdate and the wiki link point to a 404.
Could you please help me to configure this?

[evertramos]

Hello @cod3rshotout,

Add --source= and --destination= to your script execution and you should be fine.

Let me know if you got it working.

[cod3rshotout]

@evertramos Thanks for the tip, after two question I get:

? question Do you want to send to backup storage?
(default: NO) [y/N]y

✔ success Function 'confirm_user_action'
? question Do you want to DELETE the local file after sending this file to backup storage?
(default: NO) [y/N]y

✔ success Function 'confirm_user_action'
✔ success Function 'backup_compress_folder'
✔ success Function 'backup_check_tar_file_integrity'
𝝯 INFO Uploading backup file to Storage ()
✘ ERROR You must inform the required argument(s) to the function: 'ftp_send_file_ftp'

what I need to do?

Thanks

[evertramos]

nice!

You need to configure the sftp server here:

server-automation/.env.example

Line 80 in 22fcb94

BACKUP_SERVER=

I would suggest try backup locally and then send it to ftp server.

[cod3rshotout]

nice!

You need to configure the sftp server here:

server-automation/.env.example

Line 80 in 22fcb94

BACKUP_SERVER=

I would suggest try backup locally and then send it to ftp server.

How can I test the backup locally? Could you show an example please?

[evertramos]

Sure!

Using Easy-Server and NGINX-proxy-automation

In the helper ./backup.sh --help you will find how to use it. If you are running the nginx-proxy-automation and has your sites at ~/server/sites, you could run the following:

cd /server-automation/backup
./backup.sh --yes

Then your backup files would be in /server/backup

Server-Automation only

If you are running server-automation in your own setup you would run:

cd /server-automation/backup
mkdir -p ~/backup
./backup.sh -s /path_where_your_sites_are -d ~/backup --all-sites --yes

This will backup all folders, inside ´/path_where_your_sites_areat~/backup`, example:

/path_where_your_sites_are
  --/site1
  --/site2
  --/site3

~/backup
  --/site1-20220308_00000.tar.gz
  --/site2-20220308_00000.tar.gz
  --/site3-20220308_00000.tar.gz

hope it helps!

[evertramos]

@cod3rshotout did you manage to use it?

I wonder if we might set a fullpath for final backup, which would instead of getting all folders (we will keep this feature as well) we tar the informed folder, what do you think?