![]()
[<<]Message[>>] [<<]Author[>>] [<<]Subject[>>] [<<]Thread[>>]
Number : 4111 Date : 2003-03-23 Author : anders thoresson Subject : Re: using xxcopy together with zip/arj compression Size(KB) : 1
> A more complex approach which is more bullet-proof for this sort of > operation has been posted by Kan some time ago. It involves creating a > catalogue of all the files on the computer using /SZ0 (now /TR0) which > creates a directory structure and file list of zero length files. There's > an example of this in technical bulletin #11. Thank's for the tips! I've read TB#11 a couple of times now, I think I've understood how it works, but since I don't want to create a batch file that I'm 100 percent sure I know the mechanics of, I would like to check with the list members that I've got everything right: XXCOPY \src\ \ref\ /CLONE /TR0 - creates a reference directory tree which contains every directory and every file in \src\ but with the files truncated to 0 bytes. XXCOPY \src\ /AZ /S - removes the archive bit from every file in \src\ XXCOPY \src\ \ref\ /AA /S /H /U /BX - for every file, hidden or not, in \src\ that doesn't exist in \ref\ or where the file in \src\ has been modified, the archive bit is set. the /U- switch also updates the same files in \ref\. But why is the /TR0-switch not included here? Are even new files that are added to \ref\ truncated to 0 bytes? XXCOPY \src\ \dst\ /A /S /H /KS - every file in \src\ which has the archive bit set is copied to \dst\. /KS makes sure that if the file is read-only in \src\ it's read-only in \dst\ as well. Is this a correct description of the for steps included in "Differential Backup using a skeleton directory" in TB#11? The text in the bulletin states that "for illustration purpose, common switches are deliberately left out". Which switches should be added to have a working backup-set? Best regards, anders thoresson
This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.