IT Needs a Vince & Larry.....
-
Wow, that is not a good thread.
-
Uhm,.. Wow..
Although - sometimes when I am working with files on a server, I have to remind myself RIGHT CLICK and drag.. don't just drag. I want a copy of the orginial files not to move them. I have seen so many times that the MOVE (copy then delete) has failed.. thus leaving me with nothing.
-
@g.jacobse said:
Uhm,.. Wow..
Although - sometimes when I am working with files on a server, I have to remind myself RIGHT CLICK and drag.. don't just drag. I want a copy of the orginial files not to move them. I have seen so many times that the MOVE (copy then delete) has failed.. thus leaving me with nothing.
You've had a move fail? Even if a move fails, you should not lose the file. A default left drag only does a move if it is on the same filesystem and the file is not actually moving but the name only is moving, so any left drag move operation is recoverable via a recovery tool like Recuva reliably as long as you do not write over the space before doing so. The move default action is designed to have no destructive action on Windows.
-
@scottalanmiller said:
@g.jacobse said:
Uhm,.. Wow..
Although - sometimes when I am working with files on a server, I have to remind myself RIGHT CLICK and drag.. don't just drag. I want a copy of the orginial files not to move them. I have seen so many times that the MOVE (copy then delete) has failed.. thus leaving me with nothing.
You've had a move fail? Even if a move fails, you should not lose the file. A default left drag only does a move if it is on the same filesystem and the file is not actually moving but the name only is moving, so any left drag move operation is recoverable via a recovery tool like Recuva reliably as long as you do not write over the space before doing so. The move default action is designed to have no destructive action on Windows.
I know two different things,.. but Windows designed to not be destructive? What happened to your hair (or mine!)?
Generally speaking - you are correct... Move should not destroy the data. However, i have seen it happen.. but then again,.. the power did go out in the middle of it,.. so technically not a Windows issue...
-
@g.jacobse said:
Generally speaking - you are correct... Move should not destroy the data. However, i have seen it happen.. but then again,.. the power did go out in the middle of it,.. so technically not a Windows issue...
Ah ok. That's file corruption
It was a left click move in that case? -
@scottalanmiller said:
Wow, that is not a good thread.
Nope. Saw it first thing this morning and just stared at it for a few minutes, knowing how it was going to end after I asked them to post code used.
-
I'd settle for Terrance & Phillip...
-
Lol I remember these guys
-
I always do a left-click move. I find it makes it easier to see that everything has moved. I've never had a problem, but perhaps I've been lucky. I thought the delete wouldn't happen until the copy is confirmed as successful, so in case of a power cut, the source should remain. Basically, it comes down to whether I trust Windows not to screw up more than myself. Maybe I should trust myself more.
As for the SW thread, my guess he's mixed up source and destination, so it's deleted the file from the destination (which should have been the source).
-
@Carnival-Boy said:
As for the SW thread, my guess he's mixed up source and destination, so it's deleted the file from the destination (which should have been the source).
Yes, that's my thought too and someone else has already pointed that out. It's the one reason I'm not a huge fan of using the /MIR switch nor do I recommend it.
-
/MIR is great and I've used it loads of times. But as with all powerful command line tools, an administrator needs to proceed with extreme caution.
-
Whenever I use robocopy I tend to do create and move a batch of test files prior to the actual move. This helps me tweak the command to do what I actually want it to do.
As @Carnival-Boy said Robocopy is a powerful tool that should be used with caution.
-
Me too. The /l option can be useful to, it displays the results of the command without actually doing anything.
