Ошибка 1314 robocopy

• Remove From My Forums

All replies

• Please forgive me my ignorance but why do you want to use intermediate host to handle I/O? Most of NAS boxes have rsync-based file replication coming out of factory. You’d better try playing with it. My 0.02$…

  -nismo

• Robocopy can fails to backup if files are in us. So make sure to backup when no files are in us.
  

  So better option is to use NAS utility to copy files or use VSS based backup utility for copy. (it will
  have open file(file in use) backup functionality)

  below robocopy command will copy file as per you requirement & place the copy log to
  robocopy.log file.

  You can verify robocopy.log by searching it for any failed file.

  robocopy z:folder2
  x: /E /ZB /COPYALL /LOG+:robocopy.log /TEE /R:3 /W:20

• Hello Gentlemen

  Thanks for your replays !

  @
  VR38DETT

  sorry but my NAS does not have

  @
  S.Marios

  you wrote that is better way — please explain

  @
  Shrikrishna Chinchkar

  Thanks for important advice, I cant use any NAS utillity, that are simply models

  @ to ALL

  Those data are shares for users and I have to move to second NAS because the current NAS is too small

  if I use your robocopy command I see in new drive only

  NAS2
  Drive1X:

         
  Subfolder1
          Files1

  I’d like to

  NAS2
  Drive1X:

       folder2
         
  Subfolder1
          Files1

  Many thanks for your help.

• Hi,

  Robocopy will copy subfolders and files to target location, so you should manually create the folder2 in Nas2Drive1x first, or modify the command to «robocopy z:folder2 x:folder2»

  ---

  TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

  • Proposed as answer by

    Tuesday, August 14, 2012 8:27 AM

  • Unproposed as answer by
    roshni12
    Tuesday, August 14, 2012 8:27 AM

• Hi,

  Robocopy will copy subfolders and files to target location, so you should manually create the folder2 in Nas2Drive1x first, or modify the command to «robocopy z:folder2 x:folder2»

  ---

  TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

  hi,

  I am facing similar issue where i am trying to copy data to my NAS device using robocopy command «robocopy E:foldername
  \nasdevicefolder name /S /ZB /COPYALL /R:0 /W:0 /MIR /log:log.txt» while runing it failing with below permission error and when i tried manually copy the folder on to the NAS drive it prompted «the folder contain security group,
  security permission will be lost». Since those folders has user security group mapped i need to copy security permission as well, can someone help on this.

  012/08/13 03:02:41 ERROR 1314 (0x00000522) Copying NTFS Security to Destination Directory E:folderpath
  A required privilege is not held by the client.

  Regards

  Roshni.

• Well i ment a better whay would be to use your NAS’s backup or sync feature (if any ofc) or even the MS server sync folders features, or even NTbackup would work.

  The problem with Robocopy is indeed that if a file is in use it will be inaccessible.

  did you use my command and only get the root folder not the subfolders? I just tested it and it creates structure and files.also you might add the /purge switch so if a file is no loger at the source it will be deleted from the destination as well

• I always try the following options:

  robocopy <src> <dest> /e /copyall /r:1 /w:1 /fp /b /log:c:tempout.log /tee

  /e : everything including subdirectories

  /copyall : gets all the attributes

  /r : retry once (default is 30 I think)

  /w: wait 1 second between retries (default is 30 seconds)

  /fp: full path is displayed for output to terminal or log

  /b: backup mode (this is very important and allows backing up open files)

  /log: write the history and summary to a log file (be careful: I once copied 6 million files and the log was useless and caused robocopy to fail)

  /tee: only used in conjunction with /log. By default, when you use /log, it logs the output. /tee sends a copy of the log to STDOUT as well.

  I recommend reading the book on robocopy. It’s a good nightcap and xcopy is going the way of the dinosaurs. You’ll need this command more than you might know, and there are tons of options not mentioned in the replies by these other courteous folks who offered
  their two cents. : ) Hope this helps. Good luck! : )

