RTC repository splited in more than one database
Is it possible to have the RTC repository splitted in more than one database in the same Jazz Team server?
Is there a plan to provide this capability in future RTC versions (v3.0 or higher)?
My customer wants to migrate from CCase&CQuest to RTC. They have 400 CCase VOBs (160 GBs) aprox. They would like to split the database, mainly for making easier the backup&recovery procedures, apart from performance reasons.
Thanks in advance.
Is there a plan to provide this capability in future RTC versions (v3.0 or higher)?
My customer wants to migrate from CCase&CQuest to RTC. They have 400 CCase VOBs (160 GBs) aprox. They would like to split the database, mainly for making easier the backup&recovery procedures, apart from performance reasons.
Thanks in advance.
3 answers
Is it possible to have the RTC repository splitted in more than one database in the same Jazz Team server?
Is there a plan to provide this capability in future RTC versions (v3.0 or higher)?
My customer wants to migrate from CCase&CQuest to RTC. They have 400 CCase VOBs (160 GBs) aprox. They would like to split the database, mainly for making easier the backup&recovery procedures, apart from performance reasons.
Thanks in advance.
The RTC repository needs to live on a single database instance, and I don't believe there are any plans to change this. However, you can have multiple RTC repositories, perhaps putting related VOBs on one RTC repository. Also - I suspect then don't really need all 160GB of data transferred across, and once the VOBs are cleaned out - it will be much easier to move data across.
anthony
How can you define more than one repository for RTC? Does it mean creating more than one application server instance in the WAS, that is , one per repository?
Thanks again.
The RTC repository needs to live on a single database instance, and I don't believe there are any plans to change this. However, you can have multiple RTC repositories, perhaps putting related VOBs on one RTC repository. Also - I suspect then don't really need all 160GB of data transferred across, and once the VOBs are cleaned out - it will be much easier to move data across.
anthony
Thanks again.
Is it possible to have the RTC repository splitted in more than one database in the same Jazz Team server?
Is there a plan to provide this capability in future RTC versions (v3.0 or higher)?
My customer wants to migrate from CCase&CQuest to RTC. They have 400 CCase VOBs (160 GBs) aprox. They would like to split the database, mainly for making easier the backup&recovery procedures, apart from performance reasons.
Thanks in advance.
The RTC repository needs to live on a single database instance, and I don't believe there are any plans to change this. However, you can have multiple RTC repositories, perhaps putting related VOBs on one RTC repository. Also - I suspect then don't really need all 160GB of data transferred across, and once the VOBs are cleaned out - it will be much easier to move data across.
anthony
That is correct. Either a new app server within a WAS deployment (new app server is required due to needed configuration customizations ) or a new Tomcat process serving the respository.
The RTC repository needs to live on a single database instance, and I don't believe there are any plans to change this. However, you can have multiple RTC repositories, perhaps putting related VOBs on one RTC repository. Also - I suspect then don't really need all 160GB of data transferred across, and once the VOBs are cleaned out - it will be much easier to move data across.
anthony
How can you define more than one repository for RTC? Does it mean creating more than one application server instance in the WAS, that is , one per repository?
Thanks again.
Is it possible to have the RTC repository splitted in more than one database in the same Jazz Team server?
Is there a plan to provide this capability in future RTC versions (v3.0 or higher)?
My customer wants to migrate from CCase&CQuest to RTC. They have 400 CCase VOBs (160 GBs) aprox. They would like to split the database, mainly for making easier the backup&recovery procedures, apart from performance reasons.
Thanks in advance.
The RTC repository needs to live on a single database instance, and I don't believe there are any plans to change this. However, you can have multiple RTC repositories, perhaps putting related VOBs on one RTC repository. Also - I suspect then don't really need all 160GB of data transferred across, and once the VOBs are cleaned out - it will be much easier to move data across.
anthony