Can not get robocopy to work with iSCSI drive
OK this is a bit different. I am attempting to use robocopy to copy data from a 2000 server we are taking down and place it on a new iSCSI drive on a 2003 server.
I have read much about robocopy and used many of the switches in various combinations but can not make this work. This is what I have tried (you can see the error(s) I am getting. When I add the *.* for the "Files", I also get an error of Invalid Parameter #1. Am I overlooking something simple????
C:\>robocopy \\2000server\acct \\2003server\data(iscsisha
--------------------------
ROBOCOPY :: Robust File Copy for Windows :: Version XP010
--------------------------
Started : Fri Jun 29 09:35:56 2007
2007/06/29 09:35:56 ERROR 53 (0x00000035) Getting File System Type of Destination \\2003server\data(iscsisha
The network path was not found.
Source : \\2000server\acct\
Dest - \\2003server\data(iscsisha
Files : *.*
Options : *.* /S /E /COPYALL /R:1000000 /W:30
--------------------------
NOTE: NTFS Security may not be copied - Destination may not be NTFS.
2007/06/29 09:35:57 ERROR 53 (0x00000035) Accessing Destination Directory \\2003server\data(iscsisha
The network path was not found.
Waiting 30 seconds...^C
C:\>
__________________________
Another try with " marks...
C:\>robocopy "\\2000server\acct" "\\2003server\data(iscsish
--------------------------
ROBOCOPY :: Robust File Copy for Windows :: Version XP010
--------------------------
Started : Fri Jun 29 09:38:38 2007
2007/06/29 09:38:38 ERROR 53 (0x00000035) Getting File System Type of Destination \\2003server\data(iscsisha
The network path was not found.
Source : \\2000server\acct\
Dest - \\2003server\data(iscsisha
Files : *.*
Options : *.* /S /E /COPYALL /R:1000000 /W:30
--------------------------
NOTE: NTFS Security may not be copied - Destination may not be NTFS.
2007/06/29 09:38:38 ERROR 53 (0x00000035) Accessing Destination Directory \\2003server\data(iscsisha
The network path was not found.
Waiting 30 seconds...^C
C:\>
__________________________
I've checked for Error 53 - the 2000 machine has the lastest sp4 and file and print sharing is checked in the properties section of the network connection (these items according to other posts).
Help!
I have read much about robocopy and used many of the switches in various combinations but can not make this work. This is what I have tried (you can see the error(s) I am getting. When I add the *.* for the "Files", I also get an error of Invalid Parameter #1. Am I overlooking something simple????
C:\>robocopy \\2000server\acct \\2003server\data(iscsisha
--------------------------
ROBOCOPY :: Robust File Copy for Windows :: Version XP010
--------------------------
Started : Fri Jun 29 09:35:56 2007
2007/06/29 09:35:56 ERROR 53 (0x00000035) Getting File System Type of Destination \\2003server\data(iscsisha
The network path was not found.
Source : \\2000server\acct\
Dest - \\2003server\data(iscsisha
Files : *.*
Options : *.* /S /E /COPYALL /R:1000000 /W:30
--------------------------
NOTE: NTFS Security may not be copied - Destination may not be NTFS.
2007/06/29 09:35:57 ERROR 53 (0x00000035) Accessing Destination Directory \\2003server\data(iscsisha
The network path was not found.
Waiting 30 seconds...^C
C:\>
__________________________
Another try with " marks...
C:\>robocopy "\\2000server\acct" "\\2003server\data(iscsish
--------------------------
ROBOCOPY :: Robust File Copy for Windows :: Version XP010
--------------------------
Started : Fri Jun 29 09:38:38 2007
2007/06/29 09:38:38 ERROR 53 (0x00000035) Getting File System Type of Destination \\2003server\data(iscsisha
The network path was not found.
Source : \\2000server\acct\
Dest - \\2003server\data(iscsisha
Files : *.*
Options : *.* /S /E /COPYALL /R:1000000 /W:30
--------------------------
NOTE: NTFS Security may not be copied - Destination may not be NTFS.
2007/06/29 09:38:38 ERROR 53 (0x00000035) Accessing Destination Directory \\2003server\data(iscsisha
The network path was not found.
Waiting 30 seconds...^C
C:\>
__________________________
I've checked for Error 53 - the 2000 machine has the lastest sp4 and file and print sharing is checked in the properties section of the network connection (these items according to other posts).
Help!
Get rid of the brackets in the share name, get rid of the trailing backslashes in the folder names, then try again.
ASKER
I've tried the GUI. It says the job is completed but no log and no files copied. I am using the S,E and COPYALL options but nothing. It is a simple job just copying data files from one server to another...
I keep reading how this is the best utility - it has to be me but not sure what I am doing wrong
I keep reading how this is the best utility - it has to be me but not sure what I am doing wrong
ASKER
rindi
I've tried the GUI and nothing. No log file to see what happened and no copied files. I am using the S, E and COPYALL but nothing.
I kept reading how this utility was so great - it must be me but not sure what I am doing wrong.
oBdA
sorry for the confusion but the brackets I placed for the post to help explain what that was -ie the iscsishareddrive is the destination location/folder. The trailing backslashes robocopy placed. If you look at my cmd line (in both examples) I did not have those in there.
I've tried the GUI and nothing. No log file to see what happened and no copied files. I am using the S, E and COPYALL but nothing.
I kept reading how this utility was so great - it must be me but not sure what I am doing wrong.
oBdA
sorry for the confusion but the brackets I placed for the post to help explain what that was -ie the iscsishareddrive is the destination location/folder. The trailing backslashes robocopy placed. If you look at my cmd line (in both examples) I did not have those in there.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
mapping drives using the robocopy gui? there is an option there ... can you explain what you mean?
What happens if you enter
dir \\2003server\data(iscsisha
and
net view \\2003server
in a command prompt?
dir \\2003server\data(iscsisha
and
net view \\2003server
in a command prompt?
Map the drives in a batch file and test them to see that they work
net use ....
Then use drive letters rather than UNC in robocopy.
I hope this helps !
net use ....
Then use drive letters rather than UNC in robocopy.
I hope this helps !
ASKER
Took a bit of time off over the weekend. I'm trying suggestions, will get back to you soon.
Many thanks for the input.
Many thanks for the input.
ASKER
Took a bit of time off over the weekend - will get back to you as soon as I try the suggestions.
Many thanks for the input.
Many thanks for the input.
ASKER
oBdA
when I enter dir \\2003server\data returns "The network path was not found."
when I enter net view \\2003server returns:
W03 Server
Share name Type Used as Comment
shared folder Disk
shared folder Disk
NETLOGON Disk Logon server share
shared folder Disk
SYSVOL Disk Logon server share
shared folder Disk
The command completed successfully.
SysExpert
I'm not real sure what you mean:
"Map the drives in a batch file and test them to see that they work
net use ...."
I'm trying now but could you explain further?
when I enter dir \\2003server\data returns "The network path was not found."
when I enter net view \\2003server returns:
W03 Server
Share name Type Used as Comment
shared folder Disk
shared folder Disk
NETLOGON Disk Logon server share
shared folder Disk
SYSVOL Disk Logon server share
shared folder Disk
The command completed successfully.
SysExpert
I'm not real sure what you mean:
"Map the drives in a batch file and test them to see that they work
net use ...."
I'm trying now but could you explain further?
There seems to be a problem with the publication of the shared drives.
What is the result when you enter "net share" on the server?
What is the result when you enter "net share" on the server?
ASKER
I mapped drives on both machines to try it either way (from the 2000 to the 2003 and vsv) - that didn't matter. The mapped drives however seem to have been the issue. Once mapped things are working. Robocopy must not like network drives??
The log switch isn't much help however because on a rather large job, of several thousand files, the job completes and indicates "41 files skipped", but it doesn't indicate which ones. I have looked at the options but find nothing to list details. How is one to go back and get the files that were skipped or failed? I'd hate to think I have to compare each folder file by file to find missing files...
The log switch isn't much help however because on a rather large job, of several thousand files, the job completes and indicates "41 files skipped", but it doesn't indicate which ones. I have looked at the options but find nothing to list details. How is one to go back and get the files that were skipped or failed? I'd hate to think I have to compare each folder file by file to find missing files...
ASKER
oBdA
I get a list of shares both folders and printers (listed by IP)
I get a list of shares both folders and printers (listed by IP)
ASKER
printers are listed by IP... not folders - sorry.
I did a "net share" on both servers and received the same result - all seems OK
I did a "net share" on both servers and received the same result - all seems OK
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Robocopy is working fine now - using the mapped drives.
I would still like to know why it didn't work with the network "shares" - perhaps a limitation of robocopy.
I also think the log file is useless because after copying serveral thousand files, it would be nice if the log showed not just that there were X number of files skipped but the files that were not processed. But not being a programmer, it's easier said than done...
I would still like to know why it didn't work with the network "shares" - perhaps a limitation of robocopy.
I also think the log file is useless because after copying serveral thousand files, it would be nice if the log showed not just that there were X number of files skipped but the files that were not processed. But not being a programmer, it's easier said than done...
ASKER
oBdA - thanks for the response, I will try and get right back to you (that aspect of this is bugging me and I appreciate possibly finding out why it didn't work with the UNC).
Glad at least the Robocopy is working OK with Drive mappings I suggested.
Which version are you using ?
Have you looked at XXcopy ?
I hope this helps !
Which version are you using ?
Have you looked at XXcopy ?
I hope this helps !
Files that were not processed because of errors are under "failed" in the summary. Skipped files are files that are already present in the target folder.
You can use /nfl and /ndl as arguments; /nfl is "no file listing", /ndl is "no directory listing", which means you won't have a log of thousands of copied files. Errors or extra files will be logged anyway.
You can use /nfl and /ndl as arguments; /nfl is "no file listing", /ndl is "no directory listing", which means you won't have a log of thousands of copied files. Errors or extra files will be logged anyway.
ASKER
SysExpert - I attempted the GUI v 3.1.2 early on but with the problems I went back to cmd. The cmd version is XP026.
I came across XXcopy and read a bit about it when I first started this project but went with robocopy because of all the positive posts on it. (All this command line stuff I have forgotten from my old DOS days...).
oBdA - I am still waiting for the system to get freed up to check the commands you suggested. The skipped files I sort of assumed, but its those "failed" files that have me worried. For example it just finished copying a major data folder (our staff individual data) and the result was 35 "failed" in the summary... but there is no indication WHICH files failed. So now I am researching a utility that will do a compare - I can't help but think you shouldn't need to do this with a log file...
I came across XXcopy and read a bit about it when I first started this project but went with robocopy because of all the positive posts on it. (All this command line stuff I have forgotten from my old DOS days...).
oBdA - I am still waiting for the system to get freed up to check the commands you suggested. The skipped files I sort of assumed, but its those "failed" files that have me worried. For example it just finished copying a major data folder (our staff individual data) and the result was 35 "failed" in the summary... but there is no indication WHICH files failed. So now I am researching a utility that will do a compare - I can't help but think you shouldn't need to do this with a log file...
Those are in the log file. Somewhere.
Open a command prompt, enter (replacing robocopy.log with the actual name of your log file)
type robocopy.log | find /i /v "new" >temp1.log
type temp1.log | find /i /v "extra" >temp2.log
type temp2.log | find /i /v "changed" >temp3.log
Open temp3.log, which should be somewhat stripped down now.
Open a command prompt, enter (replacing robocopy.log with the actual name of your log file)
type robocopy.log | find /i /v "new" >temp1.log
type temp1.log | find /i /v "extra" >temp2.log
type temp2.log | find /i /v "changed" >temp3.log
Open temp3.log, which should be somewhat stripped down now.
ASKER
have another massive folder being copied - will check as soon as it is free. I have my fingers crossed for no "failed"...
I am realizing now that the log in question was overwritten - I didn't use the LOG+ option on this last folder... I'll have to sort that out and get back to you.
I am realizing now that the log in question was overwritten - I didn't use the LOG+ option on this last folder... I'll have to sort that out and get back to you.
ASKER
These are the results - from each server as noted:
on the 2000 server searching for the 2003 server shares
dir \\server2003\data = "The network path was not found."
net view \\server2003 = "Shared resources at \\2003server" then lists shares
dir \\server2003\netlogon = "Volume in drive \\2003server\netlogon has no lable." then identifies the the volume serial number and directory and then lists all our scripts/commands
dir \\server2003\c$ = "Volume in drive..." just as above, lists contents of C
replaced X with the drive letter that I assigned to the iscsi drive)
dir \\server2003\D$ = "The network path was not found"
On the 2003 server searching for the 2000 server shares
dir \\server2000\data = "Volume in drive \\server2000\data is Data" then identifies Volume Serial Number and Directory of \\server2000\data and lists all folders in the data folder
net view \\server2000 = "Shared resources at \\server2000" then lists all shares, folders and printers
dir \\server2000\netlogon = "Volume in drive..." , indicates Volume Serial number and Directory and then lists our scripts/commands
dir \\server2000\c$ = "Volume in drive \\server2000\c$ has no label." then indicates Volume Serial Number and Directory, then lists contents of C
(replaced X with the drive letter assigned to the iscsi drive)NOTICE I CHANGED TO THE SERVER THAT IS HOSTING THE iSCSI - WHICH IS THE 2003 SERVER, THE SERVER I AM ENTERING THESE COMMANDS ON
dir \\server2003\D$ = "The network path was not found" same result as from 2000 server
This is really strange because I can look at all the shares from the 2000 server and see the "D" iSCCI share on the 2003 server but as you can see from above, it doesn't show up with the dir lists indicated???
I set the iSCSI drive up right - it is not "shared" on the actual device (SNAP Linux system) because the MS Initiator handles it on the host system (2003 server). It is marked as "shared". I must be overlooking something really simple or have done something with "D" that is somehow not recognized on the system - wait a minute this is stupid but I can't have two "D" shares on the network can I? They are both on different servers though - but could that be the problem? We have \\server2000\data(D) and \\server2003\data (D).
About the "Failed" files, I would have to recopy everything to get another log - I really messed up not thinking about a new file - it was overwritten. I may run it again (which may be less time than attempting a compare utility) and then try the "find" command you suggested.
on the 2000 server searching for the 2003 server shares
dir \\server2003\data = "The network path was not found."
net view \\server2003 = "Shared resources at \\2003server" then lists shares
dir \\server2003\netlogon = "Volume in drive \\2003server\netlogon has no lable." then identifies the the volume serial number and directory and then lists all our scripts/commands
dir \\server2003\c$ = "Volume in drive..." just as above, lists contents of C
replaced X with the drive letter that I assigned to the iscsi drive)
dir \\server2003\D$ = "The network path was not found"
On the 2003 server searching for the 2000 server shares
dir \\server2000\data = "Volume in drive \\server2000\data is Data" then identifies Volume Serial Number and Directory of \\server2000\data and lists all folders in the data folder
net view \\server2000 = "Shared resources at \\server2000" then lists all shares, folders and printers
dir \\server2000\netlogon = "Volume in drive..." , indicates Volume Serial number and Directory and then lists our scripts/commands
dir \\server2000\c$ = "Volume in drive \\server2000\c$ has no label." then indicates Volume Serial Number and Directory, then lists contents of C
(replaced X with the drive letter assigned to the iscsi drive)NOTICE I CHANGED TO THE SERVER THAT IS HOSTING THE iSCSI - WHICH IS THE 2003 SERVER, THE SERVER I AM ENTERING THESE COMMANDS ON
dir \\server2003\D$ = "The network path was not found" same result as from 2000 server
This is really strange because I can look at all the shares from the 2000 server and see the "D" iSCCI share on the 2003 server but as you can see from above, it doesn't show up with the dir lists indicated???
I set the iSCSI drive up right - it is not "shared" on the actual device (SNAP Linux system) because the MS Initiator handles it on the host system (2003 server). It is marked as "shared". I must be overlooking something really simple or have done something with "D" that is somehow not recognized on the system - wait a minute this is stupid but I can't have two "D" shares on the network can I? They are both on different servers though - but could that be the problem? We have \\server2000\data(D) and \\server2003\data (D).
About the "Failed" files, I would have to recopy everything to get another log - I really messed up not thinking about a new file - it was overwritten. I may run it again (which may be less time than attempting a compare utility) and then try the "find" command you suggested.
ASKER
Hope you find the point split fair. SysExpert provided the solution of mapped drives for getting files copied. oBdA provided input on trying to solve a deeper issue with copying files with robocopy - thanks for hanging in there (although I noticed that there was no reply to my answers to your questions... perhaps the holiday...do you have any other feedback?). In any case, I really appreciate the time you both took to help me out. Many thanks.
I currently have absolutely no idea why a drive can be mapped to this share, but the (basically identical) command to just list the directory using the UNC can't.
Anyway, you can have as many D$ (and C$) shares as you can eat, as long as they're on different servers; you actually have them already ...
Running the copy again might be the easiest solution; robocopy is smart enough to only copy files that have changed. Use /nfl and /ndl as suggested above, and the log should be rather easy to read.
Anyway, you can have as many D$ (and C$) shares as you can eat, as long as they're on different servers; you actually have them already ...
Running the copy again might be the easiest solution; robocopy is smart enough to only copy files that have changed. Use /nfl and /ndl as suggested above, and the log should be rather easy to read.
http://www.microsoft.com/technet/technetmag/code06.aspx