After updating to SD-30Oct18,I can’t import my backup (see error message).
I try to manually import but it does not work too (see terminal script).
My server informations seems to be correct (see capture screens).
My computer is an iMac under OS 10.11.6 and my web browser is Safari 11.1.2
Sorry, I forgot attached files in my previous message.
After updating to SD-30Oct18,I can’t import my backup (see error message).
I try to manually import but it does not work too (see terminal script).
My server informations seems to be correct (see capture screens).
My computer is an iMac under OS 10.11.6 and my web browser is Safari 11.1.2
Hello @Gerard1 it looks like the export did not work correctly as the import failed to decompress the compressed archive properly. Do you still have the original image? can you decompress the archive manually on your computer? or is it corrupted?
Hi @Gerard1, if you just use the button on the Admin screen, next to ‘Server Information’ to Copy to Clipboard you can then just do a paste (no formatting required) and the information is inserted like this:
Unfortunately I do not still have the orignal image but I can decompress the archive manually using « utilitaire d’archives » standard application on my iMac.
Good to see that the data is present. Have you tried uploading multiple times? Im not sure what’s going wrong unfortunately. Did you decompress and recompress on your computer?
I tested the decompression command here in isolation on a backup which you could test as a starting point:
cd /home/pi/data/uploads
mkdir test
tar xfzv emoncms-backup-2018-11-16.tar.gz -C test
I am a beginner and I am not very familiar with Linux commands.
It seems that I am not allowed to create a test directory. Should I use sudo mkdir instead of mkdir?
However you can see on the attached screenshot that there are five backup files.
Since I was unable to restore my backup after the SD image was migrated, I reconfigured my entries to resume the recordings. That’s why the 2018-11-16-2.tar and the 2018-11-17.tar files are therefore smaller in size.
Sorry about the linux commands , Yes you could try running both as sudo.
I wonder if emoncms-backup-2018-11-16.gz is tripping it up, it shouldn’t do as the script does search for tar.gz file extension and the correct filename is listed in your log, could you move the existing uploads out of that folder and try again?
I’m not sure what’s gone wrong, maybe the archive is corrupted in some way. Would you be happy to send us the archive for us to take a look? If so, the best way to do this is upload to dropbox / grdive then send us a link to [email protected].
I will update this thread with the results of my analysis.
OK, old data has been imported successfully. It just misses the last 24h.
After that, I erased all old files from the uploads directory, created a new backup, downloaded the associated .tar.gz file, and tried to re-import the backup.
Unfortunately, I encountered the same problem.
I noticed that after downloading, the tar.gz file was transformed into a .tar file.
Could this explain the problem?
I finally found a way to import a backup.
After performing a backup and downloading the archive to my computer, I use the application “keka” to compress the downloaded file. tar in .tar.gz file and then I import this .tar.gz file.
It’s a bit complicated, but it works.
Thanks for your help.
Great to hear you got it working @Gerard1. To check I understand correctly, the emonpi is offering the backup to download with the .tar extension only?
It seems that the backup generated by emonPi is indeed in .tar.gz but when I download this file on my computer, it appears in .tar only. So I have to use “Keka” to compress the downloaded file in .tar.gz
It may be my operating system (OS El Capitan version 10.11.6 with Safari version 11.1.2) that forces the download in .tar