Module Title: Database Backup and Recovery

Unit one: Database Architecture

 1.1Architecture of database file system

• A database file system architecture is designed

to provide efficient data storage, retrieval, and
management for various types of applications.
Here is a high-level overview of the
components typically involved in the
architecture of a database file system:
• 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. The architecture of a DBMS
can be seen as either single tier or multi-tier.
The tiers are classified as follows:
 1.1.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. It
means the user can directly sit on the DBMS
and uses it.
• 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, where
programmers can directly communicate with
the database for the quick response.
• For example; when you install a DB in your
system and access it to practise SQL queries it
is tier-one architecture. But such architecture
is rarely used in production

• Figure 1.1: Single tier architecture

 1.1.2.Two-tier Architecture

• The two-tier is based on Client Server architecture.

• It is like client server application.
• The direct communication takes place between client and
server. There is no intermediate between client and server.
• 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.
 1.1.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
applications and distributed applications. 3-
tier architecture has following layers;
• Database server (Data) Tier − at this tier, the
database resides along with its query
processing languages.
• 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. All views
are generated by applications that reside in
the application tier. Example your PC, Tablet,
Mobile, etc.)
Figure 1.3. Three-tier Architecture Diagram
1.2 Risks and Failure Scenario
 Power Failure

• Power failures can lead to hardware failure.

The affected hardware components could be
cables, power supplies or storage devices. It
can render the data either inaccessible or
simply result in data loss. One would need to
isolate the affected area before investigating if
the database was affected by the power
failure.
 Disk Failure

• While power failures can lead to disk failure,

they can also fail due to physical damage or a
logical failure. Such failures are due to head
crashes or unreadable media, resulting in the
loss of parts of secondary storage. They are
the most dangerous failures and one of the
most common causes of data loss.
 Human Error (Carelessness)

• This is the failure due to unintentional destruction of

data or facilities by operators or users. An employee
may unintentionally delete some data or may modify
the data unknowingly in a way that would cease the
DBMS from interacting with the database effectively.
When DBMS software is unable to interact with the
database, it causes a ripple effect since the remaining
third party applications relying on the DBMS to
interact with the database also lose access to it.
Human error is the number one cause of data loss.
 Software Corruption

• Companies using traditional in-house IT

infrastructures are more at risk of software corruption
than those relying on cloud-based services.
• When the number of end users in a company
increase, the applications using the same resources
are divided even further among the new users,
causing problems such as freezing and crashing of the
operating systems and applications in the middle of
using the software. Crashing causes the end user to
lose the unsaved data.
 Virus Infection

• An enterprise cannot operate safely without

the use of a good security solution. Cyber-
attacks are the biggest threat a company faces
today and it is imperative that the security
solution performs real-time scanning.
Depending on the type of virus, it could have
the ability to steal, corrupt, modify and even
delete the complete database.
 Natural Disasters
• Natural disasters such as fire, floods,
earthquake, tsunami, etc have the ability to
destroy the entire infrastructure. In such an
event, there is absolutely no way to even find,
let alone recover, the data.
 Disgruntled Employees

• A disgruntled employee could provide

essential and confidential information to
outsiders, causing untold damage to an
organization. And if the employee has access
or gains unauthorized access to systems or
applications, he/she can inject a virus or
delete data to halt the company’s day to day
operations.
 Hardware Failure

• Hardware failure may include memory errors,

disk crashes, bad disk sectors, disk full error
and so on. Hardware failure can also be
attributed to design errors, poor quality
control during fabrication, overloading and
wear out of mechanical parts.
 System Crash

• System crashes are due to hardware or

software errors, resulting in the loss of main
memory. This could be the situation that the
system has entered an undesirable state,
such as Dead Lock, which prevents the
program form continuing with normal
processing.
 Network Failure

• Network failure can occur while using a

Client-server configuration or distributed
database system where multiple database
servers are connected y common network. •
Network failure such as communication
software failure or aborted asynchronous
connections will interrupt the normal
operation of the database system.
 1.3 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, here are
some general guidelines to consider when it
comes to the occupational health and safety
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.
 Security Measures
• Implement security measures to protect
personnel from potential cybersecurity 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. Encourage regular health
check-ups and screenings to monitor the
overall well-being of employees.
 Documentation and Procedures
• Document clear and detailed procedures for
database backup and recovery tasks. Include
safety guidelines and precautions within the
documentation to ensure safe work practices.
 Communication Protocols
• Establish effective communication protocols to
ensure that team members can communicate
efficiently during backup and recovery
operations. Encourage open communication
about any concerns related to health and
safety.
 Regulatory Compliance
• Stay informed about relevant OHS regulations
and ensure compliance with local, regional,
and national standards.