Monthly Backup Recovery and Restoration Process Design Document

Monthly Backup, Recovery and Restoration Process Design
AMCBANK Engineering Team

September 2010
Version 1.0
This document provides an overview of the design related to Monthly Data Backup, Storage,
Restoration and Recovery processes which are part of FR5.4 Monthly under One XXXXX Business
Intelligence (AMCBANK) Integrated Customer Relationship Analysis (ICRA).
1.1 Bulleted lists and numbered lists

FR5.4 is a process for backup, storage, restoration and data recovery as per Source System. Due to
this the AMCBANK environment can be restored to normal processing easily whenever a data issue
arises.
The objective of the design is to take the Monthly backup of all the Source Systems data, store and
restore the same based on the requirement.
Monthly backed up data is stored for 13 months.
This document is specific to Monthly backup and restoration process.

The Source System level process is defined in this document. The
process may not be fully applicable during recovery, therefore, it is
required to take care based on the impact and case by case scenario.
1.2 Overview
The scope of this document is the Technical details for FR5.4 Monthly processing from the AMCBANK
(ICRA) Detailed Requirements document. The following are the details of the requirement:
1) Extract and retain Monthly full files from the Source Systems (that is all records) to populate
month-end tables. This process:
a)
Expedi
te
s
th
e
re
co
ve
ry
or
co
rre
cti
on
pr
oc
es
se
s
b)
Facilit
at
es
th
e
re
co
nci
liat
io
n
to
st
an
da
rd
m
on
th
en
d
re
po
rts
or
fin
an
cia
l
re
po
rts
2) Retain copies of the Source System and Monthly extracts as per the following:
Monthly snapshot data should be retained for 13 months
3) The system should also support the purging of data based upon the aforementioned data
retention parameters, or additional parameters established at the local or regional level
This Backup and Restore process is mainly designed to rerun the cycles from the required date. This
result and data files are mainly for Support Teams only and not for the business users.
This activity is not applicable to restore the Initial Cycle data. If there is
any issue with the Initial Cycle data, it is required to start from the
beginning of the cycle.
This activity is not applicable to restore the History tables.
If there is any issue with History data, it is required to rebuild the
warehouse (WH) with Daily backup data process and complete the
required process.
2 Monthly backup process and flow
This topic illustrates a high level process flow diagram for Monthly Data Backup and Restore
processes.
2.1 Pre-job requirements

Refer to the following assumptions before the script run:
General prerequisites:
Scripts are run on Monthly basis on the last day of the month and after completion of Daily
cycle
Physical Storage Requirement: This current Backup and Archive process backups
accumulated data every month from all the Source Systems. It consumes more memory.
Ensure that high volume of memory space is available in DataStage or UNIX server before
starting this activity. The volume of backup file size is based on the site (Country or Region).
Individual Solution tables are not included as part of this backup and recovery process.
Table Backup process prerequisites:
Daily Cycle should be completed successfully
InputFile_AMCBANK_Monthly_BKP_Process file should be available in specified directory
($prmDirLandingBkp) which is a mandatory file to run the Table Backup script.
Archive process prerequisites:
Daily Cycle should be completed successfully to take the backup of the Daily files for
consolidation process (Daily Accumulated files) which are being used for Monthly Process
Table Backup script should be completed and .ixf files should be generated successfully for all
the required source tables
External system, OHC system, HUB system provides Monthly data files (Full image of
data).These files should be available in the specified directories.
All filelist files should be available in the specified directory ($prmDirLandingBkp) which are
mandatory files to run the scripts.
The following files should be available at $prmDirLandingBkp with valid entries:
1) Basel_Monthly_filelist
2) External_Monthly_filelist
3) HMI_Monthly_filelist
4) XXXXX_Net_Monthly_filelist
5) OHC_Monthly_filelist
6) Parameter_Monthly_filelist
2.2 Process flow diagram
This topic provides a general process flow diagram for Monthly Backup process.
Generalized flow for backup:
The following figure displays the generalised flow for Monthly Backup process:
Figure 1: Process flow diagram for backup process
The Backup, Archive scripts and DB Import or Export scripts are placed as part of Monthly Control M
schedule which runs at the end of every month.
Generalized process for backup
AMCBANK_Monthly_BKP_Process.sh
Refer to the following points regarding the script, AMCBANK_Monthly_BKP_Process.sh:
This script exports the table data to .ixf files and the same files are archived by
AMCBANK_Monthly_Archive_Process.sh script.
This script runs on a Monthly basis
This script backups the following Source System tables:
HUB tables
HUB_REM/GPS (These tables are part of HUB system)
BASEL tables
IFAI tables
HUBODS tables.
Previous Source System tables are mentioned in

InputFile_AMCBANK_Monthly_BKP_Process. It creates .ixf files in
specified directory. The .ixf file name format is mentioned as
{SourcesystemName}_{TableName}.ixf
For example: BASEL_HEW_CRR.ixf. Here, Source System name is
BASEL and Table name is HEW_CRR.
Generalized process for archive and purging:
AMCBANK_Monthly_Archive_Process.sh
Refer to the following points regarding the script, AMCBANK_Monthly_Archive_Process.sh:
This script runs after completion of AMCBANK_Monthly_BKP_Process.sh
.ixf Files - Archive process: It picks .ixf files according to Source Systems from specified
directory and tar them as one file. It further compresses and moves to archive directory for
recovery process. Monthly ixf Output files are generated by the following scripts:
$prmDirdatabkp/AMCBANK_Monthly_IFAI_ixf.
$Process_date.tar.gz
$prmDirdatabkp/AMCBANK_Monthly_BASEL_ixf.
$prmDirdatabkp/AMCBANK_Monthly_HUBODS_ixf.
$prmDirdatabkp/AMCBANK_Monthly_HUB_ixf.
Script archives export message files (for future reference), which are
generated while creating the .ixf files.
$prmDirlogbkp/AMCBANK_Monthly_ixf_msgs.$Process_date.tar.gz
$Process_date holds cycle date and it is in format of YYYY-MM
Monthly Flat Files - Archive process: It picks all Monthly source flat files from respective
directories based on Source System Input filelist and builds into single tar file for each Source
System. It further compresses all tarred files and moves to Archive directory. Refer to the
following Input files:
Basel_Monthly_filelist
External_Monthly_filelist
HMI_Monthly_filelist
XXXXX_Net_Monthly_filelist
OHC_Monthly_filelist
Parameter_Monthly_filelist
Monthly Output files generated by script:
$prmDirdatabkp/AMCBANK_Monthly_OHC.$Process_date.tar.gz
$prmDirdatabkp/AMCBANK_Monthly_BASEL.$Process_date.tar.gz
$prmDirdatabkp/AMCBANK_Monthly_XXXXX_Net.$Process_date.tar.gz
$prmDirdatabkp/AMCBANK_Monthly_PARAMETER.$Process_date.tar.gz
$prmDirdatabkp/AMCBANK_Monthly_EXTERNAL.$Process_date.tar.gz
$prmDirdatabkp/AMCBANK_Monthly_HMI.$Process_date.tar.gz
Daily Accumulate files - Archive process: Script picks all Daily Archive files (that are generated by
Daily Backup and Archive process) for specified date. It further builds into single tar file for each
Source System.
Suppose specified date is 2010-06 then it picks all 30 June month
Daily archived files for particular Source System.
For example: For BASEL system Daily archived files:
AMCBANK_Daily_BASEL.2010-06-01.tar.gz
--------------------------------------------------
-------------------------------------------------
Script tars previous 30 files as one tar file
(AMCBANK_Daily_Accumulate_BASEL.$Process_date.tar) for BASEL
system.
Daily Accumulated files generated by script:

