Well, we don't replicate the ar.cfg file.... I never had to do that for this purpose.
The ar.cfg file is the file where the environment specif information is stored, as you know, including the directory structure. So I would leave this file untouched. The only thing that may need to be updated is the SQL server database if it different than production (not the database server), and the DB password Guillaume ________________________________ From: Action Request System discussion list(ARSList) [arsl...@arslist.org] on behalf of Joe DeSouza [joe_rem...@yahoo.com] Sent: Thursday, July 15, 2010 11:44 AM To: arslist@ARSLIST.ORG Subject: Re: SQL Database Replication ** Elry, One of the reasons answers differ and vary is the configuration. All depends on what applications you are using. Does the application have configuration data that hard codes server names like AIE would in its configuration. Some applications store some environment specific information like LDAP server names and login credentials. Then there are odd cases where under certain conditions you get server names or IP Addresses of the server hardcoded into workflow such as table fields. Sometimes you need to consider looking up the meta data and make sure you do not have hard coded server name references in workflow. So for the most part, yes a simple backup and restore of the database works directly unless you need to tweak some of the application or configuration data and meta data to remove hard coded or wrong server references. Also if you choose to replicate the ar.cfg file, make sure you point that file to the right database server, or you might end up having a test server point to production... Joe ________________________________ From: Elry <elryal...@gmail.com> To: arslist@ARSLIST.ORG Sent: Thu, July 15, 2010 8:46:57 AM Subject: SQL Database Replication Hi Folks... I am going to ask this question again - because I have never seen a definitive answer. Here is what we have: 1) Independent SQL Database Tier (2005). 2) ARSystem Application Tier (7.5 Patch 2). 3) Mid-tier (7.5 Patch 2). Environments: 1) Sandbox 2) Development 3) Staging 4) Production 5) Reporting/Archiving (to be deployed). What we need to do is the following: 1) Update the Staging and Development environments with data from production 2) Replicate the Production database to our new Reporting/Archiving environment. Options being considered: A) Database Replication. B) BMC Remedy Migrator. C) DSO. We understand and know how to use options B) and C). We are looking for feedback from anyone who is successfully using option A). Specifically... 1) What type of replication. 2) Are there configuration paramaters that are retained at the database level that need to be changed. 3) Are there any considerations for ar.cfg. I have never seen a white paper on database replication ( I understand that this method is unsupported). Any feedback would be greatly appreciated. _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