• This is my go to script for migrating data around our network.  Just migrated 8TB of data last weekend.  Works like a charm.  I have found that backup mode slows down the file copy significantly which is noticeable when doing
  large data sets.  I’ve never had any issues not using it.  I do suggest placing all your data into one folder so you can copy that one folder instead of having to copy multiple folders in different scripts or copying from the drive letter share which
  will end up copying file system information which is unnecessary.

  robocopy «\NAS1Folder1» «\NAS2Folder1″ /S /E /PURGE /COPY:DATSOU /DCOPY:T /LOG+:»C:RoboCopyLogsRobocopy.log» /TEE /R:5 /W:0

  — Description: Use for innitial exact copy of data that includes folder and file security, owner info, date times stamps and directory timestamps.
  — /S — Copy Subfolders
  — /E — Copy Subfolders, including Empty Subfolders.
  — /Purge — This will delete extra/new files on the destination that are not found on the source.***  — verify paths are correct!!!
  — /COPY:DATSOU — Copies all folder and file permissions and attributes
  — /DCOPY:t — Will transfer over the time stamps on folders.  
  — Log+»» — Set the log location of your choice
  — /TEE — Output to console window, as well as the log file.
  — /R:5 — Number of Retries on failed copies — default is 1 million.
  — /W:2 : Wait time between retries — default is 30 seconds.
  — Add /MIR to this script if you need to rerun this script and must have the folder permissions update.  (this will increase script run time)
  — Add /SECFIX and /MIR to recopy file permissions if they have been updated (will signifcantly increase run time.  Consider running /mt:8 to have multiple threads)

• Thanks, Caleb44.

  What you so clearly illustrated is exactly my scenario. That is to say, I’m in the process of migrating data from a NAS about to be retired, to a new clustered array. It’s comprised of two servers on an active passive cluster, running W2008 R2 Enterprise,
  connected to a storage array. I’m going painstakingly slow with this process, testing the newly moved data inside and out, before I hit the really big folders, filled with a miriad of diverse security. I was experimenting with ROBOCOPY on test folders with
  success, but also with glitches here and there. Your code seemed to be the answer. I migrated a half-dozen folders to the new array and everything seemed to be fine. Until today.

  Here’s the issue. The newly migrated parent folder seems fine, but the ability to share sub-folders is corrupt. For instance, if I click on a sub-folder, the sharing icons and sharing status will be reflected in the explorer window’s footer, indicating the
  folder is shared. However, if I look at the folder properties and inspect sharing, that tab reports that the folder is not shared. If I go into advanced sharing, check the box to share the folder, set permissions, hit OK, the properties window still reports
  that it is not shared. If I go through the Basic sharing steps, I’ll get an error that says this folder can’t be shared. Even if I create a new folder under the parent, the issue is inherited. If I go back to the root of the drive, I can create folders with
  trouble-free sharing. This is an issue that plagued me throughout my testing. I thought it had something to do with the SEC, which I abandoned in favor of your switch selection.

  Any idea what could be causing this? My workaround is to set DFS to point to the sub-folder I would prefer to share straight up, in order to get user’s connected.

  Thanks very much for any ideas anyone might have.

• Hey Crowrock,

  I’m sorry to hear the problem you are facing.  I’ve never run into that scenario before.  I would consider trying two things.

  1. Attempt to recreate the problem from the beginning, meaning copy over a small subnet of folders and files in the same process and see if the problem persists.  Then after you do that, attempt to change around switches to see if you can resolve the
  problem.  This method should help you identify what caused the problem in your scenario.  From there that should help you know what needs to be done in order to fix it.  

  2. I suggest starting a new thread to attract new attention and other professions that may be able to help solve this problem.

• Thanks, Caleb44.

  I’ll start a new thread. Good advice.

  I have tested at length what you suggested in your first consideration. The switch that copies security is the culprit, whether it’s  /COPY:DATSOU or /SEC. Without those, of course, I might as well just drag-‘n’-drop. If I create a new folder under
  the root of the drive, everything is fine with it, along with any sub-folders. However, anytime I move data with ROBOCOPY, as you defined it, and I share the parent folder, ALL sub-folders show up shared as indicated by the Share Status at the bottom of the
  explorer window, but do not show up shared in properties. Also, when I click on the Share tab, the property window freezes for awhile before showing the Share tab. Any attempt to alter sharing on these sub-folders is futile, even if I create
  a new sub-folder.

  Thanks for your input.

• Is the source location NTFS?

• you should throw up a link to your new post.

• Hello Caleb44-

  Thanks very much for your interest. Yes, this is NTFS. In my new post, I’ve also indicated that the data is migrating from a Windows 2003, 32 bit clustered array to a Windows 2008 R2 clustered array. You asked a good question. My sense is that I’m trying
  scatch the itch in the wrong place playing with ROBOCOPY and that the issue is being caused by something more global in nature.

  The good folks at MS won’t allow me to post links or images until my account is verified. I have no idea how long that takes. The subject of my new thread is:
  Sharing Breaks After Migrating Data Using ROBOCOPY

  I will post the link when I’ve been welcomed to the inner circle:)

  Thanks! I’m new to using forums. I know, I’ve lived a sheltered life.

• Good Luck Crowrock.  You may also consider posting over in the Spiceworks forums to see if any guys there can help you out.  

  http://community.spiceworks.com/

• • Edited by
    Caleb44
    Wednesday, December 19, 2012 8:56 PM