$prmDirdatabkp/AMCBANK_Daily_Accumulate_CARM.$Process_date.tar
$prmDirdatabkp/AMCBANK_Daily_Accumulate_BASEL.$Process_date.tar
$prmDirdatabkp/AMCBANK_Daily_Accumulate_XXXXX_Net.$Process_date.tar (It holds
only one file i.e Last day file of month; It has full image of data).
$prmDirdatabkp/AMCBANK_Daily_Accumulate_PARAMETER.$Process_date.tar (It holds
only one file i.e Last day file of month; It has full image of data).
$prmDirdatabkp/AMCBANK_Daily_Accumulate_HMI.$Process_date.tar
Script picks all log files which are generated by Monthly Cycle and archiving those for future
reference and same is purging based on Retention period. Log File:
$prmDirlogbkp/AMCBANK_Monthly_log.$Process_date.tar.gz
$Process_date holds cycle date and its in format of YYYY-MM

$prmDirdatabkp is a data archive directory parameter; it holds the data
archive directory path.
$prmDirlogbkp is a log archive directory parameter; it holds the Log
archive directory path.
Purging Process for Old files: Apart from archiving the input files,
AMCBANK_Monthly_Archive_Process.sh script also checks the already backed up Monthly
files and deletes them if their Retention Period is more than 13 months. Retention Period is
passed as parameter to the script. The format YYYY-MM refers to the year and month part. For
example: 2010-06 for June 2010.
Pseudo Code for Retention: If mtime** of file is older than the Retention Period, delete the
Archive files, else retain the Archive files in the same location. ** mtime is the modification time
of the file.
2.2.1 HUB, HUB-REM and GPS Source System (iSeries)
The following figure illustrates the HUB, HUB_REM and GPS Monthly Backup process for ICRA:
Figure 2: HUB, HUB_REM and GPS Monthly Backup process
HUB/HUB-REM/GPS:
HUB-REM and GPS are part of HUB System
On Monthly basis, after the post critical batch backup, HUB team loads HUB tables which are
required for backup and archive process into new staging libraries. New Staging libraries are
created as part of the Backup process.
DBA script (AMCBANK_stg_load_recovery.sh) is run to extract data from the previous
iSeries library to the pSeries Monthly Staging Schema. New pSeries Monthly Staging Schema
is created as part of the Backup & Recovery Process.
DBA Export or Import scripts identifies the critical batch data changes based on the
MODE_FLAG filter which has a value of Blank, P for Primary records and S for shadow
updates or with help of other transaction date/time fields wherever applicable and import the
same to pSeries Monthly Schema.
If the table has MODE_FLAG columns then the script reads all the latest records based on
MODE_FLAG = P and condition
If the table does not have MODE_FLAG Columns and it belongs to the Transaction journal/
table then all the records are filtered based on Posting Date or Capture date
If the table does not have MODE_FLAG Columns and if it does not belong to Transaction
tables then full images are taken as a backup
The pSeries tables are backed up to .ixf files and are archived and stored for 13 months
HUBODS:
For the tables which are directly getting loaded from HUBODS tables, the backup process is
different. New Monthly jobs are created which captures the full image into the reprocessing
tables of the Monthly schema. Please refer to Appendix for the list of new jobs.
New jobs have the PPN_DT condition changed to <= (#prmDate#) so that full image till month
end is captured. Target reprocessing tables is in Write Truncate mode in order to capture the
fresh image of data till month end.
These jobs run after the regular cycle is completed and as part of the Monthly backup process
The previous reprocessing tables are backed to IXF files and is archived and stored for 13
months.
Archive Script generates the following output files for HUB/HUBODS Source System:
AMCBANK_Monthly_HUB_ixf.YYYY-MM.tar.gz
AMCBANK_Monthly_HUBODS_ixf.YYYY-MM.tar.gz
2.3 OHC Source System

The following figure illustrates OHC Monthly Backup Process for ICRA:
Figure 3: OHC Monthly Backup Process
OHC (One XXXXX Cards):

OHC team provides a Monthly feed of the OHC files and is available at /data/ds/<project
name>/landing/monthly/ directory
These files are of binary format
These files are at regional level and have same names as Daily files
UNIX script AMCBANK_Monthly_Archive_Process.sh picks up these files from monthly
landing directory. Then, tar and zip these files with YYYY-MM suffix at the end to differentiate
each month file in the archive directory /data/ds/<project name>/archive/monthly/ directory
in AMCBANK area
Archived monthly files are retained for 13 months; any file which is older than 13 months is
purged
Script generates the following output file for OHC Source system:
AMCBANK_Monthly_OHC.YYYY-MM.tar.gz
2.4 CARM Source System

The following figure illustrates CARM Monthly Backup Process for ICRA:
Figure 4: CARM monthly backup process
CARM (Credit Approval and Risk Management System):

In CARM there is no monthly feed and monthly process. Therefore, as part of Monthly backup
process, entire months Daily archive files (archived by Daily archive process) are taken as
source for backup.
These files are of .gz (compressed) format, since the Daily archive script compresses the Daily
files
Daily archived files are present in Daily archive directory
UNIX script AMCBANK_Monthly_Archive_Process.sh picks up all the Daily archive files
(AMCBANK_Daily_CARM.YYYY-MM*.tar.gz) from the Daily archive directory and tars them to
corresponding accumulated monthly file
Archived accumulated monthly files are retained for 13 months and any files which are older
than 13 months are purged
Script generates following output file for CARM Source System:
AMCBANK_Daily_Accumulate_CARM.YYYY-MM.tar
2.5 BASEL Source System
The following figure illustrates BASEL Monthly Backup Process for ICRA:
Figure 5: BASEL Monthly Backup Process
BASEL:
For BASEL we have both Daily files and monthly files as sources. In addition, we need to
backup the HEW_PD and HEW_CRR WH tables data in order to retain proper history.
AMCBANK_Monthly_BKP_Process.sh script exports the HEW_PD and HEW_CRR tables
data to ixf files and moves these files to backup landing directory
AMCBANK_Monthly_Archive_Process.sh script picks up the WH ixf files from the backup
landing directory, tars and zips them to a single monthly ixf file
AMCBANK_Monthly_Archive_Process.sh script picks up the monthly BASEL files from the
landing directory, tars and zips them to a single monthly file
AMCBANK_Monthly_Archive_Process.sh script picks up the archived Daily files from the
Daily archive directory and tars them to an accumulated monthly file
The previously mentioned monthly version files (ixf, Daily and monthly) are archived to monthly
archive directory
Archived Monthly files are retained for 13 months and any files which are older than 13 months
are purged.
Script generates the following output file for BASEL Source System:
AMCBANK_Monthly_BASEL_ixf.YYYY-MM.tar.gz
AMCBANK_Monthly_BASEL.YYYY-MM.tar.gz
AMCBANK_Daily_Accumulate_BASEL.YYYY-MM.tar
2.6 HMI Source System

The following figure illustrates HMI Monthly Backup Process fro ICRA:
Figure 6: HMI Monthly Backup Process
HMI (XXXXX Management Information System):

For HMI we have both Daily file (product data) as well as Monthly files.
Daily files which were archived by the Daily Archive process and placed in archive directory
and Monthly files which are present in landing directory are considered for Monthly backup and
archive process.
AMCBANK_Monthly_Archive_Process.sh script picks up the Daily archived files from the
Daily archive directory and tars them to a accumulated Monthly file.
AMCBANK_Monthly_Archive_Process.sh script picks up the Monthly HMI files from the
landing directory, tars and zips them to a single Monthly file.
Above Monthly version files (Daily and Monthly) are archived to Monthly archive directory.
are purged.
Script generates following output files for HMI Source system.
AMCBANK_Monthly_HMI.YYYY-MM.tar.gz
AMCBANK_Daily_Accumulate_HMI.YYYY-MM.tar
2.7 XXXXXnet Source System
The following figure illustrates XXXXXnet Monthly Backup Process for ICRA:
Figure 7: XXXXXnet Monthly Backup Process
XXXXX Net:
For XXXXXnet we have both Daily files as well as Monthly files
The Daily files has complete image till date, so for Monthly backup and archive purpose we
need to consider only the month end Daily files which were archived by the Daily archive
process
Monthly files are readily available in the landing directory
AMCBANK_Monthly_Archive_Process.sh script picks up the month end archived Daily files
from Daily archive directory and tars them to an accumulated Monthly file
AMCBANK_Monthly_Archive_Process.sh script picks up the Monthly files from landing
directory, tars and zips them to a single Monthly file.
Previously Monthly version (Daily and Monthly) files are archived to Monthly archive directory
The Archived Monthly files are retained for 13 months and any files which are older than 13
months are purged.
Script generates the following output files for XXXXX_Net Source System:
AMCBANK_Monthly_XXXXX_Net.YYYY-MM.tar.gz
AMCBANK_Daily_Accumulate_XXXXX_Net.YYYY-MM.tar
2.8 IFAI Source System
The following figure illustrates IFAI Monthly Backup Process for ICRA:
Figure 8: IFAI Monthly Backup Process
IFAI (Invoice Finance Application International):

We get the feed for IFAI through manual CDC process and in this process IFAI Load tables are
loaded from iSeries tables and has full image of the data
For Monthly backup and archive process previous mentioned Load tables should be backed up
to ixf files and archived to Monthly archive directory
AMCBANK_Monthly_BKP_Process.sh script backs up the Load tables to .ixf files and moves
them to backup landing directory.
AMCBANK_Monthly_Archive_Process.sh script picks up the IFAI .ixf files from backup
landing directory, tars and zips them to a single Monthly .ixf file and moves it to Monthly archive
directory.
Archived Monthly ixf files are retained for 13 months and any files which are older than 13
months are purged
Script generates the following output file for IFAI Source System:
AMCBANK_Monthly_IFAI_ixf.YYYY-MM.tar.gz
2.9 External Source System
The following figure illustrates External Monthly Backup Process for ICRA:
Figure 9: External Monthly Backup Process
External System:
External Source System (like Insurance) provides the Monthly files in Monthly landing directory.
AMCBANK_Monthly_Archive_Process.sh script picks up the Monthly files from the Monthly
landing directory (needs confirmation), tars and zips them into a single mentioned Monthly files
and place them in Monthly archive directory.
are purged.
BASEL is also part of External Source System but the backup and archive process differs from
other External Source systems. Please refer to BASEL backup and archive process for more
details.
Script generates the following output file for EXTERNAL Source System:
AMCBANK_Monthly_EXTERNAL.YYYY-MM.tar.gz
External Source systems Team has to provide consolidate Monthly

External files and corresponding directory location for the Monthly
Backup and Recovery Process
2.10 AMCBANK User Reference Data
The following figure illustrates AMCBANK User Reference Data Monthly Backup Process for ICRA:
Figure 10: AMCBANK User Reference Data Monthly Backup Process
AMCBANK User Reference Data (Parameter files):

To facilitate generation of Dashboard Report, AMCBANK CMB takes the following reference
data which are input by end users (as they are not available in the underlying Banking
Systems).
Customer Segment Grouping, Product Grouping, Relationship Manager (RM) Hierarchy,
Report Access Control, Report Dimension and Target Customer List
The reference data is stored in the pSeries. Local IT support assists the users to upload their
reference data into reference tables with ETL processing
We get both Daily and Monthly feed for this system
Daily files have full image of data, so only month end Daily files are considered for Monthly
backup and archive process. These Daily files are archived by the Daily archive script
AMCBANK_Monthly_ Archive_Process.sh script picks up the Daily archived parameter files
from Daily archive directory and tars them into accumulated Monthly file.
AMCBANK_Monthly_Archive_Process.sh script picks up the parameter Monthly files from
landing directory, tars and zips them to a single Monthly file.
Monthly version (Daily and Monthly) files are moved to Monthly archive directory
are purged.
Script generates the following output files for AMCBANK User Reference Data:
AMCBANK_Monthly_PARAMETER.YYYY-MM.tar.gz
AMCBANK_Daily_Accumulate_PARAMETER.YYYY-MM.tar
3 Monthly Archive process and flow
This topic provides details about Monthly Archive process and flow.
3.1 Pre-job requirements

The following are the assumptions before the Backup and Archive scripts run:
All the scripts should be completed to archive log files.
Backup script should be completed and .ixf files should be generated successfully.
OHC Data and files (OHC_Monthly_filelist)should be available
HMI Monthly files (HMI_Monthly_filelist) should be available.
XXXXX Net Monthly files (XXXXX_Net_Monthly_filelist) should be available.
BASEL Monthly files (Basel_Monthly_filelist) should be available
External data file(External_Monthly_filelist) should be available
Parameter Monthly files(Parameter_monthly_filelist) should be available
HUB (HUBODS) Monthly Files (InputFile_AMCBANK_Monthly_BKP_Process) should be
available.
3.2 HUB, HUB REM and GPS Data Archiving

Backup all the pSeries Monthly staging tables to IXF files
Retrieve all the .ixf files from the backup landing path($prmDirLandingBkp)
Combines all the previous IXF files to a single file named (AMCBANK_Monthly_HUB_ixf.
<Process date>.tar) using the UNIX tar command and saves at the path $prmDirdatabkp
(parameter from parameter file)
Compress the tar file using the UNIX gzip command (AMCBANK_Monthly_HUB_ixf.
<Process date>.tar.gz).
Compress the all the HUB ODS tar file using the UNIX gzip command
(AMCBANK_Monthly_HUBODS_ixf. <Process date>.tar.gz)
Removes all the HUB and HUBODS .ixf files from original location.
3.3 OHC Data Archiving

Retrieves all the OHC files (from OHC_Monthly_filelist) from Monthly landing directory
($prmDirLandingOHC).
Combines all the OHC files into a single file named (AMCBANK_Monthly_OHC. < Process
date>.tar) using the UNIX tar command and saves in the path $prmDirdatabkp (parameter
from parameter file)
Compress the tar file using the UNIX gzip (AMCBANK_Monthly_OHC. <Process
date>.tar.gz) command.
Removes all the OHC files from original location
3.4 CARM files Archiving
Retrieves all the Daily archived files with AMCBANK_Daily_CARM.<YYYY-MM>* extension
from the $prmDirdatabkp path.
Combines all the CARM archived Daily files into a single file named
(AMCBANK_Daily_Accumulate_CARM.<Process date>.tar) using the UNIX tar command
and saves at the path $prmDirdatabkp (parameter from parameter file).
3.5 BASEL Data Archiving

Retrieves all the BASEL*.ixf extension files from landing backup directory
Combines all the BASEL*.ixf files into a single file named
(AMCBANK_Monthly_BASEL_ixf.<Process date>.tar) using the UNIX tar command and
saves at the path $prmDirdatabkp (parameter from parameter file)
Compress the tar file using the UNIX gzip (AMCBANK_Monthly_BASEL_ixf.<Process
date>.tar.gz) command.
Removes all the BASEL*ixf files from original location
Retrieves all the AMCBANK_Daily_BASEL.<YYYY-MM>* extension files from the
$prmDirdatabkp path
Combines all the AMCBANK_Daily_BASEL.<YYYY-MM>* files into a single file named
(AMCBANK_Daily_Accumulate_BASEL.<Process date>.tar) using the UNIX tar command
and saves at the path $prmDirdatabkp (parameter from parameter file)
Retrieves all the BASEL Monthly files (from Basel_Monthly_filelist) from landing directory.
Combines all the BASEL Monthly files into a single file named
(AMCBANK_Monthly_BASEL.<Process date>.tar) using the UNIX tar command and saves
at the path $prmDirdatabkp (parameter from parameter file) Compress the tar file using the
UNIX gzip (AMCBANK_Monthly_BASEL.<Process date>.tar.gz) command.
Removes all the BASEL Monthly files from original location.
3.6 HMI Data Archiving

Retrieves all the Daily archived files with AMCBANK_Daily_HMI.<YYYY-MM>* extension from
the $prmDirdatabkp path
Combines all the AMCBANK_Daily_HMI.<YYYY-MM>* files into a single file named
(AMCBANK_Daily_Accumulate_HMI. <Process date>.tar) using the UNIX tar command and
saves at the path $prmDirdatabkp (parameter from parameter file).
Retrieves all the Monthly files (from HMI_Monthly_filelist) from landing directory.
Combines all the HMI Monthly files into a single file named (AMCBANK_Monthly_HMI.
(parameter from parameter file).
Compress the tar file using the UNIX gzip command (AMCBANK_Monthly_HMI. <Process
date>.tar.gz).
Removes all the HMI Monthly files from original location.
3.7 XXXXX Net Data Archiving
Retrieves the month end Daily archived files (these have full image) with
AMCBANK_Daily_XXXXX_Net <YYYY-MM>* extension from the $prmDirdatabkp path.
Combines all the XXXXX_Net archived Daily files into a single file named
(AMCBANK_Daily_Accumulate_XXXXX_Net.<Process date>.tar) using the UNIX tar
command and saves at the path $prmDirdatabkp (parameter from parameter file)
Retrieves all the XXXXX_Net Monthly files (from SBC_Net_Monthly_filelist) from landing
directory
Combines all the XXXXX Net Monthly files into a single file named
(AMCBANK_Monthly_XXXXX_Net.<Process date>.tar) using the UNIX tar command and
Compress the tar file using the UNIX gzip (AMCBANK_Monthly_XXXXX_Net.<Process
date>.tar.gz) command
Removes all the XXXXX Net files from original location.
3.8 IFAI Data Archiving

Retrieves all the files with IFAI*.ixf extension from the backup landing
path($prmDirLandingBkp)
Combines all the IFAI*.ixf files into a single file named (AMCBANK_Monthly_IFAI_ixf.
(parameter from parameter file)
Compress the tar file using the UNIX gzip command (AMCBANK_Monthly_IFAI_ixf.
<Process date>.tar.gz)
Removes all the IFAI*.ixf files from original location.
3.9 External Systems Data Archiving

Retrieves all the External files (from External_Monthly_filelist) from landing directory
Combines all the External system files into a single file named
(AMCBANK_Monthly_EXTERNAL.< Process date>.tar) using the UNIX tar command and
Compress the tar file using the UNIX gzip (AMCBANK_Monthly_EXTERNAL.<Process
Removes all the External system files from original location.
3.10 AMCBANK User Reference Data Archiving

Retrieves all the month end AMCBANK_Daily_PARAMETER.<YYYY-MM>* extension files
(contain full image) from the $prmDirdatabkp path
Combines all the AMCBANK_Daily_PARAMETER.<YYYY-MM>* files into a single file named
(AMCBANK_Daily_Accumulate_PARAMETER.<Process date>.tar) using the UNIX tar
command and saves at the path $prmDirdatabkp (parameter from parameter file)
Retrieves all the Parameter Monthly files (from Parameter_filelist) from landing directory
Combines all the Parameter Monthly files into a single file named
(AMCBANK_Monthly_PARAMETER.<Process date>.tar) using the UNIX tar command and
Compress the tar file using the UNIX gzip (AMCBANK_Monthly_PARAMETER.<Process
Removes all the Parameter Monthly files from original location.
3.11 Log files Archiving

Retrieves all the log files with .log extension present in the following paths
$prmDirlogavl (parameter from parameter file) e.g. /data/ds/dpr_gacpt_dev/joblogs/bn
<Script Directory >/ <country code>.
Combines all the log files into a single file named (AMCBANK_Monthly_log.<Process
date>.log.tar) using the UNIX tar command and saves at the path $prmDirlogbkp (parameter
from parameter file) e.g. /data/ds/dpr_gacpt_dev/scripts/bn/bkp/logs
Compress the tar file using the UNIX gzip command (AMCBANK_Monthly_log.<Process
date>.log.tar.gz).
Removes all the log files from original location
3.12 List of Archive files

At the end of backup and archive process, a script generates the following list of Archive files:
AMCBANK_Monthly_HUB_ixf. <Process date>.tar.gz
AMCBANK_Monthly_HUBODS_ixf. <Process date>.tar.gz
AMCBANK_Monthly_IFAI_ixf.<Process date>.tar.gz
AMCBANK_Monthly_BASEL_ixf.<Process date>.tar.gz
AMCBANK_Monthly_OHC.<Process date>.tar.gz
AMCBANK_Monthly_BASEL.<Process date>.tar.gz
AMCBANK_Monthly_XXXXX_Net.<Process date>.tar.gz
AMCBANK_Monthly_PARAMETER.<Process date>.tar.gz
AMCBANK_Monthly_EXTERNAL.<Process date>.tar.gz
AMCBANK_Monthly_HMI.<Process date>.tar.gz
AMCBANK_Daily_Accumulate_PARAMETER.<Process date>.tar
AMCBANK_Daily_Accumulate_CARM.<Process date>.tar
AMCBANK_Daily_Accumulate_BASEL.<Process date>.tar
AMCBANK_Daily_Accumulate_XXXXX_Net.<Process date>.tar
AMCBANK_Daily_Accumulate_HMI.<Process date>.tar
AMCBANK_Monthly_ixf_msgs.<Process_date>.tar.gz
AMCBANK_Monthly_log.<Process_date.tar>.gz
The script performs the following functions:
1) Checks whether any of the following archived gzip files are older than the retention period
2) Removes all the gzip files which are older than retention period (13 months)
Process date is the recovery date from the cycle.

4 Restoration process
This topic provides information about the process diagram and steps to be implemented as part of
restoration process.
Generalized flow for Recovery:
The following figure provides process diagram and steps to be implemented as part of restoration
process:
Figure 11: Recovery Process in General
Please implement the following steps:

1) Update the HEW_SUMM_DATE_REF table to have the recovery month and year before
running the recovery process.
2) Run the parameter update script (AMCBANK_Monthly_Recovery_PrmFileUpdate.sh) to
update the parameter files so that the combined jobs pick up the right file from the archive
folder.
Command line:
sh
/data/ds/<Project>/scripts/AMCBANK_Monthly_Recovery_PrmFileUpdate.sh
/data/ds/<Project>/scripts/<ctcd> bir2_wh_Rec_new.param
InputFile_AMCBANK_Recovery_PrmFileUpdate R
Here R indicates Recovery.
You need to update the following entries in InputFile_AMCBANK_Recovery_PrmFileUpdate:

prmDirLanding = /data/ds/<project name>/archive
prmDirXm l = /data/ds/<project name>/archive
prmDirLandingOHC = /data/ds/<project name>/archive
prmDirLandingMTHLY = /data/ds/<project name>/archive
prmDate = YYYY-MM-DD
prmDate should be recovery month date.
4.1 Check points for Restoration process:

1) Put the Daily and Monthly cycles on hold, the regular Daily/Monthly cycle is kept on hold until
the successful completion of recovery/restore process. It is mainly because the same Staging
and WH schema is used for recovery process.
2) Take backup of all the Staging, Interface and XREF and History tables
3) Verify the Backup and Archive data availability and required access privileges
4) Make sure the availability of the required team support like DBA, Admin and others
5) Before starting Restoration process; backup and clean the data from all the Staging, Interface,
WH, Summary and SNAP tables
6) Please do not run any other process along with this recovery process otherwise it may lead to
confusion and cause unknown issues
7) After successful restoration of required files; execute the corresponding jobs based on the
predefined dependency (You can use Control M Dependency document for this)
8) After completion of the source jobs; please validate the data population to staging tables and
monitor the ETL job logs for warnings/record drop
9) After completion of Recovery process, make sure to restore the Staging, Interface and History
Tables from the backup data taken before recovery process
10) You can refer to Control-M draft files and Subject Area Design Documents for the job flow and
further execution.
MKS: \Source Code and Scripts\ETL Solutions\Control-M\
5 Recovery process
This topic provides information about the Recovery process which is followed after successful
completion of Restoration process.
During original run all the external files are read from following
directory
Server Path: \<project>\landing\<CountryCode>\
But during recovery process all the files are available in backup
landing directory, so it is required to update all the parameters to read
the data from the following folder during recovery process.
Server Path: \<project>\landing\<CountryCode>\ <Recovery>
Prerequisites for consideration:

