Versioning RTC SCM configuration itself...

Hi all,

From what I have been able to determine, RTC backups are performed via a DB2 backup, either as a full backup, or as incremental backups. However, I am wondering specifically about RTC configuration, as it pertains to the SCM component.

Is it possible to version the SCM configuration itself? Consider, for example, user credential information, or system event hooks that are set to execute after a particular action is performed, or even build definitions. If these types of configurations undergo regular revision it is entirely possible that a working config/hook/etc may become nonfunctional; in this case it would be highly desirable to be able to revert to a previous revision.

I have not yet encountered evidence that the configuration data can be versioned in this way, and am hoping someone out there can perhaps enlighten me of a way to do so with RTC-SCM that does NOT involve a database restore of a previous backup operation.

Thanks,

Tom

Hi Tom

Most of the information in RTC is held directly in the repository (ie in the database) - not much is held externally. However, there is information held externally, and this includes some basic config info, and then any server-side plugins you may have created.

There is a useful article on backup considerations here:

http://jazz.net/library/article/547

that may help. It does cover the DB backup bits, but also talks about other considerations.

anthony

Hi Tom

Most of the information in RTC is held directly in the repository (ie in the database) - not much is held externally. However, there is information held externally, and this includes some basic config info, and then any server-side plugins you may have created.

There is a useful article on backup considerations here:

http://jazz.net/library/article/547

that may help. It does cover the DB backup bits, but also talks about other considerations.

anthony