On Mon, Dec 29, 2008 at 7:36 PM, Scott Klassen <[email protected]> wrote:
> 2) Robocopy. I'm thinking that this will be the way to go, if it can do
> what I need, because I can just
> start the process immediately at close of business.
What I do is prep the new folder tree on the new server in advance.
ROBYCOPY files over in advance, in stages, if need be. Then, when
you're ready to actually switch servers, you can do a final ROBOCOPY
to just sync changes, instead of having to wait for the entire dataset
to copy.
ROBOCOPY with the /MIR (mirror) switch will delete any files in the
target that don't exist in the source (thus preventing files from
"coming back from the dead" during the above).
> I need to keep folder and file timestamps, permissions, attributes, all
> subfolders and files, etc.
> Basically an exact copy of the partition contents.
>
> What arguments would I use to achieve the above if moving from \\oldserver\d$
> to
> \\newserver\d$ (not certain if admin shares are a permissable path)?
One argument you should try would be:
ROBOCOPY /?
;-) But the basics would be:
ROBOCOPY /E /COPYALL \\oldserver\d$ d:\
I usually throw on some switches for logging. /LOG to a file
somewhere. /TEE to also watch it in real-time. I also like /NFL /NDL
/NP -- that way, only warnings/errors will be logged; success is
silent. It's any trouble I'm interested in hearing about.
/R:0 /ZB may be useful if locked files or other problems are
encountered, especially during pre-copy stuff described above.
Be warned that doing a straight file copy on C:\WINDOWS and/or
anything mentioned in the registry is likely to cause Bad Things(TM)
to happen. So don't run that on a C: drive root if you want things to
keep working. But plain old files should be fine. You can exclude
system stuff and do the rest of the drive safely.
-- Ben
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
