backup incremental level <incr_level>
format 'New1<DIPSI_%s:%t:%p>.dbf'
proxy only
database
;
backup format 'New1<DIPSI_%s:%t:%p>.dbf' controlfile;
}
Starting backup sessions
To run a ZDB-to-disk, ZDB-to-tape, or ZDB-to-disk+tape backup session of an Oracle
database, use any of the following methods:
Backup methods
• Schedule a backup of an existing Oracle ZDB backup specification using the
Data Protector Scheduler. See “Scheduling backup specifications” on page 98.
• Start an interactive backup of an existing Oracle ZDB backup specification using
the Data Protector GUI or the Data Protector CLI. See “Running an interactive
backup” on page 100.
Considerations
Before running an Oracle ZDB session, consider the following:
• It is not possible to start a ZDB, restore, or instant recovery sessions using the
same source volume on the application system at the same time. A ZDB, restore,
or instant recovery session must be started only after the preceding session that
is using the same source volume on the application system has finished the ZDB
session or restore; otherwise, the session will fail.
• For the backup set method, if the Oracle database is installed on symbolic links,
then these symbolic links have to be also created on the backup system.
• On XP, if the LVM mirroring configuration is used, Data Protector displays a
warning during a backup because the volume group source volumes on the
application system do not have their BC pairs assigned. This message should be
ignored.
• If the control file, SPILE, or online redo logs are on the same source volumes as
the datafiles and the Track the replica for instant recovery option is selected, the
backup session will be aborted. In this case, you need to either reconfigure the
database or set the ZDB_ORA_INCLUDE_CF_OLF, ZDB_ORA_INCLUDE_SPF,
and ZDB_ORA_NO_CHECKCONF_IR omnirc variables. See “Reconfiguring an
Oracle instance for instant recovery” on page 421 or “ZDB integrations omnirc
variables” on page 425.
Zero downtime backup integration guide 97