Restoration Process is only applicable to restore the data based on the user requirement and it has to
be taken care case by case. The following steps required to taken care at each and every day during
recovery process without any failure:
1) Analyze the issue and complete the end to end Impact analysis.
2) Identify the required Source System recovery process.
3) Once the recovery requirements are clear regarding the recovery process, do the necessary
changes to the Input table list file so that only required tables are recovered and restored.
4) Put the Daily and Monthly cycles on hold, the regular Daily/Monthly cycle is kept on hold until
the successful completion of recovery/restore process; its mainly because of the same Staging
and WH schema used for recovery process.
5) Backup all the Staging, Interface, Xref and History tables without failure. Those table backup
are restored after successful completion of recovery process.
6) Apart from the Point# 4, advise to taking backup of all the remaining tables like all the WH,
Summary and snapping tables. This backup copy helps if not able to recovery back the data.
This copy can be used for comparison of recovery process result.
7) After successful completion of backup activity. Clean up the Staging and Interface for the
recovery process.
8) Clean up the WH tables based on the impact analysis for the records populated on or after
recovery process start date. So those records are repopulated during recovery process
9) Clean up the SUMM and SNAP tables based on the impact analysis for the records populated
on or after recovery cycle process date.
10) HEW_SUMM_DATE_REF table should be loaded with required date corresponding to recovery
process (year and month).
11) All the parameter files should contain correct prm_date for load_dt population
12) If there is a need to recover a particular subject area then do the impact analysis to see how
many sources systems need to be recovered and accordingly recover the required Source
Systems (Example: For the recovery of Customer data we have to recover XXXXX.net in
addition to HUB)
13) STG_SUMM_JOB_PARM && SK_CODE_GEN tables are one time load by DBA, It is
manually required to populate the data before and during recovery if required to update
Surrogate Key.
These backups are not effective if the Source Systems have provided any incorrect data during the
regular cycle, for this case the Source Systems should provide the corrected data and the recovery
process should be run accordingly (run Partial/Full Initial load based on the situation).
5.1 HUB, HUB-REM and GPS Source System (iSeries)

