Create Backup Set

Requirements

Please ensure that the following requirements are met:

  1. %edition_name% Installation: Latest version of %edition_name% must be installed on the Oracle database server.
  2. !

    Backup and restore of Oracle database(s) running on a remote machine is not supported.


  3. Oracle Database Server Add-On Module: Make sure that the Oracle Database Server add-on module is enabled for your %edition_name% user account.

  4. Backup Quota Requirement: Make sure that your %edition_name% user account has sufficient storage quota assigned to accommodate the storage of Oracle database backup set and retention policy.

  5. Java Heap Size: The default Java heap size setting on %edition_name% is 2048MB. For Oracle database backup, it is highly recommended to increase the Java heap size setting to be at least 4096MB to improve backup and restore performance. The actual heap size is dependent on amount of free memory available on your Oracle server.

  6. Temporary Directory Folder: The Temporary directory folder is used by %edition_name% during a backup job for the storage of:
    The spooled Oracle Database and Archived Log files
    Any incremental or differential delta files generated
    It is strongly recommended that the temporary directory folder is located on a local drive with enough free disk space to be used by the spooled databases and archived log files. The temporary folder should not be located on the Windows System C:\ drive or Oracle Home drive.
    The calculation of disk space required on the drive where the temporary folder is located is as follows:
    (Total Database Size * Delta Ratio) * number of backup destinations = Maximum Free Space Required
    Example: If the default Delta ratio is 50% for in-file delta and if the total Oracle database size is 1TB and there is only one backup destination, the minimum free space needed on the drive where the temporary directory folder is located = 1.5TB
    1TB = Total Oracle database size
    500GB = Total maximum size of incremental or differential delta files generated

    To obtain the size of the data files on the Oracle database instance, use the Oracle RMAN REPORT SCHEMA feature and sum up the total “List of Permanent Datafiles” by running the following command.
    NOTE: The values shown are just examples and might be different on your Oracle instance.
    C:\Users\Administrator>set ORACLE_SID=orcl
    C:\Users\Administrator>rman target /
    Recovery Manager: Release 19.0.0.0.0 - Production on Thu Oct 29 18:29:44 2020
    Version 19.3.0.0.0
    Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
    connected to target database: ORCL (DBID=1562659286)
    RMAN> report schema;
    using target database control file instead of recovery catalog
    Report of database schema for database with db_unique_name ORCL
    List of Permanent Datafiles
    ===========================
    File   Size(MB)  Tablespace     RB segs   Datafile Name
    ----   --------   ------------   --------     ----------------
    1       910     SYSTEM             YES   D:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF
    3       920     SYSAUX             NO   D:\ORACLE\ORADATA\ORCL\SYSAUX01.DBF
    4       60     UNDOTBS1           YES         D:\ORACLE\ORADATA\ORCL\UNDOTBS01.DBF
    5       260     PDB$SEED:SYSTEM     NO           D:\ORACLE\ORADATA\ORCL\PDBSEED\SYSTEM01.DBF
    6       280     PDB$SEED:SYSAUX     NO           D:\ORACLE\ORADATA\ORCL\PDBSEED\SYSAUX01.DBF
    7       5     USERS                 NO           D:\ORACLE\ORADATA\ORCL\USERS01.DBF
    8       100     PDB$SEED:UNDOTBS1   NO           D:\ORACLE\ORADATA\ORCL\PDBSEED\UNDOTBS01.DBF
    9       260     ORCLPDB:SYSTEM     NO           D:\ORACLE\ORADATA\ORCL\ORCLPDB\SYSTEM01.DBF
    10     300     ORCLPDB:SYSAUX       NO           D:\ORACLE\ORADATA\ORCL\ORCLPDB\SYSAUX01.DBF
    11     100     ORCLPDB:UNDOTBS1     NO         D:\ORACLE\ORADATA\ORCL\ORCLPDB\UNDOTBS01.DBF
    12     5     ORCLPDB:USERS         NO         D:\ORACLE\ORADATA\ORCL\ORCLPDB\USERS01.DBF
    List of Temporary Files
    ===========================
    File   Size(MB)  Tablespace     Maxsize(MB)   Tempfile Name
    ----   --------   ------------     --------   ----------------
    1       32     TEMP               32767             D:\ORACLE\ORADATA\ORCL\TEMP01.DBF
    2       36     PDB$SEED:TEMP     32767             D:\ORACLE\ORADATA\ORCL\PDBSEED\TEMP012020-03-12_18-17-27-260-PM.DBF
    3       128     ORCLPDB:TEMP     32767             D:\ORACLE\ORADATA\ORCL\ORCLPDB\TEMP01.DBF
    RMAN>
  7. Windows Requirements

    Ensure that the following Windows requirements and conditions are met.
  8. Supported Windows Server Version

  9. Windows User Account Permission

  10. Oracle Database-related Windows Services
  11. Linux Requirements

    Ensure that the following Linux requirements and conditions are met.
  12. Supported OS Version
  13. GUI Desktop Environment
  14. Oracle Backup Requirements

    NOTE: Please consult your Oracle database administrator before making any changes.
  15. Oracle Tools
    Although the following tools are usually installed by default on all Oracle database installations, ensure that the following tools are installed on the Oracle database server and they are functioning correctly.
  16. Oracle Internal Process Checking: For the Oracle instance to run smoothly, please ensure that the internal processes for Oracle instance are working well:
    DBW0 (Database Writer)
    LGWR (Log Writer)
    MMAN (Memory Manager Process)
    PMON (Process Monitor)
    PSP0 (Process Spawner Process)
    SMON (System Monitor)
    CKPT (Checkpoint process (thread on Windows) that runs by default on Windows)
    ARC0 (Archive Process (or thread on Windows))
    RECO (Distributed Recovery Background Process)
    SQL> select name, description from v$bgprocess where PADDR <>'00';
    NAME     DESCRIPTION
    -----   ---------------------------------------
    PMON     process cleanup
    VKTM     Virtual Keeper of TiMe process
    GEN0     generic0
    DIAG     diagnosibility process
    DBRM     DataBase Resource Manager
    VKRM     Virtual sKeduler for Resource Manager
    PSP0     process spawner 0
    DIA0     diagnosibility process 0
    MMAN     Memory Manager
    DBW0     db writer process 0
    TMON     Transport Monitor
    ARC0     Archival Process 0
    ARC1     Archival Process 1
    ARC2     Archival Process 2
    ARC3     Archival Process 3
    LGWR     Redo etc.
    CKPT     checkpoint
    SMON     System Monitor Process
    SMCO     Space Manager Process
    RECO     distributed recovery
    LREG     Listener Registration
    CJQ0     Job Queue Coordinator
    AQPC     AQ Process Coord
    MMON     Manageability Monitor Process
    MMNL     Manageability Monitor Process 2
  17. Supported Oracle Database Server Version: %edition_name% supports the following versions of Oracle database server:
    To verify if the Oracle database server version is supported by %edition_name%, use the following SQL query.
    Oracle 19c
    C:\Users\Administrator>sqlplus / as sysdba
    SQL*Plus: Release 19.0.0.0.0 - Production on Thu Nov 12 12:04:25 2020
    Version 19.3.0.0.0
    Copyright (c) 1982, 2019, Oracle. All rights reserved.
    Connected to:
    Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
    Version 19.3.0.0.0
    SQL>
    Oracle 18c
    C:\Users\Administrator>sqlplus / as sysdba
    SQL*Plus: Release 18.0.0.0.0 - Production on Mon Jan 4 11:06:36 2021
    Version 18.3.0.0.0
    Copyright (c) 1982, 2018, Oracle. All rights reserved.
    Connected to:
    Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production
    Version 18.3.0.0.0
    SQL>
    Oracle 12c
    C:\Users\Administrator>sqlplus / as sysdba
    SQL*Plus: Release 12.1.0.1.0 - Production on Mon May 26 15:33:44 2019
    Version 12.1.0.1.0
    Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to:
    Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - Production
    Version 12.1.0.1.0
    SQL>
  18. System Identifier (SID): Make sure the System Identifier (SID) is correct by using the following SQL query.
  19. Oracle_Home path:

    Oracle 19c
    The Oracle_Home path can be obtained by using the following SQL query. The Oracle_Home path for Oracle 19c is “D:\app\oracle\19.0.0\dbhome_1”.

    Oracle 18c
    The Oracle_Home path can be obtained by using the following SQL query. The Oracle_Home path for Oracle 18c is “D:\app\oracle\18.0.0\dbhome_1”.

    Oracle 12c
    The Oracle_Home path can be obtained by using the following SQL query. The Oracle_Home path for Oracle 12c is “D:\app\oracle\product\12.1.0\dbhome_1”.

  20. !

    If any of the following scenario is encountered, please contact the Oracle database administrator for further assistance:

    The value of the Oracle_Home path in init.ora file does not match the value obtained from the SQL query.

    The SQL query returns an empty or null value.

    Example of an SQL query return with a null value of the Oracle_Home path
    SQL > SELECT file_spec FROM DBA_LIBRARIES WHERE library_name = 'DBMS_SUMADV_LIB';
    no rows selected
  21. Database Status

  22. Archived Log Mode


  23. Java Installation:
    Java must be installed on the Oracle Database. To check if Java is installed, use the following SQL query. The status of the JServer JAVA Virtual Machine and Oracle Database Java Packages should be “VALID”.
    SQL > select comp_name, status from dba_registry;
    COMP_NAME                               STATUS
    ---------                               ------------
    OWB                                      VALID
    Oracle Application Express               VALID
    Oracle Enterprise Manager               VALID
    OLAP Catalog                             VALID
    Spatial                                   VALID
    Oracle Multimedia                      VALID
    Oracle XML Database                     VALID
    Oracle Text                           VALID
    Oracle Expression Filter                 VALID
    Oracle Rules Manager                     VALID
    Oracle Workspace Manager              VALID
    Oracle Database Catalog Views          VALID
    Oracle Database Packages and Types       VALID
    JServer JAVA Virtual Machine            VALID
    Oracle XDK                                  VALID
    Oracle Database Java Package             VALID
    !

    If the status of the JServer JAVA Virtual Machine and/or the Oracle Database Java Packages is INVALID, please contact the Oracle database administrator for further assistanc

  24. JAVASYSPRIV Permission for Oracle System Account:
    The Oracle system account is used by %edition_name% to connect to the Oracle database server to authenticate the backup and restore process. The following permission must be assigned to the system account.
  25. SYSDBA Privileges for Oracle System Account:
  26. TNS Listener Service
    TNS listener service must be started to allow connections to the Oracle database server. To check if the TNS listener service is running, use the lsnrctl status command. If the TNS listener service is not started, use the lsnrctl start command to start the service.
    Example: A running TNS Listener service on Oracle 19c.
    C:\Users\Administrator>lsnrctl status
    LSNRCTL for 64-bit Windows: Version 19.0.0.0.0 - Production on 14-OCT-2020 16:45:29
    Copyright (c) 1991, 2019, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
    STATUS of the LISTENER
    ------------------------
    Alias        LISTENER
    Version      TNSLSNR for 64-bit Windows: Version 19.0.0.0.0 - Production
    Start Date   14-OCT-2020 11:11:04
    Uptime       0 days 5 hr. 34 min. 27 sec
    Trace Level   off
    Security     ON: Local OS Authentication
    SNMP         OFF
    Listener Parameter File     D:\oracle\19.3.0\dbhome\network\admin\listener.ora
    Listener Log File     D:\oracle\diag\tnslsnr\w12x-5-43\listener\alert\log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ora19c-w2k16)(PORT=1521)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=ora19c-w2k16)(PORT=5500))(Security=(my_wallet_directory=D:\ORACLE\admin\orcl\xdb_wallet))(Presentation=HTTP)(Session=RAW))
    Services Summary...
    Service "CLRExtProc" has 1 instance(s).
    Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
    Service "orcl" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
    Service "orclcXDB" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
    Service "pdborcl" has 1 instance(s).
    Instance "orcl", status READY, has 1 handler(s) for this service...
    The command completed successfully
    If not,use the following command to start the TNS listener:
    C:\Users\Administrator>lsnrctl start
    LSNRCTL for 64-bit Windows: Version 19.0.0.0.0 - Production on 21-OCT-2020 15:44:41
    Copyright (c) 1991, 2019, Oracle. All rights reserved.
    TNS-01106: Listener using listener name LISTENER has already been started
    NOTE: The values shown are just examples and might be different on your Oracle instance.

  27. Localhost is Resolvable
    Verify if the localhost IP 127.0.0.1 on the Oracle database server is resolvable using the command ping 127.0.0.1 as this will be the IP address that %edition_name% will use to connect to the Oracle instance.
    C:\Users\Administrator>ping 127.0.0.1
    Pinging 127.0.0.1 with 32 bytes of data:
    Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
    Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
    Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
    Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
    Ping statistics for 127.0.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
    C:\Users\Administrator>
  28. Oracle Port Number: The default Oracle port number is 1521. To check, use the netstat and tnsping commands to verify the actual port number.
  29. Best Practices and Recommendations

    1. To enable a full Oracle database instance recovery, all databases including SYSAUX, SYSTEM, UNDOTBS1, USERS and related application databases except for “TEMP” must be selected in the backup source when creating the backup set. Otherwise, without a backup of these databases, a full Oracle database instance recovery will NOT be possible.
    2. Full database backup or incremental / differential database backups should be scheduled when system activity is low to achieve the best possible performance and to minimize the impact on the database server performance (for example: scheduled to run on weekends).
    3. For Archived Log backups, the backup frequency should be dependent on the number of transactions or activity on the database. Databases with more transaction should run archived log backup more frequently (for example: instead of a daily backup, it should be run multiple times a day).
    4. To provide maximum data protection and flexible restore options, it is recommended to configure:
      At least one offsite or cloud destination
      At least one local destination for fast recovery
    5. Perform test restores periodically to ensure your backup is set up and data are bacekd up properly.
      Performing recovery tests can also help identify potential issues or gaps in your recovery plan. It is important that you do not try to make the test easier, as the objective of a successful test is not to demonstrate that everything is flawless. There might be flaws identified in the plan throughout the test, and it is important to identify those flaws.
    6. The Restore Raw File is for advanced Oracle database administrators and should only be used if you have in-depth knowledge and understanding of Oracle database engine, Oracle database schema, knowledge of the database server and network infrastructure. Therefore, it is not recommended to use this restore option as there is need to utilize additional Oracle techniques and scripts to facilitate a manual database restore.
      Please refer to the following articles of Oracle Database Backup and Recovery User's Guide for details:
      Oracle 19c
      https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/index.html.
      Oracle 18c
      https://docs.oracle.com/en/database/oracle/oracle-database/18/bradv/index.html.
      Oracle 12c
      https://docs.oracle.com/database/121/BRADV/title.html.
    7. To ensure an optimal backup/restoration performance, it is highly recommended to set the temporary directory folder to a local disk location with sufficient free disk space.
      For %edition_name% on Windows, it must be on another location other than Drive C: (e.g., Drive E:).
      For %edition_name% on Linux, it must NOT be on the location of the Oracle Home drive.

    Limitations

    1. %edition_name% does not support Oracle Express Edition or Oracle XE.
    2. For Oracle database server on Linux CLI environment, %edition_name% does not fully support all restore options (i.e. Restore to Alternate location is not available). Whenever possible, it is recommended to use %edition_name% on Linux GUI which supports restore to:
      Original Location
      Alternate Location; and
      Restore Raw File
    3. Backup and restore of Oracle database(s) running on a remote machine is not supported.
    4. %edition_name% Oracle database module only supports backup and/or restore of standalone Oracle installations. The following advanced Oracle database setups are not supported:
      Clusterware or RAC (Real Application Clusters)
      ASM (Automatic Storage Management)
      Data Guard etc.
    5. An %edition_name% Oracle database backup set supports the backup and restore of one Oracle instance. For Oracle database server’s setup with multiple instances, a separate backup set is required for each instance.
    6. To recover a full Oracle database instance, the following items must be selected in the backup source:
      • Oracle Database Server must be selected.
      • All databases including SYSAUX, SYSTEM, UNDOTBS1, USERS and related application databases except for “TEMP” must be selected in the backup source when creating the backup set. Otherwise, without a backup of these databases, a full Oracle database instance recovery will NOT be possible.
        NOTE: Even if the “TEMP” is selected in the backup source, this database will be skipped during a backup job.

    Set the details of the backup set

    Name The name of the backup set.
    Backup set type the type of the backup set (i.e. Oracle Database Server Backup).
    Login ID The login ID of the Oracle server. The default login ID is system.
    Password The password for the login account.
    Host This value is not user configurable.
    Port The port where the connections to the Oracle server is made. The default port is “1521”.
    SID The Oracle System Identifier.

    To create a backup set:

    1. Type in a meaningful backup set name.
    2. Select the backup set type.
    3. Enter the Login ID.
    4. Enter the password.
    5. Enter the port.
    6. Enter the SID.
    7. Click [Next] button to continue.