FUJ00176531
FUJ00176531
From: Kuypers, Hannah[/O=EXCHANGELABS/OU=EXCHANGE ADMINISTRATIVE GROUP.
(FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=9F97CCEECAB741 1C9F504473CEB62758-
KUYPERS, HA]
Sent: Fri 28/01/2022 7:20:49 AM (UTC)
To: Gauntlett, Paul{”
Subject: FW: Problem statement IRE19 DCs
Mistry, Manish:
Paul, Manisha, please see below fyi. Note this is not for onward communication.
I have asked Steve for details on the comms already sent to POL and will let you know when I get the info.
Kind Regards,
Hannah
From: Browell, Steven 4
Sent: Wednesday, January 26, 2022 5:02 PM
To: Kuypers, Hannah
Cc: Wilson, Simon ¢
Subject: RE: Problem statement IRE19 DCs
; Walton, Daniel <
Hannah,
I am not aware of any formal statement having been made on this specific matter but if one is needed then I can get
Legal to craft one — with my help. We did recently explain the matter of gaps in the Audit Archives in a formal
communication to POL and it was mentioned implicitly in that response. We still await POL’s response to that comms.
It is true that the Audit Archive stores in our 2 DCs for the Horizon time period (2007-2010) are different so for this
specific point, IRE11 and IRE19 are not mirrored. However, we are currently only aware of one difference in the 2
Audit Archive stores and we have copied that specific data from IRE19 to IRE11. Therefore, based on what we know
today, there is a full Audit Archive copy in both DCs but in subtly different formats.
l asked Ed/Gerald to give me a VROM to create a true and full mirror and it looks like we could be looking at a piece of
work spanning 4 months (including procurement, provisioning, testing, copying) as we will need new hardware**. I do
not know when the AWS $3 work is due to start and finish but it would seem likely that the AWS S3 work will need to
take the Audit Archive for 2007-2010 from both DCs to ensure it has all data. In so doing, it would become pointless to
mirror the 2 DCs for this Audit Archive content.
I would prefer that this information was not just sent to POL but handled carefully to avoid unnecessary concern. I do
believe that POL know this so it will not be news. I would just advise that we avoid making written or attributable
statements without prior approval so we do not send incomplete or inconsistent messages.
** this makes our response to the extending of the audit archive CWO very challenging too which I am sure is being
handled by the relevant PM.
To: Browell, Steven ‘ Walton, Daniel
Cc: Wilson, Simon}
Subject: Problem statement IRE19 DCs
FUJ00176531
FUJ00176531
Hi Both,
The below came up on a call with POL yesterday and there was an ask whether or not we have issued a problem
statement to note the fact our DCs do not hold identical data, as was initially assumed? This will likely impact how we
respond to the Tactical Audit CWO, and POL have asked our PM to raise as a project risk...
Kind Regards,
Hannah
From: Gauntlett, Paul ¢_
Sent: Thursday, January 20, 2022 12:47 PM
To: Mistry, Manisha <
Subject: FW: RTQSRO003638 Quote Required
"} Kuypers, Hannah ¢
FYI — relates to the issue we discussed on the call earlier
From: Ashford, Edward <.
Sent: Thursday, Janua:
To: Barnes, Gerald GRO, Post Office Account Change Management
< ; : “>; Arain,
Tariq
Ce: Guy, Jam ; Post Office Account
UNIX Team <i Browell, Steven
< I, Steve (BRAO1)
8 Quote Required
Hi,
It's a bit complicated at the moment. Gerald and I have a request from Steve Browell around remediation of the Audit
Gaps, and one possible solution is to run a retrieval on ARC201 for all "Bootle only" tracks (mainly correspondence
servers, i.e Riposte) and robocopy them to ARC202 which will result in them being stored in the 19PROD CSHE, and in
parallel running a retrieval on ARC202 for all "Wigan only" tracks (ditto) and robocopy them to ARC201 for storage in
the 11PROD CSHE.
This is obviously less than doubling the storage used as we're only considering October 2007 to September 2010
(approx), but we do not have an accurate estimate of the requirement.
The Audit Tactical project is also looking to make a copy of the data in AWS S3 CDE at some stage. Ideally this would
sooner rather than later.
We are well past CSHE EOSL (31-DEC-2020) and I don't think we can offer any guarantees on the reliability of the CSHE
beyond end March 2022, so really I think we should be turning down this request and asking POL to accelerate the
Audit Tactical programme, at least the initial part of it which adds the $3 storage as additional data stores for Belfast
ARC201 and ARC202 and initiates the (well known) process of copying the CSHE data to the new stores.
Regards
Ed
From: Barnes, Gerald <"
Sent: Wednesday, January 19, 2022 2:29 PM
FUJ00176531
FUJ00176531
To: Post Office Account Change Management < - Evans, Steve
Arain, Tariq
; Guy, James
Well as long as Unix prepare their pre-impacts for the Eternuses it may be OK.
Regards,
Gerald Barnes
From: Post Office Account Change Management <__
Sent: Wednesday, J.
To: Barnes, Gerald
+. _P
Subject: RE: RTQSRO003638 Quote Required
Gerald, Steve,
The last one was pre-impacted:
HNG-X/HNGA CP2680 — Preservation of Horizon Data until 30 April 2022
Regards
Ken Westfield
Business Change Manager, Program & Project services, NWE
Fujitsu
Please consider the environment - do you really need to print this email?
From: Barnes, Gerald ¢_
Sent: Wednesday, Januar
To: Evans, Steve (BRAO1)
Cc: Post Office Account Change Management
Account UNIX Team <
Subject: RE: RTQSRO003638 Quote Required
Guy, James <
Hi,
FUJ00176531
FUJ00176531
I do not think this was pre-impacted before.
As I wrote there is little issue with the audit configuration file but there may be an issue with disk space on
the Eternuses. This needs to be properly considered by the Unix team.
Regards,
Gerald Barnes
From: Evans, Steve (BRAO1)
Sent: Wednesday, January 19, 2022 2:20 PM
To: Barnes, Gerald ¢~
-
“b; Arain, Tariq Kumar, Sunil1
Post Office
Cc: Post Office Account Change Management 1
Account UNIX Team <7"
Subject: RE: RTQSRO003638 Quote Required
Thanks Gerald
Can I ask Sunil to act as solution owner for the CP, and support James Guy in prepping it.
@Barnes, Gerald — what was the previous CP for this the last time?
It was possibly a pre-impacted CP to which we can refer
Regards,
Steve
Stephen Evans
Solutions Architecture and Business Requirements
Fujitsu Services - Post Office Account
2021 Forward Schedule of Annual Leave:
None Planned
GRO
https://www.fujitsu.com/uk,
He:
P Be GREEN, keep it on the SCREEN
From: Barnes, Gerald ¢_
Sent: Wednesday, Janua:
To: Evans, Steve (BRAO1)
<.
Cc: Post Office Account Change Management
Account UNIX Team ¢
Subject: RE: RTQSRO003638 Quote Required
Arain, Tariq Kumar, Sunil
GRO, _>; Post Office
Hi Steve,
This is a very easy thing from an audit perspective. It is just increasing by another year (in hours) the
FUJ00176531
FUJ00176531
NumExtraHoursToKeeptTracks in the EternusPurger.config file.
However you also need to run it past the Unix team (Ed Ashford is most knowledgeable) to confirm that the
Eternuses on which the files are stored has the capacity to store another year of data. This bit is totally outside of my
control.
So my bit is very easy (deliver a new EternusPurger.config) but Ed’s may not be.
Regards,
Gerald Barnes
From: Evans, Steve (BRAO1) ¢
Sent: Wednesday, January 19, 2022 2:07 PM
To: Arain, Tariq <. >; Barnes, Gerald <
Kumar, Sunil1
Cc: Post Office Account Change Management <"
Subject: FW: RTQSRO003638 Quote Required
Gerald
Can you please confirm that an extension to the prevention of Audit Archive deletion, 30 April 2023, would still
be within your remit.
Perhaps you could brief Sunil on what needs to be done here, to support a CP (James Guy is the PM),
and what would need to be done to implement.
Regards,
Steve
Stephen Evans
Solutions Architecture and Business Requirements
Fujitsu Services — Post Office Account
2021 Forward Schedule of Annual Leave:
None Planned
Sent: Wednesday, January 19, 2022 11:21 AM
To: Kuypers, Hannah
Ce: Smith, Claire ¢ $
Subject: FW: RTQSRO003638 Quote Required
; Evans, Steve (BRAO1)
Hannah, Steve,
We have just received this “confidential “ Cr come through from POL - which we had been expecting
FUJ00176531
FUJ00176531
We have performed this activity for several years — last time PM was Mick R and Techie was Gerald B
Hannah — who do you want to handle this time?
Steve — Still ok to use Gerald B
Regards
Ken Westfield
Business Change Manager, Program & Project services, NWE
kshire. RG12 8SN
From: Post Office ServiceNow{_
Sent: Wednesday, January 19, 2022 11:15 AM
To: Post Offi
‘Management < GRO >
GRO }
juote Required
Hi Fujitsu,
Request RTQSR0003638 has been assigned to you.
Please review and provide a quote.
RTQSR Number: RTQSR0003638
POREQ Number: POREQO005601
Request title: Preservation of data on the HNG-X System until 30 April 2023
Request Category: Operational Change
Operational budget code: 100000
Background: Post Office have requested that Fujitsu Services continue to preserve data (including
Post Office Personal Data) generated on the HNG-X System as per work order CWO0395b until 30
FUJ00176531
FUJ00176531
April 2022.
Request Summary: Post Office would like Fujitsu to continue to preserve data for a further 12
months i.e. Until 30th April 2023.
Acceptance Criteria: Fujitsu Services will preserve Horizon data until the 30 April 2023
Fujitsu Services delays the purging of Horizon data from 30 April 2022 and extends it to 30 April 2023
This is an automated email sent from ServiceNow, please contact the team directly if you have any
questions or concerns.
Kind Regards,
Request To Quote Team
No 1 Future Walk
West Bars
Chesterfield
S49 1PF
Ref:MSG6985833