Dobe
Mechanical
- Oct 1, 2003
- 51
We are currently replacing a server, and have some questions regarding copying of existing Solid Edge files from the old server. We tried this before and lost several files.
Conversation between Engineers and IT:
Is it possible to just name the new drive NTFS 2? (this would ensure there is not file path issue at all)
I don’t see why not.
Suggestion… if IT wishes to retain use of the old drive, maybe re-name it NTFS4.
While I am not sure if it would ignore the designation for NTFS 4 or not, I know that if it does not ignore it trouble abounds.
It would take over a year to re-connect files, if it could be done at all.
There are occasions where a single part file is used in 70+ separate assemblies.
Each assembly would need to be opened and the link re-established.
Problem with that is how do we know what assemblies it is used in if the links are broken?
There is no way to be efficient about this.
We have many assemblies that are missing standard parts due to incorrect database transfers.
These assemblies require that an engineer re-connect the missing hardware, which may take over an hour.
These are easy when compared to the possible issue above since we know where the missing hardware now exists (working folder).
Solid Edge files are very delicate, and we should plan to store them on a drive that will not require frequent replacement due to storage capacity concerns.
Conversation between Engineers and IT:
Is it possible to just name the new drive NTFS 2? (this would ensure there is not file path issue at all)
I don’t see why not.
Suggestion… if IT wishes to retain use of the old drive, maybe re-name it NTFS4.
While I am not sure if it would ignore the designation for NTFS 4 or not, I know that if it does not ignore it trouble abounds.
It would take over a year to re-connect files, if it could be done at all.
There are occasions where a single part file is used in 70+ separate assemblies.
Each assembly would need to be opened and the link re-established.
Problem with that is how do we know what assemblies it is used in if the links are broken?
There is no way to be efficient about this.
We have many assemblies that are missing standard parts due to incorrect database transfers.
These assemblies require that an engineer re-connect the missing hardware, which may take over an hour.
These are easy when compared to the possible issue above since we know where the missing hardware now exists (working folder).
Solid Edge files are very delicate, and we should plan to store them on a drive that will not require frequent replacement due to storage capacity concerns.