Set up a clean (new) db as part of the installation of ARS 9. All the defs and data will be copied through tools using the ARS api (dev studio for defs, rrrchive for data).
The new and old server names should NOT be the same. Typically, the official production server name should be a DNS alias that is changed to point to the current prod server. For example: ‘RemProd’ is a dns alias that points to ‘oldserver’ until the cut-over; at which point, the alias is modified to point to ‘newserver’. This approach will also support DR fall-over: change the alias record to point to the hot back-up until the prod is fixed. By copying form old to new, you’ll have the added benefit of discarding any ‘bad data’ that may have developed in the old server. If, say, a selection menu has had a value removed, or a field property has been changed, but the old values still reside in a record. The data import will reject the invalid values, allowing you to examine the record and choose to either skip it of fix it on the new server. I had a client with so many bad records (100% custom app) that it was causing crashes. After the upgrade and clean-up, all was well. HTH, Joel. Joel Sender jdsen...@earthlink.net 310.829.5552 From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Su Kaur Sent: Wednesday, January 20, 2016 7:53 PM To: arslist@ARSLIST.ORG Subject: Re: Upgrade from 7.6 to 9 ** Yes, we are planning to set up a new 9.x environment. We did setup a test server by first copying the data to new database server and then doing an upgrade. But it didn't copy the customizations and we had to manually do all the changes. Not sure if this was the right approach. When you say stand up a new 9.x environment does that means doing a fresh installation and then copy the def files? How to setup the database server prior to installation? We also want the name of the server to be the same as current prod. For this, during the installation should we bring down the current prod and do the installation on a fresh box? -Kaur On Fri, Jan 15, 2016 at 5:21 PM, Joel Sender <jdsen...@earthlink.net> wrote: It sounds like your best bet is to stand up the new 9.x environment and copy the definitions and data: 1. Use the developers' studio to copy your definitions 2. Use rrrchive ( https://www.rrr.se/cgi/index?pg=chive ) to copy the data. Rrrchive lets you update records from the source to target. The first copy will take a long time, but each night's update will happen quickly. The rrrchive CFG file lets you control the Form Data copied. You can also run rrrchive in multiple CMD windows to take advantage of multiple ARS (fast) threads. With proper planning, the go live cut-over can be completed in less than an hour (your mileage may vary) 3. The APPLICATION should be frozen once you copy the definitions to new server. If the freeze NEEDS to be violated, "Emergency updates" would need to be applied to the new server as well. HTH, Joel Joel Sender jdsen...@earthlink.net 310.829.5552 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Su Kaur Sent: Friday, January 15, 2016 8:23 AM To: arslist@ARSLIST.ORG Subject: Re: Upgrade from 7.6 to 9 No, we are not using overlays. Everything is in base development mode. Upgrade would be on Windows system. How about the data/tickets that are modified during the upgrade? How can we copy that change to new prod? Thanks! Kaur _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
