$ tbsql SYS/tibero
tbSQL 7
TmaxData Corporation Copyright (C) 2008-. All rights reserved.
Connected to Tibero
SQL>
!
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
- 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.
- 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).
- 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).
- 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
- 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.
- 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.
- 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
- CloudBacko Pro only supports Tibero 6 and 7.
- 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
- Backup and restore of Tibero database(s) running on a remote machine is not supported.
- 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)
- 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.
- To recover a full Tibero database instance, the following items must be selected in the backup source:
- Tibero Database Server must be selected.
-
All databases including SYSTEM, TBS1, UNDO, 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.
NOTE: Even if the “TEMP” is selected in the backup source, this database will be skipped during a backup job.
- Restore to Alternate location is not possible with a Tibero Database Server during a Backup Set Restore process.
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:
- Type in a meaningful backup set name.
- Select the backup set type.
- Enter the Login ID.
- Enter the Password.
- Enter the Host.
- Enter the Port.
- Enter the SID.
- Click [Next] button to continue.