We've detected that your browser language is Chinese. Would you like to visit our Chinese website? [ Dismiss ]
By: Emma

Oracle Hot Backup Mode lets administrators copy datafiles while the database stays open. It is used for user-managed online backups when taking the database offline is not an option.

Oracle continues processing transactions during this mode, but the corresponding redo logs need to be preserved and applied to make the copied files consistent.

What Is Oracle Database Hot Backup Mode?

Oracle Hot Backup Mode is a database state that allows datafiles to be copied while the database remains open and active. It is designed for user-managed online backups, so backup operations can run without interrupting normal transactions.

When a tablespace or the entire database enters backup mode, Oracle freezes checkpoint updates in the relevant datafile headers. Reads and writes continue as normal throughout.

Key characteristics:

  • Database availability: The database stays open and accessible during the backup.
  • Continued write operations: Applications can continue modifying data while datafiles are being copied.
  • Additional redo generation: Oracle writes extra redo information, including full block images for blocks modified during backup mode.
  • Recovery dependency: Copied datafiles require the corresponding archived redo logs and media recovery before they can be used as a consistent database.

Unlike a cold backup, hot backup mode does not require a database shutdown. It does not, however, guarantee that copied files are immediately recoverable without the required redo logs.

oracle database hot backup mode how it works how to use it

How Does Oracle Hot Backup Mode Work?

Hot Backup Mode relies on two mechanisms to support online backups: checkpoint SCN freezing and redo-based recovery.

1. Checkpoint SCNs and fractured blocks: When a tablespace enters backup mode, Oracle freezes checkpoint updates to the headers of its associated datafiles.

A checkpoint SCN (System Change Number) tracks which changes are already reflected in a datafile — freezing it tells Oracle where recovery needs to begin. Database writes continue normally, which creates a risk called a fractured block, where a copied block contains parts from different points in time.

To handle this, Oracle records full block images in the redo logs for blocks modified during backup mode, alongside normal redo records.

2. Redo generation and archived redo logs: Because Oracle writes additional full block images during backup mode, redo generation increases. Archive destinations should have sufficient space, and backup mode should stay active only for as long as it takes to copy the files.

Copied datafiles are not a consistent backup on their own — Oracle needs the corresponding archived redo logs to recover them to a consistent state. These logs should be retained alongside the datafile copies.

How to Enable and Disable Oracle Hot Backup Mode

Oracle supports two approaches for entering hot backup mode: at the tablespace level for selected datafiles, or at the database level for all datafiles at once. The right choice depends on the scope of the backup.

Prerequisites for Enabling Hot Backup Mode

Traditional user-managed online backups require the database to run in ARCHIVELOG mode, which allows Oracle to archive the redo logs needed to recover copied datafiles.

Check the current archiving mode with:

bash
ARCHIVE LOG LIST;

The output should show:

Database log mode Archive Mode

Automatic archival Enabled

If the database is in NOARCHIVELOG mode, it needs to be switched to ARCHIVELOG mode before proceeding.

Before starting, also confirm:

  • The database account has the necessary privileges to execute backup mode commands.
  • Sufficient storage is available for additional redo and archived redo logs.
  • The backup destination has enough space for all required datafiles.

Enable Hot Backup Mode for a Tablespace

To place a specific tablespace into backup mode:

bash
ALTER TABLESPACE users BEGIN BACKUP;

This freezes checkpoint updates to the headers of the tablespace’s datafiles while normal operations continue. Before copying, identify the associated datafiles:

bash
SELECT FILE_NAME
FROM DBA_DATA_FILES
WHERE TABLESPACE_NAME = 'USERS';

Replace USERS with the actual tablespace name. The query returns the file paths that need to be copied.

Enable Hot Backup Mode for the Entire Database

To place all datafiles into backup mode at once:

bash
ALTER DATABASE BEGIN BACKUP;

This is useful when a coordinated full database file copy is needed. Keep in mind that all tablespaces enter backup mode simultaneously, which increases overall redo generation for the duration of the operation.

Disable Hot Backup Mode After Backup

Backup mode should be ended as soon as the required datafiles have been copied.

For a tablespace-level backup:

bash
ALTER TABLESPACE users END BACKUP;

For a database-level backup:

bash
ALTER DATABASE END BACKUP;

