New
#170
That is what i did, dis not work
If in Vista or later, right-click the batch file and choose "Run as Administrator".
I have read the thread and haven't seen anyone else ask this. We are using Robocopy to back up and restore our users data in prep for either migration from Vista to Win 7 or lfe cycling old equipment.
Robocopy works great we just point the users to the batch file location and theyrun the back up. Later they run the restore again this works great.
Here's the problem, one user got a little nosey and figured out that they could look into the files that had been backed up from another user.
So how can the files be secured, but still accessible for the user who they belong to?
Last edited by rhopper; 23 Nov 2012 at 15:42. Reason: Misspelling
As I see it, this isn't really a Robocopy issue. It's an issue that you're making your shares too broad, allowing everyone to read everyone else's folders.
Perhaps you could make the backup folders non-readable by standard users? Or, share each folder only to its user, so other users have no read rights.
You also have the ability, using Robocopy options, to preserve or eliminate file attributes such as ownership. If a user has no security rights to another user's files, he wouldn't be able to read them locally, though I'm uncertain if that changes over a network. As I say, limiting the network shares to each user's own folder may be the way to go.
Thank you...giving this a run now.
Out of interest. I am rescuing data from a drive that is slowing down aka dieing. How does Robocopy identify this in regards to corrupt data. Does it skip over and move on, will it just simply hang and await a force closure or simply auto end the process?
I dont expect an issue as I believe the corrupt data area is actually in the repository recycle folder (hidden).
Thanks
Robocopy works at file level, so if it cannot properly read a file I presume that particular one would be skipped and listed as failed.
Use Robocopy's logging options to create a log file. At the bottom you will see a column for "Failed, which will show how many files/folders failed to copy.
There is a /R:n switch which determines the number of retries in the case of a copy failure. If you don't specify this switch, robiocopy uses a default of 1 million retries with 30 secs between retries.
I often use /R:3 - 3 retries with 30 secs between retries.
If you're copying locally (e.g. second drive in another bay, or external USB/Firewire/eSATA drive) you might want to use something like /R:4 /W:2. That would retry each four times with a two-second interval. Robocopy's default of a 30-second interval is intended more for network access situations.
Hi I want to use robocopy or xcopy to copy a HTM file with a linked folder. Its not copying the linked folder now. But when i manually copy either the HTM file or the folder, both of then get copied .