[<<]Message[>>]    [<<]Author[>>]    [<<]Subject[>>]    [<<]Thread[>>]

Number   :  3444
Date     :  2003-01-05
Author   :  yodaslo
Subject  :  Re: HELP!!! Major blunder!!! How to restore files back to their directory??
Size(KB) :  3


Good point!!

Kan, why is there no "undo" switch in xxcopy?

Simplified in my terms: the ability to 'remeber' or put to a temp 
directory everything that was done, and leave it there for __ period 
of time [user defined], so that in case of a serious mistake (as we 
all have done) we could run xxcopy /undo and it would undo and 
put back to normal everything it did on it's last running. (Just like 
if we never ran the command at all)

True, for DOS and early windows, pre Win95, hard drive size and 
memory is a major concern, but I know hard drive sizes and memory are 
increasing on pc's daily, so it's usually not a problem for users. 
For those users where it is a problem, there can be a switch to 
simply forgo the undo option.

True, it requires that the user set up a valid naming for the 
original operation so they know which xxcopy to undo, but if xxcopy 
saved it automatically as the command line they ran with the 
date/time stamp attached, it would probably cover most users needs. 
(and most of the time it is the one we just got done running)

In fact, if space is a major consideration, it could be used with 
WinZip (again automatically) to zip up the undo stuff.

Just thinking aloud
Rich

--- In xxcopy@yahoogroups.com, Kan Yabumoto  wrote:
> 
> The /RC operation is essentially a move operation. Therefore, it 
is not
> a total loss at all. Depending on the original condition, you may
> select exactly what you had earlier and restore the original 
condition.
> 
> Let me assume that before the operation, you did not have anything 
at
> the \\congo\cdb_files\ directory with the corresponding files that
> were overwritten by the action (but the inclusion of the /Y switch
> suggests that you had reason to overwrite).
> 
> Anyway, based on the principle that a newly copied file (not
> a file that was overwritten) always gets assigned with a fresh
> Creation time, you can select the files that were moved by the
> /RC operation. If the operation was done 3 hours ago, you can say 
this:
> 
> 
> xxcopy \\Congo\cdb_files\*.cdb /ldtzl/s/h/da#3h/fc
> 
> The /FC modifies the selection of the timestamp from the
> otherwise-default LastWrite timestamp to the Creation timestamp.
> 
> This is just a starter. It lists the files that were created
> at the location within 3 hours. A more serious one is;
> 
> xxcopy \\Congo\cdb_files\*.cdb g:\client\ /s/h/da#3h/fc
> 
> This will copy back the files to their original locations.
> If you add /RCY/PD0 it will not only copy the file back to the
> original location, but also delete from the current location
> (closer to restoring the original condition).
> 
> One thing you cannot undo from your mistake is to recover the
> files that were overwritten in the first place.
> 
> Kan Yabumoto
> ===================================================================
> 
> At 2003-01-03 17:08, you wrote:
> 
> 
> >Here it is:
> >
> 
>XXCOPY "G:\Client\*.cdb" "\\Congo\CDB_Files\" /E /C /F /H /R /K /Y 
/
> >V /I /RCY /ED /PD0
> >
> >The killer was RCY. %^&*() Why the &^*() didn't i see it. Agghhh.
> >The deal is that i had user's working while this was in process.
> >moreover, many of the files are three and for folders deep. what a 
%
> >^&*() mess!
> >
> >suggestions?
> >
(snip)



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.