- #Spideroak linux archive
- #Spideroak linux full
- #Spideroak linux software
- #Spideroak linux download
- #Spideroak linux free
I have tried to close the application, but no avail. Then the old devices was removed, but the CPU utilization was still up. This took ages and also tons of CPU power, without any real usage of the network.
#Spideroak linux download
I first tasked it to delete my old files such that I would not have to download the meta data for them again.
#Spideroak linux software
This is great, as the software should then have nothing to do. I have no idea what the point of this was, but it still took lots of time and CPU power.Īfter it has set itself up again, there were no files selected to be backed up. When I logged into the application again and registered my laptop under a new name, it would still download all the meta data from the old device. I have still done it, I was short of canceling the service anyway. Just deleting everything, reinstalling does not seem like an intelligent measure, rather brute force. They could store this on the device locally, this would not be a privacy issue. There should be options to look at log files, view telemetry or something like that.
This feels like a last-resort thing, and the support does not really seem to dig into the problem.
#Spideroak linux free
They have replied saying that they don't see any other option than to delete all data and to register my laptop as a new device, deleting all old data on the server to free the quota. On I have again contacted the support team and pointed them to a draft version of this blog post. I want a timely backup of my data, and I don't want to have a whole CPU core blocked from the software. As you can see below in the readout from my modem, the upload is nowhere nearly saturated, and most of it comes from a video conference I was attending via my mobile phone.Īt this rate the backup service is useless to me. This cannot be blamed on my overall connection either. One can see that some files did get uploaded, but changes to files are piling up faster than the software makes to trickle to the servers. I have watched this for a few hours, and you can see the time of day, remaining files to upload and remaining size to upload in the following table. I have to send the kill signal to get rid of it. Trying to quit the program will leave a CPU bound background process which does not react to the term signal. This pattern repeats itself again and again. There is a short break in the CPU load, then it uploads something for a few seconds and then stalls again, using the CPU. On the right you can see the four virtual CPU cores, on the bottom there is the network usage.
#Spideroak linux archive
The program packs a few of them into an archive and sends that in one go. On the left you can see the queue of files that are to be uploaded. After a restart I had the same syndication process, so apparently I had already done that using the built-in functionality.Īfter that went through, upload progress was super slow again. Then I tried the advice from the support and deleted the ~/.config/SpiderOakONE directory. The progess was still super poor, and would only hog the CPU but not do any actual uploading. It eventually got that it had to upload a bunch of files that where changed since the last backup. This process took some time, and that is fine. After a restart of the software I saw the syndication screen. So I chose the option to delete the upload queue in the program. On Monday I experienced troubles again, it would just not upload. I asked the support on Twitter and they said that they had some issues with the servers, but it should be good again. Then last week I had the issue again, it would just not upload anything. At the time it seemed to work fine again after a few simple restarts, so I did not follow through on this at that time. Then it would do the syndication again and it should work fine. I got a reply telling me to move the ~/.config/SpiderOakONE directory somewhere else and sign back into the program. So I wrote to the support on about this issue. I have the feeling that the GUI cannot really cope with ten thousand of files being listed, so it just freezes up as it tries to display it all. Often this is triggered by using the GUI. I would restart the application and then it would stop this.
#Spideroak linux full
Often it would not utilize my upload bandwith (10 Mbit/s) fully but rather utilize one full CPU core, which seems excessive. I recall that I tried the service a few years ago and had just exactly the same issues with it. My laptop could burst in flames and I would only lose a few minutes of work.īut the performance of the system is bad, again and again. Using inotify it will automatically put files into the queue just as I save them. Also it creates backups continiously, so I don't have to wait for the full hour to have a backup. It costs more than the usage of Duplicity with Backblaze B2, but it promises to work better.
As I wrote earlier, I have been using the SpiderOak One Backup service for a while now.
0 kommentar(er)
