We are having a devil of a time with getting our Solidworks(SW) "vault" off our Domain Server so we can clean it down in orderto rebuild it.
Our vault is approximately 45 gigs and we are trying to move it offof our Windows 2003 Domain Controller to a high powered XP SP3 boxusing the same Network that we have used for at least 5-10 years.The two machines are connected on the same subnet and all of thethree components are rated at 1000 mb (i.e. the Server NetworkCard, the XP Network Card and the gig switch connected directly tothe two machines in an adjacent room).
What we are finding is that certain SW parts that can be opened onthe Vault located on the Windows 2003 Server open as they alwayshave for the past 4 years. However after getting the vault moved tothe XP box, we find that some parts open fine, other SW indicates a"file error".
At first we thought the problem was with SW because we stumbledupon one assembly that consistently gave us trouble when we went toopen it within SW. We finally got SW to assist us through a web exsession. After a bunch of research, they determined with a filecomparison utility that even though the two vault files were thesame physical size, using a byte comparison program they providedshowed the two files were not the same. Windows did not provide anyerror messages that there was a problem with the copy of the vault.
A general search (not specific to SW) on the internet seems toindicate people do have issues some times when moving large filesacross a network. We also found instances where people have had thesimilar issues in general when trying to eliminate the network byusing say a USB drive as the transport mechanism.
Unfortunately this is all "news" to us.
In trying to come up with a solution that not only works but alsoprovides "confidence" that the vault is pure, do you think any ofthese approaches are valid in our attempt to move a 45 gig filefrom one machine to the other:
* Use FTP in command line mode instead of the standard WindowsCopy Command across the network.
* Use FTP in windows mode instead of the standard Windows CopyCommand across the network.
* Use Windows Backup to save the file across the network to thenew machine and then restore using Windows backup on the newmachine.
* Use Acronis Disk Imaging software to save an image across thenetwork using Acronis Server and then restore the image usingAcronis Workstation.
* Use a Tape backup product on the Server and then restore on theXP Box.
What we don't know is if the Windows backup and/or the Tape backupinterfaces are using the same techniques as a Windows "copy" ornot.
If none of these approaches are sound, are there any approachesthat "work".SolidworksWorkgroup Pdm
Our vault is approximately 45 gigs and we are trying to move it offof our Windows 2003 Domain Controller to a high powered XP SP3 boxusing the same Network that we have used for at least 5-10 years.The two machines are connected on the same subnet and all of thethree components are rated at 1000 mb (i.e. the Server NetworkCard, the XP Network Card and the gig switch connected directly tothe two machines in an adjacent room).
What we are finding is that certain SW parts that can be opened onthe Vault located on the Windows 2003 Server open as they alwayshave for the past 4 years. However after getting the vault moved tothe XP box, we find that some parts open fine, other SW indicates a"file error".
At first we thought the problem was with SW because we stumbledupon one assembly that consistently gave us trouble when we went toopen it within SW. We finally got SW to assist us through a web exsession. After a bunch of research, they determined with a filecomparison utility that even though the two vault files were thesame physical size, using a byte comparison program they providedshowed the two files were not the same. Windows did not provide anyerror messages that there was a problem with the copy of the vault.
A general search (not specific to SW) on the internet seems toindicate people do have issues some times when moving large filesacross a network. We also found instances where people have had thesimilar issues in general when trying to eliminate the network byusing say a USB drive as the transport mechanism.
Unfortunately this is all "news" to us.
In trying to come up with a solution that not only works but alsoprovides "confidence" that the vault is pure, do you think any ofthese approaches are valid in our attempt to move a 45 gig filefrom one machine to the other:
* Use FTP in command line mode instead of the standard WindowsCopy Command across the network.
* Use FTP in windows mode instead of the standard Windows CopyCommand across the network.
* Use Windows Backup to save the file across the network to thenew machine and then restore using Windows backup on the newmachine.
* Use Acronis Disk Imaging software to save an image across thenetwork using Acronis Server and then restore the image usingAcronis Workstation.
* Use a Tape backup product on the Server and then restore on theXP Box.
What we don't know is if the Windows backup and/or the Tape backupinterfaces are using the same techniques as a Windows "copy" ornot.
If none of these approaches are sound, are there any approachesthat "work".SolidworksWorkgroup Pdm
