Browse Prior Art Database

Intelligent mechanism to take database level backups efficiently in optimum time by making use of earlier taken backup image.

IP.com Disclosure Number: IPCOM000244755D
Publication Date: 2016-Jan-11
Document File: 8 page(s) / 156K

Publishing Venue

The IP.com Prior Art Database

Abstract

Intelligent mechanism to take database level backups efficiently in optimum time by making use of earlier taken backup image.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 01 of 8

Intelligent mechanism to take database level backups efficiently in optimum time by making use of earlier taken backup image

backup image.

.

In today's competitive IT market almost all companies are focusing on 24x7 production availability with absolutely no downtime. This applies to all resources in the production environment like applications, databases, operating system and network etc. The relational database is an integral and important part of any production environment. In the era of database warehouse, the database size goes up to several terabytes and it takes few hours/days to take the complete database backup. The backup is an important activity for any production database and this needs to be performed on regular basis.

The backup process significantly impacts the performance of database server, so it's always important to have efficient backup process that takes least possible time to complete.Most of the customers are taking the full backup once in a week. For large data warehouse clients, it is always a challenge to backup huge databases due to time and storage limitations.

Most of the production databases use following backup strategies:
- Full database backup over weekend (preferably offline)

- Incremental or Delta backup (on weekdays)

We cannot ignore taking backup on production system as we may need to recover database in crisis situation using backup taken earlier.

We are proposing a solution to reduce the time to take database backup significantly so as to reduce the maintenance window on the production system. With this new approach, we are eliminating the need of separate incremental and delta backup everyday.

Known solutions


Various backup methods such as:

Full, incremental & delta (Differential) backup.

Online, Offline backup

Drawbacks of known solutions


- If we use Full + Incremental + Delta backup strategy, we need to maintain multiple copiesof the database backup images. In case of a problem

with any single backup image(either full or incremental or delta backup image), your may lose some or all data.

- If we use Full + Incremental + Delta backup strategy, and later on if there is need to restore the database backup images, we need to perform multiple restore operations(once for each backup image).

- If we are taking full backup (online or offline) on daily or weekly basis, the time to take full backup is same or more compared to time taken by

1



Page 02 of 8

last full backup (unless you have deleted large amount of data or dropped one or more tablespaces).

We are proposing an idea of editing same database backup image repetitively.

Let's consider we are having huge database with around 100 tablespaces in it. In most of the cases, we have seen that the data in 20-25 tablespaces does not get changed on daily basis. Those tablespaces are used mainly for month end or quarter end or year end report generation. The data gets loaded into such tablespaces only for report generation. If we a...