• Remove From My Forums

All replies

• Please forgive me my ignorance but why do you want to use intermediate host to handle I/O? Most of NAS boxes have rsync-based file replication coming out of factory. You’d better try playing with it. My 0.02$…

  -nismo

• Robocopy can fails to backup if files are in us. So make sure to backup when no files are in us.
  

  So better option is to use NAS utility to copy files or use VSS based backup utility for copy. (it will
  have open file(file in use) backup functionality)

  below robocopy command will copy file as per you requirement & place the copy log to
  robocopy.log file.

  You can verify robocopy.log by searching it for any failed file.

  robocopy z:folder2
  x: /E /ZB /COPYALL /LOG+:robocopy.log /TEE /R:3 /W:20

• Hello Gentlemen

  Thanks for your replays !

  @
  VR38DETT

  sorry but my NAS does not have

  @
  S.Marios

  you wrote that is better way — please explain

  @
  Shrikrishna Chinchkar

  Thanks for important advice, I cant use any NAS utillity, that are simply models

  @ to ALL

  Those data are shares for users and I have to move to second NAS because the current NAS is too small

  if I use your robocopy command I see in new drive only

  NAS2
  Drive1X:

         
  Subfolder1
          Files1

  I’d like to

  NAS2
  Drive1X:

       folder2
         
  Subfolder1
          Files1

  Many thanks for your help.

• Hi,

  Robocopy will copy subfolders and files to target location, so you should manually create the folder2 in Nas2Drive1x first, or modify the command to «robocopy z:folder2 x:folder2»

  ---

  TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

  • Proposed as answer by

    Tuesday, August 14, 2012 8:27 AM

  • Unproposed as answer by
    roshni12
    Tuesday, August 14, 2012 8:27 AM

• Hi,

  Robocopy will copy subfolders and files to target location, so you should manually create the folder2 in Nas2Drive1x first, or modify the command to «robocopy z:folder2 x:folder2»

  ---

  TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

  hi,

  I am facing similar issue where i am trying to copy data to my NAS device using robocopy command «robocopy E:foldername
  \nasdevicefolder name /S /ZB /COPYALL /R:0 /W:0 /MIR /log:log.txt» while runing it failing with below permission error and when i tried manually copy the folder on to the NAS drive it prompted «the folder contain security group,
  security permission will be lost». Since those folders has user security group mapped i need to copy security permission as well, can someone help on this.

  012/08/13 03:02:41 ERROR 1314 (0x00000522) Copying NTFS Security to Destination Directory E:folderpath
  A required privilege is not held by the client.

  Regards

  Roshni.

• Well i ment a better whay would be to use your NAS’s backup or sync feature (if any ofc) or even the MS server sync folders features, or even NTbackup would work.

  The problem with Robocopy is indeed that if a file is in use it will be inaccessible.

  did you use my command and only get the root folder not the subfolders? I just tested it and it creates structure and files.also you might add the /purge switch so if a file is no loger at the source it will be deleted from the destination as well

• I always try the following options:

  robocopy <src> <dest> /e /copyall /r:1 /w:1 /fp /b /log:c:tempout.log /tee

  /e : everything including subdirectories

  /copyall : gets all the attributes

  /r : retry once (default is 30 I think)

  /w: wait 1 second between retries (default is 30 seconds)

  /fp: full path is displayed for output to terminal or log

  /b: backup mode (this is very important and allows backing up open files)

  /log: write the history and summary to a log file (be careful: I once copied 6 million files and the log was useless and caused robocopy to fail)

  /tee: only used in conjunction with /log. By default, when you use /log, it logs the output. /tee sends a copy of the log to STDOUT as well.

  I recommend reading the book on robocopy. It’s a good nightcap and xcopy is going the way of the dinosaurs. You’ll need this command more than you might know, and there are tons of options not mentioned in the replies by these other courteous folks who offered
  their two cents. : ) Hope this helps. Good luck! : )

