The upgrade was successful by moving the database off the cluster onto a dedicated server, performing the upgrade, and then moving it back to the cluster.
On Mon, Jul 29, 2013 at 1:47 PM, Robertson, Casey <[email protected] > wrote: > Just curious what ever came of this…**** > > ** ** > > Semi-related… is there a good fool-proof procedure for creating a lab > environment from you current production system? My 3 servers (management, > dw management server and portal) are all VMs. SQL is remote. **** > > ** ** > > I’m being asked to test/try some things esp. with runbooks that I don’t > want to run in production. But it would be VERY nice to have it set up > like my current prod environment.**** > > ** ** > > Thanks,**** > > Casey**** > > ** ** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Travis Wright > *Sent:* Wednesday, May 1, 2013 12:02 PM > > *To:* [email protected] > *Subject:* RE: [servman] SCSM Upgrade in Lab then Move to PRD**** > > ** ** > > I’ve heard that we have our best escalation engineer assigned to the case > now. Let me know if you don’t start getting traction in the next couple of > days.**** > > ** ** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Hemsell, Todd > *Sent:* Wednesday, May 1, 2013 12:53 PM > *To:* [email protected] > *Subject:* RE: [servman] SCSM Upgrade in Lab then Move to PRD**** > > ** ** > > case has been open for months now. We already have demos scheduled with > ServiceNOW :-(**** > > **** > > They are going to drop the entire system center suite pretty soon.**** > > **** > ------------------------------ > > *From:* [email protected] [[email protected]] > On Behalf Of Marcum, John [[email protected]] > *Sent:* Tuesday, April 30, 2013 6:56 PM > *To:* [email protected] > *Subject:* RE: [servman] SCSM Upgrade in Lab then Move to PRD**** > > I’m not a SM guy but I’d be very surprised if that’s even close to being > supported. Will it work? Maybe so but MS only supports tested scenarios and > I doubt they tested that. **** > > **** > > Why not just call MS And make them fix the issue in the PRD upgrade?**** > > **** > > **** > > **** > > **** > > **** > > **** > > **** > > **** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Brody Kilpatrick > *Sent:* Tuesday, April 30, 2013 10:02 AM > *To:* [email protected] > *Subject:* Re: [servman] SCSM Upgrade in Lab then Move to PRD**** > > **** > > During the upgrade, it fails while making a modification to a stored > procedure. A SQL trace shows the stored procedure running, but the stored > procedure times out. From my understanding, in that particular stored > procedure inside the upgrade, there is a hard time out. In terms of SQL > Server configuration query and timeout connections are all set to > unlimited. It consistently fails on the same procedure each time, and > always with a time out error as shown in the trace. **** > > **** > > **** > > On Tue, Apr 30, 2013 at 9:52 AM, Travis Wright < > [email protected]> wrote:**** > > What is the issue that is happening with upgrade? Why would > snapshotting it to test and back help solve that problem?**** > > **** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Brody Kilpatrick > *Sent:* Tuesday, April 30, 2013 7:24 AM > *To:* [email protected] > *Subject:* [servman] SCSM Upgrade in Lab then Move to PRD**** > > **** > > I have a client that has a production SCSM 2012 installation. We are > having trouble upgrading to SP1 in production, and have very limited > windows/chances to upgrade. I want to throw the below question out to see > if Microsoft will support this approach to the upgrade. I believe it is our > only option. Otherwise, the client is looking to remove SCSM from their > environment and replace it with another solution.**** > > **** > > Wi Will Microsoft Support the following upgrade method:**** > > a. Take a snapshot of the SCSM Production Environment**** > > b. Enter the Environment into a LAB**** > > c. Upgrade SCSM to SP1 and the latest CU**** > > d. Verify the Upgrade is successful**** > > e. Migrate the Lab installation into Production via Snapshot and > Database Restore**** > > **** > > -- **** > > Thank you, > Brody Kilpatrick**** > > **** > > > > **** > > **** > > -- **** > > Thank you, > Brody Kilpatrick**** > > **** > > **** > ------------------------------ > > > Confidentiality Notice: This e-mail is from a law firm and may be > protected by the attorney-client or work product privileges. If you have > received this message in error, please notify the sender by replying to > this e-mail and then delete it from your computer.**** > > ** ** > ------------------------------ > > > Confidentiality Notice: This e-mail is from a law firm and may be > protected by the attorney-client or work product privileges. If you have > received this message in error, please notify the sender by replying to > this e-mail and then delete it from your computer.**** > -- Thank you, Brody Kilpatrick
