For Concerns 2 and 3 ... In the DSO mapping you can use a transfer mode of "Copy + Delete" so the DSO process will do the delete if the copy succeeds. You do not need any escalations (Proposed Solution part 4) to do the delete. As for the stability, you can set up multiple pools for DSO to use.
Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Vikram Sent: Thursday, January 03, 2013 8:09 AM To: [email protected] Subject: Archiving Case Study.... hi All, First of all a Happy New Year to all. I have a situation at hand and would like some help. Its going to be a long one please bare with me. First some details about the environment, 1) Production Server : Server group environment (4) servers. ARS 7.5 P004, CMDB 7.6 Patch 001, ITSM 7.6 Patch 001, SLM 7.6 Patch 001 and SRM 7.6 Patch 001. Windows 32 bit servers and Remote SQL 2008 R2. 2) Reporting Server : Same config as Production server but a stand alone system with remote database. The Reporting server database is linked to Production database by a replication link which replicates data from selected forms from Production to Reporting DB. 3) Archival Server : Same config as Production but a stand alone system with remote database. Problem : We are trying to achieve data archiving from Production server to a newly setup archival server. The conditions are : 1) Production server should have 13 months data only. 2) Reporting server should have 13 months data only (which is taken care of by the database replication link which works on all DML statements including Delete) 3) Archival server should have all the data from the start of time till current. Proposed Solutions : There are few steps and methods we are thinking to implement in order to achieve the above goal. 1) Identify the forms to be archived. Using development studio to get to a list of forms. 2) Dump the entire production database onto the archival database this will ensure we have all the data of production server on the archival server. 3) Write DSO workflow on the forms we want data to be archived. Set DSO periodic transfer weekly/daily. 4) Write escalations to delete data from the forms on which DSO is set for data transfer to archival server. Concerns : Now this is the part I would need your insights on. 1) Is DSO the right approach here? We have evaluated RRR|Chive and sure it is a great tool but unfortunately the business does not want to implement any tool for which they don't have support already bought and not get into one more contract. 2) How stable is DSO and what should be our best strategy to implement it? Can a fail safe be built in the system just in case a DSO transfer fails? 3) Is writing escalations to delete data from forms a safe way to delete data from remedy? Is there anything else we can look into? 4) Have I missed anything in the above strategy? Any other random though around archiving that comes to mind will also be a great help for us right now as we are about to start the implementation phase soon. Thanks in advance, Vikram _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
