Where the DB resides will make an impact. I encountered extensive upgrade delays (ie 24+hrs) when running the installers for a CMDB 1.0-2.01 upgrade in parallel within a desktop virtual environment which hosted both the DB and AR services.
Perfmon confirmed it was disk IO of the SQL process which was leading to the extended upgrade time. CMDB upgrades are understandably quite harsh on DB system resources and was quite evident in such an environment. This was a development effort with an empty DB, so I have little to share on suggested VM specs for a populated CMDB. On Aug 6, 11:38 am, Brian Baker <[EMAIL PROTECTED]> wrote: > Hello All, > > I am planning for a CMDB upgrade from 1.1 to 2.0.1 in a virtual environment. > I was wondering if anyone has done this and if there are any issues/gotchas > that I need to know about. Specifically, I need to know what kind of virtual > server performance is required for a successful upgrade. We have about > 150,000 CI's at the current time. > > Regards, > Brian > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > Platinum Sponsor:www.rmsportal.comARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
