backup operation

A backup operation that uses DB2 ACS is often referred to as a snapshot backup.

Monitoring an ongoing backup operation is possible by executing a tail -f on your onbar activity logfile.

Each of these logged events corresponds to a particular part of the backup operation.

To track the data pages, a log backup operation relies on a bulk-changes bitmap page that contains a bit for every extent.

The differential backup operation relies on a bitmap page that contains a bit for every extent.

If you try to create or delete a database file while a backup operation is in progress, the create or delete operation fails.

Used for internal data structure synchronization within a backup operation, such as database, log, or file backup.

The name of the database involved in the backup operation.

An earlier Exchange snapshot backup operation is still in progress.

The name of the user who performed the backup operation.

The user must belong to the appropriate fixed database or server roles and provide the correct media password to perform a backup operation.

A backup operation may optionally specify passwords for a media set, a backup set, or both.

Only one file backup operation can occur at a time.

Difference between local time (where the backup operation is taking place) and Coordinated Universal Time (UTC) in 15-minute intervals.

Every backup operation to a media set must write to the same number and type of backup devices.

Meanwhile, the backup operation continues writing data to the devices whose media still have space available.

For a backup operation to write (that is, to create or extend) a mirrored media set, all the mirrors must be present.

When creating a backup checksum, a backup operation does not add any checksums to pages.

If this behavior occurs, use different media or designate another file, and run the backup operation again.

The time and date of the last transaction log backup operation on the primary database.

Cannot locate the specified media or backup device. This backup operation will terminate.

Command Line Problem: A valid backup operation was not specified on the command line.

If a backup operation overlaps with a file-management or shrink operation, a conflict arises.

Cannot locate the assigned media or backup device. This backup operation will terminate.

Meanwhile, the backup operation continues writing data to the other two devices.

Date and time when the backup operation finished, presented in the regional setting of the client.

If a monitor server is not specified, an alert job runs on the primary server instance, which monitors the backup operation.

Each backup operation generates a set of events.

If something is not working as expected, you can trace the backup operation.

You can actually define business-based policies that trigger the backup operation.

A media set is created on the backup media during a backup operation by formatting the backup media.

Date and time the backup operation finished.

IDS stores information about each backup operation (dbspaces and logical logs) in a database called sysutils.

Sort order of the server performing the backup operation.

Date and time the backup operation started.

Code page of the server performing the backup operation.

The backup operation was requested to continue despite errors.

The following events are logged during an Exchange snapshot backup operation.

If a disk file fills while a backup operation is appending a backup to the media set, the backup operation fails.

Also, every backup operation such as database, table space or incremental will include a copy of the recovery history file (RHF).

The time and date of the last log backup operation.

Data written by a backup operation to a backup device that is being used by a media set.

After 5 GB of data have been written to the third tape, the backup operation stops writing to the third device.

Daily and monthly backup operation.

When a tape drive is used, a backup operation may fill one tape and continue onto another tape.

The backup program that is running the earlier backup operation performs the appropriate cleanup API calls.

Any backup operation that implicitly or explicitly references data that is offline fails.

During a backup, most operations are possible; for example, INSERT, UPDATE, or DELETE statements are allowed during a backup operation.

At that point, the whole backup operation pauses until a new tape is mounted on the third device.

Name of the server running the SQL Server backup operation.

Specifies that SQL Server will keep the tape open after the backup operation.

This option causes SQL Server to keep the tape or tapes open after the backup operation.

A SQL Server backup operation that writes to any tape device supported by Windows XP or Windows Server 2003.

The name of the Database-Engine instance that performed the backup operation.

The name of the instance of the Database Engine that performed the backup operation.

This means that even if the vendor's code traps, the database engine will not go down (obviously the backup operation itself will fail).

Therefore, the current backup operation and all subsequent backup operations are unsuccessful until one of the following conditions is true

To continue the above example, a second backup operation (a differential backup) appends information to the same media set

Is the time of the backup operation with

Specifies a logical or physical backup device to use for the backup operation, as follows

Method 3: An earlier backup operation is not in progress

Select the type of backup operation to perform: , t

Backup in Progress 0x800 This is a transient state that is only in effect during a backup operation. Issue an online BACKUP DATABASE command

While the backup operation is running, execute the following script from another session

Generally, SQL Server performs these tasks during a BACKUP operation

Backup operation fails when you back up Exchange Server 2003 databases and System State Information at the same time