The following figure illustrates the HUB Monthly Recovery Process for ICRA:
Figure 12: HUB Monthly Recovery Process
Refer to the following points regarding HUB Monthly Recovery Process:

1) HUB-REM and GPS source tables are part of the HUB (iSeries) Source System and library.
2) Validate the impact analysis and identify the required Source System, tables and date for
recovery, if HUB data is impacted then follow the steps to recover HUB data
3) Make sure all the prerequisites are met
4) After the Untar process script is completed, the IXF files are available at backup landing
directory
5) Reload the data into staging schema from .ixf backup files
6) Source jobs (list provided in appendix) which use HUBODS and ORDNDTA library tables as
source are force OKd since the Monthly backup process already backed up the target tables of
these source jobs. The list of jobs which needs to be force okd can be found in the HUBODS
inventory list attached in the Appendix topic.
7) For HUBODS recovery, load the reprocessing tables with the corresponding months recovery
data from the backup IXF files
8) The LOAD_DT for all the records processed during recovery cycle are end of month date of
recovery month
9) Using the initial draft (CTM_SWHCPTICRA_INITIAL.DRF) Control-m file run all the HUB
related jobs till interface tables are loaded. Find the updated draft files from MKS
10) Run all the required Source and combine jobs based on the impact
11) Run all the required Load jobs and populated WH tables based on the impact
12) When other systems are also being recovered, wait till the corresponding interface jobs are
done and then run the WH, Summary and Snap Shot process to load WH, SNAP and
SUMMARY tables
13) After successful completion of restore and recovery process, run the Reconciliation process to
make sure the matching reconciliation result after recovery and restore process.
5.2 OHC
The following figure illustrates the OHC Monthly Recovery Process for ICRA:
Figure 13: OHC Monthly Recovery Process
Refer to the following points regarding OHC Monthly Recovery Process:

