SpiderOak does not follow symbolic links when doing a backup scan on Linux. The reason for this is that there are too many possible ways to create a recursive backup loop using symbolic links and it leads to a number of very weird potential problems. Those often include a great deal of confusion at restore time, confusion regarding usage reporting ("Why is SpiderOak using 2.8 GB to backup this small folder?") and so on.
Articles in this section
- ONE does not launch on Linux
- Failure to launch GUI due to incorrect/missing ZLIB dependencies
- Which Linux Distributions and Releases Are Supported?
- Does SpiderOak Follow Symbolic Links?
- Why Does Installation of an Apt Package Fail With "Public Key Is Not Available"?
- What Are the Apt Sources Lines for SpiderOak?
- What Is the RPM Signing Key for SpiderOak?