Document Type | Technical Information
Category | Utility
Applicable Product Versions | Tibero 7.2.3, Tibero 7.2.4
Document Number | TUTTI032
Overview
This document describes a method to perform TSC synchronization using tbrmgr without system downtime.
This document is applicable after TAC - TSC installation; please refer to the separate manual for TAC - TSC installation.
Method
Current Configuration
Example Configuration
Check synchronization status before configuration
SQL> select STANDBY_ADDR, TYPE, FLAGS from v$standby_dest ; STANDBY_ADDR TYPE FLAGS -------------------- -------------------------------- -------------------------------- Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED 9 rows selected.Perform backup using tbrmgr - [Execute on Primary]
- Perform backup with the command: tbrmgr backup --for-standby -o [/backup/destination/path].
- On TAC (Primary Node), if both nodes share the same LOG_ARCHIVE_DEST path, tbrmgr backup can be performed while both TAC nodes are running. However, if the LOG_ARCHIVE_DEST paths differ between nodes, you must shut down one node before performing backup with tbrmgr.
[tibero@node1 ~]$ tbrmgr backup --for-standby -o /tibero/tbrmgr/ ============================================================================== = Recovery Manager(RMGR) starts = = = = TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. = ============================================================================== archive log check succeeded RMGR '-o' option used : backing up to /tibero/tbrmgr/ ============================================================================== RMGR - Backup (FOR STANDBY) ============================================================================== Initializing the backup progress, it may take few minutes... BACKUP (set_id: 2, ts_id: 0, df_id: 0) 100.0% |===============================| 12992/12992 blks 1.01s Synchronizing... BACKUP (set_id: 2, ts_id: 1, df_id: 1) 100.0% |===============================| 12800/12800 blks 0.00s Synchronizing... BACKUP (set_id: 2, ts_id: 3, df_id: 2) 100.0% |===============================| 12800/12800 blks 0.00s Synchronizing... BACKUP (set_id: 2, ts_id: 4, df_id: 3) 100.0% |===============================| 130560/130560 blks 1.02s Synchronizing... BACKUP (set_id: 2, ts_id: 5, df_id: 4) 100.0% |===============================| 12800/12800 blks 0.00s Synchronizing... BACKUP (set_id: 2, ts_id: 6, df_id: 5) 100.0% |===============================| 12800/12800 blks 0.00s Synchronizing... BACKUP (set_id: 2, ts_id: 7, df_id: 6) 100.0% |===============================| 12800/12800 blks 0.00s Synchronizing... Switching an online logfile... Backing up archive logfiles... Archivelog log-t0-r0-s31.arc (thread: 0, set_id: 2, low_tsn: 2098374, next_tsn: 2116547) 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 endsTransfer the backup files obtained by tbrmgr to the standby server and build standby using tbrmgr
[tibero@node3 ~] sftp tsc@10.10.10.65 tsc@10.10.10.65's password: Connected to 10.10.10.65. sftp> get -r /tibero/tbrmgr /tibero/. Fetching /tibero/tbrmg/ to /tibero/./tbrmgr/. Retrieving /tibero/tbrmgr bkp_20260320_3_0_0_0 bkl_3_t0_redo011.redo bkl_3_t0_redo021.redo bkp_20260320_3_1_1_0 bkp_20260320_3_4_3_0 bkl_3_t0_redo001.redo bkl_3_t0_r0_s16.arc bkp_20260320_3_cf_0 bkp_20260320_3_3_2_0Perform standby recovery using tbrmgr
- Use the command: tbrmgr recover --for-standby -o [/path/to/received/backup]
- The existing control files on the standby server must be deleted before recovery.
[root@node3 tbdata]$ tbrmgr recover --for-standby -o /tools/tbrmgr ============================================================================== = Recovery Manager(RMGR) starts = = = = TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. = ============================================================================== RMGR '-o' option used : restoring from /tools/tbrmgr ============================================================================== RMGR - recovery (STANDBY) ============================================================================== CM information =========================================================== CM NAME : cm2 CM UI PORT : 28629 RESOURCE FILE PATH : /root/tibero_engine/config/cm0_res_file CM MODE : GUARD ON, FENCE OFF, ROOT ON LOG LEVEL : 2 CM BLOCK SIZE : 1024 =========================================================== Trying to shutdown other instances =============================== SUCCESS! =============================== Succeeded to request at the local node to stop the service. Please use "cmrctl show service" command to verify the result. ======================================================================= Shutdown succeeded 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 (/share/tac/tbctl1/c1.ctl) is NOT accessible Control file #1 (/share/tac/tbctl2/c2.ctl) is NOT accessible No existing control files are found. The backup control file must be restored. Recover control file #0 /share/tac/tbctl1/c1.ctl from /tools/tbrmgr/bkp_20260327_2_cf_0 Recover control file #1 /share/tac/tbctl2/c2.ctl from /tools/tbrmgr/bkp_20260327_2_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 /root/tibero_engine/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: 2 Last incremental backup set_id: 2 RESTORE (set_id: 2, ts_id: 0, df_id: 0) - FULL BACKUP 100.0% |===============================| 12992/12992 blks 0.00s Synchronizing... RESTORE (set_id: 2, ts_id: 1, df_id: 1) - FULL BACKUP 100.0% |===============================| 12800/12800 blks 0.00s Synchronizing... RESTORE (set_id: 2, ts_id: 3, df_id: 2) - FULL BACKUP 100.0% |===============================| 12800/12800 blks 0.00s Synchronizing... RESTORE (set_id: 2, ts_id: 4, df_id: 3) - FULL BACKUP 100.0% |===============================| 130560/130560 blks 3.05s Synchronizing... RESTORE (set_id: 2, ts_id: 5, df_id: 4) - FULL BACKUP 100.0% |===============================| 12800/12800 blks 0.00s Synchronizing... RESTORE (set_id: 2, ts_id: 6, df_id: 5) - FULL BACKUP 100.0% |===============================| 12800/12800 blks 1.01s Synchronizing... RESTORE (set_id: 2, ts_id: 7, df_id: 6) - FULL BACKUP 100.0% |===============================| 12800/12800 blks 0.00s Synchronizing... Settling... Restoring logfiles... Archivelog log-t0-r0-s31.arc (thread: 0, set_id: 2, low_tsn: 2098374, next_tsn: 2116547) 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 /root/tibero_engine/bin/prof. Listener port = 8629 Tibero 7 TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. Tibero instance started up (RECOVERY mode). RMGR recovery endsSet TSC synchronization parameters in $TB_SID.tip file (Execute on Primary - ignore if already set)
LOG_REPLICATION_MODE=PERFORMANCE LOG_REPLICATION_DEST_1="10.10.10.67:8633 LGWR ASYNC" LOG_REPLICATION_1_ENABLE=YVerify synchronization on the primary server
SQL> select STANDBY_ADDR, TYPE, FLAGS from v$standby_dest ; STANDBY_ADDR TYPE FLAGS -------------------- -------------------------------- -------------------------------- 10.10.10.67:8633 LGWR ASYNC MAIN CONNECTED 10.10.10.67:8633 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED Not Assigned:0 LGWR DEAD NODE PROXY NOT CONNECTED 9 rows selected.
Troubleshooting
If the password for the sys account differs, backup using tbrmgr will not be performed correctly.
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 perform the operation using the '--userid' property.
Use '--userid sys/'[password]@[your own alias in tbdsn.tbr]' when executing.
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 endsIf an existing control file exists on the standby server during recovery using tbrmgr, the process will not proceed as below.
โป The process will proceed normally after deleting the control file on the standby server and re-executing.
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.'If both TAC nodes are running and the LOG_ARCHIVE_DEST paths differ between nodes, backup will not proceed when running tbrmgr.
[tibero@node1 ~]$ tbrmgr backup --for-standby -o /root/tbrmgr/ ============================================================================== = Recovery Manager(RMGR) starts = = = = TmaxTibero Corporation Copyright (c) 2020-. All rights reserved. = ============================================================================== archive log check succeeded RMGR Error: All instances must have same LOG_ARCHIVE_DEST on the shared disk to backup archive logfiles.In this situation, you must shut down the other node that is not running the 'tbrmgr backup --for-standby' command and then execute tbrmgr.