Hey Hari... Some quick opinions :
1. Looks like you will be doing selective archiving & not fixed archiving. What this means for us is that you will be selecting criteria for tickets that will be archived as opposed to archiving all tickets for a fixed time period. This means that you will have to make multiple passes during each archive transaction to get older tickets. 2. If you are going to close tickets - then you will probably want to get all the data associated with the ticket (i.e. work logs, attachments etc.). 3. You have to decide whether or not you want to use the same Remedy interface to look at and retrieve the archived data (you could just rely on reports). 4. If you use the Remedy interface then - you will have to stand up another Remedy instance (granted - that there will be only viewing of data - so there will not be a need for write licenses). 5. Frequency of archiving, and server performance will depend on how much data you will be moving. 6. DSO may not be the best method for data migration. 7. If you use archive forms - note that the archive forms must be on the same server as your Remedy instance (this still leaves your data on your production box). 8. Remedy Migrator is another option (if you can afford it). You are able to configure private TCP ports to help reduce the load on the server. Only drawback - it does not look like there is a way to delete your record after archiving; therefore, this will have to be an escalation or some other workflow. 9. In the past I have used EIE OR AIE OR AI - not sure what they are calling it now. This works ok, but it's newest incarnation that leverages the Pentaho Spoon ETL engine looks to be superior (I think you need version 7.6.04 of ITSM). There are third party options like (rrchive is free and picks up where the Migrator left off): META-UPDATE: http://www.softwaretoolhouse.com/product/SthMupd/index.html RRCHIVE: http://www.rrr.se/en/ On Feb 14, 8:31 am, Hari Vishwakarma <hsvishwaka...@gmail.com> wrote: > Hi, > > We are planning to have archiving server with the following strategies in > place: > > 1. We will be moving our production server data to the newly created > archiving server with certain conditions like incident=closed or > cancelled, and we will be archiving the data on an interval of 2-3 > months. > > Here, i have few queries: > a.Will this archival server requires any new hardware,os,remedy ars, > remedy apps, licenses. > Plz note that my current remedy environment is on windows 2003 server, sql > serv > er 2005 database,ARS 7.5.04,remedy ITSM apps7.6.01 > b. Can this archival server be synched on an database level, if yes then how? > > 2. what frequency shall we use to archive the data from the production? > > 3. will this hamper my production server performance? > > 4. We are planning to use archiving forms or DSO, please suggest its > pros & cons while implementing. > > Please suggest . > > Regards > > Hari > > One more thing, how this movement of data will happen even after > 1.We want our production data to be moved from production to archival se > > > > > > > > > > On Tue, Feb 14, 2012 at 1:17 AM, Elry <elryal...@gmail.com> wrote: > > > Well Hari... > > > We currently just finishing up the creation of an archival server. > > > I guess my key questions would be: > > > 1. Do you have any Archive Policies in place (i.e. Incident Tickets > > will be automatically closed after 90 Days). > > 2. What applications are you running (i.e. ITSM or Custom > > Applications)? > > 3. What do you want to archive? > > 4. How are you going to archive (Archive forms, DSO, Remedy Migrator, > > DRIVER.EXE, etc.)? > > > On Feb 13, 1:32 pm, Hari Vishwakarma <hsvishwaka...@gmail.com> wrote: > > > Hi All, > > > > I want to create an archival server which will offload my production > > > server > > > load & improves my production server performance > > > Can anyone suggest what are all the prerequisites for the required > > > archival > > > server.And what need to be kept in mind while configuring this. Also will > > > it require any short of customizations for achieveing an archival server. > > > > Please suggest to achieve the same. > > > > -- > > > Best Regards, > > > > Hari shankar Vishwakarma > > > Mobile:- +91-9833675872 > > > E-mail:- hsvishwaka...@gmail.com > > > > ___________________________________________________________________________ > > > ____ > > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > > attend wwrug12www.wwrug12.comARSList:"Where the Answers Are" > > > ___________________________________________________________________________ > > ____ > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > attend wwrug12www.wwrug12.comARSList: "Where the Answers Are" > > ___________________________________________________________________________ > ____ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > attend wwrug12www.wwrug12.comARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
