Overview

Method

Caution

RMGR Backup / RMGR Delete functions cannot be used without connecting to the Catalog

• For databases registered in the Catalog, the backup management responsibility shifts from the individual database to the Catalog.
• The Catalog assigns an appropriate Backup Set ID for each backup and manages to ensure that no backups with the same ID exist within a database having the same DB_NAME.
• Registered databases cannot issue Backup Set IDs on their own, so RMGR backup cannot proceed without the Catalog. Likewise, deletion of backups must be managed through the Catalog, making it impossible to proceed without it.

Note

In a TSC environment, recovery can be performed using backups made by other nodes

• If both the Primary and Standby in a TSC environment are registered in the Catalog, recovery can be performed using backups made by each other's databases.
• To do this, connection to the Catalog using --cat-userid is also required during the recovery process.
• If the latest backup set or the specified (-b|--backup-set) used during recovery was performed on another database and does not exist in the control file, the Catalog automatically adds the necessary backup set information to the control file before proceeding with recovery.

1. Example tbrmgr Commands

$ tbrmgr recover --cat-userid sys/tibero@catalog -o /home/rmgr1/backup
$ tbrmgr backup --cat-userid sys/tibero@catalog -o /home/rmgr1/backup -w
$ tbrmgr delete --cat-userid sys/tibero@catalog -b 1 -o /home/rmgr1/backup

2. Recovery Example

#. The SID of the Catalog DB should be entered beforehand in tbdsn.tbr as follows.
#. tbdsn.tbr

catalog=(
   (INSTANCE=(HOST=[Catalog DB IP])
             (PORT=[Catalog DB Port Number])
             (DB_NAME=[Catalog DB Name])
   )
)



#. Enter the [User id]/[Password]@[Catalog DB SID] for connecting to the catalog db in --cat-userid.
$ tbrmgr backup --cat-userid sys/tibero@catalog -o /home/rmgr1/backup -w

==============================================================================
=   Recovery Manager(RMGR) starts                                            =
=                                                                            =
=   TmaxTibero Corporation Copyright (c) 2020-. All rights reserved.         =
==============================================================================
archive log check succeeded
RMGR '-o' option used
: backing up to /home/rmgr1/backup

==============================================================================
   RMGR - Backup (FULL)
==============================================================================

Recovery Catalog DB resynchronization succeeded

Get new set id 2 from catalog
Initializing the backup progress, it may take few minutes...

BACKUP  (set_id:  2, ts_id:  0, df_id:  0)
100.0% |===============================|   15360/15360   blks    0.00s
Synchronizing...
BACKUP  (set_id:  2, ts_id:  1, df_id:  1)
100.0% |===============================|   25600/25600   blks    1.02s
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% |===============================|   88320/88320   blks    1.02s
Synchronizing...



Switching an online logfile...
Backing up archive logfiles...
Archivelog log-tibero-t0-r272923-s13.arc (thread: 0, set_id: 2, low_tsn: 349747, next_tsn: 394898) backed up

Archive logfiles backup succeeded

Backing up the control file...
Backup set update to Recovery Catalog DB succeeded
Control file backup succeeded

Database backup succeeded

RMGR backup ends