Process flow for Essbase Application Backup
Overview
This post briefly explains the Essbase Application backup process flow for
PlanIT_Sapplication
Pre
requisites
·
Autosys
client should be installed in all the source server (cbisispapp4X4v)
· Source
servers RSA key should be transferred to backup server for user hypbackup (Cbissapp403V)
· SFTP
user (hypbackup) should be created in backup server with home directory (Cbissapp403V:/export/home/hypbackup)
·
JIL
(Job Information Language) should be defined in Autosys server (Work with Autosys Team or raise a ticket (based on client's production process system to schedule JIL)
Process flow
diagram
Essbase Application
Backup will be scheduled using Autosys tool in Autosys server. Autosys server
will trigger the job at specified time in Essbase Server on which Autosys
client is installed. Backup shell scripts will be available on cbispapp414v server from where Autosys client will trigger the
shell scripts.
Once the backup is completed, cbispapp414v server
will hold current day backup data under the path /essbase/hyperion/Backup/PlanIT_S. This
backup data will also be transferred
(SFTP) to the backup server XXXXXapp403V. The backup server Cbisapp413V contains the Daily, Weekly and
Monthly Backup of Essbase Application under the path /essbase/hyperion/PRD_Backup/PlanIT_S/EssbaseApp_Backup
Types of Back up
- Daily Backup will be scheduled every day
except Sunday
- Weekly Backup will be scheduled every
Sunday
- Monthly Backup will be scheduled every
month on 28th
Check List for Back up
- Level - 0 Data Backup
(Level0data.txt)
- Outline file (.otl)
- Calc script (.csc)
- Rule files (.rul)
- Page file (.pag)
- index file (.ind)
- Security file
(.bak,.sec,.cfg)
Essbase
Application Backup Process (GSBapp454v)
Detailed Process:
- The shell script is invoked
which will trigger an e-mail to corresponding Distribution list, alerting the
date and time when the backup started
- Archive the essbase database
in to read only mode
- Take level 0 data backup and
store under the path /essbase/hyperion/products/Essbase/EssbaseServer/app/PlanIT_S/Budget
- Remove the previous backup
using rm command
- Zip the entire application
folder using zip command (/essbase/hyperion/products/Essbase/EssbaseServer/app/PlanIT_S/Budget) and store it in location /essbase/hyperion/Backup/PlanIT_S/Essbase_app.zip
- Zip the Security files
essbase.bak, essbase.cfg, essbase.sec available under the path /essbase/hyperion/products/Essbase/EssbaseServer/bin
and store it in
location /essbase/hyperion/Backup/PlanIT_S/Security.zip
- Zip both the file Essbase_app.zip and Security.zip in to a single file
(eg: Monday.zip, Tuesday.zip)
- Transfer the zip file to
backup server (Cbissapp423V)
- End archive; bring the
essbase in to normal mode
- If there is any error while
running the backup process, it will send out a mail to Distribution list
else mail on successful completion is sent with completion date and time
- Quit
Details of backup shell scripts:
Backup Shell Script will be
available in path: /essbase/hyperion/scripts/
- PlanIT_S_Essbase_Daily_Backup.sh --> runs every day except Sunday
- PlanIT_S_Essbase_Weekly_Backup.sh --> runs every week i.e., on Sunday
- PlanIT_S_Essbase_Monthly_Backup.sh --> runs every month end i.e., on 28th
Log details:
Server contains all the log details which
has been captured during backup process in path /essbase/hyperion/Backup/PlanIT_S/Log and the log file name will be
followed as
<Shell
script name>.<yyyymmdd>.log
Example:
PlanIT_S_Essbase_Daily_Backup.sh.YYYYMMDD.log
PlanIT_S_Essbase_Weekly_Backup.sh.YYYYMMDD.log
Backup server details (XXXXXXV)
xxxxxxv server holds the entire Essbase
Application backup for PlanIT_S application as mentioned below
The server contains daily, weekly
and monthly backup. The backup files will be overwritten if it is already
exists on the server (CBissapp413V)
Flow diagram shows how the backup
files are organized in xxxxxxV
server for PlanIT_S
application
No comments:
Post a Comment