I like Jiri's approach... Sometimes the devil is in the details. Even well planned out approaches usually result in more time and effort that originally imagined.
Upgrades that involve major jumps between versions can become uncontrollable. Maybe back in the day when the ITSM deployments were less complex this sort of thing could be done seamlessly, but now if you don't keep pace - "cut over" is a good option to explore. Last time I did a major upgrade like this - I aged 10 years in 6 months. Good Luck Bud! On Wednesday, November 21, 2012 5:02:36 AM UTC-5, Jiri Pospisil wrote: > > Hi, > > After being through upgrade from 7.0.1 to 7.6.03, I would strongly > recommend considering a different strategy. > Rather than spending tons of time making the upgrade scripts work, I would > recommend building a fresh version 8 environment, recreate your > customisations and then invest time in defining procedure for data > migration. > With the data management tool, this should not be that difficult. > You may also consider other tools such as rrrchive to migrate the data. > > Other option might be trying to convince your stakeholders to leave > historical data in the old system and start fresh in the new environment > with the old data remaining available for reporting/viewing. > > Hope this helps. > > Jiri Pospisil > Remedy Specialist, IT Production > LCH Clearnet > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > ars...@arslist.org <javascript:>] On Behalf Of Mary C. > Sent: 21 November 2012 02:05 > To: ars...@arslist.org <javascript:> > Subject: AR System & ITSM Upgrades (we are WAY behind) > > Hi, > > We are on AR System 7.0.01 Patch 006, CMDB 2.0.1, ITSM 7.0.3 Patch 006 and > SLM 7.0.1 Patch 4. We were unable to consider upgrading until now, and of > course this is going to be a major effort from what I can see. We have > some customizations, but I think I could rebuild them from scratch if I had > to. We are in a Windows/SQL server setup and are running a server group. > We want to upgrade everything to 8.0 > > Here is a high-level upgrade path that Support recommended. > A) Upgrade ITSM 7.0.3 patch 6 to ITSM 7.0.3 patch 9. > B) Run ARserver 7.6.04 patch 4 in upgrade mode. > C) Run the difference report to find the customization. > D) Create Overlay to retain customization. > E) Then upgrade CMDB 7.6.04 patch 4 > F) Then upgrade ITSM 7.6.04 patch 4. > G) Once everything is working fine upgrade ARS, CMDB and ITSM to 8.0 > > Do you all agree with this upgrade path? Would you recommend another > approach? > Any advice you can give me would be appreciated. Many of you have listed > lots of gotchas, so I am semi-planning for those pitfalls. > > Thank! > > _______________________________________________________________________________ > > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > > > A copy of the LCH.Clearnet e-mail disclaimer can be found at: > www.lchclearnet.com/disclaimer/email > > LCH.Clearnet Limited, Registered Office: Aldgate House, 33 Aldgate High > Street, London EC3N 1EA. > Recognised as a Clearing House under the Financial Services & Markets Act > 2000. Reg in England No.25932. > LCH.Clearnet SA, Siège Social, 18 rue du Quatre Septembre, 75002 Paris, > Chambre de Compensation conformément au Code Monétaire et Financier. > > _______________________________________________________________________________ > > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
