Database Security & Recovery

Database Security & Recovery
Anchal Mishra
WHAT IS RECOVERY
During the life of a transaction, that is, a after the
start of a transaction but before the transaction
commits, several changes may be made in a
database state. The database during such a state
is in an inconsistent state. What happens when a
failure occurs at this stage? Why did this problem
occur? Because although a transaction is
considered to be atomic, yet it has a life cycle
during which the database gets into an
inconsistent state and failure has occurred at that
stage.
What is the solution? In this case where the
transaction has not yet committed the changes
made by it, the partial updates need to be
undone.
How can we do that? By remembering information
about a transaction such as when did it start,
what items it updated etc. All such details are
kept in a log file.
Kinds of Failures
• Software failures
• Hardware failure
• External failure
Software Failures
In such cases, a software error abruptly stops the
execution of the current transaction (or all transactions),
thus leading to losing the state of program excution and
the state/ contents of the buffers. But what is a buffer?
A buffer is the portion of RAM that stores the partial
contents of database that is currently needed by the
transaction. The software failures can further be
subdivided as:
• Statement or application program failure
• Failure due to viruses
• DBMS software failure
• Operating system failure
Hardware Failures
Hardware failures are those failures when some

hardware chip or disk fails. This may result in loss
of data. One such problem can be that a disk gets
damaged and cannot be read any more. This may
be due to many reasons.
For example, a voltage fluctuation in the power
supply to the computer makes it go off or some
bad sectors may come on disk or there is a disk
crash. In all these cases, the database gets into an
inconsistent state.
External Failure
A failure can also result due to an external

cause, such as fire, earthquakes, floods,
etc. The database must be duly backed up
to avoid problems occurring due to such
failures.
Failure Controlling Methods
• Having a regulated power supply.
• Having a better secondary storage system such as
RAID (Redundant Array of Independent Disks).
• Taking periodic backup of database states and keeping
track of transactions after each recorded state.
• Properly testing the transaction programs prior to use.
• Setting important integrity checks in the databases as
well as user interfaces etc.
However, it may be noted that if the database system is
critical it must use a DBMS that is suitably equipped
with recovery procedures.
RECOVERY TECHNIQUES
• Backward Recovery (UNDO)
• Forward Recovery (Redo

Backward Recovery (UNDO)
In this scheme the uncommitted changes
made by a transaction to a database are
undone. Instead the system is reset to the
previous consistent state of database that is
free from any errors.
Forward Recovery (Redo)
In this scheme the committed changes made by a
transaction are reapplied to an earlier copy of the
database. In simpler words, when a particular
error in a system is detected, the recovery system
makes an accurate assessment of the state of the
system and then makes the appropriate
adjustment based on the anticipated results - had
the system been error free.
Security & Integrity
• Physical: The site or sites containing the
computer system must be physicaly secured
against illegal entry of unauthorised person
• Human: An authorisation is given to a user to
reduce the chance of any information leakage
and unwanted manipulations.
• Operating System: Even though foolproof
security measures are taken to secure database
systems, weakness in the operating system
security may serve as a means of unauthorised
access to the database.
• Network: Since databases allow distributed or
remote access through terminals or network,
software level security within the network
software is an important issue.
• Database System: The data items in a database
need a fine level of access control. For example,
a user may only be allowed to read a data item
and is allowed to issue queries but would not be
allowed to deliberately modify thedata. It is the
responsibility of the database system to ensure
that these accessrestrictions
Relationship between Security and Integrity
AUTHORISATION
• READ: it allows reading of data object, but not
modification, deletion or insertion of data object.
• INSERT: allows insertion of new data, but not the
modification of existing data, e.g., insertion of colum in
a relation.
• UPDATE: allows modification of data, but not its
deletion. But data items like primary-key attributes may
not be modified.
• DELETE: allows deletion of data only.
A user may be assigned all, none or a combination of
these types of authorisation, A which are broadly called
access authorisations.

Database Security & Recovery

Uploaded by

Copyright:

Available Formats

Database Security & Recovery

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Database Security & Recovery

Uploaded by

Copyright:

Available Formats

Database Security & Recovery

Hardware failures are those failures when some

A failure can also result due to an external

• Backward Recovery (UNDO)

• Forward Recovery (Redo

You might also like