Sunteți pe pagina 1din 5

Refresh Test/Dev/Staging Database from

Production Database















1 Overview

Purpose of this document to highlight and document the steps needed to refresh backend
database on Test/Dev/Staging environment from Production environment for BMC Remedy
ITSM application

This document highlights the steps for Test database refresh



2 Refresh Production DB to Test DB
2.1 Software/Hardware specifications
2.1.1 Database Specifications
Production Environment Test Environment
Oracle 11g R2 on AIX Oracle 11g R2 on AIX
Tablespace ARSYSTEM Tablespace ARSYSTEM
Remedy DB Admin - ARAdmin Remedy DB Admin - ARAdmin

2.1.2 Application Specifications
Production Environment Test Environment
BMC Remedy ARS 7.6.04 SP2
BMC Atrium Core 7.6.04 SP2
BMC Remedy ITSM 7.6.04 SP2
BMC SRM 7.6.04 SP2
BMC SLM 7.6.04 SP1
BMC RKM 7.6.04 SP2
BMC Remedy ARS 7.6.04 SP2
BMC Atrium Core 7.6.04 SP2
BMC Remedy ITSM 7.6.04 SP2
BMC SRM 7.6.04 SP2
BMC SLM 7.6.04 SP1
BMC RKM 7.6.04 SP2
Server Group Install Server Group Install
Running on Windows Server 2008 R2 SP1-
64bit
Running on Windows Server 2008 R2 SP1-
64bit

2.2 Steps
1. Take the backup of all custom, overlay AR System objects from Test System using
BMC Remedy Developer Studio/User Tool addition to Test DB backup
2. Export all the necessary metadata from Test System like:
a. AR System License Key from Server Information - Add/Remove Licenses
b. Export all AIE Instances from EIE:BackUpLoadFlag form in *.arx format
including all the fields
c. All data from AR System Server Group Operation Ranking form in *.arx
format including all the fields
d. Take a note of the configuration from Email mailbox configuration, ARDBC
Plug-in and AREA LDAP configuration forms



e. Open SHARE:Application_Properties and search for Help file URLs and take a
note of it
f.
g. All other custom form metadata which needed to preserved or retained even
after refresh
3. Communicate to DBA to start the refresh activity from Prod to Test, it may needed to
stop AR services running on all the servers of Test System (server1n)
4. Once refresh activity completed, Test System ARAdmins password will be overwritten
with the Prod password, if both the passwords are not same then open SQL Plus tool
and change the ARAdmin users password
RDP to system where you Oracle Client installed, open Command Prompt
Type: sqlplus ARAdmin@<OracleSIDName>
Enter the Password (If refreshed with Prod DB, enter Prods ARAdmin DB
password)
Once successfully connecting to SQL client, type password (To reset the
password)
It will ask you the Old Password, enter that (If refreshed with Prod DB, enter
Prods ARAdmin DB password)
Enter New Password (Put the password maintained by you for Test System)
5. Change the password in ar.cfg file, as it contains encrypted ARAdmins (DB-Password)
encrypted password, which needs to be refresh. This steps needs to be repeat for all
the servers where AR System is running
6. After putting the password in ar.cfg file, start the AR System Service and other
necessary services, except Email Engine service, as we refreshed the data from Prod, it
may be having still pending messages which get copied to Test System, and can leads
to confusion to users if triggered/sent

7. Once all the servers in server group UP and running, login to each server via BMC
Remedy User Tool with the user having admin rights and configure the licenses, which
copied in Step 2.a.

8. Open the AR System Admin console and then Server Information, click on Database
tab, put the ARAdmin password same as put in ar.cfg file and save, it will ensure that
password encrypted in ar.cfg file.
9. Change the passwords for Demo & appadmin (If its there), if exists in the environment,
as they will be having prod passwords
10. Open AR System Email Mailbox Configuration form, search the entries and do
necessary changes like:
a. Replace Prod email address with Test email address
11. Check the configuration on AREA and ARDBC Plug-In configuration forms and validate
with the data backed-up in step 2.d
12. Open SHARE:Application_Properties and search for help file URLs and do the
necessary changes, as it may be overwritten with Prod help file URLs
13. Open following forms and change server references in respective fields for all the
entries:
Form Name Field Name Old Value New Value













14. Open CTM:People form and Set Notification Availability= No for all the people, if you
dont have it enabled on Test Environment
15. Open AR System Email Messages form and clear all pending messages, then Start the
Email Engine service on Test System
16. Login to BMC Remedy Import Tool and import the *.arx files (taken in step 2.b & 2.c)
in respective forms
17. Open Active Link named: ANA:Analytics:OpenURL (If you are using Analytics)
And replace the Prod link with Test link
And Save it
18. Stop the Tomcat Services, flush the caches and plugin cache and then restart it.
CAI:AppRegistry (CAI
Application Registry)
Server <ProdServerName> <TestServerName>
PDL:ApplicationSettings HostName
<ProdServerName> <TestServerName>
Report Server
<ProdServerName> <TestServerName>
SRM:AppInstanceBridge SR Server
App Instance Server
<ProdServerName> <TestServerName>
AR System Searches
Preference
Server
<ProdServerName> <TestServerName>
AR System User
Preference
Server Login List
<ProdServerName> <TestServerName>
AIS:GlobalPreferences AIS Cell Host
<ProdServerName> <TestServerName>

S-ar putea să vă placă și