Posted on Nov 7, 2020 by eTeam Inc.
Job Title: Backup Architect
Location: Amsterdam, NL
Type: Permanent role
- Client is in execution of a Cloud Transformation. The Cloud Transformation entails the creation of a resilient and secure Landing Zone making use of Amazon Web Services (AWS). Upon successful creation of the landing zone the two data centres in Ireland will, step by step, migrate onto the Landing Zone.
- One out of the 36 building blocks from the landing zone (see appendix) concerns Back-Up Management.
- Back-up management is typically one of the services for which the Landing Zone has to provide a standardized service based on the Client policies and provide a pre-selected solution (or multiple) which can then be used by the applications making use of the Landing Zone.
- Before the building of the Back-up Management can commence a deeper understanding of the requirements, design, architecture, solutions, and regulatory requirements is needed. We call this the
- Backup Management Strategy.
- As Client currently does not have the capacity nor a deep understanding of different backup solution available to create the Backup Management Strategy Client decided to request the support of a supplier.
- This document details the scope, key components of the back-up strategy and expected timelines regarding this request.
- Scope of the back-up management strategy
The Back-up Management Strategy should at least address/include the following:
- Covering all Client's entities including Client Corporation
- Relevant different (application) technology platforms/stack like AS400, Infinite-I, Windows, Linux, SQL, DB2, AWS, Azure and SAP
- Adhering to the regulations of Client's entities eg being able to remove personal identifiable data resulting from GDPR compliancy, local legislation, DNB requirements etc.
- Existing contracts that are in place between local entities and Digital & IT for the existing backup services
- Key components of the back-up management strategy
Items to be part of the Back-up Management strategy should at least be:
- Service definition defining a (limited) number of service levels
- Retention, backup and restore policies
- Cost management
- Architecture of the backup
- Tool selection including a comparison of functional, non-functional, cost and risk. Costs not only including licensing of the backup but also detailing cost of eg storage and network traffic (TCO calculation)
Expectations of your proposal
- Resume(s) who could execute backup management requirement, high level design, low level design and LP approval by interacting various