Create Backup Set

Requirements

Please ensure that the following requirements are met:

  1. CloudBacko Pro Installation: Latest version of CloudBacko Pro must be installed on the Tibero Database Server
  2. !

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


  3. Java Heap Size: The default Java heap size setting on CloudBacko Pro is 2048MB. It is highly recommended to increase the Java heap size setting a higher value to improve backup and restore performance. The actual heap size is dependent on amount of free memory available on your Tibero server.


  4. Windows Requirements
    Ensure that the following Windows requirements and conditions are met:

    1. Supported Windows Server Version
      • Tibero 6
        The backup of Tibero 6 is supported on the following Windows Server versions:
        Windows Server 2016 (64-bit only)
        Windows Server 2019 (64-bit only)
      • Tibero 7
        The backup of Tibero 7 is not available for any Windows Server versions.


    2. Tibero Database-related Windows Services
      Ensure that all Tibero database-related services are started:
      Tibero_tibero

      Tibero_tibero is the Tibero Database Server service name.
      To verify, click the start menu and search for "Services". Look for the Tibero database-related services. Their statuses should be "Running".

  5. Linux Requirements Ensure that the following Linux requirements and conditions are met.
    1. Supported OS Version

      • LINUX/x86
        OS:
        Red Hat Enterprise Linux 7 kernel 3.10.0 or later

      • LINUX/Itanium
        OS:
        Red Hat Enterprise Linux 7 kernel 3.10.0 or later

      • LINUX/Power8 (Big/Little)

      • OS:
        Red Hat Enterprise Linux 7 kernel 3.10.0 or later

      • Solaris
        OS:
        Solaris 11 64-bit kernel

      • AIX
        OS:
        AIX 7.1 64-bit kernel
        AIX 7.2 64-bit kernel


    2. Compiler and JDK Version Requirements
      In addition to satisfying the Linux requirements, ensure that the following additional requirements for Compiler and JDK Versions

      Platform

      • LINUX/x86
        Compiler:
        C99 compatible compiler, gcc version 4.8.5 or later

        JDK Version:
        JDK 1.5.17 or later


      • LINUX/Itanium
        Compiler:
        C99 compatible compiler, gcc version 4.8.5 or later

        JDK Version:
        JDK 1.5.17 or later


      • LINUX/Power8 (Big/Little)
        Compiler:
        C99 compatible compiler, gcc version 4.8.5 or later

        JDK Version:
        JDK 1.7.0 or later


      • Solaris
        Compiler:
        C99 compatible computer, Sun C 5.8 2005/10/13

        JDK Version
        JDK 1.5.17 or later


      • AIX
        Compiler:
        C99 compatible compiler, IBM XL C/C++ Enterprise Edition V7.9

        JDK Version:
        JDK 1.5.17 or later


    3. GUI Desktop Environment
      The Linux machine must be installed with a GUI desktop environment (i.e., GNOME, KDE, Cinnamon etc.).

  6. Tibero Backup Requirements
    Supported Tibero Database Server Version: CloudBacko Pro supports the following versions of Tibero Database Server:


  7. Other Requirements
  8. Database Status
    !

    To make use of SQL commands, the tbSQL utility must first be executed normally. This can be done by first using the tbsql command first without the system user and password

Best Practices and Recommendations

  1. To enable a full Tibero database instance recovery, all databases including SYSAUX, SYSTEM, TBS1, UNDO, and USR 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 Tibero 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 option is for advanced Tibero database administrators and should only be used if you have in-depth knowledge and understanding of Tibero's database schema, knowledge of the database server and network infrastructure.
    Please refer to the following articles of Tibero Database Backup and Recovery User's Guide for details:
    Tibero 6
    https://technet.tmaxsoft.com/upload/download/online/tibero/pver-20170217-000001/tibero_admin/ch_BackupRecovery.html.
    Tibero 7
    https://technet.tmaxsoft.com/upload/download/online/tibero/pver-20220622-000001/index.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 CloudBacko Pro on Windows, it must be on another location other than Drive C: (e.g., Drive E:).
    For CloudBacko Pro on Linux, it must NOT be on the location of the Tibero Home drive.

Limitations

  1. CloudBacko Pro only supports Tibero 6 and 7.
  2. For Tibero Database Server on Linux CLI environment, CloudBacko Pro does not fully support all restore options (e.g. Restore to Alternate location is not available). Whenever possible, it is recommended to use CloudBacko Pro on Linux GUI which supports restore to:
    Original Location
    Alternate Location; and
    Restore Raw File
  3. Backup and restore of Tibero database(s) running on a remote machine is not supported.
  4. CloudBacko Pro Tibero database module only supports backup and/or restore of standalone Tibero installations. The following advanced Tibero database setups are not supported:
    Tibero Active Cluster (TAC)
    Tibero Standby Cluster (TSC)
    Tibero Active Storage (TAS)
  5. An CloudBacko Pro Tibero database backup set supports the backup and restore of one Tibero instance. For Tibero database server’s setup with multiple instances, a separate backup set is required for each instance.
  6. To recover a full Tibero database instance, the following items must be selected in the backup source:

Key:

Field Description
Name The name of the backup set.
Backup set type The type of backup set (i.e. Tibero Database Server Backup).
Login ID The login ID of the Tibero server. The default login ID is SYS.
Password The password for the login account.
Host This is the host of the Tibero Database Server. Default uses localhost or 127.0.0.1
Port The port where the connections to the Tibero server is made. The default port is “8629”.
SID The Tibero Database Server System Identifier (SID).

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 Host.
  6. Enter the Port.
  7. Enter the SID.
  8. Click [Next] button to continue.