![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: down migration miltiple ccm databases into one instance Topic Summary: WANTED: information, experiences, hints and background information Created On: 14-Nov-2005 12:39 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello,
We are running CMSynergy 6.3 (SP4) and ChangeSynergy 4.3 (SP4) on a single site Solaris Server. Currently we have 36 instances (CMSynergy databases) of different sizes (from 3.5 Mb up to 4.5 Gb backup size) on a single informix database server. Some instances are used only for change management whereas other instances are used for config.- and change management. Up to now the instances are managed in a system context - that means one system per instance - or they are managing several (small) systems in one (bigger) instance e.g. one specific instance is managing changes for about 18 systems (change mgmt only) - the Change Requests system membership is identified by an attribute "product_name". Now we have to establish a project view for change management, where we have to manage changes for several systems according to a defined release scenario. Typically we have two or three releases a year with a changing set of systems, that are affected by that release and therefore have to be managed by the change management by a spanning ChangeSynergy Web Fronend. The use of ChangeSynergy for such an overall Change Management is a major drawback due to the system view of CS. A year ago we had issued an offering request for set up of Enterprise Change Synergy (ECS). ECS would have been afforded to set up Distributed ChangeSynergy and DCM. Our Managers had not been willing to afford that. Now they have an idea of going the other direction - the integration of all instances (all systems) into one huge instance with one single Change Management view in ChangeSynergy. For this case scenario I have the following questions: - multi-client capabilities ? May be we need some security restrictions: we have to restrict access and visibility of Changes in one Instance with several systems (clients). This restrictions should be on the level of systems (clients), users and roles representing the visibility and change rights of a user with a certain role for a special system. "Read Security Values" in ChangeSynergy doesn't make it because, as far as I understand, it is restricted to a many to one level (a user can only have one read sec. value concerning one system and not more ...). "Group Security" in CM Synergy is a means to control changes to objects but does not restrict visibility ? Are there other possibilities, solutions to achieve certain security restrictions (like special branch security "tricks" in ChangeSynergy) ? - feasability ? Generally speaking is it possible to rearrange / migrate several instances to a single one conserving the histories (sources, projects, CRs) of the instances ? How would you rate the costs and efforts of such a migration ? - impact on the tool performance ? with several instances, the performance (reconfigure, CR query ) is somehow scaling up the instances size (database or filesystem) ? If we consolidate to one instance, can we give a statement about the expected or required performance ? - backup performance ? we use CMSynergy admin backup (ccmdb pack ...) for all instances once a day. On our 8 CPU Solaris Server we have an overall backup duration of 511 minutes parallelized to 150 min. which is feasible to be executed once every night. Is it possible to use an other backup strategy to boost up the backup for a huge single instance ? - other boundary conditions ? thank you for any response, Jörg Aldinger |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.