Hello all, I wanted to bounce off a couple of things off the folks in here.I have two servers with Remedy installed with the following specifics:-
SERVER1 OS - CentOS ARServer Version - 7.1 patch 3 ITSM version - 7.0.03 patch 8 ( everything OOB) Database - oracle 10 g(remote) Midtier - 7.1 patch 3 SERVER 2 OS - Rhel 5 ARServer Version - 7.1 patch 3 ITSM version - 7.0.03 patch 8 Database - oracle 10g ( remote) (same host as box 1 but separate DB instance) Midtier - 7.1 patch 3 Contains customizations to ITSM modules, in - house ARS apps, and their integration. I need to let go of SERVER 2 but have all the data, custom apps and customizations moved over to SERVER1. what would be a good approach to accomplish this. I am thinking of following two ways to accomplish this: 1) Do a DB refresh from SERVER 2 to SERVER 1 and clean out all the server name references ,config forms. Please let me know of any gotcha's or caveats in this approach. 2) Is it possible for SERVER1 to connect to DB instance of SERVER2 by doing the ar.conf,TWOTASK, etc changes? I am betting it cant be this easy.if its possible what should be my approach for it? Thanks On Tue, Feb 2, 2010 at 8:47 AM, Pierson, Shawn <shawn.pier...@sug.com>wrote: > ** > > One thing we do in our discovery process is to match on serial number as a > unique identifier for our discovery. We don’t force Change Requests for > that, even for servers, because often we have VM servers that are used for a > short testing period then thrown away, or various other things that would > result in it getting out of control. For production, however, we do force > Change Requests and the full approval process, but that is very rare. > Usually when we bring up a new server, we leave the old one in place for a > while as a fallback so the new server gets a new name, and if it is customer > facing we use DNS names to point to the new system. For example, from my > users’ perspective, they can go to http://remedy or http://help but on the > back end if we upgrade to a new server it goes from being named something > like sou-rem01p to sou-rem02p and most likely three separate Change Requests > are initiated: 1) To bring the new server online, 2) to install the > applications, and 3) to redirect the DNS entry to the new server. > > > > I hope this offers some useful information. > > > > Shawn Pierson > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] *On Behalf Of *Kathy Morris > *Sent:* Tuesday, February 02, 2010 10:09 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Discovery and Servers Changes > > > > ** > > Hi All, > > > > We have host name changes all the time. Our users are sending emails to > development every time the host name changes. I am implementing a new > process where host name changes are done thru Change Management as part of > automatic maintenance. I was just curious - what are other people doing > when there are host name changes. If the host name changes do you go > rediscover the asset. Do you request your users to submit a change request, > or is an email sufficient, and then you go and rediscover the asset? > > > > Also we find servers that are not pingable and someone is marking the > servers as down. I do not believe servers should automatically be marked as > down if they are not pingable. A server can be not pingable for many > reasons and it does not mean its down. > > > > > > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ > Private and confidential as detailed > here<http://www.sug.com/disclaimers/default.htm#Mail>. > If you cannot access hyperlink, please e-mail sender. > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