recover, if OHC data impacted than follow the steps to recover OHC data
2) Make sure all the Prerequisites (topic 3.1/3.2/3.3) are met.
3) Run the AMCBANK_Monthly_Untar_Process.sh script with OHC_MONTHLY.txt which untars
and unzips the required OHC files to the backup folder. Find more details in Generalised topic.
4) Once Untar script is completed, please check the backup landing directory and make sure the
required files to start the recovery process are restored. Use the Source System wise excel
sheet attached in the appendix for verification.
5) Update the OHC and Combine job parameter values to read the data from backup directory.
The parameter values should be given while running the DS jobs.
6) Validate the required data availability in input files, Lookup tables, Parameter values.
7) Run the OHC source jobs with help of OHC Control M Draft (CTM_SWHCPTICRA_OHC.DRF)
file. This file is available in MKS. MKS: \Source Code and Scripts\ETL Solutions\Control-M\
8) Run OHC Source jobs and itll split Regional (*.bin) level data into Country Level(*.txt) which is
required for our OHC and Combine job process from Initial Load draft file
(CTM_SWHCPTICRA_INITIAL.DRF). Run the jobs under the groups PCPTTHOHCF_G and
PCPTTHOHCS_G from the Control-M file
9) Validate required HUB (Customer and Arrangement) data availability, since OHC depended
with HUB Customer information
done and then run the WH, Summary and Snap Shot process to load corresponding WH,
SNAP and SUMMARY tables
11) Once the combined group is completed, depending upon the number of Source System
recovery run the load, snap and summary jobs in sequential order
make sure that the data is reconciling after recovery and restore process.
5.3 CARM
The following figure illustrates CARM Recovery Process for ICRA:
Figure 14: CARM Recovery Process
Refer to the following points regarding CARM Recovery Process:

recover, if CARM data impacted than follow the steps to recover CARM data.
2) Make sure all the Prerequisites (Section 3.1/3.2/3.3) are met.
3) As of now there is no Monthly table using CARM Source data.
4) Run the AMCBANK_Monthly_Untar_Process.sh script with CARM_MONTHLY.txt for
unzipping and untarring
sheet attached in the appendix for verification
6) Validate the required data availability in input files, Lookup table, Parameter values and Target
tables
7) Run the CARM related jobs pointing the source file location to the backup landing directory
where the files are present
done and then run the WH process to load WH tables
After successful completion of restore and recovery process, run the Reconciliation process to make
sure that the data is reconciling after recovery and restore process.
5.4 BASEL
The following figure illustrates BASEL Monthly Recovery Process for ICRA:
Figure 15: BASEL Monthly Recovery Process
Refer to the following points regarding BASEL Monthly Recovery Process:

recover, if BASEL data impacted than follow the steps to recover BASEL data
2) Make sure all the Prerequisites (Section 3.1/3.2/3.3) are met
3) Run the AMCBANK_Monthly_Untar_Process.sh script with BASEL_MONTHLY.txt for Untar
and unzip
a) Restore one month previous data as of recovery month to the HEW_PD and HEW_CRR
WH tables from the Archive Driectory with help of new script.
b) Script fetches the (recovery month 1) ixf file from the archive directory and load into
HEW_PD and HEW_CRR tables. For example if recovery date is Mar 2010 then the Ixf file
picked is of Feb 2010.
c) On successful Unzip process, it untars the unzipped file. Untarred files are automatically
placed in landing Monthly backup directory.
5) Run the BASEL Combined jobs to load the corresponding Interface tables. In case of the
combined jobs which use Daily files, run the jobs in chronological order. For Example 1st day
Daily file should copied in landing directory and run the BASEL combine jobs and populate into
corresponding Interface tables than continue with 2nd day file.
6) Run the load jobs to load the WH tables.
7) Make sure all the Monthly backup files are available in the respective folder which we are
mentioned in the Parameter files
8) Complete all other Source System dependent jobs and run BASEL Monthly jobs from Control
M draft file CTM_SWHCPTICRA_SUMM.DRF
9) Validate the data in the BASEL Monthly Interface tables like all the data are populated and
Load_DT for each of the records
done and then run the Summary and Snap Shot process to load SNAP and SUMMARY tables.
5.5 External
The following figure illustrates External Monthly Recovery Process for ICRA:
Figure 16: External Monthly Recovery Process
Refer to the following points regarding External Monthly Recovery Process:

recover, if External or data files data impacted than follow the steps to recover External and
data file source data with help of Monthly files
2) Make sure all the Prerequisites (Section 3.1/3.2/3.3) are met
3) Run the AMCBANK_Monthly_Untar_Process.sh script with EXTERNAL_MONTHLY.txt to
restore the accumulated and archived external files to the landing backup directory by running
the Untar script
5) Run the External related combined jobs pointing the source file location to the backup landing
directory where the restored files are present
7) Validate and confirm the recovery process and data population before start the ongoing
process.
5.6 XXXXXnet
The following figure illustrates XXXXX.net Recovery Process for ICRA:
Figure 17: XXXXX.net Recovery Process
Refer to the following points regarding XXXXXnet Monthly Recovery Process:

recover, if XXXXXnet data impacted than follow the steps to recover XXXXXnet data
3) Run the AMCBANK_Monthly_Untar_Process.sh script with XXXXXNET_MONTHLY.txt
5) If there is no impact on WH tables then we can directly proceed to Step2 since none of the WH
tables are used as source or lookup other than Xref and HEW_SUMM_Date_Ref tables.
6) Make sure the following XXXXXnet tables are backed up and cleaned up before starting the
recovery process. Since the list of tables used for CDC process to populate change data.
a) VSXACCT
b) VSXACPF
c) VSXCUST
d) VRSCLAC
e) VSXICSS
7) Make sure the following HUB tables which are used as lookup are loaded with data till recovery
date:
a) SSBKLSP
b) EWIUCRSP
c) CUST_POT_MAP
8) Run the XXXXXnet related jobs pointing the source file location to the backup landing directory
where the restored files are present.
9) Using the initial draft (CTM_SWHCPTICRA_INITIAL.DRF) Control-m file run all the Initial load
jobs and populated into corresponding WH tables. Updated draft files can get from MKS
10) Populate the data into WH table and make sure the Daily file (rsclac0.bin) is available for the
Monthly process.
11) Using the Monthly draft (CTM_SWHCPTICRA_SUMM.DRF) Control-m file run all the Monthly
jobs and populated into corresponding SNAP and Summary tables. Updated draft files can get
from MKS
recovery run the load, snap and summary jobs in sequential order.
Step 1 mainly for WH table recovery process; however in XXXXXnet

Monthly (Step 2) process is partially independent with Daily process.
All the Monthly tables can be recovered independently with out WH
table recovery until unless Xref and HEW_SUMM_DATE_REF tables
are having valid records.
5.7 IFAI
This topic provides details about IFAI Recovery Process as displayed in the following figure:
Figure 18: IFAI Recovery Process

Refer to the following points regarding IFAI Monthly Recovery Process:
recover, if IFAI data impacted than follow the steps to recover IFAI data
3) Run the AMCBANK_Monthly_Untar_Process.sh script with IFAI_MONTHLY.txt.
5) Import the IFAI table related data to the corresponding Load tables. Clean up the Staging and
CHG tables. Since manual CDC process is run as initial load process, we need to clean up the
Staging tables and CHG tables. Currently manual CDC process is being used for IFAI system.
Load tables to be loaded from backup ixf files:
a) FOIETWK_LOAD
b) FCLETWK_LOAD
c) FCLEAWK_LOAD
d) FCCYMWK
e) FDRETWK_LOAD
Staging tables to be cleaned up:
a) FOIETWK
b) FCLETWK
c) FCLEAWK
d) FDRETWK
Change tables to be cleaned up:
a) FOIETWK_CHG
b) FCLETWK_CHG
c) FCLEAWK_CHG
d) FDRETWK_CHG
6) Make sure the following HUB tables which are used as lookup are loaded with data till recovery
date.
a) DDACMSP
b) SSCUSTP
c) SSGMCPP
d) SSCYIFP
e) SSCYIFP
7) Run the jobs with Initial draft file(CTM_SWHCPTICRA_INITIAL.DRF) except for the
AMCBANK_Monthly_Recovery_stg_load.ksh script.
8) Run all the IFAI source and combined jobs. Source jobs should be run pointing the source file
location to the backup landing directory where the restored files are present.
9) Validate the data in the Interface table and make sure the LOAD_DT for all the records
done and then run the WH, Summary and Snap Shot process to load WH, SNAP and
SUMMARY tables.
5.8 HMI
The following figure illustrates HMI Recovery Process for ICRA:
Figure 19: HMI Recovery Process
Refer to the following points regarding HMI Recovery Process:

recover, if HMI data impacted than follow the steps to recover HMI data
3) Run the AMCBANK_Monthly_Untar_Process.sh script with HMI_MONTHLY.txt
sheet attached in the appendix for verification.
5) Also make sure the HUB table SSCUSTP which is used as lookup in the Source to Interface
jobs are loaded with data till recovery date. These get loaded as part of HUB recovery process.
6) Run the HMI related jobs pointing the source file location to the backup landing directory where
the restored files are present.
recovery run the load, snap and summary jobs in sequential order.
After successful completion of restore and recovery process, run the Reconciliation process to make
sure that the data is reconciling after recovery and restore process.
5.9 AMCBANK User Reference Data (Parameter Files)
The following figure illustrates AMCBANK User Reference Data Recovery Process for ICRA:
Figure 20: AMCBANK User Reference Data Recovery Process
Refer to the following points regarding AMCBANK User Reference Data Recovery Process:
recover, if AMCBANK User Reference data impacted than follow the steps to recover
2) Make sure all the prerequisites are met.
3) Run the AMCBANK_Monthly_Untar_Process.sh script with
AMCBANKUSERREF_MONTHLY.txt
5) Run all the AMCBANK User Reference (Parameter) related jobs pointing the source file
location to the backup landing directory where the restored files are present
7) Validate and confirm the recovery process and data population before start the ongoing
process
5.10 Check points for Recovery process

Put the Daily and Monthly cycles on hold, the regular Daily/Monthly cycle is kept on hold until
the successful completion of recovery/restore process; its mainly because of the same Staging
and WH schema used for recovery process
Take backup of all the Staging, Interface and xref and History tables
Verify the Backup and Archive data availability and required access privileges
Make sure the availability of the required team support like DBA, Admin and others
Before starting Recovery process; backup and clean the data from all the Staging, Interface,
WH, Summary and SNAP tables
Please do not run any other process along with this recovery process otherwise it may lead to
confusion and cause unknown issues
After successful restoration of required files; execute the corresponding jobs based on the
predefined dependency (You can use Control M Dependency document for this)
After completion of the source jobs; please validate the data population to staging tables and
monitor the ETL job logs for warnings/record drop
After completion of Recovery process, make sure to restore the Staging, Interface and History
Tables from the backup data taken before recovery process.
You can refer to Control-M draft files and Subject Area Design Documents for the job flow and further
execution.
MKS: \Source Code and Scripts\ETL Solutions\Control-M\
6 Appendix
Source System analysis details
Source_Systemwise_
Files_Tables.xls
Library information details
Library Analysis.xls
Consolidate information for the jobs and tables
Consolidate
J ob_table_file Details.xls
HUBODS Inventory:
\\
HYDNFIL06.corp.capgemini.com\users$\nanali\My Documents\OHBI\FR5.4\Monthly\HUBODS_Inventory.xls
Control sheet for change details
ICRA Integration
Change Control For FR5.4 Monthly.xls
Backup and Recovery Script Execution flow