After ending backup mode, archive the current redo log using ALTER SYSTEM ARCHIVE LOG CURRENT to ensure the redo needed for recovery is preserved.

ALTER SYSTEM ARCHIVE LOG CURRENT;
Note: END BACKUP does not make the copied datafiles immediately recoverable on its own. The corresponding archived redo logs, control file information, and media recovery are still required.

How to Perform an Oracle Online Backup Using Hot Backup Mode

The following example demonstrates a traditional user-managed backup of the USERS tablespace on a Linux system.

Step 1: Identify the Datafiles to Back Up

Query DBA_DATA_FILES to get the file paths associated with the target tablespace:

bash
SELECT FILE_NAME
FROM DBA_DATA_FILES
WHERE TABLESPACE_NAME = 'USERS';

Record the returned paths and confirm the backup destination has enough space. A complete backup strategy should also account for control files and relevant database metadata.

Step 2: Start Hot Backup Mode

Enable backup mode for the USERS tablespace:

ALTER TABLESPACE users BEGIN BACKUP;

Oracle freezes checkpoint updates to the tablespace’s datafile headers while transactions continue normally. Confirm backup mode is active before copying any files:

bash
SELECT FILE#, STATUS
FROM V$BACKUP
WHERE STATUS = 'ACTIVE';

Step 3: Copy the Datafiles

Use an OS utility to copy the datafiles to a separate backup location. On Linux:

bash
cp /u01/oradata/ORCL/users01.dbf /backup/

Keep the copy window as short as possible to limit additional redo generation. The copied files are not yet recoverable at this stage — the corresponding redo logs are also required.

Step 4: End Backup Mode and Archive Redo Logs

End backup mode as soon as the files have been copied:

bash
ALTER TABLESPACE users END BACKUP;

Then archive the current redo log using ALTER SYSTEM ARCHIVE LOG CURRENT:

bash
ALTER SYSTEM ARCHIVE LOG CURRENT;

The archived redo logs needed for recovery should be stored alongside the datafile copies.

Step 5: Verify the Backup

Check that no datafiles remain in backup mode:

bash
SELECT FILE#, STATUS
FROM V$BACKUP
WHERE STATUS = 'ACTIVE';

An empty result means no files are still in active backup mode. Also confirm:

  • The copied datafiles exist at the destination and have the expected sizes.
  • All required archived redo logs have been preserved.
  • Control files and database metadata are included in the backup.

A file copy alone does not guarantee recoverability. The backup should be tested by restoring and running media recovery in a separate environment.

The commands above illustrate a basic tablespace-level workflow and are not a complete production backup script. A production backup also requires handling control files, archived redo logs, and recovery validation.

Common Oracle Hot Backup Mode Issues and How to Fix Them

Incorrect backup procedures can cause operational and recovery problems. The following covers common issues encountered during traditional user-managed online backups.

Database Stays in Backup Mode

A failed script, interrupted file copy, or forgotten END BACKUP command can leave datafiles in backup mode longer than intended, causing unnecessary redo generation.

Query V$BACKUP to identify any affected files:

bash
SELECT FILE#, STATUS
FROM V$BACKUP
WHERE STATUS = 'ACTIVE';

If active files are found, end backup mode with the appropriate command:

bash
ALTER TABLESPACE users END BACKUP;
-- or
ALTER DATABASE END BACKUP;

If the database crashed or the backup was interrupted mid-operation, check the database state and follow Oracle’s recovery procedure before making further changes.

Excessive Redo Log Generation

Hot backup mode generates additional full block images for modified blocks, so heavy write activity or a long backup window can increase redo volume and pressure on archive destinations.

To keep this manageable:

  • End backup mode as soon as the files are copied.
  • Monitor archive log destination space throughout the operation.
  • Schedule large backups during periods of lower write activity where possible.

Backup Fails or Datafiles Are Inconsistent

Copying a datafile outside the correct backup mode procedure, or interrupting the copy mid-way, can produce a file that cannot be recovered consistently.

If a backup looks incomplete or suspect:

  • Confirm the file copy completed and the datafile is intact at the destination.
  • Verify that all required archived redo logs are available.
  • Test restoration and media recovery in a separate environment before relying on the backup.

If the required recovery information is missing, a new backup is needed.

Missing Archived Redo Logs During Recovery