• This is my go to script for migrating data around our network.  Just migrated 8TB of data last weekend.  Works like a charm.  I have found that backup mode slows down the file copy significantly which is noticeable when doing
  large data sets.  I’ve never had any issues not using it.  I do suggest placing all your data into one folder so you can copy that one folder instead of having to copy multiple folders in different scripts or copying from the drive letter share which
  will end up copying file system information which is unnecessary.

  robocopy «\NAS1Folder1» «\NAS2Folder1″ /S /E /PURGE /COPY:DATSOU /DCOPY:T /LOG+:»C:RoboCopyLogsRobocopy.log» /TEE /R:5 /W:0

  — Description: Use for innitial exact copy of data that includes folder and file security, owner info, date times stamps and directory timestamps.
  — /S — Copy Subfolders
  — /E — Copy Subfolders, including Empty Subfolders.
  — /Purge — This will delete extra/new files on the destination that are not found on the source.***  — verify paths are correct!!!
  — /COPY:DATSOU — Copies all folder and file permissions and attributes
  — /DCOPY:t — Will transfer over the time stamps on folders.  
  — Log+»» — Set the log location of your choice
  — /TEE — Output to console window, as well as the log file.
  — /R:5 — Number of Retries on failed copies — default is 1 million.
  — /W:2 : Wait time between retries — default is 30 seconds.
  — Add /MIR to this script if you need to rerun this script and must have the folder permissions update.  (this will increase script run time)
  — Add /SECFIX and /MIR to recopy file permissions if they have been updated (will signifcantly increase run time.  Consider running /mt:8 to have multiple threads)

• Thanks, Caleb44.

  What you so clearly illustrated is exactly my scenario. That is to say, I’m in the process of migrating data from a NAS about to be retired, to a new clustered array. It’s comprised of two servers on an active passive cluster, running W2008 R2 Enterprise,
  connected to a storage array. I’m going painstakingly slow with this process, testing the newly moved data inside and out, before I hit the really big folders, filled with a miriad of diverse security. I was experimenting with ROBOCOPY on test folders with
  success, but also with glitches here and there. Your code seemed to be the answer. I migrated a half-dozen folders to the new array and everything seemed to be fine. Until today.

  Here’s the issue. The newly migrated parent folder seems fine, but the ability to share sub-folders is corrupt. For instance, if I click on a sub-folder, the sharing icons and sharing status will be reflected in the explorer window’s footer, indicating the
  folder is shared. However, if I look at the folder properties and inspect sharing, that tab reports that the folder is not shared. If I go into advanced sharing, check the box to share the folder, set permissions, hit OK, the properties window still reports
  that it is not shared. If I go through the Basic sharing steps, I’ll get an error that says this folder can’t be shared. Even if I create a new folder under the parent, the issue is inherited. If I go back to the root of the drive, I can create folders with
  trouble-free sharing. This is an issue that plagued me throughout my testing. I thought it had something to do with the SEC, which I abandoned in favor of your switch selection.

  Any idea what could be causing this? My workaround is to set DFS to point to the sub-folder I would prefer to share straight up, in order to get user’s connected.

  Thanks very much for any ideas anyone might have.

• Hey Crowrock,

  I’m sorry to hear the problem you are facing.  I’ve never run into that scenario before.  I would consider trying two things.

  1. Attempt to recreate the problem from the beginning, meaning copy over a small subnet of folders and files in the same process and see if the problem persists.  Then after you do that, attempt to change around switches to see if you can resolve the
  problem.  This method should help you identify what caused the problem in your scenario.  From there that should help you know what needs to be done in order to fix it.  

  2. I suggest starting a new thread to attract new attention and other professions that may be able to help solve this problem.

• Thanks, Caleb44.

  I’ll start a new thread. Good advice.

  I have tested at length what you suggested in your first consideration. The switch that copies security is the culprit, whether it’s  /COPY:DATSOU or /SEC. Without those, of course, I might as well just drag-‘n’-drop. If I create a new folder under
  the root of the drive, everything is fine with it, along with any sub-folders. However, anytime I move data with ROBOCOPY, as you defined it, and I share the parent folder, ALL sub-folders show up shared as indicated by the Share Status at the bottom of the
  explorer window, but do not show up shared in properties. Also, when I click on the Share tab, the property window freezes for awhile before showing the Share tab. Any attempt to alter sharing on these sub-folders is futile, even if I create
  a new sub-folder.

  Thanks for your input.

• Is the source location NTFS?

• you should throw up a link to your new post.

• Hello Caleb44-

  Thanks very much for your interest. Yes, this is NTFS. In my new post, I’ve also indicated that the data is migrating from a Windows 2003, 32 bit clustered array to a Windows 2008 R2 clustered array. You asked a good question. My sense is that I’m trying
  scatch the itch in the wrong place playing with ROBOCOPY and that the issue is being caused by something more global in nature.

  The good folks at MS won’t allow me to post links or images until my account is verified. I have no idea how long that takes. The subject of my new thread is:
  Sharing Breaks After Migrating Data Using ROBOCOPY

  I will post the link when I’ve been welcomed to the inner circle:)

  Thanks! I’m new to using forums. I know, I’ve lived a sheltered life.

• Good Luck Crowrock.  You may also consider posting over in the Spiceworks forums to see if any guys there can help you out.  

  http://community.spiceworks.com/

• • Edited by
    Caleb44
    Wednesday, December 19, 2012 8:56 PM