cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Suggestions on speedy cloning of a large Intralink 3.4 server

Highlighted
Newbie

Suggestions on speedy cloning of a large Intralink 3.4 server

Hi,
Starting some early prep work for the big Migration to Windchill. I need
to clone our 3.4 server which is kinda large. We have aroudn 250,000
files in the vault and using windows to transfer them is very very slow.
What suggestions do you have to make a clone of an intralink 3.4 server
and suggestions to speed up the process?

Thanks!

Andrew Amsden
CAD\PDM Administrator
Midmark Corporation
937-526-8770

4 REPLIES 4
Highlighted

RE: Suggestions on speedy cloning of a large Intralink 3.4 server

I can't help you speed copying the data across the network once, but I would suggest youplace the Intralink Clone Vault on the same volume asit will eventually reside for PDMLink. The migrator can then do an in-place 'move' of the vault data which is much faster than copying it a second time. You do not need 2X thedisk on this volume as the data is basically just reassigned from Intralink to PDMLink. It is easy to reassign the vault locations within Intralink 3.x, just a couple of sqlplus alter commands.
Highlighted

Suggestions on speedy cloning of a large Intralink 3.4 server

Use robocopy to mirror the vault.

Set all your current Pro/INTRALINK vaults read-only, create one new file vault and use this one for all the folders. Then you know you only need to copy/mirror your new filevault when it is the big day. Since the other vaults were made read-only, no data will be created in them.

Best regards

Tony
Highlighted

Suggestions on speedy cloning of a large Intralink 3.4 server

Depending on your hardware, we saw efficiencies with respect to vaults
with PDMLink. You might be able to draw a parallel. When you clone, the
database and data in the vaults should be identical. After cloning, they
can vary. Anything new in the test server would not be in the production
vault. We create a read-only mount to the production vault folders.
This is so the test server can read but not write to the vault folder.
In the test server after cloning, we mark the mounted folder in PDMLink
as read-only and create a new, empty folder for each vault that it can
write to. If it needs to access anything from what was cloned in
Production, it goes into the read-only folder. Anything new is from the
new vault folders.



Again, not an Intralink expert but maybe this could be translated to the
Intralink fileserver interface.


Highlighted

Suggestions on speedy cloning of a large Intralink 3.4 server

Hi Andrew, and the others who already replied.

Very interesting thread for sure.
We are in the same process with multiple intralink sites being migrated into one central PDMLink.

I have one suggestion though that we are putting in place and explaining to our customer: in case you could suggest to purge the clone Intralink 3.4 by keeping for example just the last iteration of all. Extract the files required then by SQL, and copy only the required on the PDMLink partition for the Pre-Copy usage with the Migrator.
We are also removing the Documents non CAD and we are doing a migration of only CAD Documents. Working at the metdata level might help solving space issues.
The history can be retreive one day if needed from the Legacy Intralink server. Only if the history is required.

Christophe




Announcements