I am about to move to a headless operation of this server, but I have found an issue that, either I am not doing something right (damn good chance), OR, what I AM doing, there is no way around other than to be ON the desktop of WHS.
Once this server was built, I spent 2 days collecting all my data from multiple nodes on the network and moving it all to WHS. Once that was done, the data size totaled 3.3TB. No Big Deal. This was the point behind building this server in the first place....to get all my files in ONE place permanently. But herein lays my issue. I was 'lazy' for lack of a better term, in moving my data over. I created a share and dumped EVERYTHING there with the intention of running a file dupe against the data, and once dupes were removed, migrating the data into its final home (ie, Video files, Personal User Files, Music, ect ect).
Just now I went to verify something that I belived to be true, which was I accessed the server through the remote Server Console from a node on my network, and attempted to 'move' a file from one share directory to another. And the process performed exactly how I expected it (read: DIDNT WANT IT TO) do. The data chose a path from server, to node, back to alternate server share, instead of relocating itself quickly in a way that a normal file would move from one directory to another on a standard migration process from spot to spot on the same computer.
Did I miss something with this process? is there an environment setting I can make to tell the server to move it 'virtually' instead of actually takeing across the network and back again?
This seems the last reason and time I would need to access the WHS desktop directly. migrating this data into its final home would take days if I chose to do it from a node on the environment, UNLESS, again, I am missing something?
Thanks all again for the input and help. This forum has been a great resource, and I certainly apprecate all the feedback and advice.
-Andrew
As I previously informed you in the thread titled
Copying data from a Non-storage drive to a storage drive (my second post in that thread), that's how shares work (on all Windows PCs, not just WHS). Unfortunately, you will have to "go out and back in again" one way or another (moving files from D:\shares is unsupported and has caused problems in the past for some users, including myself when I tested it). You could try logging into the server desktop and use
\\localhost (instead of
\\server) for the UNC path. It may speed it up slightly. Of course, logging into the server desktop is unsupported.
