We are going to create a server group for our production environment including 2 servers. Currently our users connect via the server remedy.domain.com, if we create our server group as remedy, with they still be able to use remedy.domain.com or do that have to modify it? And just as a sanity check, I want to see if we are good on our steps for this migration. I've spoken with BearingPoint a few times on this...as well as BMC, but something doesn't feel right:
Are we forgetting anything on our move to a server group? Here are the steps: 1) backup remedy database 2) stop remedy services on primary application server blnmt001svrmd 3) startup remedy service on secondary application server 4) patch secondary server to match primary server 5) shutdown secondary application server 6) copy all change management/approval and flashboard directories to secondary server 7) startup remedy services on both primary and secondary services 8) create server group in remedy admin tool and add both servers 9) apply server group licenses in admin tool 10) make modification to DNS 11) make modification to Load Balancer Can anyone comment on this please? Thank you, Bob Halstead Advanced Services "The superior man cannot be known in little matters, Bresnan Communications The small man may not be entrusted with great concerns, Billings, Montana but he may be known in little matters." _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
