SATA TECHNOLOGY AND

BUSINESS COLLEGE
Sector-ICT
Department of WDDBA
2ND YEAR

Database Backup and Recovery

By: Mesfin.M(MBA)
 LO:1
Database
Architecture
 What is Architecture of database file system ?

Database architecture: focuses on database design

and construction for large enterprise database
systems that manage massive amounts of
information for organizations.
Database architecture: includes setting the
standards for the security and programming aspects
of these databases, as well as figuring out how
these databases will operate and function within
existing structures.
computer systems to perform
 Cont’t
The design of a DBMS depends on its
architecture.
Selecting the correct Database Architecture
helps in quick and secure access to data.
It can be centralized or decentralized or
hierarchical.
 CLASSIFICATION OF TIERS
1. Single tier architecture
The simplest of Database Architecture are 1 tier where the Client,
Server, and Database all reside on the same machine.
 In other word, it keeps all of the elements of an application,
including the interface, Middleware and back-end data, in one place.
Developers see these types of systems as the simplest and most
direct way:
The database is directly available to the user.
Any changes done here will directly be done on the database itself.
It doesn't provide a handy tool for end users.
The 1-Tier architecture is used for development of the local
application, action and implementation
 Cont.'s

Figure 1.1: Single tier architecture

 Continuous
2. Two-tier Architecture
 The two-tier is based on Client Server architecture.
 The direct communication takes place between client and server.
 There is no intermediate between client and server.
 Applications on the client end can directly communicate with the database at the
server side.
 The user interfaces and application programs are run on the client-side.
 The server side is responsible to provide the functionalities like: query processing
and transaction management.
 To communicate with the DBMS, client-side application establishes a connection
with the server side
 2 tier architecture provides added security to the DBMS as it is not exposed to the
end user directly.
A two-tier architecture is a database architecture where :
1. Presentation layer runs on a client (PC, Mobile, Tablet, etc)
2. Data is stored on a Server.

Introduction to HCI AP Dr. Siti Salwah Salim

 3. Three-tier Architecture
 It is an extension of the 2-tier architecture.
 A 3-tier architecture separates its tiers from
each other based on the complexity of the
users and how they use the data present in the
database.
 The three tier architecture is the most popular
DBMS architecture.
 This architecture has different usages with
different applications. It can be used in web
 Con’t
3-tier architecture has following layers;
Database server (Data) Tier − at this tier, the database
resides along with its query processing languages.
 We also have the relations that define the data and their
constraints at this level.
Application (Middle) Tier – also called business logic layer
and it processes functional logic, constraint, and rules before
passing data to the user or down to the DBMS.
User (Presentation) Tier − End-users operate on this tier and
they know nothing about any existence of the database beyond
this layer.
At this layer, multiple views of the database can be provided
by the application.
 Goals of Three-tier architecture ?.....
 To separate the user applications and physical database
 Proposed to support DBMS characteristics
 Program-data independence
 Support of multiple views of the data
N-tier architecture: N-tier architecture would involve dividing
an application into three different tiers. These would be the
Logic tier, presentation tier, and data tier.

Introduction to HCI
 Risks and Failure Scenario.....
 A database is the means of organizing information so it can be
easily managed, updated and retrieved.
 Losing a database would also mean losing the associated data.
 This means that if a business loses its databases for any number
of reasons, with no backups stored, it is fair to assume that they
will most likely lose the data too.

Introduction to HCI AP Dr. Siti Salwah Salim

 SCENARIOS OR CAUSES THAT COULD LEAD TO A
DATABASE LOSS

Sy
Network Failure Disk Failure n
i o

st e
fe ct

m
I n
s

Cr
r u
Vi

ash
Disgruntled Employees

rs
Human Error (Carelessness)

ste
isa
lD
ra
Software Corruption

tu
Sabotages

Na
Hardware Failure Power Failure
 OHS
Occupational Health and Safety (OHS):
requirements for database backup and
recovery are crucial to ensure the well-being
and safety of individuals involved in
managing and maintaining databases.
While OHS standards may vary by region
and organization,
 OHS aspects of database backup and recovery:
Training and Competency
Ensure that personnel responsible for database backup and recovery are
adequately trained and competent in their roles. Provide ongoing training to keep
them updated on the latest backup and recovery procedures and technologies .

Ergonomics
Design workstations and environments with ergonomic principles in mind to
prevent musculoskeletal issues among personnel. Ensure that seating, lighting,
and computer equipment are conducive to a healthy working environment.
Workload Management
Monitor and manage the workload of personnel involved in database backup and recovery
to prevent stress and burnout. Encourage breaks and time away from the computer to
reduce the risk of repetitive strain injuries.

Emergency Procedures
Establish clear emergency procedures for unexpected situations during database backup
and recovery processes. Ensure that personnel are aware of evacuation plans and
procedures in case of emergencies.
 Cont’….
Security Measures
Implement security measures to protect personnel from potential cyber-security threats
during backup and recovery operations. Provide guidelines on handling sensitive data
securely to prevent data breaches and unauthorized access.

