Professional Documents
Culture Documents
Assessment 2 - Practical Demonstration ICTSAS526
Assessment 2 - Practical Demonstration ICTSAS526
Unit Name and Code: ICTSAS526 - Review and update disaster recovery and
contingency plans
To be completed by Trainer
FEEDBACK
Trainer/Assessor :
Assessment item : #2- Practical Demonstration
Due date : Week 3 (Extension upon trainer’s approval only)
o The assessment tasks for the unit assume that you will work in the Information
Technology industry. Case studies/ exercises used in this assessment reflect a
workplace scenario.
o If you are not sure about any aspect of this assessment, please ask for
clarification from your assessor. If the assessment is not satisfactory, the trainer
will allow one more attempt to the assessment item.
The assessment of this Unit will be in a simulated environment where you will be
provided access to:
3. Specific instructions
To do this activity you’ll need:
PCs,
Backup software To do backup or similar software
TASK 1: Scenario
You are an ICT technician. As part of your job role, you are required to back up the
system, restore information, secure the system and information in a stand-alone or
client-server environment.
Your client has advised you that when they were migrating all their data and
applications from disaster recovery environment to the cloud, they acknowledged
the applications and data were too complex and required too much horsepower
and caused significant downtime.
Through the initial analysis, you have identified that your client has two choices:
find a cloud service provider that could cost-effectively deliver the compute needed
to support the business, or move its DR environment to a third-party, on-premise
provider that could accommodate its complexity and horsepower requirements.
In this assessment activity, you are required to read and understand the
information provided above and complete the following activities.
○ Executive summary
○ Findings
○ Lessons learned
● Recommendations
You are required to develop a contingency plan that identifies threats and minimize
down time for business-critical functions in this assessment activity.
Your contingency plan must include the following information:
a. Purpose
b. Applicability
c. Scope
d. Planning principles
e. Assumptions
f. Constraints
g. Concept of operations
h. Notification and activation
i. Recovery operations
j. Return to normal operations
DS-SP-05/23 PRAC-ICTSAS526 V2.1
RTO Provider Code: 91151
CRICOS Provider Code: 02668F Page 7 of 20
You must complete the contingency plan according to the information provided in
the template below.
1 INTRODUCTION
1.1 PURPOSE
This migration of data to the cloud Contingency Plan establishes procedures to recover the
migration of data to the cloud following a disruption. The following objectives have been
established for this plan:
Identify the critical activities, resources, and procedures needed to carry out
operations during prolonged interruptions to normal operations.
Assign responsibilities to designated personnel.
Provide guidance for recovering operations during prolonged periods of interruption to
normal operations.
Ensure coordination contingency planning stakeholders and staff.
The intended audience of migration of data to the cloud Contingency Plan is the project
manager, project team, project sponsor, procurement officer/office, and any senior leaders
whose support is needed to carry out acquisition plans.
1.2 APPLICABILITY
The migration of data to the cloud Contingency Plan applies to the functions, operations,
and resources necessary to restore and resume normal migration of data to the cloud
operations at India. The migration of data to the cloud Contingency Plan applies to State
bank of India and all other persons associated with migration of data to the cloud as
identified in this document.
The migration of data to the cloud Contingency Plan is supported by Amazon Web Services
(AWS), Microsoft Azure.
Various scenarios were considered to form a basis for the plan, and multiple assumptions
were made. The applicability of the plan is predicated on:
Data Volume and Complexity.
Network Bandwidth and Connectivity.
Cloud Service Provider Reliability.
Downtime and Business Impact.
Budget and Cost Management.
1.3.2 Assumptions
This section identifies the statements believed to be true and from which a conclusion was
drawn to define this plan.
1. Data Source and Destination: The plan assumes the availability and accessibility of the
data source and the cloud destination during the migration process.
2. Timeline: The plan assumes a specific migration timeline, including start and end dates,
as well as any critical milestones or phases.
1.3.3 Constraints
This section identifies any limitation that must be taken into consideration regarding the
content of this plan.
1. Bandwidth Constraints: Limited network bandwidth may slow down data transfer to the
cloud, especially for organizations with large volumes of data to migrate.
2. Cost and Budget Constraints: Limited budget or unexpected costs during the migration
can impact the choice of migration strategies and timelines.
2 CONCEPT OF OPERATIONS
2.1 SYSTEM DESCRIPTION AND ARCHITECTURE
System Architecture:
The system architecture for the data migration to the cloud contingency plan typically
consists of the following components:
Data Source: This represents the on-premises data systems, databases, applications, and
files from which the data will be extracted for migration.
Data Transfer: This component encompasses the secure movement of data from the on-
premises environment to the cloud. Various data transfer methods like direct network
transfer, physical data shipment, or specialized data transfer tools may be used.
Cloud Infrastructure: This refers to the target cloud environment where the data will be
stored and accessed. It includes cloud storage services, databases, and other necessary
cloud resources.
Data Validation: After migration, the data should undergo validation to ensure accuracy,
completeness, and integrity. This step involves comparing the migrated data with the source
data to identify any discrepancies.
Monitoring and Logging: The system may include monitoring and logging functionalities to
track the progress of the migration, detect errors, and provide insights into the migration
process.
Functionality:
The functionality of the data migration to the cloud contingency plan revolves around the
seamless and reliable transfer of data while minimizing downtime and ensuring data
integrity. Key functions include:
Automated Data Extraction: To reduce manual effort and errors, the plan may include
tools for automated data extraction from the source systems.
Data Mapping and Transformation: If required, the system should handle data mapping
and transformation to match the format and structure of the data with the cloud environment.
Incremental Data Transfer: To minimize downtime, the system may support incremental
data transfer, where only the changes made since the last migration are moved.
Data Validation: After migration, the plan should include mechanisms for data validation to
verify the accuracy and completeness of the migrated data.
Contingency and Rollback: The plan should define contingency measures, such as
rollback procedures, in case migration encounters significant issues.
By combining these functionalities and components, the contingency plan aims to ensure a
smooth and secure migration of data to the cloud, with minimal disruptions and data integrity
preserved throughout the process. The specifics of the system architecture and functionality
will depend on the organization's requirements, cloud provider, and the complexity of the
migration project.
Deputy CIO:
Name: Shri Prakash Chandra Kandpal
Contact no: 0411144295
2.3 RESPONSIBILITIES
In the event of a disruption or disaster during the data migration to the cloud, the following
individuals, teams, and departments may be trained and responsible for responding and
coordinating recovery operations:
Addressing the initial actions taken to detect and assess damage inflicted by a disruption
involves a well-structured incident response plan that outlines the steps to be taken in case
of any unexpected events. Here are the key items to consider:
Automated Alerts: Implement monitoring and alerting systems that automatically detect
and notify the relevant IT teams when certain predefined thresholds or anomalies are
exceeded. These alerts can trigger immediate response actions.
IT Operations Team: The IT Operations Team is typically the first point of contact for
assessing the disruption. They identify the nature and extent of the issue, conduct initial
Data Migration Team: The Data Migration Team assesses the impact of the disruption on
the migration process and determines if any data integrity issues have arisen. They work
with the IT Operations Team to coordinate recovery efforts.
Failover and Redundancy: If the primary systems are affected, rely on redundant or
failover systems to assess the damage and continue operations.
Automated Alerts: Implement monitoring and alerting systems that automatically detect
and notify the relevant IT teams when certain predefined thresholds or anomalies are
exceeded. These alerts can trigger immediate response actions.
IT Operations Team: The IT Operations Team is typically the first point of contact for
assessing the disruption. They identify the nature and extent of the issue, conduct initial
troubleshooting, and attempt to restore services.
Data Migration Team: The Data Migration Team assesses the impact of the disruption on
the migration process and determines if any data integrity issues have arisen. They work
with the IT Operations Team to coordinate recovery efforts.
Failover and Redundancy: If the primary systems are affected, rely on redundant or
failover systems to assess the damage and continue operations.
4 RECOVERY OPERATIONS
[List the procedures for all recovery options available for the restoration of normal operations
and the procedures for executing each option.]
Recovery Goal 1: IT Operations Team: The IT Operations Team is typically the first point
of contact for assessing the disruption. They identify the nature and extent of the issue,
conduct initial troubleshooting, and attempt to restore services.
Name: Gorock Shetty
Contact Information: 041119524
Responsibility: To restore services
Recovery Goal 2: Cloud Service Provider Support Team: The Cloud Service Provider's
Support Team provides technical support for the cloud infrastructure. In case of disruptions
affecting the cloud environment, they offer assistance and guidance to resolve the issues.
Name: Jan Gillbank-(case officer at Amazon web services)
Contact Information: 045562589
Responsibility: offer support and assistance and guidance to resolve the issues and bring
the data from cloud server.
Resumption procedures are crucial for ensuring a smooth transition back to normal
operations after a disruption. They involve a coordinated effort among necessary teams to
operate the system at the original or new site and thoroughly test it to ensure proper
functionality. Here are the outlined procedures:
You are required to develop clear and specific directions on how to handle serious
downtime.
You must use the template below to write your answer.
Write in 100-150 words how to handle serious down time according to the information
provided in the scenario.
_________________________________________________________________
_________________________________________________________________
_________________________________________________________________
______________________________
Assessor Date: