We have a desire to create a new Teamcenter environment, which we would call SUPPORT. It would be a full clone of our production environment (config, data model, volume data, etc) with regular (weekly?) refreshes to keep it in sync with PROD. It would be used by our engineering users to develop new NX automations and processes without polluting data. The SUPPORT environment would not need to be architecturally identical to PROD, but should be identical from a configuration and content perspective.
We are on TC 10.1 running on .NET and MS SQL.
Is anyone doing this now, and would you willing to share your recommendations with me?
Thanks Randy. We do indeed have a DEV -> TEST -> UAT -> PROD environment chain in our Teamcenter development lifecycle. UAT is end-user acceptance testing and is architecturally identical to PROD.
What we are really wanting is a SUPPORT environment, that comes after PROD in the above chain. it's just like prod, updated ... daily? weekly? ... that can be used to diagnose production issues with production data, and also to allow the business to 'experiment' with their own data, and we don't want them in our DEV/TEST/UAT environments because they are NOT configured like PROD (that's where we are updating the data model, creating new workflows, etc).
So not only do I want to clone an environment, at least far as configuration goes, but also update the content. Clearly, jiggering around the volume stuff would be a part of that. Our PROD environment has three remote volumes overseas and I'm not sure we want to duplicate that in SUPPORT (although we did in UAT).
Do a backup & Recovery Process
Command for changing site id
UPDATE POM_BOOT SET site = old site id
Remember to also update this site ID in fsc master wherever this is used as import site.
Check transient volume entry in fmsmaster file.
<fsc id="FSC_cinsun4_v10002a1" address="http://cinsun4:44021">
<transientvolume id="f4986a4ab9b155d11da1afceb35f55ac" root="/m/v10002/transientVolume_v10002a" />
Default transient vol ID & tran vol ID should be same and update same in fms master from backupinfo.
While changing value be careful to press modify twice in value fiels and for preference itself.