The most common way I have seen discussed is actually an 'upgrade in place on new hardware'
That meaning, to standup a new server, install the current version of Remedy onto it, restore the prod DB to it, and follow the recommend upgrade path to bring it to the latest version/patch that you are moving to, then do vigorous testing to ensure that everything is cool...then do a DDM of data from current prod over to 'new prod'....and release it back into the wild. On Wed, Apr 8, 2015 at 9:17 AM, Koyb P. Liabt <tekkyto...@aol.com> wrote: > ** Hi, > > Our company is upgrading from 7.0.3 ITSM/AR System 7.5 to 8.1.2. > > We are trying to figure out if we should do: > a) implement new 8.1.2 install on a separate server, and bring selected > customizations over (after we modify them via Dev Studio) OR > b)" upgrade in place" the AR System and ITSM to 8.1.2 > > Any ideas/thoughts? > > > > _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"