Equipment Safety
Regularly inspect and maintain all equipment used in database backup and recovery to
ensure it meets safety standards. Provide guidelines for the safe use of backup and recovery
tools and equipment.
Health Monitoring
Implement health monitoring programs to identify and address any health issues among
personnel promptly.
Documentation and Procedures
Document clear and detailed procedures for database backup and recovery tasks.
Communication Protocols
Establish effective communication protocols to ensure that team members can communicate efficiently
during backup and recovery operations.
Regulatory Compliance
Stay informed about relevant OHS regulations and ensures compliance with local, regional, and national
standards.
LO:2-Database Backup Methods
Main contents
 Methods for back-up and recovery
Range of back-up and restoration
Off-line back-ups
On-line file back-ups
Disk mirroring
RAID
Off-site back-up files
Onsite Backup
Hybrid storage
 Introduction to Backup
Backup is the process of creating a copy of data to protect against
accidental or malicious deletion, corruption, hardware failure,
ransom ware attacks, and other types of data loss. Data backups
can be created locally, offsite, or both

Restore is the process of retrieving data from a backup. This might

mean copying data from backup media to an existing device or to
a new device. It also could mean copying data from the cloud to a
local device or from one cloud to another.
Recovery refers to the process of restoring data and operations (e.g., returning a
server to normal working order following hardware failure).
Restore and recovery times can vary widely depending on the backup format and
data recovery methods you choose.
 The most common type of database
backups are:
Logical backup - backup of data is stored in a
human-readable format like SQL
Physical backup - backup contains binary data
 Methods for back-up and recovery
There are different types of backup, and each backup process works
differently.
 1-Full backups
The most basic and complete type of backup operation is
a full backup.
As the name implies, this type of backup makes a copy
of all data to a storage device, such as a disk or tape.
The primary advantage to performing a full backup
during every operation is that a complete copy of all data
is available with a single set of media.
This results in a minimal time to restore data, a metric
known as a recovery time objective.
However, the disadvantages are that it takes longer to
perform a full backup than other types (sometimes by a
factor of 10 or more), and it requires more storage space.
 2. Incremental backups
 An incremental backup operation will result in copying only the
data that has changed since the last backup operation of any type.
 An organization typically uses the modified time stamp on files
and compares it to the time stamp of the last backup.
 Backup applications track and record the date and time that
backup operations occur in order to track files modified since
these operations
 3. Differential backups
• A differential backup operation is similar to an incremental the
first time it is performed, in that it will copy all data changed
from the previous backup.
• However, each time it is run afterwards, it will continue to copy
all data changed since the previous full backup.
4.Mirror backups
Determining appropriate
methods
Five factors which can be used in making a decision
How active are your read/write activities?
What is your tolerance for recovery time?
How many of your data assets are actively being update?
How much storage space can you dedicate?
How much data do you have?
Con’t….
 Advantages
 Scalability
 Cost & Value
 Fast Deployment
 Managed Storage Service
 Connectivity
 Performance
Disadvantages Offsite Storage
LO:3- Database Recovery Points &
Procedures
content coverage and topics:
 Database recovery point
 Database recovery is the process of restoring
the database to a correct (consistent) state in the
event of a failure.
 In other words, it is the process of restoring the
database to the most recent consistent state that
existed shortly before the time of system
failure.
 There are many situations in which a
transaction may not reach a commit or abort
point. Some of them include;
The DBMS can crash
System failure(e.g. power outage)
oAffects all transactions currently in progress but
does not physically damage the data (softcrash)
 Media failures(e.g. Head crash on the disk)
o damage to the database (hard crash) need
backup data
The system might lose power
Human error can result in deletion of critical
data.
When a DBMS recovers from a crash, it should maintain
the following:
It should check the states of all the transactions, which
were being executed.
A transaction may be in the middle of some operation;
the DBMS must ensure the atomicity of the transaction
in this case.
It should check whether the transaction can be
completed now or it needs to be rolled back.
No transactions would be allowed to leave the DBMS
in an inconsistent state.
In case of any type of failures, a transaction must either be
aborted or committed to maintain data integrity.
 Transaction log plays an important role for database
recovery and bringing the database in a consistent state in
the event of failure.
 Transactions represent the basic unit of recovery in a
database system.
 The recovery manager guarantees the atomicity and
durability properties of transactions in the event of failures.
 During recovery from failure, the recovery manager ensures
that either all the effects of a given transaction are
permanently recorded in the database or none of them are
recorded.
 A transaction begins with successful execution of a
<T, BEGIN>” (begin transaction) statement.
 Database Recovery Techniques
For fast restoration or recovery of data, the
database must hold tools which recover the
data efficiently.
It should have atomicity means either the
transactions showing the consequence of
successful accomplishment perpetually in the
database or the transaction must have no sign
of accomplishment consequence in the
database.
Immediate Update: As soon as a data item is modified in
cache, the disk copy is updated.
Deferred Update: All modified data items in the cache are
written either after a transaction ends its execution or after a
fixed number of transactions have completed their execution.
Shadow update: The modified version of a data item
does not overwrite its disk copy but is written at a
separate disk location.
In-place update: The disk version
of the data item is overwritten by
the cache version.
Two approaches of Recovery
Manual Reprocessing
Automated Recovery with Rollback / Roll
forward
Con’t…
Con’t…
 Testing restore
process
Test Database recovery testing is used to ensure
that the database is recovered. Recovery testing
allows you to find out whether the application is
running properly and to check retrieving invaluable
data that would have been lost if your recovery
method is not properly setup.
Restore a database to a
point in time