<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Symbolic Link on Artur Rios Lab</title><link>https://lab.artur-rios.tech/tags/symbolic-link/</link><description>Recent content in Symbolic Link on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 22:00:00 +0000</lastBuildDate><atom:link href="https://lab.artur-rios.tech/tags/symbolic-link/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Back Up Any Folder With OneDrive</title><link>https://lab.artur-rios.tech/tutorials/back-up-any-folder-with-onedrive/</link><pubDate>Wed, 21 Oct 2026 22:00:00 +0000</pubDate><guid>https://lab.artur-rios.tech/tutorials/back-up-any-folder-with-onedrive/</guid><description>&lt;p&gt;OneDrive backs up what is inside its own folder, usually&#10;&lt;code&gt;C:\Users\&amp;lt;you&amp;gt;\OneDrive&lt;/code&gt;, and nothing else. Its built-in folder backup&#10;extends that to a fixed set of folders: Desktop, Documents, Pictures, Music&#10;and Videos.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; A folder anywhere else, say &lt;code&gt;D:\Projects&lt;/code&gt;, is not&#10;backed up unless it is moved into OneDrive, and moving it breaks every&#10;program, shortcut and script that expects it at &lt;code&gt;D:\Projects&lt;/code&gt;.&lt;/p&gt;&#10;&lt;p&gt;The trick that gets passed around is to leave the folder where it is and put&#10;a symbolic link to it inside OneDrive. That does not work reliably, for&#10;reasons explained &lt;a href="#why-not-a-link-inside-onedrive"&gt;below&lt;/a&gt;. What works is&#10;the same idea pointed the other way: move the folder into OneDrive, where it&#10;syncs like any other folder, and leave a link at the old path, so everything&#10;that used &lt;code&gt;D:\Projects&lt;/code&gt; still finds it there.&lt;/p&gt;</description></item></channel></rss>