Upload Vesta user backups to Dropbox automatically daily

[vesta_mtl]

It is possible that there is no backup with the current date. The script needs to run on the same day that the backup is created, because it looks for a backup with the current date in its name.

[ruinzaO]

It is possible that there is no backup with the current date. The script needs to run on the same day that the backup is created, because it looks for a backup with the current date in its name.

I did the whole process again.
Even with a new backup, after doing the test the error appears.

I can send the file to the dropbox, but when I run the command the error appears.

I find it strange every time I type the command sh /usr/local/bin/send_site_backup_files_to_dropbox.sh it requests the token and after typing the token gives error.

Prints
https://imgur.com/a/xyrgC
https://imgur.com/a/UyWll
https://imgur.com/a/8M95S

[vesta_mtl]

Friend, thanks for the great work!
I noticed that my backups were added "admin.2018-01-15_05-10-12.tar" the time, so the file is not being renamed to admin.tar in the dropbox, could you add a fix in the script?

Many thanks and I'm sorry, I'm using google.

Yes, the script needed to be updated because Vesta now includes the time in the backup filename. I have updated my original post and the script should now work with the old Vesta (only yyyy-mm-dd in filename) and the new Vesta (yyyy-mm-dd_hh-mm-ss in the filename).

Let me know if you have any trouble. Your Google translation is excellent! :-)

Thanks for the answer!
Friend in setup this error appears.
/dropbox/dropbox_uploader.sh: line 1559: : No such file or directory

Am I doing something wrong?

There is an issue with the latest release of the Dropbox script. I have updated my instructions (the "curl" command above) to retrieve the older version of the script from github and it should work again.

You can remove the dropbox folder by doing this:

Code: Select all

rm -rf /dropbox

And then re-do the steps above using the new github url.

[vesta_mtl]

The "dropbox_uploader.sh" bug has been fixed on github, so I have re-updated my instructions to load the latest version from there.

Again, remove your original by doing:
rm -rf /dropbox

Then repeat the instructions for configuring "dropbox_uploader.sh".

[ruinzaO]

The "dropbox_uploader.sh" bug has been fixed on github, so I have re-updated my instructions to load the latest version from there.

Again, remove your original by doing:
rm -rf /dropbox

Then repeat the instructions for configuring "dropbox_uploader.sh".

100%
Thank you my friend!

[YellowJuice]

Thanks, that's a great solution for simple backups.

[n0x]

Really nice script and solution for remote backup storage.

Running nicely on the VM now :)

[fifthfloor]

I get the following errors with the attached set-up. Running the attached via the command line works, but when its done as a cron it gets one of these errors. Im no expert so any help would be appreciated. I'm sure its something stupid I'm doing. See the following:

https://imgur.com/qzyJriN

(Cron Daemon) <admin@serverhost>
3:15 PM (1 hour ago)
to me

/bin/sh: -c: line 0: unexpected EOF while looking for matching `"'
/bin/sh: -c: line 1: syntax error: unexpected end of file

This happens if I leave the quotes in "[%Y-%m-%d %H:%M:%S]" as seen in the attached. If I remove the quotes I get:

(Cron Daemon) <admin@serverhost>
5:02 PM (14 minutes ago)
to me

sudo: no tty present and no askpass program specified
sudo: no tty present and no askpass program specified

[vesta_mtl]

It seems that the code you copied may have replaced a quote mark with a tick mark (has an angle to it). Double check that.

[fifthfloor]

Yeah, that was the first thing I tried. I typed out the whole thing to make sure.

Also note: Running the command from a ssh session works with the same copied line. It just errors as a cron job.