• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 693
  • Last Modified:

Transfer files between 2 Win2K servers and keep the same file permissions

I need a way to transfer a large number of files over the network from one Windows 2000 Server to another Windows 2000 Server and keep the same permissions on the files I am moving on the server they are going to.

If I just move them using Windows copy and paste the files all get the default "everyone" has full access... Anyone know of either a different way to transfer them that will keep their permissions or a program that will do so.  

And, I need an answer SOON!!!  In 1 hour!

Thanks!
0
tebacher
Asked:
tebacher
  • 4
  • 3
  • 2
  • +1
2 Solutions
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Use the Windows NT 4 Resource Kit utility, SCOPY.EXE.

First connect a network drive to the share on the other server you want to copy to.  Then execute the following command (once you have SCOPY on the machine)

SCOPY <sourcedrive:\path\file.ext> <destdrive:\path\file.ext> /o /s

/o = copy owner information
/s = copy security information
0
 
tebacherAuthor Commented:
From what I can tell, it would do what I need.  But, where do I get scopy for windows 2000?
0
 
tebacherAuthor Commented:
BTW, thanks for the quick response, leew!
0
Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

 
visioneerCommented:
XCOPY in Windows 2000 will do the same thing.  The /O switch will transfer ownership and ACL information.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Visioneer is correct concerning XCOPY - I just never use it in favor of SCOPY.  

Below are two links concerniny XCOPY and a 3rd for downloading SCOPY direct from Microsoft.

http://www.winnetmag.com/Article/ArticleID/15141/15141.html

http://support.microsoft.com/default.aspx?scid=kb;en-us;174273

http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-us/scopy.mspx
0
 
tebacherAuthor Commented:
Well, I found a way around this problem for the time being... I am using our backup software and tapes to make a copy of the data, then redirect the restore to the other server where I want the data.  The permissions stay intact this way.

0
 
visioneerCommented:
Is that really faster than using XCOPY?
0
 
Rob StoneCommented:
probably not, but depending on the amount of data it would help reduce network traffic using the backup.
0
 
tebacherAuthor Commented:
I ended up having some problems backing up the data and restoring it to a different place.  So, I used XCOPY and it worked pretty well.  It was faster than the backup method, of course.  The only complaint I had about XCOPY was that I ran into some permission issues that would stop the transfer.  I would be 1/2 way through transferring 8 Gb of data and it would stop.  I didn't see the /C option to "continues copying even if errors occur" until I was done :-)  That would have been nice to know!

Anyway, I got the data transferred with the same permissions it had on the old computer, so everyone is happy.

Thanks for the help leew and visioneer!!

0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
As a quick note - SCOPY has never (to my memory) stopped on me in the middle of a transfer unless I ran out of quota or disk space.  If it hits something it can't copy, it just moves on to the next item, noting an error message.  Thus, it can be really helpful if you use SCOPY and redirect output to a file.  Then you can review the file for missed files and remedy the situation.
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 4
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now