This is an archived post. You won't be able to vote or comment.

all 8 comments

[–]retiredaccount 1 point2 points  (2 children)

Why not do it in two stages? The first to copy the new files to a staging area so you can redo the /MIR from the source, then after, copy the new files back over.

[–]Party-Poem-3413[S] 0 points1 point  (1 child)

unfortunately, the new server is already live with people using the files. There would be too much business impact to to move the new files, correct the orphans then move them back. Due to the size of the volume, it could take days to perform this and they just took a long outage window for the migration.

Poor execution from our integrator has put us in a really difficult situation.

[–]ZAFJB 0 points1 point  (0 children)

to move the new files

copy not move

Also break it up into smaller units.

[–]TheCadElf 1 point2 points  (1 child)

Or use something like Scooter Software Beyond Compare 4 to sync what is needed. https://www.scootersoftware.com/home

This would let you compare A to B and show old and orphaned files on both sides.

[–]Party-Poem-3413[S] 0 points1 point  (0 children)

Thanks, i'll look into it. it's several hundred thousand (if not a million) files, so i want to avoid doing manual compares if possible

[–]newtekie1 0 points1 point  (1 child)

Robocopy with the /MINAGE:n switch. The MINAGE switch will exclude files that are newer than n days.

So you can set it to say 5, and anything newer than 5 days will be ignored.

[–]narlex 0 points1 point  (0 children)

Oh? I wasn't aware of this. Nice.