What file/database gets updated when adding new workareas and/or branches?

We have TeamSite/OpenDeploy running on a clustered environment (one hot node and one cold) so I have to keep them in sync by deploying configuration files from the hot node to the cold node. I am trying to discover what I need to keep in sync for workarea and branch additions/deletions/modifications.

Is there a file that I can deploy to my hot node that is written to when adding/deleting/editing workareas and branches?

Thanks.

Find more posts tagged with

Comments

nipper

I do not think there is anything outside the backingstore. Since I have copied one backingstore to other machines and never had an issue with missing branches, I would think you are in the clear.

Andy

SethHickel

Ah - cool - so since we "share" one backing store between the nodes when I bring up the cold node my workareas are there? Correct?

thanks - as usual!!

nipper

Ah - cool - so since we "share" one backing store between the nodes when I bring up the cold node my workareas are there? Correct?

thanks - as usual!!

Yep. And you got the failover to work for two different servers ? When I did that on 7.2.1 it was a serious pain because of the common services DB.

That took a while to figure out.

Andy

SethHickel

We have DB as part of the cluster management. Our fail-over is only partially automated. Cluster ownership changes automatically but we have services set to manual so that we can check for store corruption before we crank up the services.