-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
are all 7 of those backups the last 7 days? (as it should overwrite them if you've used the default values in the script I did)
Do you have enough space in Google Drive?
If you run the script manually now (the tmbackup script, not the manual backup) does it work then?
Yes, the backups are all dated consecutively over the last 7 days.
I've already tried
./tmbackup.sh
and that creates a new backup for today with a current time stamp.
Plenty of Google space, I’m using 2.28GB out of 17GB.
Looks like no log files unless you specify to create one!
How to generate log file for rclone?
Maybe see if it works overnight following the bounce, doesn't make an awful lot of sense that it worked fine this whole time :/
Update on the auto backup.
No file was saved to Google overnight, so I ran the script manually which saved the file to the Pi, then a couple of minutes later to Google drive. So the script is working, but the cron job isn’t.
I’ve checked and the cron job was still there. I’ve edited it to a different time and resaved it, so will see what happens tonight.
No file was saved to Google overnight, so I ran the script manually which saved the file to the Pi, then a couple of minutes later to Google drive. So the script is working, but the cron job isn’t.
I’ve checked and the cron job was still there. I’ve edited it to a different time and resaved it, so will see what happens tonight.
goRt
Active Member
Grab the backup file from the Pi using sftp (you might be able to do it via the command line, but that's above my pay grade
) - alternatively, if you used the google drive backup script, run the tmbackup script again and grab the latest file from Google Drive, upload the backup to the new hosted solution (again, sftp) then follow the restore procedure that goRT linked to above, replacing the backup file name with your oneI edited the cron to this:
0 12 * * * /home/pi/tmbackup/tmbackup.sh
which has saved the file to the Pi at midday but it didn’t copy over to Google drive. Is that because there’s already one there that’s less than 24 hours old?
Fresh install complete, used the guide again, so thanks @DaveW. Have made a note of details now and triple checked!
I tried adding in TeslamateAgile and charged overnight but it didn't populate. Added in via Services and updated the geo and rate but no luck.
I know a few of you got it up and running, any ideas?
I tried adding in TeslamateAgile and charged overnight but it didn't populate. Added in via Services and updated the geo and rate but no luck.
I know a few of you got it up and running, any ideas?
MrBadger
Badger out
Just guessing, but from experience elsewhere, is it possible that the cron job is making some assumption about the working directory ? So it thinks something should exist in current working directory, but its running not where it thinks it should be.
It shouldn't care about that, if you run that script manually now it'll copy over.
Can I suggest you remove both versions of the cron (I'm going to guess you've now got a root access copy and a normal user one)
Clear out the first one:
crontab -e
Delete the contents you've added
Then clear out the root one:
sudo -i
crontab -e
Once both are empty, recreate whilst still under sudo -i
You edit the recreated one to run this afternoon and see if it works?
You're a man of suspense Roy
Similar threads
