setting up a QuickBuild Mirror Server for Disaster Recovery #2177

qbuser · 1 decade ago

We are setting up a mirror of our QuickBuild 4 Server for disaster recovery. Our mirror server will use a database that is refreshed nightly from our production QuickBuild server. Since the database is identical to the production server, there are some changes that we need to make immediately when bringing up our mirror server for testing.

For example, we will need to:

1) remove all schedule tags from the mirror QB configurations, so that production builds are not triggered on the mirror host.

2) change the value of our 'projectBuildAgent' variable to point to the mirror build host address.

We plan to make these and other changes through a script that interacts with the configurations using the RESTful API. Since we will need to start up the mirror server in order to run the RESTful API commands, there is a small risk that a few builds might be triggered before our script finishes removing the schedule tags. As long as we delete the schedule tags before we modify the projectBuildAgent value, any triggered builds will fail, so this should not present a problem. Still, it is not a perfect solution, and we wondered if anyone had a better idea.

We would be interested in hearing about solutions that other users have implemented in setting up DR mirrors of their QuickBuild servers. Any tips you may have related to QuickBuild mirroring will be appreciated.

Many thanks!
-- Joanne

replies 2
views 1556
stars 0

robinshen ADMIN · 1 decade ago

The most recent 5.0.8 version has a new system setting "pause system" to prevent all builds from running, and a RESTful call can be issued to set this flag. Refer to below link for details:
http://wiki.pmease.com/display/QB50/Pause+System

Jonathan · 1 decade ago

We too are currently setting up a remote QuickBuild server for DR purposes.

So far our approach has been to simply sync the configuration from the main server to the DR server on an hourly basis. Using the in built sync configurations task.

We use an Ivy repository to hold the artefacts of our builds, this is also synced to a mirrored repository for DR reasons. The DR build machines publishy their artefacts locally which prevents them from poluting the main repository.

However I have a question regarding the syncing of Subversion repository passwords from the source to the destination server. At present this does not appear to be working (using QB 3.1.62) and they have to be set manually. Is this fixed in a more recent build of QuickBuild or is there another solution?

viewtopic.php?f=1&t=2473