<?xml version="1.0" encoding="iso-8859-1"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
<channel>
<atom:link xmlns:atom="http://www.w3.org/2005/Atom" rel="hub" href="https://pubsubhubbub.appspot.com/" />
<atom:link xmlns:atom="http://www.w3.org/2005/Atom" type="application/rss+xml" rel="self" href="http://backupforum.progforums.com/BackupForum/rss.php?tid=228" /> 
<title>Backup forum : IDrive : Glitches or Snags : How to deal with data moving after Windows reinstall</title>
<link>https://backupforum.progforums.com/BackupForum</link>
<description> Backup forum</description>
<language>en</language>
<docs>http://backend.userland.com/rss</docs>
<item>
<title>How to deal with data moving after Windows reinstall in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=846#p846</link>
<guid isPermaLink="false">846@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: How to deal with data moving after Windows reinstall

Message: Thanks for the tip Mike. Very useful information.
</description>
<pubDate>Sat, 18 Mar 2023 20:45:45 +0000</pubDate>
</item>
<item>
<title>How to deal with data moving after Windows reinstall in IDrive : Glitches or Snags</title>
<link>https://backupforum.progforums.com/BackupForum/viewtopic.php?pid=845#p845</link>
<guid isPermaLink="false">845@https://backupforum.progforums.com/BackupForum</guid>
<description>Topic: How to deal with data moving after Windows reinstall

Message: Hi, I've been using IDrive for a few years now.Some info on how to deal with a problem I ran into.&#160; I had 700GB of data (photos mostly) stored in C:\Documents that was backed up to IDrive.&#160; I reinstalled windows on an new SSD which became my C: drive.&#160; My old drive then became D:.&#160; So now my real data was on D:\Documents but IDrive had it mapped as C:\Documents.&#160; IDrive technical support gave the sage advise to delete the data off of IDrive and re-add and backup the new location.&#160; This would mean I would have to transfer 700GB of data over the wire to IDrive again.&#160; With Comcast's 1.2TB monthly limit and the amount of video streaming we do, that was not a preferred option.&#160; &#160;This is not a solution for me but might work for some folks (untested): Create a shortcut on the C: drive pointing to the old drive.&#160; Unfortunately in Windows 10+ I couldn't seem to create a shortcut in the root of C: (i.e. C:\Documents).The solution that worked (in case it wasn't as obvious to you as it wasn't obvious to me): Create a symbolic link in C: pointing to the location on D:.&#160; Yes, Windows seams to have symbolic links now (something inspired from Linux). Open a windows power shell (might work with normal cmd.exe also?) with administrator privilege (click Windows icon, type &#34;Windows Power Shell&#34;, right-click on the power shell icon and select &#34;Run as Administrator&#34;).&#160; Then enter the command (replace link location: C:\Documents and target location D:\Documents with your locations):New-Item -ItemType SymbolicLink -Path &#34;C:\Documents&#34; -Target &#34;D:\Documents&#34;This works because while the data is actually stored on D:\Documents, the symbolic link makes it look like it is also stored on C:\Documents thereby allowing IDrive to traverse C:\Documents like it used to. Hope this helps others.-Mike
</description>
<pubDate>Sat, 18 Mar 2023 20:38:51 +0000</pubDate>
</item>
</channel>
</rss>
