
- #Spideroak command line how to
- #Spideroak command line install
- #Spideroak command line pro
- #Spideroak command line download
You can substitute yum or apt-get depending on your distribution below.
#Spideroak command line install
Later after I’ve restored my files here I will log out to runlevel 3 and copy them into place, ensuring the currently running desktop configuration would not conflict in any way.Īfter a quick, fresh Fedora installation the first step for restoration of data is to install SpiderOAk.
Instead, I made a /home/restore directory and set permissions to 777 and used that as the initial restore location. The important thing to note is that I was already running as the same username / uid / gid as my previous desktop in X11 and a lot of my files were specific to my desktop environment (XFCE) as well as application, browser and environment settings so I did not want to copy them directly into place. SpiderOak has some documentation about restoration here which I loosely followed.
#Spideroak command line download
Download files from my previous backup of the device. Reinstall Fedora (version 26 as of writing this). Then I could install SpiderOak and perform a file-level restore of the items from my home directory. In my case the fastest recovery path was to replace the failed disk and re-install the OS (Fedora 24 at time of failure, moving to Fedora 26 for re-installation). My SpiderOak backups were about a week old, I wasn’t backing up my /home ( where anything important is kept) on an interval but instead whenever I felt like it or before traveling – I made a mental note to stop doing it this way. Usually, with little exception if this fails you’re better off restoring from backups. Later versions of XFS (xfs_repair) will attempt to mount multiple superblocks (secondary, tertiary) that it knows about if the primary fails. #Spideroak command line pro
There is nothing pro about my Samsung 850 SSD Pro, it died in less than 6months and I’ll try to get a replacement. I had physical damage to the disk and eventually it stopped being identified by the OS. After accessing my Luks-encrypted LVM volumes I was unable in any way to mount the filesystems or repair them, I even tried using alternate superblocks and read through quite a bit of debug documentation to no avail. I then booted to a Fedora LiveCD to investigate further and hopefully run an xfs_repair. I was unable to read, copy or view data in any way. Looking at logs there were all manner of I/O and disk hardware errors. I first noticed there was an issue with my Fedora desktop when opening the Remmina application, it contained none of my settings, the theme was distorted and something was off.
#Spideroak command line how to
How to setup backups on a schedule via the SpiderOak CLI. How to setup backups on a schedule with the SpiderOak Linux desktop version. How to restore data from SpiderOak backups from a failed device. Experiences in a data loss / restoration scenarios using SpiderOak. I’m going to cover the following items here in hopes it is useful to others. It works natively on Linux, Windows and OSX and mobile clients. It also deduplicates all common data across all your devices which can be useful. SpiderOak is a blind (zero knowledge) encrypted cloud backup and file sharing service – only you have access to the encryption keys and it’s encrypted at rest and in transit so SpiderOak itself cannot access your data. Being the first time I’ve needed to restore data with SpiderOak here’s some things I’ve learned and impressions of the service on Linux. Luckily I had SpiderOak backups as my employer offers this as a service to associates. Recently the SSD Operating System disk on my primary work desktop failed without warning and no manner of arcane xfsrepair or xfsdump/xfsrestore chicanery would bring it back.