BKP Script Sample Command line:
sh /data/ds/dpr_gacpt_dev/scripts/AMCBANK_Monthly_BKP_Process.sh
/data/ds/dpr_gacpt_dev/scripts/bn bir2_wh.param
InputFile_AMCBANK_Monthly_BKP_Process INST<1 to N>
The following figure illustrates the Backup Process for AMCBANK ICRA:
Figure 21: Backup Process

Recovery Script Sample Command line:
sh
/data/ds/dpr_gacpt_dev/scripts/AMCBANK_Monthly_Recovery_Process.sh
InputFile_AMCBANK_Monthly_BKP_Process ALL INST<1 to N>
To restore the entire Source System data need to mention the Source
System code as ALL for all instances.
To restore the Source system wise Data use following command lines.
To restore the IFAI Source System:
sh
InputFile_AMCBANK_Monthly_BKP_Process IFAI INST1
To restore the BASEL Source System:
sh
InputFile_AMCBANK_Monthly_BKP_Process BASEL INST2
To restore the HUBODS Source System:
sh
InputFile_AMCBANK_Monthly_BKP_Process HUBODS INST3
To restore the HUB Source System:
sh
InputFile_AMCBANK_Monthly_BKP_Process HUB INST<4 to N>
The following figure illustrates the Recovery Process for AMCBANK ICRA:
Figure 22: Recovery Process

7 Points for Consideration
All the OHC Monthly Files is placed into Landing\Monthly folder for backup process
All data contains same LOAD_DT after Recovery process
Parameter files and input files have to updated during recovery process
The entire source input Files / Tables list have to update if there any new tables are files newly
add into our product.
The Monthly backup Files contain accumulative data from the beginning of the cycle; it
occupies more volume of space in the server. Required to provide more space for Archive
Process
Retention period required to define by the business based on the requirement and storage
space availability. Advise to maintain minimum 13 Months, So retention period parameter
should have = 396 days ( Retention period should be in number of days format)
Based on the available Development environment (till Interface table level) tested all the scripts
manually, its required to test till WH and Summary table levels.
This process defined in Source system level during recovery based on the issue or scenario
advice to customise the input file/table and process.
All the process should run with same ETL/DB users id and all the files should have required
privileges.
As part of HUB Monthly Backup, HUB Source system copies the required month end data into
New Staging library for our backup and recovery process.
HUB new staging library should available for Monthly Backup and Archive process.
The delivery contains code and components providing the Backup and recovery Process only.
It has to customise based on the situation.
Considered End of the HUB Critical batch is Day1 images. After completion of HUB Critical
process changes are considered as Day2 data.
There is no Monthly data process for External Source system. Its required to provide external
source for accumulative and consolidate data file for backup and recovery process.
XXXXX net, HMI and IFAI gets full image of data for the Daily process, so the last day of the
month Daily cycle input file contains full image of data for backup process. Its confirmed by
HSTA CMB Development team.
We are taking HUB data based on Mode Flag = P and Blank
STG_SUMM_JOB_PARM && SK_CODE_GEN tables are one time load by DBA, Manually
required to populate the data before during recovery if required to update Surrogate Key.
Individual Solution tables and jobs are not part of this Monthly Backup and recovery process.

Monthly Backup Recovery and Restoration Process Design Document

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Monthly Backup Recovery and Restoration Process Design Document

Transféré par

Droits d'auteur :

Formats disponibles

Monthly Backup, Recovery and Restoration Process Design

AMCBANK Engineering Team

1.1 Bulleted lists and numbered lists

This document is specific to Monthly backup and restoration process.

2.1 Pre-job requirements

Figure 1: Process flow diagram for backup process

HUB_REM/GPS (These tables are part of HUB system)

Previous Source System tables are mentioned in

$Process_date holds cycle date and it is in format of YYYY-MM

Daily Accumulated files generated by script:

$Process_date holds cycle date and its in format of YYYY-MM

Figure 2: HUB, HUB_REM and GPS Monthly Backup process

2.3 OHC Source System

Figure 3: OHC Monthly Backup Process

OHC (One XXXXX Cards):

2.4 CARM Source System

Figure 4: CARM monthly backup process

CARM (Credit Approval and Risk Management System):

Figure 5: BASEL Monthly Backup Process

2.6 HMI Source System

Figure 6: HMI Monthly Backup Process

HMI (XXXXX Management Information System):

Figure 7: XXXXXnet Monthly Backup Process

Figure 8: IFAI Monthly Backup Process

IFAI (Invoice Finance Application International):

Figure 9: External Monthly Backup Process

External Source systems Team has to provide consolidate Monthly

Figure 10: AMCBANK User Reference Data Monthly Backup Process

AMCBANK User Reference Data (Parameter files):

3.1 Pre-job requirements

3.2 HUB, HUB REM and GPS Data Archiving

3.3 OHC Data Archiving

3.5 BASEL Data Archiving

3.6 HMI Data Archiving

3.8 IFAI Data Archiving

3.9 External Systems Data Archiving

3.10 AMCBANK User Reference Data Archiving

3.11 Log files Archiving

3.12 List of Archive files

Process date is the recovery date from the cycle.

Figure 11: Recovery Process in General

Please implement the following steps:

Here R indicates Recovery.

You need to update the following entries in InputFile_AMCBANK_Recovery_PrmFileUpdate:

prmDate should be recovery month date.

4.1 Check points for Restoration process:

Prerequisites for consideration:

5.1 HUB, HUB-REM and GPS Source System (iSeries)

Figure 12: HUB Monthly Recovery Process

Refer to the following points regarding HUB Monthly Recovery Process:

Figure 13: OHC Monthly Recovery Process

Refer to the following points regarding OHC Monthly Recovery Process:

Figure 14: CARM Recovery Process

Refer to the following points regarding CARM Recovery Process:

Figure 15: BASEL Monthly Recovery Process

Refer to the following points regarding BASEL Monthly Recovery Process:

Figure 16: External Monthly Recovery Process

Refer to the following points regarding External Monthly Recovery Process:

Figure 17: XXXXX.net Recovery Process

Refer to the following points regarding XXXXXnet Monthly Recovery Process:

Step 1 mainly for WH table recovery process; however in XXXXXnet

Figure 18: IFAI Recovery Process

Figure 19: HMI Recovery Process

Refer to the following points regarding HMI Recovery Process: