JJ on Sat, 19 Jan 2019 04:13:21 +0700 typed in
alt.windows7.general the following:
On Fri, 18 Jan 2019 12:24:18 -0800, pyotr filipivich wrote:
Doing backups. Very simple, one would think, a simple batchfile, the
important line of which is:

Robocopy c:\ I:backup /s /s /xo /XJ /np /ndl /w:1 /r:1 /Tee
/Log+:%Logfile%.rtf /xf *.bak *.lnk *.cat *.regtrans-ms *.tmp
pagefile.sys hiberfil.sys /xd C:\Windows

(Which being translated means copy drive C:\ to directory Backup on
drive I, include subdirectories, only copy those changed, exclude
junctions, don't show progress {% copied} wait 1 second if something
'fails" and repeat once if it does, where to log all this, don't copy
bak link &c do not copy anything in Directory "C:\Windows". )

It works. (Yeah!)

Unfortunately, despite having "emptied the recycle bin", there are
7 gigs of files copied from said "empty" recycle bin to
I:\Backup\$Recycle. And directory I:\Backup is now a hidden system
directory.

You should exclude the $RECYCLE.BIN directory using the /XD switch.

I did in subsequent iterations.

But the fact remains, an "empty" recycle.bin had 7 gigs of files
in it. I know that neither DOS nor Windows actually erases the file,
but just marks the directory entry as "not in use". But this seems
to be ... wrong. Apparently the directory entry is just moved, and
the subsequent file is sill "intact", form the first block onward.

OTOH, I did find out how to actually delete tose files and
actually empty the recycle bin. Again, from the command line. "I'm
having so much fun."
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?