Minutes of Meeting

Date: 25-Jan-2018
Location: Amogh Sir’s cabin, 17th floor, YBL Mumbai
Attended By:  Jayesh Sawant
 Veeresh Kattimath
 Sagar More
 Dimple Rane
 Ashish Gaikar
 Chirag Kothari
 Amogh Sawant

Points Discussed
1) Application Replication Requirement (File Replication and Sync N.A
Monitoring):

 YBL Requirement is to monitor and sync application files on PR

and DR Servers.
 Perpetuuiti’s DataSync tool capabilities and limitations was
discussed:
(a) It was explained that Datasync is a file replicator only
(b) It was discussed that limitations are : (1) At a point max
150gb of data can be replicated (2) Number of files within
a folder cannot exceed 25000 files in number (3) Datasync
cannot replicate open files
(c) It was also discussed that Data sync is an agent based
utility and JRE is mandatory

2) Application Replication Testing/POC : Jayesh to

initiate/
 It was discussed that application replication will be carried out Perpetuuiti to
for two applications: Custody (Linux Platform) and BI Staging respond
(Windows Platform)
 Jayesh will initiate formal communication for this request on
email and Perpetuuiti team will respond with DataSync
prerequisites

3) Jayesh asked if the following Application Replication requirements are N.A

possible :
(a) Bidirectional mode of data transfer
>> Possible
(b) File level replication:
>> Veeresh clarified data sync is a file replicator but open
files will not be replicated
(c) Replication to any network
>> It is possible
(d) Comprehensive audit file and reporting through log files
(History Tracking)
 >> It is possible
(e) Write order protection
>> No. Datasync is only for file replication. No other tasks
can be performed by Datasync
4) Change in CP UI Dashboard - Online Monitoring of databases and lag: Veeresh
Single consolidated view required of all databases configured in CP
with lag (real-time basis), Veeresh to check feasibility and confirm
5) Jayesh will check and verify the RTOs/RPOs of all applications Jayesh & Jitesh
configured in CP
6) Application Discovery Feature in CP : Perpetuuiti to inform/explain the Perpetuuiti
use of this feature to YBL stakeholders
7) DataLag status reports takes too much time to load. Perpetuuiti team Perpetuuiti
to look into it
8) Isolation Testing by Application owners directly:
Veeresh discussed handing over configured workflows to individual
application owners for executing if isolation testing is required to be
performed by Application owners.
Ashish responded stating application owners will not be executing
workflows. CP team only will function as Maker and Checker for
workflows.
8) CP5 Roadmap: YBL wants to know CP5 planned feature Perpetuuiti
listing/enhancements. Perpetuuiti team to get back on the same
9) CP Memory Utilization Issue RCA: Amogh Sir asked if RCA has been YBL to set up
provided. It was clarified that Perpetuuiti team had provided inputs for meeting
troubleshooting the issue. The last status on this was that a meeting
was to be setup with Nayan.
10) Naming conventions in workflows : It was discussed that specific terms YBL & PTECH
like “Mock” , “Live” should be included in the workflow name for
distinguishing specific workflows