Document Type | Technical Information
Category | Utility
Applicable Product Versions | Tibero 7.2.3, Tibero 7.2.4
Document Number | TUTTI031
Overview
This document describes how to perform TSC synchronization using tbrmgr without system downtime.
Since this document applies after TSC installation, please refer to a separate manual for TSC installation.
Configuration Status
Method
Configuration Example
Check synchronization status before configuration
SQL> select * from v$standby_dest;
STANDBY_ADDR TYPE THREAD# FLAGS SENT_SEQ SENT_BLKNO ACKED_SEQ ACKED_BLKNO DELAY
------------------------------ -------------------- ---------- -------------------- ---------- ---------- ---------- ----------- ----------
192.168.41.164:8633 LGWR ASYNC MAIN 0 NOT CONNECTED -1 -1 -1 -1 0
Perform backup using tbrmgr - [Executed on Primary]
- Execute backup with tbrmgr backup --for-standby -o [/backup/destination/path].
tsc@localhost /data ➤ tbrmgr backup --for-standby -o /data/rmgr_dir
==============================================================================
= Recovery Manager(RMGR) starts =
= =
= TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. =
==============================================================================
archive log check succeeded
RMGR '-o' option used
: backing up to /data/rmgr_dir
==============================================================================
RMGR - Backup (FOR STANDBY)
==============================================================================
Initializing the backup progress, it may take few minutes...
BACKUP (set_id: 3, ts_id: 0, df_id: 0)
100.0% |===============================| 12800/12800 blks 1.02s
Synchronizing...
BACKUP (set_id: 3, ts_id: 1, df_id: 1)
100.0% |===============================| 12800/12800 blks 1.01s
Synchronizing...
BACKUP (set_id: 3, ts_id: 3, df_id: 2)
100.0% |===============================| 16384/16384 blks 0.00s
Synchronizing...
BACKUP (set_id: 3, ts_id: 4, df_id: 3)
100.0% |===============================| 38400/38400 blks 2.04s
Synchronizing...
Switching an online logfile...
Backing up archive logfiles...
Archivelog log-t0-r0-s16.arc (thread: 0, set_id: 3, low_tsn: 248382, next_tsn: 250392) backed up
Archive logfiles backup succeeded
Backing up online logfiles...
Backing up the control file...
Control file backup succeeded
Backing up the password file...
Password file backup succeeded
Database backup succeeded
RMGR backup ends
Transfer the backup files received by tbrmgr to the standby server - [Executed on Standby Server]
tsc@localhost ~ ➤ sftp tsc@192.168.41.163
tsc@192.168.41.163's password:
Connected to 192.168.41.163.
sftp> get -r /data/rmgr_dir /data/.
Fetching /data/rmgr_dir/ to /data/./rmgr_dir
Retrieving /data/rmgr_dir
bkp_20260320_3_0_0_0 100% 100MB 229.9MB/s 00:00
bkl_3_t0_redo011.redo 100% 50MB 240.2MB/s 00:00
bkl_3_t0_redo021.redo 100% 50MB 235.7MB/s 00:00
bkp_20260320_3_1_1_0 100% 100MB 240.2MB/s 00:00
passwd 100% 88 271.8KB/s 00:00
bkp_20260320_3_4_3_0 100% 300MB 239.5MB/s 00:01
bkl_3_t0_redo001.redo 100% 50MB 283.3MB/s 00:00
bkl_3_t0_r0_s16.arc 100% 2156KB 192.5MB/s 00:00
bkp_20260320_3_cf_0 100% 73MB 245.9MB/s 00:00
bkp_20260320_3_3_2_0 100% 128MB 223.3MB/s 00:00
tsc@localhost /data/rmgr_dir ➤ ls -alrt
total 874060
drwxr-xr-x. 6 tsc dba 4096 Mar 20 09:56 ..
-rw-------. 1 tsc dba 104857600 Mar 20 09:56 bkp_20260320_3_0_0_0
-rw-------. 1 tsc dba 52428800 Mar 20 09:56 bkl_3_t0_redo011.redo
-rw-------. 1 tsc dba 52428800 Mar 20 09:56 bkl_3_t0_redo021.redo
-rw-------. 1 tsc dba 104857600 Mar 20 09:57 bkp_20260320_3_1_1_0
-rw-------. 1 tsc dba 88 Mar 20 09:57 passwd
-rw-------. 1 tsc dba 314572800 Mar 20 09:57 bkp_20260320_3_4_3_0
-rw-------. 1 tsc dba 52428800 Mar 20 09:57 bkl_3_t0_redo001.redo
-rw-------. 1 tsc dba 2207744 Mar 20 09:57 bkl_3_t0_r0_s16.arc
-rw-------. 1 tsc dba 77021184 Mar 20 09:57 bkp_20260320_3_cf_0
drwxr-xr-x. 2 tsc dba 4096 Mar 20 09:57 .
-rw-------. 1 tsc dba 134217728 Mar 20 09:57 bkp_20260320_3_3_2_0
Configure standby recovery using tbrmgr
- Run tbrmgr recover --for-standby -o [/received/backup/path]
- The existing control file on the standby server must be deleted.
tsc@localhost /data ➤ rm /data/tbdata/c1.ctl
tsc@localhost /data ➤ tbrmgr recover --for-standby -o /data/rmgr_dir
==============================================================================
= Recovery Manager(RMGR) starts =
= =
= TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. =
==============================================================================
RMGR '-o' option used
: restoring from /data/rmgr_dir
==============================================================================
RMGR - recovery (STANDBY)
==============================================================================
Shutting down the instance...
tbdown failed. proc info file is deleted.
Hint: Please check if the tbsvr instance was already stopped.
info file is deleted.
unlink failed.: No such file or directory
Control file #0 (/data/tbdata/c1.ctl) is NOT accessible
No existing control files are found. The backup control file must be restored.
Recover control file #0 /data/tbdata/c1.ctl from /data/rmgr_dir/bkp_20260320_3_cf_0
Control files are recovered from the backup control file.
Restoring the password file...
Password file restoration succeeded
Booting up the instance...
Change core dump dir to /home/tsc/tibero7/bin/prof.
Listener port = 8629
Tibero 7
TmaxTibero Corporation Copyright (c) 2020-. All rights reserved.
Tibero instance started up (MOUNT mode).
Initializing the restore progress, it may take few minutes...
RMGR begins restoring backup files.
Full backup set_id: 3
Last incremental backup set_id: 3
RESTORE (set_id: 3, ts_id: 0, df_id: 0) - FULL BACKUP
100.0% |===============================| 12800/12800 blks 0.00s
Synchronizing...
RESTORE (set_id: 3, ts_id: 1, df_id: 1) - FULL BACKUP
100.0% |===============================| 12800/12800 blks 0.00s
Synchronizing...
RESTORE (set_id: 3, ts_id: 3, df_id: 2) - FULL BACKUP
100.0% |===============================| 16384/16384 blks 0.00s
Synchronizing...
RESTORE (set_id: 3, ts_id: 4, df_id: 3) - FULL BACKUP
100.0% |===============================| 38400/38400 blks 0.00s
Synchronizing...
Settling...
Restoring logfiles...
Archivelog log-t0-r0-s16.arc (thread: 0, set_id: 3, low_tsn: 248382, next_tsn: 250392) restored
Archive logfiles restoration succeeded
Restoring online logfiles...
Database restoration succeeded
recoverSQL: ALTER DATABASE RECOVER AUTOMATIC FOR STANDBY
Database automatic recovery succeeded
Shutting down the instance...
Tibero instance terminated (NORMAL mode).
Booting up the instance...
Change core dump dir to /home/tsc/tibero7/bin/prof.
Listener port = 8629
Tibero 7
TmaxTibero Corporation Copyright (c) 2020-. All rights reserved.
Tibero instance started up (RECOVERY mode).
RMGR recovery ends
Check synchronization on the primary server
SQL> select * from v$standby_dest;
STANDBY_ADDR TYPE THREAD# FLAGS SENT_SEQ SENT_BLKNO ACKED_SEQ ACKED_BLKNO DELAY
-------------------- -------------------- ---------- -------------------- ---------- ---------- ---------- ----------- ----------
192.168.41.164:8633 LGWR ASYNC MAIN 0 CONNECTED 17 32 17 32 0
1 row selected.
Troubleshooting
If the password for the sys account is different, backup will not be performed correctly when running tbrmgr.
SQL> alter user sys identified by 'Tibero123!@#';
User 'SYS' altered.
tsc@localhost ~ ➤ tbrmgr backup --for-standby -o /data/rmgr_dir
==============================================================================
= Recovery Manager(RMGR) starts =
= =
= TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. =
==============================================================================
RMGR Error: can't connect to Databases.
RMGR Server Error: -17001
<Solution>
You can run it using the '--userid' property.
Run with '--userid sys/'[password]@[your own alias in tbdsn.tbr]'.
tsc@localhost ~ ➤ tbrmgr backup --for-standby -o /data/rmgr_dir --userid sys/'Tibero123!@#@tsc'
==============================================================================
= Recovery Manager(RMGR) starts =
= =
= TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. =
==============================================================================
archive log check succeeded
RMGR '-o' option used
: backing up to /data/rmgr_dir
==============================================================================
RMGR - Backup (FOR STANDBY)
==============================================================================
Initializing the backup progress, it may take few minutes...
BACKUP (set_id: 4, ts_id: 0, df_id: 0)
100.0% |===============================| 12800/12800 blks 0.00s
Synchronizing...
BACKUP (set_id: 4, ts_id: 1, df_id: 1)
100.0% |===============================| 12800/12800 blks 0.00s
Synchronizing...
BACKUP (set_id: 4, ts_id: 3, df_id: 2)
100.0% |===============================| 16384/16384 blks 0.00s
Synchronizing...
BACKUP (set_id: 4, ts_id: 4, df_id: 3)
100.0% |===============================| 39680/39680 blks 0.00s
Synchronizing...
Switching an online logfile...
Backing up archive logfiles...
Archivelog log-t0-r0-s17.arc (thread: 0, set_id: 4, low_tsn: 250392, next_tsn: 251553) backed up
Archive logfiles backup succeeded
Backing up online logfiles...
Backing up the control file...
Control file backup succeeded
Backing up the password file...
Password file backup succeeded
Database backup succeeded
RMGR backup ends
If an existing control file exists during recover using tbrmgr on the standby server, the process will not proceed as shown below.
※ The process works normally after deleting the control file on the standby server and retrying.
tsc@localhost /data ➤ tbrmgr recover --for-standby -o /data/rmgr_dir
==============================================================================
= Recovery Manager(RMGR) starts =
= =
= TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. =
==============================================================================
RMGR '-o' option used
: restoring from /data/rmgr_dir
==============================================================================
RMGR - recovery (STANDBY)
==============================================================================
Shutting down the instance...
shmget failed. errno: 2
Tibero instance terminated (ABNORMAL mode).
info file is deleted.
unlink failed.: No such file or directory
Control file #0 (/data/tbdata/c1.ctl) is accessible
RMGR Error: Control files must not exist for the option '--for-standby.'