![]() Follow the release notes feed and manually upgrade as stable versions are released. On unsupported platforms, keeping up to date becomes your responsibility. For Debian (and perhaps other Linux distributions) SpiderOak maintains their own repository which is set up in your package manager when the client is installed. On supported platforms, SpiderOak should keep itself up to date using your operating system’s usual methods. When SpiderOak appears to delete files during a sync, they are in fact moved to the sync subdirectory of the appdata directory. This fails for me if the network is being heavily used temporarily throttling all other network traffic usually solves the issue. It is preferable to sign in to the SpiderOak user forums via the desktop client (right-click on taskbar icon, then Help – User Forums). System administrators who fear that end users will be tempted to monkey with the settings and break things if SpiderOak calls too much attention to itself can conceal it. Recall that %sysdrive%\Users\USER\AppData\ is a hidden directory. I shall refer to this as the appdata directory. SpiderOak’s per-user files are at %sysdrive%\Users\USER\AppData\Roaming\SpiderOak\ on Windows Vista and later. I then assigned menu.lst to the backup group and changed its permissions to 640. ![]() I created the group “backup” and added myself as a member of the group. For example, I wanted to back up /boot/grub/menu.lst, which is owned by root and has default permissions of 600. To work around this, set that file’s read permission to include the user running SpiderOak. This implies that if that user doesn’t have read permission for a given file, SpiderOak can’t back it up. On Linux, SpiderOak runs with the permissions of the user that spawned it (see ps u | grep Spider). When run this way, SpiderOak never slows down my box. Find where SpiderOak is being called at login and change the command from SpiderOak to nice SpiderOak. Linux users can run SpiderOak on startup at low priority. For clarity’s sake I shall refer to this as the appdata directory. SpiderOak’s per-user files are at ~/.SpiderOak/. Once logged in, you can browse and download your data. Use the desktop client when possible, as the web interface is less secure. Log in to the web interface (JavaScript must be enabled for ). ![]() For example, the reported size of directory /foo/ does not include the size of subdirectory /foo/bar/. Be aware that in the stats output, directories are reported non-recursively. The SpiderOak client can generate useful statistics for this purpose. The flip side to this is that your used space will increase over time as historical versions accumulate, and you will want to keep an eye on this. One of SpiderOak’s strengths is that it retains historical versions of files. Synchronization is very simple to set up, but there are a few cases that merit special consideration: excluding files or subdirectories from synchronization, cross-platform synchronization, and synchronizing an individual file. Finally, in the SpiderOak client on either Source or Target, go to Sync, press New, and follow the instructions. On Target, create an empty directory to contain the synchronized data on the target computer, and in the SpiderOak client mark that directory for backup. On Source, open the SpiderOak client and back up the directory to be synchronized. For illustration purposes I’ll consider the simple case of synchronizing a directory between two computers, which I will uncreatively call Source and Target. You can synchronize directories between devices, or even between locations on the same device (for example, an external memory device and your hard disk). I enable the “show hidden files” toggle first. Go to Back Up and select the directories and files you want to back up.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |