{"id":678,"date":"2020-02-17T22:20:14","date_gmt":"2020-02-18T01:20:14","guid":{"rendered":"http:\/\/www.fernandosimon.com\/blog\/?p=678"},"modified":"2020-07-19T19:12:26","modified_gmt":"2020-07-19T22:12:26","slug":"zdlra-osb-and-clone-to-tape","status":"publish","type":"post","link":"https:\/\/www.fernandosimon.com\/blog\/zdlra-osb-and-clone-to-tape\/","title":{"rendered":"ZDLRA, OSB and Clone to Tape"},"content":{"rendered":"

As you saw in my last post<\/a>, the configuration to enable clone to tape for ZDLRA it is not complicated, but you need to take care of some details to avoid errors. Besides that, ZDLRA relies on OSB to do that (when configured with native tape support) and this has some details that you need to be aware of.<\/p>\n

In this post, I will show how the clone to tape works for ZDLRA. And how you can check some details about OSB.<\/p>\n

<\/p>\n

Basic Config<\/h2>\n

Below you can see how I configured the clone to tape templates:<\/p>\n

SQL> BEGIN\r\n  2      DBMS_RA.CREATE_SBT_JOB_TEMPLATE (\r\n  3          template_name => 'ONLYTAPE_FULL_ARCH',\r\n  4          protection_policy_name => 'ZDLRA_ONLY_TAPE',\r\n  5          attribute_set_name => 'bronzerepfull',\r\n  6          backup_type => 'FULL,ARCH',\r\n  7          priority => DBMS_RA.SBT_PRIORITY_LOW,\r\n  8          window => INTERVAL '4' HOUR\r\n  9      );\r\n 10  END;\r\n 11  \/\r\n\r\nPL\/SQL procedure successfully completed.\r\n\r\nSQL> BEGIN\r\n  2      DBMS_RA.CREATE_SBT_JOB_TEMPLATE (\r\n  3          template_name => 'ONLYTAPE_ARCH',\r\n  4          protection_policy_name => 'ZDLRA_ONLY_TAPE',\r\n  5          attribute_set_name => 'bronzerepfull',\r\n  6          backup_type => 'ARCH',\r\n  7          priority => DBMS_RA.SBT_PRIORITY_LOW,\r\n  8          window => INTERVAL '4' HOUR\r\n  9      );\r\n 10  END;\r\n 11  \/\r\n\r\nPL\/SQL procedure successfully completed.\r\n\r\nSQL><\/pre>\n
Basic configuration for the protection policy ZDLRA_ONLY_TAPE and with FULL and ARCHIVELOGS clones. For more details, you can check my previous post.<\/p>\n
You can check the table RASYS.RA_SBT_JOB to check all the templates already configured:<\/p>\n
SQL> set linesize 250\r\nSQL> col LIB_NAME format a30\r\nSQL> col TEMPLATE_NAME format a50\r\nSQL> col LAST_SCHEDULE_TIME format a35\r\nSQL> col POLICY_NAME format a50\r\nSQL> select TEMPLATE_NAME, BACKUP_TYPE, LAST_SCHEDULE_TIME, LIB_NAME, DB_UNIQUE_NAME, POLICY_NAME FROM RA_SBT_JOB WHERE LIB_NAME = 'OSBSBT' ;\r\n\r\nTEMPLATE_NAME                                      BACKUP_TYPE      LAST_SCHEDULE_TIME                  LIB_NAME                       DB_UNIQUE_NAME                 POLICY_NAME\r\n-------------------------------------------------- ---------------- ----------------------------------- ------------------------------ ------------------------------ --------------------------------------------------\r\nBRONZE_ARCH                                        ARCH             29-DEC-19 11.59.59.513917 PM +01:00 OSBSBT                                                        ZDLRA_BRONZE\r\nBRONZE_FULL_ARCH                                   FULL, ARCH       03-JAN-20 11.10.27.411320 PM +01:00 OSBSBT                                                        ZDLRA_BRONZE\r\nGOLDEN_ARCH                                        ARCH                                                 OSBSBT                                                        ZDLRA_GOLDEN\r\nGOLDEN_FULL_ARCH                                   FULL, ARCH       01-JAN-20 11.10.47.987397 PM +01:00 OSBSBT                                                        ZDLRA_GOLDEN\r\nONLYTAPE_FULL_ARCH                                 FULL, ARCH                                           OSBSBT                                                        ZDLRA_ONLY_TAPE\r\nONLYTAPE_ARCH                                      ARCH                                                 OSBSBT                                                        ZDLRA_ONLY_TAPE\r\n\r\n6 rows selected.\r\n\r\nSQL><\/pre>\n
Check that if the clone for this template was called you can see the information in the column LAST_SCHEDULE_TIME. And in this case, since I have not created the scheduler for this, it is empty.<\/p>\n
To do that, just created the scheduler for that:<\/p>\n
SQL> BEGIN\r\n  2      DBMS_SCHEDULER.CREATE_JOB(\r\n  3          job_name => 'SBTJOB_ONLYTAPE_FULL_ARCH',\r\n  4          job_type => 'PLSQL_BLOCK',\r\n  5          job_action => 'dbms_ra.queue_sbt_backup_task(''ONLYTAPE_FULL_ARCH'');',\r\n  6          start_date => SYSDATE+(1\/1440),\r\n  7          enabled => TRUE,\r\n  8          auto_drop => TRUE,\r\n  9          repeat_interval => 'freq=WEEKLY; BYDAY=SUN; BYHOUR=20'\r\n 10      );\r\n 11  END;\r\n 12  \/\r\n\r\nPL\/SQL procedure successfully completed.\r\n\r\nSQL> BEGIN\r\n  2      DBMS_SCHEDULER.CREATE_JOB(\r\n  3          job_name => 'SBTJOB_ONLYTAPE_ARCH',\r\n  4          job_type => 'PLSQL_BLOCK',\r\n  5          job_action => 'dbms_ra.queue_sbt_backup_task(''ONLYTAPE_ARCH'');',\r\n  6          start_date => SYSDATE+(1\/1440),\r\n  7          enabled => TRUE,\r\n  8          auto_drop => TRUE,\r\n  9          repeat_interval => 'freq=HOURLY; BYMINUTE=40'\r\n 10      );\r\n 11  END;\r\n 12  \/\r\n\r\nPL\/SQL procedure successfully completed.\r\n\r\nSQL><\/pre>\n
Database Backup<\/h2>\n
For ZDLRA I have the database ORCL18C linked with this protection policy and I have some backups for this database. You can see below the backups for datafile 1:<\/p>\n
RMAN> list backup of datafile 1;\r\n\r\n\r\nList of Backup Sets\r\n===================\r\n\r\n\r\nBS Key  Type LV Size       Device Type Elapsed Time Completion Time\r\n------- ---- -- ---------- ----------- ------------ -------------------\r\n16512   Incr 0  330.35M    SBT_TAPE    00:03:03     02\/02\/2020 16:12:04\r\n        BP Key: 16513   Status: AVAILABLE  Compressed: YES  Tag: BKP-DB-INC0\r\n        Handle: VB$_1891149551_16507I   Media:\r\n  List of Datafiles in backup set 16512\r\n  File LV Type Ckp SCN    Ckp Time            Abs Fuz SCN Sparse Name\r\n  ---- -- ---- ---------- ------------------- ----------- ------ ----\r\n  1    0  Incr 1909028    02\/02\/2020 16:09:01              NO    \/u01\/app\/oracle\/oradata\/ORCL18C\/system01.dbf\r\n\r\nBS Key  Type LV Size       Device Type Elapsed Time Completion Time\r\n------- ---- -- ---------- ----------- ------------ -------------------\r\n16673   Incr 1  96.00K     SBT_TAPE    00:00:04     02\/02\/2020 16:27:01\r\n        BP Key: 16674   Status: AVAILABLE  Compressed: YES  Tag: BKP-DB\r\n        Handle: VB$_1891149551_16669I   Media:\r\n  List of Datafiles in backup set 16673\r\n  File LV Type Ckp SCN    Ckp Time            Abs Fuz SCN Sparse Name\r\n  ---- -- ---- ---------- ------------------- ----------- ------ ----\r\n  1    1  Incr 1910623    02\/02\/2020 16:26:57              NO    \/u01\/app\/oracle\/oradata\/ORCL18C\/system01.dbf\r\n\r\nBS Key  Type LV Size       Device Type Elapsed Time Completion Time\r\n------- ---- -- ---------- ----------- ------------ -------------------\r\n16701   Incr 0  329.22M    SBT_TAPE    00:00:04     02\/02\/2020 16:27:01\r\n        BP Key: 16702   Status: AVAILABLE  Compressed: YES  Tag: BKP-DB\r\n        Handle: VB$_1891149551_16669_1   Media:\r\n  List of Datafiles in backup set 16701\r\n  File LV Type Ckp SCN    Ckp Time            Abs Fuz SCN Sparse Name\r\n  ---- -- ---- ---------- ------------------- ----------- ------ ----\r\n  1    0  Incr 1910623    02\/02\/2020 16:26:57              NO    \/u01\/app\/oracle\/oradata\/ORCL18C\/system01.dbf\r\n\r\nRMAN><\/pre>\n
Check that I have the backupsets 16512 and 16701 that are the full backup. And the same for archivelogs.<\/p>\n
During the Clone<\/h2>\n
When the scheduler trigger the clones, we can follow it inside of ZDLRA in several ways. But the point is that (as usual), for ZDLRA, everything is a task. So, we can see information in the tables RA_TASK and in RA_SBT_TASK.<\/p>\n
You can create your sql\u2019s to check what it is running, but look at this example:<\/p>\n
SQL> col state format a20\r\nSQL> col ERROR_TEXT format a50\r\nSQL> SELECT TASK_ID, STATE, DB_UNIQUE_NAME, ERROR_TEXT, BS_KEY, PIECE# FROM RA_SBT_TASK WHERE LIB_NAME = 'OSBSBT' AND  DB_UNIQUE_NAME = 'ORCL18C' ORDER BY DB_UNIQUE_NAME, BS_KEY, PIECE#;\r\n\r\n   TASK_ID STATE                DB_UNIQUE_NAME                 ERROR_TEXT                                             BS_KEY     PIECE#\r\n---------- -------------------- ------------------------------ -------------------------------------------------- ---------- ----------\r\n     33698 EXECUTABLE           ORCL18C                                                                                16542          1\r\n     33700 EXECUTABLE           ORCL18C                                                                                16565          1\r\n     33702 EXECUTABLE           ORCL18C                                                                                16582          1\r\n     33721 EXECUTABLE           ORCL18C                                                                                16618          1\r\n     33704 EXECUTABLE           ORCL18C                                                                                16701          1\r\n     33722 EXECUTABLE           ORCL18C                                                                                16706          1\r\n     33706 EXECUTABLE           ORCL18C                                                                                16725          1\r\n     33708 EXECUTABLE           ORCL18C                                                                                16734          1\r\n     33710 EXECUTABLE           ORCL18C                                                                                16743          1\r\n     33712 EXECUTABLE           ORCL18C                                                                                16752          1\r\n     33714 EXECUTABLE           ORCL18C                                                                                16761          1\r\n\r\n   TASK_ID STATE                DB_UNIQUE_NAME                 ERROR_TEXT                                             BS_KEY     PIECE#\r\n---------- -------------------- ------------------------------ -------------------------------------------------- ---------- ----------\r\n     33716 EXECUTABLE           ORCL18C                                                                                16782          1\r\n     33718 EXECUTABLE           ORCL18C                                                                                16791          1\r\n     33723 EXECUTABLE           ORCL18C                                                                                16795          1\r\n     33720 EXECUTABLE           ORCL18C                                                                                16825          1\r\n\r\n15 rows selected.\r\n\r\nSQL><\/pre>\n
The output above I picked up exactly when the job SBTJOB_ONLYTAPE_FULL_ARCH was running. You can see that ZDLRA put all the backupsets that was not cloned yet in the queue. At this moment, ZDLRA is creating the backupsets (since they exist jus in RA.VBDF table) and sending them (one to one) to OSB.<\/p>\n
You can do the same for RA_TASK:<\/p>\n
SQL> select TASK_ID, TASK_TYPE, STATE, WAITING_ON, DB_KEY, DB_UNIQUE_NAME, CREATION_TIME, ERROR_COUNT, INTERRUPT_COUNT, BP_KEY,BS_KEY,DF_KEY,VB_KEY from rasys.ra_task where DB_UNIQUE_NAME = 'ORCL18C' and task_type LIKE '%SBT' order by 5,2,7,10,11,12,13;\r\n\r\n   TASK_ID TASK_TYPE                      STATE                     WAITING_ON     DB_KEY DB_UNIQUE_NAME                 CREATION_TIME                       ERROR_COUNT INTERRUPT_COUNT     BP_KEY     BS_KEY     DF_KEY     VB_KEY\r\n---------- ------------------------------ ------------------------- ---------- ---------- ------------------------------ ----------------------------------- ----------- --------------- ---------- ---------- ---------- ----------\r\n     33698 BACKUP_SBT                     RUNNING                                   15993 ORCL18C                        02-FEB-20 04.40.36.631549 PM +01:00           0               0                 16542\r\n     33700 BACKUP_SBT                     RUNNING                                   15993 ORCL18C                        02-FEB-20 04.40.36.833354 PM +01:00           0               0                 16565\r\n     33702 BACKUP_SBT                     RUNNING                                   15993 ORCL18C                        02-FEB-20 04.40.36.844599 PM +01:00           0               0                 16582\r\n     33704 BACKUP_SBT                     EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.861902 PM +01:00           0               0                 16701\r\n     33706 BACKUP_SBT                     EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.883175 PM +01:00           0               0                 16725\r\n     33708 BACKUP_SBT                     EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.898718 PM +01:00           0               0                 16734\r\n     33710 BACKUP_SBT                     EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.905336 PM +01:00           0               0                 16743\r\n     33712 BACKUP_SBT                     EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.924090 PM +01:00           0               0                 16752\r\n     33714 BACKUP_SBT                     EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.939241 PM +01:00           0               0                 16761\r\n     33716 BACKUP_SBT                     EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.961104 PM +01:00           0               0                 16782\r\n     33718 BACKUP_SBT                     EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.980517 PM +01:00           0               0                 16791\r\n\r\n   TASK_ID TASK_TYPE                      STATE                     WAITING_ON     DB_KEY DB_UNIQUE_NAME                 CREATION_TIME                       ERROR_COUNT INTERRUPT_COUNT     BP_KEY     BS_KEY     DF_KEY     VB_KEY\r\n---------- ------------------------------ ------------------------- ---------- ---------- ------------------------------ ----------------------------------- ----------- --------------- ---------- ---------- ---------- ----------\r\n     33720 BACKUP_SBT                     EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.992346 PM +01:00           0               0                 16825\r\n     33721 BACKUP_SBT                     EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.37.059282 PM +01:00           0               0                 16618\r\n     33722 BACKUP_SBT                     EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.37.061375 PM +01:00           0               0                 16706\r\n     33723 BACKUP_SBT                     EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.37.063679 PM +01:00           0               0                 16795\r\n     33699 PLAN_SBT                       COMPLETED                                 15993 ORCL18C                        02-FEB-20 04.40.36.783661 PM +01:00           0               0                 16542      16014      16538\r\n     33701 PLAN_SBT                       COMPLETED                                 15993 ORCL18C                        02-FEB-20 04.40.36.834255 PM +01:00           0               0                 16565      16012      16561\r\n     33703 PLAN_SBT                       COMPLETED                                 15993 ORCL18C                        02-FEB-20 04.40.36.845368 PM +01:00           0               0                 16582      16018      16577\r\n     33705 PLAN_SBT                       COMPLETED                                 15993 ORCL18C                        02-FEB-20 04.40.36.862820 PM +01:00           0               0                 16701      16006      16669\r\n     33707 PLAN_SBT                       COMPLETED                                 15993 ORCL18C                        02-FEB-20 04.40.36.883803 PM +01:00           0               0                 16725      16008      16710\r\n     33709 PLAN_SBT                       COMPLETED                                 15993 ORCL18C                        02-FEB-20 04.40.36.899324 PM +01:00           0               0                 16734      16022      16729\r\n     33711 PLAN_SBT                       COMPLETED                                 15993 ORCL18C                        02-FEB-20 04.40.36.906037 PM +01:00           0               0                 16743      16010      16738\r\n\r\n   TASK_ID TASK_TYPE                      STATE                     WAITING_ON     DB_KEY DB_UNIQUE_NAME                 CREATION_TIME                       ERROR_COUNT INTERRUPT_COUNT     BP_KEY     BS_KEY     DF_KEY     VB_KEY\r\n---------- ------------------------------ ------------------------- ---------- ---------- ------------------------------ ----------------------------------- ----------- --------------- ---------- ---------- ---------- ----------\r\n     33713 PLAN_SBT                       EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.924844 PM +01:00           0               0                 16752      16020      16747\r\n     33715 PLAN_SBT                       EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.939997 PM +01:00           0               0                 16761      16024      16756\r\n     33717 PLAN_SBT                       EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.961701 PM +01:00           0               0                 16782      16016      16777\r\n     33719 PLAN_SBT                       EXECUTABLE                                15993 ORCL18C                        02-FEB-20 04.40.36.981277 PM +01:00           0               0                 16791      16026      16786\r\n\r\n26 rows selected.\r\n\r\nSQL><\/pre>\n
Inside OSB<\/h3>\n
At OSB side we can check some information about how it is processing the clones. For OSB, everything is one job, and we can check in with obtool.<\/p>\n
To check the jobs we execute obtool lsjob:<\/p>\n
[root@zdlras1n1 ~]# obtool lsjob\r\nJob ID           Sched time  Contents                       State\r\n---------------- ----------- ------------------------------ ---------------------------------------\r\noracle\/38        none        database ORCL18C (dbid=558466555) processed; Oracle job(s) scheduled\r\noracle\/38.2      none        datafile backup                running since 2020\/02\/02.16:43\r\noracle\/38.4      none        datafile backup                running since 2020\/02\/02.16:44\r\n[root@zdlras1n1 ~]#<\/pre>\n
Some important information here. For every scheduler that was triggered by ZDLRA, we can see the job for each database, in this case, oracle\/38<\/em>. This is the master job, just to control what is happening. If you have more than one database in the same job being cloned, you will see more.<\/p>\n
For each backupset that it is needed to be cloned, you will see child jobs (derived from the master). And for this, we can see logs from what is happening. All the logs for OSB are in the folder \/usr\/etc\/ob\/xcr\/<\/em>. Doing a cat from one finished job we can see useful information:<\/p>\n
[root@zdlras1n1 ~]# cat \/usr\/etc\/ob\/xcr\/oracle@38.2\r\n[4100000001]2020\/02\/02.16:43:15 ______________________________________________________________________\r\n[4100000001]2020\/02\/02.16:43:15\r\n[4100000002]2020\/02\/02.16:43:15         Transcript for job oracle\/38.2 running on zdlras1n1\r\n[4100000002]2020\/02\/02.16:43:15\r\n[3100000003]2020\/02\/02.16:43:15 Info: mount data verified.\r\n[3100000004]2020\/02\/02.16:43:15 Info: volume in tape04 is usable for this operation.\r\n[1100000005]2020\/02\/02.16:43:15 (pvfw) not at BOT\r\n[1100000006]2020\/02\/02.16:43:15 (pvfw) previous state is invalid\r\n[1100000007]2020\/02\/02.16:43:15 (alv)  backup image label is valid, file 21, section 1\r\n[1100000008]2020\/02\/02.16:43:15 (pvfw) at OB EOD, returning (1)\r\n[1100000009]2020\/02\/02.16:43:15 (pvfw) pos_vol_cleanup not returning pstate\r\n[010000000A]2020\/02\/02.16:43:15 (dmap) tape04 success\r\n[410000000B]Volume label:\r\n[410000000C]    Volume tag:             E01011L4\r\n[410000000D]    Volume UUID:            a1f8db28-109b-1038-847b-080027b2a93d\r\n[410000000E]    Volume ID:              zdlras1-osbmf-000006\r\n[410000000F]    Volume set ID:          zdlras1-osbmf-000002\r\n[4100000010]    Previous volume:        zdlras1-osbmf-000002\r\n[4100000011]    Volume sequence:        2\r\n[4100000012]    Volume set owner:       root\r\n[4100000013]    Volume set created:     Sun Dec 29 23:35:18 2019\r\n[4100000014]    Volume set closes:      Wed Oct 19 00:35:18 2022 (no writes after this time)\r\n[4000000015]    Media family:           zdlras1-osbmf\r\n[4100000016]\r\n[4100000017]    Volume set expires: never; content manages reuse\r\n[4100000018]\r\n[4100000019]Archive label:\r\n[410000001A]    File number:            21\r\n[410000001B]    File section:           1\r\n[410000001C]    Owner:                  root\r\n[410000001D]    Client host:            zdlras1n1\r\n[410000001E]    Backup level:           0\r\n[410000001F]    S\/w compression:        no\r\n[4100000020]    Archive created:        Sun Feb 02 16:43:15 2020\r\n[4100000021]    Archive owner:          oracle (UUID bbad0004-01a9-1038-abb2-080027b2a93d)\r\n[4100000022]    Owner class:            oracle (UUID a43aa638-01a9-1038-8809-080027b2a93d)\r\n[4100000023]    Backup piece name:      RA_SBT_ORCL18C_558466555_16849_rpunhlqh_1_2_16701\r\n[4100000024]    Backup db name:         ORCL18C\r\n[4100000025]    Backup db id:           558466555\r\n[4100000026]    Backup copy number:     not applicable\r\n[4100000027]    Backup content:         full\r\n[4100000028]    Encryption:             off\r\n[4100000029]    Catalog data:           no\r\n[410000002A]    Backup image UUID:      4599459c-27f8-1038-adc6-080027b2a93d\r\n[410000002B]    Backup instance UUID:   459945b0-27f8-1038-adc6-080027b2a93d\r\n[410000002C]    Backup instance created:Sun Feb 02 16:43:15 2020\r\n[410000002D]\r\n[410000002E]\r\n[410000002E]Backup statistics:\r\n[410000002F]status 0\r\n[4000000030]devices\r\n[4000000031] tape04\r\n[4100000032]\r\n[4000000033]volumes\r\n[4000000034] zdlras1-osbmf-000006\r\n[4100000035]\r\n[4000000036]voltags\r\n[4000000037] E01011L4\r\n[4100000038]\r\n[4100000039]file 21\r\n[410000003A]host zdlras1n1\r\n[410000003B]encryption off\r\n[410000003C]compression no\r\n[410000003D]start_time  Sun Feb 02 2020 at 16:43:15 (1580658195)\r\n[410000003E]end_time    Sun Feb 02 2020 at 16:44:20 (1580658260)\r\n[410000003F]backup_time Sun Feb 02 2020 at 16:43:15 (1580658195)\r\n[4100000040]dev_kbytes 753036\r\n[4100000041]dev_iosecs 60\r\n[4100000042]dev_iorate 12.9 MB\/S\r\n[4100000043]wrt_iosecs 65\r\n[4100000044]wrt_iorate 11.9 MB\/S\r\n[4100000045]physical_blks_written 368\r\n[4100000046]write_errors 0\r\n[4100000047]physical_blks_read 0\r\n[4100000048]read_errors 0\r\n[4100000049]error_rate 0%\r\n[410000004A]piece RA_SBT_ORCL18C_558466555_16849_rpunhlqh_1_2_16701 completed, status 0\r\n[root@zdlras1n1 ~]#<\/pre>\n
Some important details from there:<\/p>\n