Same-server file copies
-
The answer may be obvious, but I would appreciate confirmation of my understanding. Scenario: in a Windows network, a very large number of files exist in a folder on Server A, but need to be moved to a different folder on the same Server A. User B, which might be a human logged into Server B or an app running on Server B, cannot log into Server A via RDP, but can access its files from Server B. If User B uses File Explorer or a command window to move those files or the C# app uses a File.Move, do those files first get copied across the network from Server A to a temporary folder on Server B and back again? If the user has execute permissions on a folder on Server A and executes a batch/command file in that folder that moves those files, that would not involve actual file copying but changes in the NTFS file tables, right?
There are no solutions, only trade-offs.
- Thomas SowellA day can really slip by when you're deliberately avoiding what you're supposed to do.
- Calvin (Bill Watterson, Calvin & Hobbes) -
The answer may be obvious, but I would appreciate confirmation of my understanding. Scenario: in a Windows network, a very large number of files exist in a folder on Server A, but need to be moved to a different folder on the same Server A. User B, which might be a human logged into Server B or an app running on Server B, cannot log into Server A via RDP, but can access its files from Server B. If User B uses File Explorer or a command window to move those files or the C# app uses a File.Move, do those files first get copied across the network from Server A to a temporary folder on Server B and back again? If the user has execute permissions on a folder on Server A and executes a batch/command file in that folder that moves those files, that would not involve actual file copying but changes in the NTFS file tables, right?
There are no solutions, only trade-offs.
- Thomas SowellA day can really slip by when you're deliberately avoiding what you're supposed to do.
- Calvin (Bill Watterson, Calvin & Hobbes) -
Standard file mapping software will insure that a copy on the same physical system will remain on that system. The executable permission has nothing to do with the rest of the question at all.
jschell wrote:
The executable permission has nothing to do with the rest of the question at all.
True, but then that really wasn't the question. I'm not sure you understood my questions at all, but that's probably my fault for not being clear. My question is about which, if any, of the various scenarios presented will result in those files flowing across the network. I'm also confused by your use of "standard file mapping software". I'm talking about the operating system's Copy and Move commands, as well as the File.Move command in C#.
There are no solutions, only trade-offs.
- Thomas SowellA day can really slip by when you're deliberately avoiding what you're supposed to do.
- Calvin (Bill Watterson, Calvin & Hobbes) -
The answer may be obvious, but I would appreciate confirmation of my understanding. Scenario: in a Windows network, a very large number of files exist in a folder on Server A, but need to be moved to a different folder on the same Server A. User B, which might be a human logged into Server B or an app running on Server B, cannot log into Server A via RDP, but can access its files from Server B. If User B uses File Explorer or a command window to move those files or the C# app uses a File.Move, do those files first get copied across the network from Server A to a temporary folder on Server B and back again? If the user has execute permissions on a folder on Server A and executes a batch/command file in that folder that moves those files, that would not involve actual file copying but changes in the NTFS file tables, right?
There are no solutions, only trade-offs.
- Thomas SowellA day can really slip by when you're deliberately avoiding what you're supposed to do.
- Calvin (Bill Watterson, Calvin & Hobbes)Your situations are not entirely clear so I'll answer it like this. The only time the files will NOT cross the wire is when you are MOVING (NOT COPYING!) the files from one folder to another ON THE SAME VOLUME ON THE SAME SERVER.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave Kreskowiak -
Your situations are not entirely clear so I'll answer it like this. The only time the files will NOT cross the wire is when you are MOVING (NOT COPYING!) the files from one folder to another ON THE SAME VOLUME ON THE SAME SERVER.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave KreskowiakDave Kreskowiak wrote:
will NOT cross
but with any luck, won't be truncated (therefore "moved"). Windows 10, on my multi-processor box, with tons of fast memory, COPY/XCOPY/MOVE TRUNCATES files. Particularly image files. To boot, there's little evidence that anyone with a respectable claim to knowledge concerning the faux pas is ever going to see fit to fix the problem. And to TNCaver (if you're listening): I wouldn't want to hijack a post by claiming I knew anything about servers or hosting because I'm really a general computer user with some basic understanding of system processing, but in my experience, there's only one way to handle transfering of files from point A to point B ... and so far ... that's by zipping them up in an archive. If that sounds kosher to you, lemmee know and I'll go into more detail.
-
Dave Kreskowiak wrote:
will NOT cross
but with any luck, won't be truncated (therefore "moved"). Windows 10, on my multi-processor box, with tons of fast memory, COPY/XCOPY/MOVE TRUNCATES files. Particularly image files. To boot, there's little evidence that anyone with a respectable claim to knowledge concerning the faux pas is ever going to see fit to fix the problem. And to TNCaver (if you're listening): I wouldn't want to hijack a post by claiming I knew anything about servers or hosting because I'm really a general computer user with some basic understanding of system processing, but in my experience, there's only one way to handle transfering of files from point A to point B ... and so far ... that's by zipping them up in an archive. If that sounds kosher to you, lemmee know and I'll go into more detail.
RedDk wrote:
COPY/XCOPY/MOVE TRUNCATES files
I will note that I have decades of work experience and I have never seen a problem specifically like that. I have seen problems such as empty files, corrupted files, failed moves, moves that never complete. Probably some others as well. That includes within one physical disk, across disks, across shared file systems (via various mechanisms that allow that.) Problems that I have seen are most often user error to some extent. But hardware and network problems have also been at fault. Even long ago ejecting disks (or memory cards) before it was completed.
-
Dave Kreskowiak wrote:
will NOT cross
but with any luck, won't be truncated (therefore "moved"). Windows 10, on my multi-processor box, with tons of fast memory, COPY/XCOPY/MOVE TRUNCATES files. Particularly image files. To boot, there's little evidence that anyone with a respectable claim to knowledge concerning the faux pas is ever going to see fit to fix the problem. And to TNCaver (if you're listening): I wouldn't want to hijack a post by claiming I knew anything about servers or hosting because I'm really a general computer user with some basic understanding of system processing, but in my experience, there's only one way to handle transfering of files from point A to point B ... and so far ... that's by zipping them up in an archive. If that sounds kosher to you, lemmee know and I'll go into more detail.
It's not going to be fixed by Microsoft because it's something specific to your machine/network setup. I've NEVER had anything like that happen in any version of Windows and I've been using every version since you had to type "win" at a DOS prompt to start Windows.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave Kreskowiak -
Dave Kreskowiak wrote:
will NOT cross
but with any luck, won't be truncated (therefore "moved"). Windows 10, on my multi-processor box, with tons of fast memory, COPY/XCOPY/MOVE TRUNCATES files. Particularly image files. To boot, there's little evidence that anyone with a respectable claim to knowledge concerning the faux pas is ever going to see fit to fix the problem. And to TNCaver (if you're listening): I wouldn't want to hijack a post by claiming I knew anything about servers or hosting because I'm really a general computer user with some basic understanding of system processing, but in my experience, there's only one way to handle transfering of files from point A to point B ... and so far ... that's by zipping them up in an archive. If that sounds kosher to you, lemmee know and I'll go into more detail.
-
It's not going to be fixed by Microsoft because it's something specific to your machine/network setup. I've NEVER had anything like that happen in any version of Windows and I've been using every version since you had to type "win" at a DOS prompt to start Windows.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave KreskowiakServer accounts management, portfolio, is macros, in instantiated form, of overruling.