Online backups depend on archived redo logs to bring copied datafiles to a consistent state. Missing logs can make recovery impossible regardless of whether the datafile copies are intact.

  • Retain the archived logs generated from BEGIN BACKUP through END BACKUP for every backup set.
  • Store backup files and their corresponding logs together, or maintain a clear mapping between them.
  • Validate log availability as part of regular backup and recovery testing.

Simplify Oracle Database Backup with i2Backup

User-managed online backups require careful coordination of backup mode commands, file copies, archived redo logs, and recovery validation. For teams managing multiple Oracle instances or mixed database environments, this overhead adds up quickly.

i2Backup is an enterprise backup solution that handles Oracle database protection without the manual steps involved in traditional hot backup workflows.

  • Automated database backup: i2Backup supports scheduled and real-time backup for Oracle instances, including standalone and cluster environments such as RAC and ADG. Continuous capture of redo and archive logs keeps RPO near zero without manual intervention.
  • No manual backup mode required: Unlike user-managed online backups, i2Backup manages backup consistency through its own mechanisms, removing the need to execute BEGIN BACKUP and END BACKUP commands manually.
  • Point-in-time recovery: Continuous log capture allows recovery to any specific point in time, covering accidental deletions, corruption, or other data loss events.
  • Broad compatibility: Supports Oracle alongside other major databases including MySQL, SQL Server, and DB2, as well as physical servers and virtualized environments, all managed from a single web-based console.
  • Immutable backup storage: Backups can be written to WORM-compliant storage with AES or SM4 encryption, protecting backup data from unauthorized changes or deletion.

For teams looking to move beyond manual Oracle backup procedures, i2Backup offers a more automated and consistent approach to Oracle database backup and recovery.

Evaluate Your
Backup and Recovery Capabilities

Assess backup and recovery capabilities to find a solution that meets your organization’s data protection needs.

FAQ

Q1: Does Oracle Hot Backup Mode Affect Database Availability?

No. The database stays open and accessible throughout the backup. Users can continue reading and writing data as normal.

 

Q2: Does Hot Backup Mode Freeze Datafile Writes?

No. It freezes checkpoint updates to datafile headers only. Database writes continue normally during the backup.

 

Q3: Can You Enable Hot Backup Mode in NOARCHIVELOG Mode?

No. Traditional user-managed online backups require ARCHIVELOG mode. Oracle needs archived redo logs to recover the copied datafiles after the backup.

 

Q4: How Can You Check Whether a Tablespace Is in Backup Mode?

Query V$BACKUP:

bash
SELECT FILE#, STATUS FROM V$BACKUP;

ACTIVE means the datafile is in backup mode. NOT ACTIVE means it is not.

 

Q5: What Happens If You Forget to Run END BACKUP?

The datafiles stay in backup mode and Oracle continues generating extra redo. If the database crashes while files are still active, media recovery will be required at the next startup. Run ALTER DATABASE END BACKUP; to clear the state.

 

Q6: Is Oracle Hot Backup Mode Deprecated?

No. User-managed hot backup is still supported in current Oracle versions. However, Oracle recommends RMAN for most backup workflows, as it handles consistency and recovery automatically without manual BEGIN BACKUP and END BACKUP commands.

Conclusion

Oracle Hot Backup Mode lets you copy datafiles without taking the database offline, but it requires careful execution. End backup mode promptly after copying, and retain the corresponding archived redo logs for recovery to succeed.

For most production environments, RMAN is the more practical choice — it handles backup consistency and recovery management without manual commands. For teams looking for a more automated approach to database protection, Info2soft offers solutions covering backup, recovery, and replication across Oracle and other database platforms.

Emma is the bridge between complex engineering and the people who need it. As a content creator at Info2soft, she spends her days translating "tech-speak" into clear, actionable stories about data resilience. She’s not just documenting software; she's uncovering how data replication and recovery actually change the way businesses run.

More Related Articles

Ready to Enhance Business Data Security?

· Enterprise & Mid-market Customers Worldwide.

· Support team available to assist you throughout your trial.

· Start a 60-day free trial or view demo to see how Info2soft protects enterprise data.

Please fill out the form and submit it, our customer service representative will contact you soon.
By submitting this form, I confirm that I have read and agree to the Privacy Notice.
{{ isSubmitting ? 'Submitting...' : 'Submit' }}