IBM® Database Backup and Recovery solutions are designed to help your organization meet the demands of a high-performance environment. The backup strategies for IBM database systems include full, differential, incremental, and compressed backup types that can reduce or eliminate data loss.

The IBM® Database Backup and Recovery with IBM® Data Server Solutions publication helps you understand the different methods for backing up and restoring data. It covers new features in Db2 10, including the ability to restore compressed backup sets that offer more efficient storage usage.

Why backup is required?

DBAs are so engrained with backups. They should be the first and last things that come to mind, and they should be completed appropriately. We make regular backups so that we can recover data in the event of a human, software, or hardware failure. Before and after upgrades or fixpacks, as well as substantial application or database structure changes, we perform ad-hoc backups. Backups are frequently used to transfer data between servers.

  • Protection against hardware and software failures
    • Much better approaches are now available
    • H/W Clusters, HADR, Q Repl, CDC, and so on
  • Switching to a new platform (hardware or operating system)
    • If the OS is the same, HADR should be considered.
    • If the operating systems are dissimilar, consider logical replication.
  • Set up a QA/Dev system.
    • If you don’t need the complete database, try using Transportable Schemas or the on restoration, there is a REBUILD option.
  • Logical Security
    • The data has been tampered with, and you must roll it back.
    • If the problem is limited in scope, you might be able to use Db2 Tooling.
      • Export Recovery
      • Unloading with High Performance

All Blue Solutions provides expert Db2 consulting services

Contact Us

Developing a Recovery Strategy

The frequency with which you backup is determined by your recovery strategy. Developing a recovery strategy entail expressing a Recovery Point Objective (RPO) and a Recovery Time Objective (RTO). These are decisions that may or may not be within the DBA’s control. A DBA must frequently ask questions and listen closely to grasp what is crucial about a database’s recovery objectives, as well as assisting a business in understanding the budgetary implications of decisions made in this area. The scope of this paper does not include determining such a strategy.

Backup Options

When it comes to backups, you have a lot of alternatives. Let’s focus on a handful of the most fundamental.

Online vs Offline

One of the most basic backup decisions is whether to backup the database whether it is online or offline. If you take an offline database backup, no one will be able to access the database while it is being backed up, thus you’ll need to disconnect all connections and deactivate the database first.

It’s crucial to think about if your database is even set up for online backups. Online backups are only possible in databases that use archive logging. You won’t be able to take an online backup if a database employs circular logging by default. Because the database is not recoverable or a backup pending condition is in existence, online backup is not permitted.

Backup Types

The following are types of backups that can be made:

  • Full – backs up the full database
  • Incremental – Changes since the last full backup are backed up incrementally (restore requires a full image and the incremental image)
  • Delta – Changes since the last full, incremental, or delta backup are backed up as delta backups (restore requires a full image and all incremental and delta images since the full image)

Db2 Backup and recovery should be a priority for any company that has an investment in their data. Choosing the right solution can make all the difference when trying to recover your data in a timely manner.

If you’re looking for a reliable solution or want help choosing one, contact an All Blue Solutions expert today.