J
JensN
Hi there,
In order to work with Lightroom directory tree from a previous failed NAS which was backed up to OneDrive I need the ca 1TB pictures restored to a like structure on a new NAS.
When trying to Restore / copy picture files from my local Onedrive folder to an external drive (NAS) I kept getting this error:
"There is not enough free space on Local Disk. You need an additional xxx GB to copy these files"
One solution was to enable files on demand (I'm aware the opposite has been stated as a solution) and select a 'fitting' number of directories to copy.
Every so often the error would repeat and a renewed 'free space' command on my onedrive directory got the copy function back working.
THEN I started to get to messages 'Files are not awailable for synching, skip or try again'... only Skip worked
After doing this, I checked the directory tree manually and found several directories missing on the NAS.
This time I went for manual directory by directory copying, Ctrl C, Alt Tab, Ctrl V, Alt-Tab arrow down and so on... (no I didnt write a script, though I'm tempted to do so.)
During this I also found several directories allready copied during the first process had 1-2 missing pictures , so now I have to make a dir -r > tjeck NAS.txt and same for OneDrive (if the DOS command works there) and then compare the text files
This would likely not be a problem if I had a free 2TB harddisk all OneDrive files could sync to (I think). I also suppose the 'Files not awailable for sync' may be caused by files having same filenames even being in different directories.
So far I'm hoping the process will allow me to free one of the previously backed up harddisks, mappping that to OneDrive and the issue will not be present, but It is STILL a major issue for the reliability seen of OneDrive as a cloud backup...
I also have a nasty comment regarding the initial error message: It was not apparent the directory with not enough space was my local hard disk, thinking the NAS was at fault, since only the directory name was flagged, not the drive letter... took me some more time to realise that.
So all in all a easy restore operation has turned into a long drawn out manual job.
Best hopes of a good reply/solution
Continue reading...
In order to work with Lightroom directory tree from a previous failed NAS which was backed up to OneDrive I need the ca 1TB pictures restored to a like structure on a new NAS.
When trying to Restore / copy picture files from my local Onedrive folder to an external drive (NAS) I kept getting this error:
"There is not enough free space on Local Disk. You need an additional xxx GB to copy these files"
One solution was to enable files on demand (I'm aware the opposite has been stated as a solution) and select a 'fitting' number of directories to copy.
Every so often the error would repeat and a renewed 'free space' command on my onedrive directory got the copy function back working.
THEN I started to get to messages 'Files are not awailable for synching, skip or try again'... only Skip worked
After doing this, I checked the directory tree manually and found several directories missing on the NAS.
This time I went for manual directory by directory copying, Ctrl C, Alt Tab, Ctrl V, Alt-Tab arrow down and so on... (no I didnt write a script, though I'm tempted to do so.)
During this I also found several directories allready copied during the first process had 1-2 missing pictures , so now I have to make a dir -r > tjeck NAS.txt and same for OneDrive (if the DOS command works there) and then compare the text files
This would likely not be a problem if I had a free 2TB harddisk all OneDrive files could sync to (I think). I also suppose the 'Files not awailable for sync' may be caused by files having same filenames even being in different directories.
So far I'm hoping the process will allow me to free one of the previously backed up harddisks, mappping that to OneDrive and the issue will not be present, but It is STILL a major issue for the reliability seen of OneDrive as a cloud backup...
I also have a nasty comment regarding the initial error message: It was not apparent the directory with not enough space was my local hard disk, thinking the NAS was at fault, since only the directory name was flagged, not the drive letter... took me some more time to realise that.
So all in all a easy restore operation has turned into a long drawn out manual job.
Best hopes of a good reply/solution
Continue reading...