Produced by Araxis Merge on 10/18/2017 8:22:12 AM Central Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.
# | Location | File | Last Modified |
---|---|---|---|
1 | RAMS.zip\RAMS\Docs | RAMS_Integration_R2-0_Installation_and_Backout_Plan_Production_PROD_Final.doc | Wed Oct 18 12:53:36 2017 UTC |
2 | RAMS.zip\RAMS\Docs | RAMS_Integration_R2-0_Installation_and_Backout_Plan_Production_PROD_Final.doc | Wed Oct 18 13:09:05 2017 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 12 | 1200 |
Changed | 11 | 22 |
Inserted | 0 | 0 |
Removed | 0 | 0 |
Whitespace | |
---|---|
Character case | Differences in character case are significant |
Line endings | Differences in line endings (CR and LF characters) are ignored |
CR/LF characters | Not shown in the comparison detail |
No regular expressions were active.
1 | Installati on, Back-o ut, and Ro llback Gui de Templat eResearch Administra tive Manag ement Syst em (RAMS) R2.0 | |
2 | Deployment , Installa tion, Back -Out, and Rollback G uide for P roduction | |
3 | ||
4 | July, 2017 | |
5 | Department of Vetera ns Affairs | |
6 | Office of Informatio n and Tech nology (OI &T) | |
7 | Revision H istory | |
8 | DateVersio nDescripti onAuthor6/ 28/20172.5 Added cust omization for PPD an d PRD depl oymentsByL ight5/26/2 0172.4Adde d item “a “ under st ep 2 in se ction 6.5. 1.ByLight5 /24/20172. 3Revision following UAT test a nd GOLD bu ild instal l to SQA 0 5/23/2017B yLight05/0 9/20172.2R evision fo r RAMS rel ease 2.0 b ased on SQ A deployme nt session ByLight05/ 04/20172.1 Revision f or RAMS re lease 2.0B yLight04/1 9/20172.0I nitial ver sion for R AMS releas e 2.0.ByLi ghtArtifac t Rational e | |
9 | The Instal lation & B ack-out Pl an defines the order ed, techni cal steps required t o install the produc t, and if necessary, to back-o ut the ins tallation to the pre viously in stalled ve rsion. | |
10 | Table of C ontents | |
11 | 1 Introduc tion | |
12 | 5 | |
13 | 1.1 Purpos e | |
14 | 5 | |
15 | 1.2 Depend encies | |
16 | 5 | |
17 | 1.3 Constr aints | |
18 | 5 | |
19 | 2 Roles an d Responsi bilities | |
20 | 5 | |
21 | 3 Deployme nt | |
22 | 7 | |
23 | 3.1 Timeli ne | |
24 | 7 | |
25 | 3.2 Site R eadiness A ssessment | |
26 | 8 | |
27 | 3.2.1 Depl oyment Top ology (Tar geted Arch itecture) | |
28 | 9 | |
29 | 3.2.2 Site Informati on (Locati ons, Deplo yment Reci pients) | |
30 | 9 | |
31 | 3.2.3 Site Preparati on | |
32 | 9 | |
33 | 3.3 Resour ces | |
34 | 10 | |
35 | 3.3.1 Faci lity Speci fics (opti onal) | |
36 | 10 | |
37 | 3.3.2 Hard ware | |
38 | 10 | |
39 | 3.3.3 Soft ware | |
40 | 11 | |
41 | 3.3.4 Comm unications | |
42 | 11 | |
43 | 3.3.4.1 De ployment/I nstallatio n/Back-Out Checklist | |
44 | 11 | |
45 | 4 Installa tion | |
46 | 12 | |
47 | 4.1 Pre-in stallation and Syste m Requirem ents | |
48 | 12 | |
49 | 4.2 Platfo rm Install ation and Preparatio n | |
50 | 12 | |
51 | 4.3 Downlo ad and Ext ract Files | |
52 | 12 | |
53 | 4.4 Databa se Creatio n | |
54 | 12 | |
55 | 4.5 Instal lation Scr ipts | |
56 | 13 | |
57 | 4.6 Cron S cripts | |
58 | 13 | |
59 | 4.7 Access Requireme nts and Sk ills Neede d for the Installati on | |
60 | 13 | |
61 | 4.8 Instal lation Pro cedure | |
62 | 13 | |
63 | 4.9 Instal lation Ver ification Procedure | |
64 | 26 | |
65 | 4.10 Syste m Configur ation | |
66 | 26 | |
67 | 4.11 Datab ase Tuning | |
68 | 26 | |
69 | 5 | |
70 | Back-Out P rocedure | |
71 | 26 | |
72 | 5.1 Back-O ut Strateg y | |
73 | 26 | |
74 | 5.2 Back-O ut Conside rations | |
75 | 27 | |
76 | 5.2.1 | |
77 | Load Testi ng | |
78 | 27 | |
79 | 5.2.2 | |
80 | User Accep tance Test ing | |
81 | 27 | |
82 | 5.3 Back-O ut Criteri a | |
83 | 27 | |
84 | 5.4 Back-O ut Risks | |
85 | 27 | |
86 | 5.5 Author ity for Ba ck-Out | |
87 | 27 | |
88 | 5.6 Back-O ut Procedu re | |
89 | 27 | |
90 | 5.7 Back-o ut Verific ation Proc edure | |
91 | 28 | |
92 | 6 Rollback Procedure | |
93 | 28 | |
94 | 6.1 Rollba ck Conside rations | |
95 | 28 | |
96 | 6.2 Rollba ck Criteri a | |
97 | 28 | |
98 | 6.3 Rollba ck Risks | |
99 | 28 | |
100 | 6.4 Author ity for Ro llback | |
101 | 28 | |
102 | 6.5 Rollba ck Procedu re | |
103 | 28 | |
104 | 6.5.1 REST ORE RAMS S HAREPOINT CONTENT DA TABASE | |
105 | 28 | |
106 | 6.5.2 REST ORE RAMS U SER DB | |
107 | 29 | |
108 | 6.6 Rollba ck Verific ation Proc edure | |
109 | 31 | |
110 | 1 Introduc tion | |
111 | This docum ent descri bes how to deploy an d install the Resear ch Adminis trative Ma nagement S ystem (RAM S) R2.0, a s well as how to bac k-out the product an d rollback to a prev ious versi on or data set. This document is a compa nion to th e project charter an d manageme nt plan fo r this eff ort. Two s eparate ve rsions of this docum ent were w ritten to be used wh en upgradi ng the SQA and Pre-p roductions environme nts. This version ha s been cus tomized fo r the depl oyment to the Produc tion envir onment. | |
112 | 1.1 Purpos e | |
113 | The purpos e of this plan is to provide a single, c ommon docu ment that describes how, when, where, an d to whom the Resear ch Adminis trative Ma nagement S ystem (RAM S) R2.0 wi ll be depl oyed and i nstalled, as well as how it is to be bac ked out an d rolled b ack, if ne cessary. T he plan al so identif ies resour ces, commu nications plan, and rollout sc hedule. Sp ecific ins tructions for instal lation, ba ck-out, an d rollback are inclu ded in thi s document . | |
114 | 1.2 Depend encies | |
115 | None | |
116 | 1.3 Constr aints | |
117 | The end ta rget envir onment wil l be the V A producti on environ ment. Sche duling of the event will requi re coordin ation of a ll necessa ry support staff req uired to c omplete th e installa tion and i f needed c omplete th e back out as planne d. | |
118 | The upgrad e process described in this do cument can only be e xecuted th is one tim e, only be cause ther e are no p roduction users of R AMS. The p rocess des cribed in the follow ing sectio ns copy a cleaned RA MS Content database from the P re-product ion enviro nment to t he Product ion enviro nment. Onc e users ar e in the s ystem and Study Appl ications p rocessed, replacing the RAMS C ontent dat abase will not be al lowed beca use the da ta would b e lost. | |
119 | 2 Roles an d Responsi bilities | |
120 | RAMS 2.0 I nstallatio n Requires the coord ination of the follo wing Teams | |
121 | ||
122 | RAMS Integ ration Tea m, provide s v 2.0 pa ckage | |
123 | ||
124 | RAMS Susta inment Tea m, Applica tion Manag ement, | |
125 | Verifies v 2.0 Code and produc tion insta llation le ad | |
126 | ||
127 | Data Cente r Team, PI TC, Techni cal Manage ment and a ssist with Installat ion | |
128 | ||
129 | RAMS OIT T eam – Over all manage ment of th e installa tion | |
130 | Installati on and Bac k-Out Tech nical Team s | |
131 | RAMS Integ ration Tea m: | |
132 | Applicatio n – Chita Nilak, Tom Ryan, Mik e Hussey, Ren Shaw | |
133 | Database – Sheetal N ilak | |
134 | Configurat ion Manage ment – Lee Culbreth | |
135 | SharePoint Administr ator – Chi ta Nilak | |
136 | RAMS Susta inment Tea m | |
137 | ||
138 | Applicatio n – Myo Si thu, Britt any Pugh, Luis Catac ora | |
139 | ||
140 | Database – Mamunul I slam | |
141 | ||
142 | Configurat ion Manage ment – Bri an Finkboh ner | |
143 | SharePoint Administr ator – Jos h Koilpill ai | |
144 | Data Cente r Team | |
145 | Applicatio n – TBD | |
146 | ||
147 | Database – TBD | |
148 | ||
149 | Configurat ion Manage ment – TBD | |
150 | ||
151 | SharePoint Administr ation - TB D | |
152 | Additional details o f roles an d responsi bilities a re contain ed through out the do cument. | |
153 | Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties | |
154 | IDTeamPhas e / RoleTa sksProject Phase (Se e Schedule )VA OI&T P MDeploymen tPlan and schedule d eployment (including orchestra tion with vendors)VA OI&T PMDe ployment D etermine a nd documen t the role s and resp onsibiliti es of thos e involved in the de ployment.R AMS Sustai nmentDeplo ymentTest for operat ional read iness PITC and RAMS Sustainmen tDeploymen tExecute d eploymentP ITC Instal lationPlan and sched ule instal lation RAM S Sustainm entInstall ationEnsur e authorit y to opera te and tha t certific ate author ity securi ty documen tation is in placeNA Installati onValidate through f acility PO C to ensur e that IT equipment has been a ccepted us ing asset inventory processesV A OI&T PMI nstallatio nCoordinat e training VA OI&T P M, PITCBac k-outConfi rm availab ility of b ack-out in structions and back- out strate gy (what a re the cri teria that trigger a back-out) PITC and RAMS Susta inmentPost Deploymen tHardware, Software and System Support3 Deployment | |
155 | The deploy ment is pl anned as a single in stallation to the Ve terans Adm inistratio n Data Cen ter, Phila delphia (P ITC). RAMS is an ent erprise ap plication with one p roduction instance. | |
156 | This secti on provide s the sche dule and m ilestones for the de ployment. | |
157 | RAMS curre ntly has n o producti on users o n the appl ication. | |
158 | 3.1 Timeli ne | |
159 | The deploy ment and i nstallatio n is sched uled to ru n for 4 ho urs plus a n addition al 3 hours if a back out is re quired, as depicted in the mas ter deploy ment sched ule. | |
160 | Table 2 Ma ster Deplo yment Sche dule | |
161 | StepActivi tyResponsi ble Group Estimated Duration1S tart Insta llationVA OIT PM5 mi n2Environm ent Prepar ationPITC, RAMS Sust ainment1.5 hours3App lication U pgradePITC , RAMS Sus tainment1. 5 hours4Sm oke TestRA MS Sustain ment & Int egration45 min5End D eployment VA OIT PM5 min6Order Back out (if Requir ed)VA OIT PM5 min7Pe rform Back outPITC, RAMS Susta inment3 ho urs3.2 Sit e Readines s Assessme nt | |
162 | Deployment is comple ted throug h a remote access to each of t he servers in the ho st environ ment. The product to be deploy ed is the RAMS Integ ration R2. 0 upgrade and is to be install ed on the system of three serv ers for ea ch environ ment. No d esktop app lication w ill be ins talled. Se e Table 3 chart in s ection bel ow. This s ection dis cusses the locations that will receive t he RAMS de ployment. The deploy ment will be in the following sequence w ith each s ucceeding deployment dependent on the su ccess and acceptance of the pr evious dep loyment: | |
163 | Table 3: S ite Prepar ation | |
164 | Environmen tSharePoin t ServerDa tabase Ser verApplica tion Serve rProd DNS RAMCMS20 DNS RAMSQL21 DNS RAMAPP203. 2.1 Deploy ment Topol ogy (Targe ted Archit ecture) | |
165 | ||
166 | 3.2.2 Site Informati on (Locati ons, Deplo yment Reci pients) | |
167 | The deploy ment will be done re motely on servers ho sted at th e PITC sit e. | |
168 | 3.2.3 Site Preparati on | |
169 | The follow ing table describes preparatio n required by the si te prior t o deployme nt. These steps will be covere d in detai l in secti on 4. | |
170 | Table 4: S ite Prepar ation | |
171 | Site/Other Problem/Ch ange Neede dFeatures to Adapt/M odify to N ew Product Actions/St epsOwnerPr oductionEn sure appli cation is working at current r elease lev elNAPre-de ployment s moke testT BDProducti onCreate b ackup data baseNAFull RAMS data base backu pTBDProduc tionVerify backupNAC onfirm bac kup is in the backup directory TBDProduct ionCreate external c opy of bac kupNACopy and save R AMS_Prod_F ull.bak to external locationTB DProductio nCreate ba ckup of RA MS Content databaseN ACustomize and run s cripts for the envir onment for backupTBD Production Validate backupNAEx ecute SQL commands t o validate database backupTBDP roductionB ackup Tomc at config filesNACop y and save to separa te shared drive: RAM S-0.0.3xml , | |
172 | RAMS-0.0.3 .warTBD3.3 Resources | |
173 | The RAMS R 2.0 is an applicatio n upgrade to the exi sting RAMS applicati on and doe s not requ ire new ha rdware or facilities . However, access to Rational tool suite is requir ed to acce ss artifac ts. The de ployment t eam will n eed access to the re spective e nvironment servers h osting the RAMS appl ication, d atabase an d SharePoi nt. Docume ntation in support o f this app lication u pgrade dep loyment in cludes the following : | |
174 | RAMS Integ ration Req uest for C hange Orde r (RFCO) | |
175 | RAMS Integ ration Dep loyment, I nstallatio n, Back-Ou t, and Rol lback Guid e (this do cument) | |
176 | 3.3.1 Faci lity Speci fics (opti onal) | |
177 | N/A | |
178 | Table 5: F acility-Sp ecific Fea tures | |
179 | SiteSpace/ RoomFeatur es NeededO therN/A3.3 .2 Hardwar e | |
180 | The follow ing table describes hardware s pecificati ons requir ed at each site prio r to deplo yment. | |
181 | Table 6: H ardware Sp ecificatio ns | |
182 | Required H ardwareMod elVersionC onfigurati onManufact urerOtherN /APlease s ee the Rol es and Res ponsibilit ies table in Section 2 for det ails about who is re sponsible for prepar ing the si te to meet these har dware spec ifications . | |
183 | 3.3.3 Soft ware | |
184 | The follow ing table describes software s pecificati ons requir ed at each site prio r to deplo yment. | |
185 | Table 7: S oftware Sp ecificatio ns | |
186 | Required S oftwareMak eVersionCo nfiguratio nManufactu rerOtherN/ APlease se e the Role s and Resp onsibiliti es table i n Section 2 above fo r details about who is respons ible for p reparing t he site to meet thes e software specifica tions. | |
187 | 3.3.4 Comm unications | |
188 | All notifi cation of activities will be b y email. D uring actu al deploym ent, a Lyn c session will be es tablished with an op en mic whe re the act ivities pe rformed by the techn icians are visible i n a shared screen. | |
189 | 3.3.4.1 De ployment/I nstallatio n/Back-Out Checklist | |
190 | Table 8: D eployment/ Installati on/Back-Ou t Checklis t | |
191 | ActivityDa yTimeIndiv idual who completed taskDeploy TBAInstall TBABack-Ou tTBD4 Inst allation | |
192 | 4.1 Pre-in stallation and Syste m Requirem ents | |
193 | CD2 approv al must be provided to proceed with the RAMS Integ ration R2. 0 upgrade. Full syst em backup will be re quired bef ore start of deploym ent. | |
194 | 4.2 Platfo rm Install ation and Preparatio n | |
195 | Verify tha t database s and soft ware are c onsistent with 1701 baseline. | |
196 | 4.3 Downlo ad and Ext ract Files | |
197 | Provided i n the foll owing sect ion is a l ist of all the softw are instal lation fil es, their locations, and the c hronologic al steps f or downloa ding and e xtracting the softwa re prior t o installa tion. All files refe renced in this docum ent are in cluded in the R2.0Fi les.zip fi le hosted in RTC. | |
198 | Double c licking th e icon to the left w ill take t he reader with prope r RTC acce ss to the location o f the ZIP file in RT C. | |
199 | Click to o pen ZIP fi le locatio n | |
200 | List of fi les to be applied du ring the i nstall pro cess are a s follows: | |
201 | Java Appli cation Ser ver Files | |
202 | backup.sh | |
203 | deploy.sh | |
204 | RAMS-2.0.0 .war | |
205 | RAMS-2.0.0 .xml | |
206 | Database B ackup and Upgrade Sc ripts | |
207 | Backup_RAM SContentDB .sql | |
208 | Backup_RAM S.sql | |
209 | Create_tab les.sql | |
210 | Create_tab les_rollba ck.sql | |
211 | InsertScri pts.sql | |
212 | InsertScri pts_rollba ck.sql | |
213 | RestoreRam sContentDa tabase.sql | |
214 | RestoreDat abaseRAMS. sql | |
215 | PowerShell Scripts | |
216 | ModifyCont entDatabas e.ps1 | |
217 | Content Da tabase Bac kup File | |
218 | SP_RAMS_WS S_Content_ IRB_Applic ation_DB_2 _0_0503.FU L (This fi le is prov ided separ ately from the zip b ecause of its large size.) | |
219 | 4.4 Databa se Creatio n | |
220 | N/A | |
221 | 4.5 Instal lation Scr ipts | |
222 | N/A | |
223 | 4.6 Cron S cripts | |
224 | N/A | |
225 | 4.7 Access Requireme nts and Sk ills Neede d for the Installati on | |
226 | These role s describe d here are specific to the pro duction de ployment e nvironment . | |
227 | Database A dministrat or – to ru n database scripts | |
228 | Local and/ or System Administra tor for se rvers – in sure serve r settings are as ne eded and v erify cert ificates a re updated , deploy n ew Java we b applicat ion, verif y correct URLs | |
229 | SharePoint Administr ator – rem ove existi ng content database, add new c ontent dat abase, and place new or update d files in place. | |
230 | 4.8 Instal lation Pro cedure | |
231 | Stopping a nd Startin g the Tomc at service as shown below must be done b y a Linux Admin on t he vaphira mapp20 Lin ux server. All the o ther steps below ref erence Win dows serve r names in the Produ ction envi ronment. T o connect to the ser ver indica ted a remo te connect ion is mad e using th e Remote D esktop Con nection ut ility some times refe rred to as RDP in th e instruct ion to fol low. This utility is accessed from the S tart promp t on the d esktop the Admin is using. | |
232 | Example: | |
233 | ||
234 | Backup the environme nt | |
235 | STOP Tomca t services | |
236 | sudo servi ce tomcat7 stop | |
237 | Verify con nection to RAMS data base by ru nning comm and SP_WHO in new qu ery window on vaphir amsql21 fo r the Prod uction ins tall. Mak e sure the re is no a ctive user connectio n to RAMS database. | |
238 | Perform fu ll backup of RAMS da tabase. | |
239 | Open Micro soft SQL S erver Mana gement Stu dio on vap hiramsql21 for the P roduction install. | |
240 | ||
241 | Search Mic rosoft SQL Server Ma nagement S tudio in t he Windows Start Men u | |
242 | Click on t he program to open | |
243 | Connect to the SQL S erver inst ance. | |
244 | A “Connect to SQL Se rver” wind ow will ap pear. | |
245 | Select “Da tabase Eng ine” as th e Server t ype. | |
246 | Select the correct i nstance va phiramsql2 1 for Prod uction. | |
247 | Select the correct l ogin crede ntials wit h admin ri ghts. | |
248 | Click the “Connect” button. | |
249 | Perform a full ad-ho c backup o f the RAMS database. | |
250 | Open SSMS, and in a new query window run command S P_helpdb R AMS to fin d the size of the RA MS databas e | |
251 | Check the local back up directo ry to make sure suff icient dis k space is available to accomm odate RAMS database backup. | |
252 | NOTE: Do n ot proceed with back up task if sufficien t disk spa ce is NOT available on the loc al server directory to accommo date backu p file | |
253 | Open “Back up_RAMS.sq l”, in a n ew SSMS qu ery window to comple te a full backup of the origin al RAMS da tabase. | |
254 | OR copy an d paste th e below st atements i n a new qu ery window | |
255 | BACKUP DAT ABASE [RAM S] | |
256 | TO DISK = N'D:\2-0_B ackups\RAM S_Prod_Ful l.bak' | |
257 | WITH DESC RIPTION = N'RAMS Pro d Full Bac kup Before DB Refres h', NOFORM AT, NOINIT , | |
258 | NAME = N'R AMS-Full D atabase Ba ckup', SKI P, NOREWIN D, NOUNLOA D, STATS = 10 | |
259 | GO | |
260 | declare @b ackupSetId as int | |
261 | select @ba ckupSetId = position from msdb ..backupse t | |
262 | where data base_name= N'RAMS' an d backup_s et_id=(sel ect max(ba ckup_set_i d) from ms db..backup set where database_n ame=N'RAMS ' ) | |
263 | if @backup SetId is n ull begin raiserror( N'Verify f ailed. Bac kup inform ation for database ' 'RAMS'' no t found.', 16, 1) en d | |
264 | RESTORE VE RIFYONLY F ROM DISK = N'D:\2-0 _Backups\R AMS_Prod_F ull.bak' W ITH FILE = @backupS etId, NOU NLOAD, NO REWIND | |
265 | GO | |
266 | Note: Mod ify the lo cation pat h in two p laces with in the scr ipt to ref lect the p roper loca tion of th e followin g items: | |
267 | Current lo cation of backup fil e shown as N'D:\2-0_ Backups\RA MS_Prod_Fu ll.bak' ( Make sure to select correct lo cation in 'TO DISK' line). | |
268 | Current lo cation of backup fil e shown as N'D:\2-0_ Backups\RA MS_Prod_Fu ll.bak'. ( in 'RESTOR E VERIFYON LY FROM D ISK ' line ) | |
269 | Click Pars e in ssms to validat e the quer y. | |
270 | Click the “Execute” button at the top on the toolb ar. | |
271 | You will s ee the mes sages “100 percent p rocessed”, “BACKUP D ATABASE su ccessfully processed xxx pages in xxx se conds.” an d “The bac kup file i s valid” u nder the “ Messages” box. | |
272 | You will a lso see th e message “Query exe cuted succ essfully.” at the bo ttom of th e query wi ndow. | |
273 | Verify the completed backup se t is in th e backup d irectory | |
274 | Copy and s ave “RAMS_ Prod_Full. bak” to a separate s hared dire ctory away from the local serv er to use it as part of rollba ck procedu re if need ed later. | |
275 | Perform fu ll backup of RAMS Co ntent Data base | |
276 | a) Open “B ackup_RAMS ContentDB. sql”, in a new SSMS query wind ow to comp lete a ful l backup o f the orig inal RAMS SharePoint content d atabase. | |
277 | OR copy an d paste th e below st atements i n a new qu ery window | |
278 | BACKUP DAT ABASE [SP_ RAMS_WSS_C ontent_IRB _Applicati ons_DB] | |
279 | TO DISK = N'D:\2-0_ Backups\SP _RAMS_WSS_ Content_IR B_Applicat ions_DB_ba ckup_Prod_ Full.bak' | |
280 | WITH NOFOR MAT, NOINI T, NAME = N'SP_RAMS _WSS_Conte nt_IRB_App lications_ DB-Full Da tabase Bac kup', SKIP , NOREWIND , NOUNLOAD , STATS = 10 | |
281 | GO | |
282 | declare @b ackupSetId as int | |
283 | select @ba ckupSetId = position from msdb ..backupse t | |
284 | where data base_name= N'SP_RAMS_ WSS_Conten t_IRB_Appl ications_D B' | |
285 | and backup _set_id=(s elect max( backup_set _id) from msdb..back upset wher e database _name=N'SP _RAMS_WSS_ Content_IR B_Applicat ion_DB' ) | |
286 | if @backup SetId is n ull begin raiserror( N'Verify f ailed. Bac kup inform ation for database ' 'SP_RAMS_W SS_Content _IRB_Appli cations_DB '' not fou nd.', 16, 1) end | |
287 | RESTORE VE RIFYONLY | |
288 | FROM DISK = N'D:\2- 0_Backups\ SP_RAMS_WS S_Content_ IRB_Applic ations_DB_ backup_Pro d_Full.bak ' | |
289 | WITH FILE = @backup SetId, NO UNLOAD, N OREWIND | |
290 | GO | |
291 | Note: Mod ify the lo cation pat h in two p laces with in the scr ipt to ref lect the p roper loca tion of th e followin g items: | |
292 | Current lo cation of backup fil e shown as N'D:\2-0_ Backups\SP _RAMS_WSS_ Content_IR B_Applicat ions_DB_ba ckup_Prod_ Full.bak' (Make sur e to selec t correct location i n 'TO DIS K' line). | |
293 | Current lo cation of backup fil e shown as N'D:\2-0_ Backups\SP _RAMS_WSS_ Content_IR B_Applicat ions_DB_ba ckup_Prod_ Full.bak'. (in 'REST ORE VERIFY ONLY FROM DISK ' li ne) | |
294 | Click Pars e in ssms to validat e the quer y. | |
295 | Click the “Execute” button at the top on the toolb ar. | |
296 | You will s ee the mes sages “100 percent p rocessed”, “BACKUP D ATABASE su ccessfully processed xxx pages in xxx se conds.” an d “The bac kup file i s valid” u nder the “ Messages” box. | |
297 | You will a lso see th e message “Query exe cuted succ essfully.” at the bo ttom of th e query wi ndow. | |
298 | Verify the completed backup se t is in th e backup d irectory | |
299 | Copy and s ave “SP_RA MS_WSS_Con tent_IRB_A pplication s_DB_backu p_Prod_Ful l.bak” to a separate shared di rectory aw ay from th e local se rver. | |
300 | Backup Tom cat config files | |
301 | Verify tha t $CATALIN A_HOME is set. | |
302 | Run “echo $CATALINA_ HOME” - i f a value is returne d move on to step b) . | |
303 | If no valu e is set, export the CATALINA_ HOME varia ble to poi nt to the location o f Tomcat. For all to mcat relat ed command s, make su re this en vironment variable i s set. | |
304 | export CAT ALINA_HOME ="/usr/sha re/apache- tomcat-7.0 .57" | |
305 | Using Secu re or WinS CP copy th e backup.s h and depl oy.sh file s from the zip file to $CATALI NA_HOME. | |
306 | Change per missions o n backup.s h and depl oy.sh | |
307 | sudo chmod 755 backu p.sh | |
308 | sudo chmod 755 deplo y.sh | |
309 | Run backup .sh to mov e the exis ting RAMS- *.xml, RAM S-*.war in to “backup ” director y, and del ete the ex ploded WAR directory . | |
310 | sudo $CATA LINA_HOME/ backup.sh | |
311 | Verify tha t the RAMS -*.xml and RAMS-*.wa r files ar e in the $ CATALINA_H OME/backup directory . | |
312 | sudo ls –l a $CATALIN A_HOME/bac kup | |
313 | Verify tha t the CATA LINA_HOME/ deploy dir ectory exi sts. | |
314 | sudo ls –l a $CATALIN A_HOME/dep loy | |
315 | Verify tha t the $CAT ALINA_HOME /webapps d irectory n o longer c ontains RA MS-*.war o r the expl oded war d irectory o f the same RAMS-* na me. | |
316 | sudo ls –l a $CATALIN A_HOME/web apps | |
317 | Using secu re copy or WinSCP th e new RAMS -*.xml and RAMS-*.wa r to the $ CATALINA_H OME/deploy directory . | |
318 | SQL Update s | |
319 | Use the fi les includ ed in the R2.0Files. zip file t o update t he RAMS da tabase. Ru n Create_t ables scri pt then In sertScript s although the order does not matter. | |
320 | InsertScri pts.sql | |
321 | Create_tab les.sql | |
322 | Create a n ew Content Database | |
323 | The follow ing steps are to be completed by EO DBA: | |
324 | Start RDP and connec t to serve r vaphiram sql21 | |
325 | Create Dir ectory if it doesn’t exist on the server vaphirams ql21 at D: \Integrati onReleaseB ackups\503 | |
326 | Copy Conte nt databas e file fro m Pre-prod uction ser ver DNS RAMSQL41, D:\ Integr ationRelea seBackups\ 503 to D:\Inte grationRel easeBackup s\503 on t he Product ion server vaphirams ql21 | |
327 | Open “Rest oreRamsCon tentDataba se.sql” in a new que ry window. | |
328 | Or Copy an d paste th e below st atements t o a new qu ery window | |
329 | USE master | |
330 | GO | |
331 | Restore da tabase [SP _RAMS_WSS_ Content_IR B_Applicat ion_DB_2_0 ] | |
332 | FROM DISK = N'D:\Int egrationRe leaseBacku ps\503\SP_ RAMS_WSS_C ontent_IRB _Applicati on_DB_2_0_ 0503.FUL' | |
333 | WITH FILE = 1, | |
334 | MOVE N'SP_ RAMS_WSS_C ontent_IRB _Applicati ons_DB' | |
335 | TO N'E:\Mi crosoft SQ L Server\M SSQL\Data\ SP_RAMS_WS S_Content_ IRB_Applic ation_DB_2 _0.mdf', | |
336 | MOVE N'SP_ RAMS_WSS_C ontent_IRB _Applicati ons_DB_log ' | |
337 | TO N'L:\Mi crosoft SQ L Server\M SSQL\Data\ SP_RAMS_WS S_Content_ IRB_Applic ation_DB_l og_2_0.LDF ', | |
338 | NOUNLOAD, STATS =5 | |
339 | GO | |
340 | Note: Modi fy the loc ation path in three places wit hin the sc ript that are highli ghted in b old Red to reflect t he proper location o f the foll owing item s: | |
341 | ||
342 | Current lo cation of backup fil e shown as N'D:\Inte grationRel easeBackup s\503\SP_R AMS_WSS_Co ntent_IRB_ Applicatio n_DB_2_0_0 503.FUL' (Make sure to select correct b ackup file “SP_RAMS_ WSS_Conten t_IRB_Appl ication_DB _2_0_0503. FUL”). | |
343 | ||
344 | Data file location s hown as N' E:\Microso ft SQL Ser ver\MSSQL\ Data\SP_RA MS_WSS_Con tent_IRB_A pplication _DB_2_0.md f'. (.mdf file locat ion) | |
345 | ||
346 | Log file l ocation sh own as N'L :\Microsof t SQL Serv er\MSSQL\D ata\SP_RAM S_WSS_Cont ent_IRB_Ap plication_ DB_log_2_0 .LDF'. (.L DF file lo cation) | |
347 | Verify the user [ DN S \ramtstsp1 3WebApp1] has [SPDat aAccess] R ole member ship to RA MS content database (SP_RAMS_W SS_Content _IRB_Appli cation_DB_ 2_0) | |
348 | SharePoint | |
349 | Use the ne w Content Database | |
350 | See above in “4.8”, subsection “A. Backu p the envi ronment”, step “3) P erform ful l backup o f RAMS dat abase”, su b-step a) for instru ctions for accessing SQL Manag ement Stud io for com pleting th e followin g steps on the vaphi ramsql21 s erver. | |
351 | Go to Shar ePoint Cen tral Admin istration Web site ( See above “4.8” subs ection “A. Backup th e environm ent”, step 3a), Clic k on “Mana ge content databases ” ( click on “SP_RAM S_WSS_Cont ent_IRB_Ap plication_ DB”, shoul d be the o ne mapped to the “/s ites/IRBAp plications ” site col lection. | |
352 | Check the “Remove Co ntent Data base” opti on shown b elow, and then click on “Ok” b utton at t he bottom of the pag e. | |
353 | ||
354 | SharePoint Administr ator for a bove use S harePoint Content Ma nagement S erver on p roduction server DNS RAMCHS20 | |
355 | Add new Co ntent Data base | |
356 | Run the fo llowing Po werShell s cript Modi fyContentD atabase.ps 1 in the S harePoint PowerShell console. | |
357 | Mount-SPCo ntentDatab ase -Name SP_RAMS_WS S_Content_ IRB_Applic ation_DB_2 _0 -WebApp lication v aww.sqa.ra m.msp. DNS -DatabaseS erver vaph iramsql21. DNS for Produc tion envir onment | |
358 | Or follow the steps below | |
359 | Add the ne w content Database “ SP_RAMS_WS S_Content_ IRB_Applic ation_DB_2 _0“ as sho wn below, please use the value s highligh ted below for number of sites fields. | |
360 | SharePoint Administr ator for a bove use t he appropr iate Web A pplication name for the produc tion envir onment, th en uses Sh arePoint C ontent Man agement Se rver on se rver DNS RAMCHS20. Content da tabase nam e is “SP_R AMS_WSS_Co ntent_IRB_ Applicatio n_DB_2_0” | |
361 | After you click on “ ok” you sh ould see t he new con tent datab ase and th e associat ed site co llection “ /sites/IRB Applicatio ns” as bel ow: | |
362 | ||
363 | SharePoint Configura tion | |
364 | For each w orkflow at the /site s/IRBAppli cation lev el, publis h the mana ge personn el notific ation work flow. | |
365 | Open the w orkflow | |
366 | Click Publ ish | |
367 | For each w orkflow at each faci lity subsi te level, publish th e: | |
368 | Add to IAC UC Agenda | |
369 | Add to RDC Agenda | |
370 | Applicatio n Initial Submit Not ification | |
371 | Applicatio n Submissi on Type | |
372 | Applicatio n Type Cha nge | |
373 | Approved A pplication Submitted notificat ion | |
374 | Committee Broker | |
375 | New Agenda Notificat ion WF | |
376 | Notificati on Rules, Send Remin der to AO | |
377 | Open the w orkflow | |
378 | Click Publ ish | |
379 | Update the StudyID-L ink column definitio n in each Committee Topics lis t for each subsite a s below, j ust change the URL t o the envi ronment sp ecific val ue. e.g. S QA below ( This examp le is for SQA. Use a ppropriate URL for P roduction environmen t) | |
380 | =CONCATENA TE("<div>< a href='", "https://v aww.sqa.ra m.msp. DNS /sites/IRB Applicatio ns/SiteAss ets/irb-ap plications -general.h tml?",Stud y_ID,"","' >",Study_I D,"</a></d iv>") | |
381 | ||
382 | ||
383 | Open RAMS- environmen t.js in th e Site Ass ets/js fol der in Sha rePoint De signer and update th e URL show n below fo r the RAMS -environme nt being d eployed | |
384 | Change htt p to https in 2 plac es, ShareP oint URL a nd Web Ser vices URL highlighte d in bold red below. | |
385 | Change the port from PORT to PORT | |
386 | // Define environmen tal consta nts for RA MS web-app s. | |
387 | //Ren Chan ge here | |
388 | window.RAM S = window .RAMS || { }; | |
389 | RAMS.Envir onment = { | |
390 | ||
391 | SharePoint : { | |
392 | ||
393 | ||
394 | URL: "http s://" + wi ndow.locat ion.hostna me + "/", | |
395 | ||
396 | ||
397 | CentralIRB Site: "Cen tral IRB", | |
398 | ||
399 | ||
400 | List: {} / / Column m appings de fined belo w. | |
401 | ||
402 | }, | |
403 | ||
404 | WebService : { | |
405 | ||
406 | ||
407 | URL: "http s://" + wi ndow.locat ion.hostna me + ": PORT /RAMS-2.0. 0/" | |
408 | ||
409 | ||
410 | // Form ma ppings def ined below . | |
411 | ||
412 | } | |
413 | }; | |
414 | //////// ////////// | |
415 | // REPLAC E HERE // | |
416 | ////////// //////// | |
417 | RAMS.Envir onment.Sha rePoint.Li st.Applica tion = { | |
418 | ||
419 | FacilityLo okupId: | |
420 | ||
421 | ||
422 | "FacilityL ookupId", | |
423 | ||
424 | LinkToAppl ication: | |
425 | ||
426 | ||
427 | "LinktoApp lication", | |
428 | ||
429 | PrincipalI nvestigato rId: | |
430 | ||
431 | "Principal Investigat orId", | |
432 | CoPrinci palInvesti gatorId: | |
433 | ||
434 | "CoPIId", | |
435 | ||
436 | PrimaryRev iewersId: | |
437 | ||
438 | ||
439 | "PrimaryRe viewersId" | |
440 | }; | |
441 | RAMS.Envir onment.Web Service.Fo rm = { | |
442 | ||
443 | Parent: 60 , | |
444 | ||
445 | ||
446 | ||
447 | ||
448 | 60: "Paren t", | |
449 | ||
450 | Local: 61, | |
451 | ||
452 | ||
453 | ||
454 | ||
455 | 61: "Local ", | |
456 | ||
457 | Adverse: 6 2, | |
458 | ||
459 | ||
460 | ||
461 | ||
462 | 62: "Adver se", | |
463 | ||
464 | ContReview : 63, | |
465 | ||
466 | ||
467 | ||
468 | 63: "ContR eview", | |
469 | ||
470 | Closeout: 64, | |
471 | ||
472 | ||
473 | ||
474 | ||
475 | 64: "Close out", | |
476 | ||
477 | Administra tiveUpdate : 65, | |
478 | ||
479 | ||
480 | 65: "Admin istrativeU pdate" | |
481 | }; | |
482 | //////// ////////// | |
483 | // REPLAC E HERE // | |
484 | ////////// //////// | |
485 | Check out Master Pag es/RAMS Ma sterPageTe mplate/ ir b-applicat ions.html, in ShareP oint Desig ner. Chang e the Pers onal Page Link for t he environ ment you a re deployi ng to. Cha nge “itst” to approp riate serv er ID for Production . Possibly “prd”. Ch eck in the change an d supply a comment a bout the d eployment. | |
486 | In the Sit e Assets f older modi fy irb-app lications- general.ht ml, in Sha rePoint De signer, un comment th e Personal Page Link for the e nvironment you are d eploying t o and comm ent out th e itst per sonal page link. | |
487 | The Notifi cation Rul es Workflo w is depen dent on an Environme nt List (c ontained i n each sub site). Upd ate the UR L in each subsite fr om “itst” to appropr iate serve r ID, poss ibly “prd” for the p roduction environmen t to match the domai n name of the enviro nment. | |
488 | ||
489 | Create Smo ke Test Us ers | |
490 | Add Site A dministrat ors with a ppropriate access. | |
491 | 2) These Site Admin istrators will add s moke test users to a ppropriate security groups bas ed on thei r roles. | |
492 | Java/Tomca t | |
493 | 3) Run $C ATALINA_HO ME/deploy. sh script, which wil l deploy t he war and xml to de stination folders sh own in the table bel ow. | |
494 | sudo $CATA LINA_HOME/ deploy.sh | |
495 | File/Compo nentDestin ationAdd o r Update?R AMS-2.0.0. warRAMS Ja va applica tion | |
496 | $CATALINA_ HOME /weba ppsUpdateR AMS-2.0.0. xml$CATALI NA_HOME /c onf/Catali na/localho stUpdate4) In the $ CATALINA_H OME /conf/ Catalina/l ocalhost/R AMS-2.0.0. xml verify that the rams/sp/ba seSiteUrl and rams/s p/document SiteUrlPat tern URLs are for th e correct environmen t. The pat tern is (e xample is for SQA en vironment. Use produ ction serv er ID): | |
497 | "https://v aww.sqa.ra m.msp. DNS /sites/irb applicatio ns” and “h ttps://vaw w.sqa.ram. msp. DNS /sites/irb applicatio ns", respe ctively. | |
498 | 5) In the $CATALINA _HOME /con f/Catalina /localhost /RAMS-2.0. 0.xml veri fy and val idate that super use r credenti als are va lid for th e environm ent. Colla borate wit h DBA to e nsure that connectio n string t o RAMS DB is still v alid in to mmee.xml | |
499 | 6) Restar t Tomcat. | |
500 | sudo servi ce tomcat7 start | |
501 | verify tha t new WAR file is un packed int o a new di rectory wi th the sam e name | |
502 | 4.9 Instal lation Ver ification Procedure | |
503 | After succ essful com pletion of the deplo yment step s above, E O will ale rt the RAM S-Sustainm ent team t hat the en vironment is ready f or smoke t esting. A RAMS-Sust ainment te am member will then perform po st-deploym ent testin g. Testing will veri fy that th e high-lev el functio nality of the system is workin g as expec ted and th at any new changes d id not aff ect the cu rrent func tionality in an unex pected way . | |
504 | At a high- level, smo ke testing will incl ude: | |
505 | logging in to the app lication | |
506 | Verify tha t users ar e in appro priate sec urity grou ps | |
507 | starting a n IRB appl ication | |
508 | verifying radio butt on, checkb ox, text f ield, and save/cance l buttons work | |
509 | submitting an applic ation, cli cking on t he Committ ee Activit ies Page a nd Local S ite Admini strator Co ntrol Pane l Page | |
510 | accessing previously submitted data to v iew front end functi onality | |
511 | submit a n ew study a pplication to IRB an d CIRB for review – 1 email ex pected to each commi ttee. CIRB Is throug h CIRB wor kflow. IRB is throug h Committe e Broker w orkflow. C ontinue wo rkflow to completion . | |
512 | Approve th e study ap plication and check routing to RDC. | |
513 | Any other specific t esting wil l be perfo rmed on an ad-hoc ba sis. | |
514 | 4.10 Syste m Configur ation | |
515 | Ensure the target en vironment servers ha ve all upd ates and s ecurity ce rtificatio ns in plac e. | |
516 | 4.11 Datab ase Tuning | |
517 | N/A | |
518 | Back-Out P rocedure | |
519 | Back-Out p ertains to returning the softw are to the last know n good ope rational s tate of th e software and appro priate pla tform sett ings. Back -out is no t complete until bot h Section 5 and Sect ion 6 are complete. | |
520 | 5.1 Back-O ut Strateg y | |
521 | Back-out s trategy de fines how to revert the softwa re back to a previou s version in the eve nt the new release f unctions i mproperly. The back- out strate gy for thi s installa tion is to restore t he | |
522 | RAMS-0.0.3 .war and R AMS-0.0.3. xml. Code in SharePo int will b e rolled b ack in Sec tion 6 whe n the Roll back occur s. | |
523 | 5.2 Back- Out Consid erations | |
524 | If it is d etermined that the i nstallatio n of RAMS version 2. 0 failed a nd product ion system contains major defe cts, the V A OIT Proj ect Manage r will ord er a Back- out of the release. The Back-o ut order s hall be fo llowed up with an em ail that d escribes t he reason for the Ba ck-out ord er. | |
525 | Rollback w ill be con sidered fo llowing fa ilure to d eploy by e ither the inability to execute any of th e steps, i ncluding p re-deploym ent smoke test, back ups, resto ring conte nt DB, dep loyment of RAMS-2.0. 0 applicat ion, confi guring Sha rePoint, o r smoke te sting. The VA Projec t Manager in consult ation with the deplo yment, the RAMS Inte gration, a nd the RAM S Sustainm ent teams, will dete rmine if t he applica tion deplo yment issu es can be resolved i n a timely manner by fixing th e encounte red proble ms or by a uthorizing a rollbac k to the p re-deploym ent state. | |
526 | Load Testi ng | |
527 | N/A | |
528 | User Accep tance Test ing | |
529 | The RAMS S ustainment Team will perform v alidation testing to ensure th e deployme nt was suc cessful. | |
530 | 5.3 Back-O ut Criteri a | |
531 | If the rel ease canno t be succe ssfully de ployed or post-deplo yment vali dation fai ls, the VA Project M anager res ponsible f or RAMS wi ll be noti fied and a sked to ap prove a ba ck-out of the releas e. | |
532 | 5.4 Back-O ut Risks | |
533 | N/A - Ther e are no k nown back- out risks. | |
534 | 5.5 Author ity for Ba ck-Out | |
535 | The VA OIT Project M anager has the autho rity to or der a back -out due t o signific ant failur es of the release in stallation . | |
536 | 5.6 Back-O ut Procedu re | |
537 | Once the V A OIT PM d etermines the need t o remove t he build, follow the procedure s in Secti on 6. Perf orm the fo llowing st eps as the Linux Sys tem Admini strator. | |
538 | STOP Tomca t services | |
539 | sudo servi ce tomcat7 stop | |
540 | Copy the R AMS-0.0.3. war from t he $CATALI NA_HOME/ba ckup direc tory to th e $CATALIN A_HOME/web apps direc tory | |
541 | Delete the RAMS-2.0. 0.war from the $CATA LINA_HOME/ webapps di rectory an d delete t he explode d war file subdirect ory, if th ere is one . | |
542 | Copy the R AMS-0.0.3. xml from t he $CATALI NA_HOME/ba ckup direc tory to th e $CATALIN A_HOME/con f/Catalina /localhost directory | |
543 | Delete the RAMS-2.0. 0.xml from the $CATA LINA_HOME/ conf/Catal ina/localh ost direct ory | |
544 | Restore th e RAMS Dat abase as d escribed i n Section 6. This st ep may nee d to hand off to the Database Administra tor or Sha rePoint Ad ministrato r. | |
545 | Start the Tomcat web services. | |
546 | sudo servi ce tomcat7 start | |
547 | 5.7 Back-o ut Verific ation Proc edure | |
548 | Once the B ack-out pr ocedure is complete a smoke te st will be performed by the Su stainment Team and t he VA to v erify RAMS is operat ing to the standards prior to the instal lation. | |
549 | 6 Rollback Procedure | |
550 | Rollback p ertains to returning the datab ases to th e last kno wn good op erational state. Rol lback is n ot complet e until bo th Section 5 and Sec tion 6 are complete. | |
551 | 6.1 Rollba ck Conside rations | |
552 | If the rel ease canno t be succe ssfully de ployed or post-deplo yment vali dation fai ls, the VA Project M anager wil l be asked to approv e a back-o ut/rollbac k of the r elease. | |
553 | 6.2 Rollba ck Criteri a | |
554 | After the installati on of the release th e RAMS pro duct is no t function al or majo r defect o ccur that prevent th e user fro m performi ng critica l tasks an d the prob lem can be traced to the new r elease a b ack-out/ro llback sho uld be con sidered to return RA MS to an o perating c apability. | |
555 | Minor defe cts that d o not inte rfere with the funct ional oper ation of t he product will not be conside red a majo r defect a nd will no t be an in dication t o order a back-out/r ollback | |
556 | 6.3 Rollba ck Risks | |
557 | If the ins tructions identified in Sectio n 6.0 are followed t he risk fo r a rollba ck are min imal. Fail ure to fol low the pr ocedure co uld alter the core f unctionali ties and i ncrease th e downtime of the ap plication. | |
558 | 6.4 Author ity for Ro llback | |
559 | The VA OIT Project M anager has the autho rity to or der a back -out due t o signific ant failur es of the release in stallation . | |
560 | 6.5 Rollb ack Proced ure | |
561 | 6.5.1 REST ORE RAMS S HAREPOINT CONTENT DA TABASE | |
562 | The follow ing steps should be performed by the Sha rePoint Ad ministrato r | |
563 | Disconnect all open sessions f rom the RA MS databas e. | |
564 | Disconnect the Conte nt Databas e | |
565 | Verify the database name accor ding to th e environm ent. For S QA the cor rect name is “SP_RAM S_WSS_Cont ent_IRB_Ap plication_ DB_2_0”. | |
566 | Go to Shar ePoint Cen tral Admin istration Web site, Click on “ Manage con tent datab ases” cli ck on “SP_ RAMS_WSS_C ontent_IRB _Applicati on_DB_2_0” , should b e the one mapped to the “/site s/IRBAppli cations” s ite collec tion. | |
567 | Check the “Remove Co ntent Data base” opti on shown b elow, and then click on “Ok” b utton at t he bottom of the pag e. | |
568 | ||
569 | For conten t database -> Point SP back to original content da tabase by running th e followin g PowerShe ll in the SharePoint PowerShel l console. Example b elow is fo r SQA use appropriat e server I D for Prod uction env ironment. | |
570 | Mount-SPCo ntentDatab ase -Name SP_RAMS_WS S_Content_ IRB_Applic ations_DB -WebApplic ation vaww .sqa.ram.m sp. DNS -DatabaseS erver vaph iramsql61. DNS | |
571 | To remove the deploy ed content database from SQL S erver: | |
572 | Connect to the datab ase server vaphirams ql21 for P roduction environmen t and run the follow ing script to remove the deplo yed conten t DB: | |
573 | ||
574 | USE [maste r] | |
575 | GO | |
576 | DROP DATAB ASE [SP_RA MS_WSS_Con tent_IRB_A pplication _DB_2_0] | |
577 | GO | |
578 | ||
579 | 6.5.2 REST ORE RAMS U SER DB | |
580 | The follow ing steps should be performed by the Dat abase Admi nistrator. | |
581 | For User D atabase -> Copy “RA MS_Prod_fu ll.bak” fr om the sha red direct ory noted earlier in SQL step 3 (e) of s ection 4.6 to the lo cal server directory D:\2-0_Ba ckups\Rest oringBACKU PSET. If t he directo ry does no t exist, c reate it. Remember t his locati on will be used as t he ‘From D isk’ locat ion in the next step . | |
582 | Open “Rest oreDatabas eRAMS.sql” in a new query wind ow. | |
583 | Or Copy an d paste th e below st atements t o a new qu ery window . The back up and log file name s will var y dependin g on the e nvironment . Example below is f or SQA. | |
584 | USE [maste r] | |
585 | RESTORE DA TABASE [RA MS] | |
586 | FROM DISK = N'D:\2- 0_Backups\ RestoringB ACKUPSET\R AMS_R2-0_S QA_Full.ba k' | |
587 | WITH FILE = 1, MOV E N'RAMS' TO N'G:\Pr ogram File s\Microsof t SQL Serv er\Data\RA MS.mdf', | |
588 | MOVE N'RAM S_log' TO N'L:\Progr am Files\M icrosoft S QL Server\ Logs\RAMS_ log.LDF', | |
589 | NOUNLOAD, REPLACE, STATS = 5 | |
590 | GO | |
591 | Note: Modi fy the loc ation path in three places wit hin the sc ript that are highli ghted in b old Red to reflect t he proper location o f the foll owing item s: | |
592 | Current lo cation of backup fil e shown as N'D:\2-0_ Backups\Re storingBAC KUPSET\RAM S_R2-0_SQA _Full.bak' (Make su re to sele ct correct backup fi le “RAMS_P rod_full.b ak”). | |
593 | Data file location s hown as N' G:\Program Files\Mic rosoft SQL Server\Da ta\RAMS.md f'. (.mdf file locat ion) | |
594 | Log file l ocation sh own as N'L :\Program Files\Micr osoft SQL Server\Log s\RAMS_log .LDF'. (.L DF file lo cation) | |
595 | Right clic k within t he query w indow and choose “Co nnection”. Next, ch oose “Chan ge Connect ion”. A “ Connect to Server” w indow will appear. | |
596 | Select “Da tabase Eng ine” as th e Server T ype. | |
597 | Select the correct i nstance na me for Ser ver Name: vaphiramsq l61 | |
598 | Click the “Connect” button. | |
599 | Click Pars e in ssms to validat e the quer y. | |
600 | ||
601 | Click the “Execute” button at the top of the toolb ar. | |
602 | Make sure script exe cuted succ essfully. | |
603 | You will s ee the fol lowing mes sages: | |
604 | “Processed xxx pages for datab ase ‘RAMS’ , file ‘RA MS’ on fil e 1.” | |
605 | “Processed xxx pages for datab ase ‘RAMS’ , file ‘RA MS_log’ on file 1.” | |
606 | “RESTORE D ATABASE su ccessfully processed xxx pages in xxx se conds” und er the “Me ssages” bo x. | |
607 | “Query exe cuted succ essfully.” at the bo ttom of th e query wi ndow. | |
608 | Refresh SQ L Server I nstance. | |
609 | Verify con nection to RAMS data base by ru nning “SP_ WHO” comma nd in new query wind ow | |
610 | 6.6 Rollb ack Verifi cation Pro cedure | |
611 | Once the B ack-out/Ro ll procedu re is comp lete a smo ke test wi ll be perf ormed by t he Sustain ment Team and the VA to verify RAMS is o perating t o the stan dards prio r to the i nstallatio n. |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.