Skip to main content
poduvalarun1-Visitor
1-Visitor
November 19, 2010
Question

Migration in two stage

Hi Experts,

I would like to know the issues/cons of doing a migration event in two stage. The plan is to

1. Ask users to check-in data to Intralink and delete their workspaces, clone Intralink and start migration. Open the production back for the users.

2. When migration is finished, ask the users to check-in their data again. Find the delta data between the clone and Production and manually migrate them ( open in Pro/E in Intralink workspace and save it to PDMLink workspace).

Please let me know your experience -level of difficulty/problems in manual migration etc. This is Intralink 3.4 to PDMLink 9.1M050 migration and we have nearly 300 users who will be using the production Intralink during migration.

Regards,

Arun

5 replies

Anonymous
November 19, 2010

I would also like to hear about doing this automatically.

For example, I would like to migrate a clone of our 3.4 data, which could take days.
During the migration, users would be allowed to continue using the production 3.4 system.

After the migration is complete, we would want to do a 2nd migration of the incrementally-added files created in the 3.4 system.
This would be a very small number of files compared to the initial migration.
We would assume that nothing else changed in 3.4.
This is: Nothing deleted, no new users or commonspace folders.
We might even be able to hold off of promotions during this period.

Can the migrator identify and migrate the incremental files only?
(which could be completely new, and/or new versions/revisions)

Translate
ptc-1458451-Visitor
1-Visitor
November 19, 2010
What I did, when I preformed a ProI 3.3 to Windchill 7 upgrade was this:


1. Had users check in ALL work and delete ALL ProI Workspaces
2. Made Production ProI 'Read Only'
3. Cloned Production ProI
4. Migrate off of Cloned ProI
5. Brought Windchill up.
6. Trained users on how to migrate their data from ProI Workspace to
Windchill Workspace and gave a 'Shutdown' date of 1 week out.
7. Helped users migrate their delta data.
8. Shutdown Production ProI

Hope this helps.


On Fri, Nov 19, 2010 at 1:59 PM, Gerry Champoux
<->wrote:

> I would also like to hear about doing this automatically.
>
> For example, I would like to migrate a clone of our 3.4 data, which could
> take days.
> During the migration, users would be allowed to continue using the
> production 3.4 system.
>
> After the migration is complete, we would want to do a 2nd migration of the
> incrementally-added files created in the 3.4 system.
> This would be a very small number of files compared to the initial
> migration.
> We would assume that nothing else changed in 3.4.
> This is: Nothing deleted, no new users or commonspace folders.
> We might even be able to hold off of promotions during this period.
>
> Can the migrator identify and migrate the incremental files only?
> (which could be completely new, and/or new versions/revisions)
>
Translate
poduvalarun1-VisitorAuthor
1-Visitor
November 22, 2010

Thanks, James

Any challenges you faced in migrating from ProI Workspace to PDMLink? And was that mandatory to keep Intralink read-only? What could be the downside of letting users use the Intralink for regular actions?

Regards,

Arun

Translate
SteveVinyard1-Visitor
1-Visitor
November 23, 2010
Clone your existing Production system and setup your new PDMLink system to migrate from the clone thus not touching your Production system during your rehearsal migrations. Once you've done the rehearsal 2-3 times and have your process completely dialed in, then take your Production system down. Clone it again, do the production migration and then after a day or so you should be up and running.

[cid:image001.gif@01CB8AEE.26492B10]

Steve Vinyard
Application Engineer
Translate
patrick.chin11-Visitor
1-Visitor
November 25, 2010

As soon as you said, open in a Pro/I workspace and perform a checkin to Windchill, this is not a migration of data. The windchill check-in process of Pro/E will either start by creating new objects starting at the initial revand iteration or just iterate the objects without new revisions.

What are the concerns of mirgrating in a single stage?

Allowing the Pro/I to be live (modifciation allowed) will be branching modifications and which system becomes the source? After a migration to PDMLink, all your data should be in PDMLink. Pro/I should be turned off.

Translate
Terms & ConditionsAccessibility statement