Oracle DBaaS 1z0-160 part 6:Creating you first single instance database in Oracle cloud

1.You will get following dashboard once you login to oracle cloud

2.Please select Database option as below

3.Please select option “Custom”

4.Please provide below details

4.a Instance Name:-

The name for the new database deployment. The name:

  • Must not exceed 50 characters.
  • Must start with a letter.
  • Must contain only letters, numbers, or hyphens.
  • Must not contain any other special characters.
  • Must be unique within the identity domain.
4.b Region:-

(Available only if your identity domain is enabled for regions.)

If you choose a region that supports Oracle Cloud Infrastructure, the Availability Domain and Subnet fields are displayed, and the deployment will be created on Oracle Cloud Infrastructure. Otherwise, the deployment will be created on Oracle Cloud Infrastructure Classic. Choose No Preference to let Database Cloud Service choose an Oracle Cloud Infrastructure Classic region for you.

Note: If you are creating a database deployment that uses Oracle Data Guard on Oracle Cloud Infrastructure Classic, choose the value No Preference. Currently, region specification is not supported for deployments that use Oracle Data Guard on Oracle Cloud Infrastructure Classic.

4.c Availability Domain

(Available only on Oracle Cloud Infrastructure) The availability domain (within the region) where the database deployment will be placed.

4.d Subnet

(Available only on Oracle Cloud Infrastructure) The subnet (within the availability domain) that will determine network access to the database deployment.

4.e Service level

The service level for the new deployment:

Oracle Database Cloud Service

Oracle Database Cloud Service – Virtual Image (Not available in accounts that use the Universal Credits payment model) (Not available on Oracle Cloud

Infrastructure)

4.f IP NETWORK

Select the IP network where you want the database deployment placed.

Choose

No Preference  to use the default

shared network provided by Oracle Cloud Infrastructure Compute Classic.

Note:

Currently, the following limitations apply to IP networks:

  • Only database deployments hosting a single-instance database support IP networks.
  • Database deployments that use Oracle Data Guard do not support IP networks.
  • Database deployments that use Oracle RAC do not support IP networks.

 

5.Now please generate public key and private key using puttygen (Puttygen will be installed automatically if you install putty)

SSH is a cryptographic network protocol that uses two keys, one public and one private, to provide secure communication between two networked computers. Port 22 is the standard TCP/IP port that is assigned to SSH servers, and on Database Cloud Service instances this port is accessible to external clients by default.

When creating a database deployment, you specify the public key on the Service page of the Create Instance wizard by:

  • Uploading a public key file. You can specify a file on your local system that contains the public key value.
  • Pasting the public key value. You can paste the public key value into a box provided by the wizard. If you do so, make sure the value does not contain line breaks or end with a line break.
  • Having the wizard generate a key pair for you. You can have the wizard create an SSH key pair and use the generated public key value. You download a zip file containing both the public key file and the private key file.

When you access a compute node using SSH, you must provide the private key that matches the public key specified when the database deployment was created.

Puttygen is required to generate public and private key which is required next section to enable SSH access.After that you need to click “Generate” button and move mouse cursor frequently to generate randomness.

You need to provide public key during next section of database creation so that public key will be saved in DB server.You need to keep private key secretly.Please save the public key in notepad.

Please save public key

6.Go to next screen and provide other details as well as public key which we generated previous step.

6.a Storage Consideration

During creation of database deployment you choose the usable amount of data storage increment upto maximum 2TB.You may add space after creation of instance too.

By adding more space you can increase storage upto 4.6 TB with local backup and 12 TB without local backup.7.6 TB for deployment hosting for oracle RAC database backup.

Scaling up storage is responsibility for CLoud Dabatase Admin.

6.b Backup Destination

Controls how backups for the deployment are to be configured:

Both Cloud Storage and Local Storage

—backups are

configured to be created automatically and stored both on local storage and on cloud storage.If this choice is selected, the Cloud Storage Container,User Name and Password fields are displayed.

Cloud Storage Only

— backups are configured to be

created automatically and stored on cloud storage.If this choice is selected, the Cloud Storage Container,User Name and Password fields are displayed.

Note:

This choice is not currently available for database deployments that use Oracle Real Application Clusters(Oracle RAC).

None

—Backups are not configured for the deployment.

7.Please check all details before proceed to database creation.

8.Once you press create button,your instace is being created now

9.Once instance created,you will get confirmation mail.

10.Please check Activity tab for details about instance creation

 

 

  •  

Oracle DBaaS 1z0-160 part 5:-OS account in cloud ( OPC,ORACLE,GRID,ROOT)

Different OS user account details

User Description
OPC The system administrator account you use to connect to the compute node using SSH. This user can use the sudo command to perform operations that require root-user access.
ORACLE The Oracle Database administrator account you use to access the system and perform non-root database administration tasks. A home directory, /home/oracle, is created for this user. This user cannot use the sudo command to perform operations that require root-user access. Additionally, by default you cannot connect as this user to the compute node using SSH. You can add the

public key to the user’s $HOME/.ssh/authorized_keys file to grant persistent SSH access, or you can connect as the opc user and then use the sudo -s command to start a root-user command shell, followed by an su – oracle command to switch to the oracle user.

Grid The Oracle Grid Infrastructure administrator account you use to perform ASM, ACFS, and clusterware administration tasks. A home directory, /home/grid, is created for this user. This user cannot use the sudo command to perform operations that require root-user access. Additionally, by default you cannot connect as this user to the compute node using SSH. You can add the public

key to the user’s $HOME/.ssh/authorized_keys file to grant persistent SSH access, or you can connect as the opc user and then use the sudo -s command to start a root-user command shell, followed by an su – grid command to switch to the grid user.

root The root administrator for the system. You do not have direct access to this account. To perform operations that require root-user access, use the sudo command as the opc user.

Oracle DBaaS 1z0-160 part 4:-Creating Cloud service roles and users and assign new roles

The DBaaS Database Administrator role is created for Oracle Database Cloud Service.When the Database Cloud Service account is first set up, the service administrator is given this role. User accounts with this role must be added before anyone else can access and use Database Cloud Service.

The identity domain administrator can create more Database Cloud Service administrators by creating user accounts and assigning them the DBaaS Database Administrator role. See Managing User Accounts in Managing and Monitoring Oracle Cloud.

DBaaS Administrator Role has following privileges:-

1.Create and delete database deployments.

2.Scale/Patch and Backup or Restore.

3.Monitor and manage services of DBaaS.

1.Creating new user from Identity Management Console

1.A Please navigate to identity management console

1.B Please click on add user details

1.C You need to provide user details in that form

1.D Your mate will get email after you have created the role

1.E But After user activated his account he can not access Database cloud service.

2.Please provide DBaaS role to the user now

2.A  You need to navigate to identity management console to provide DBaaS roles to the user you created

2.B Please select DBAAS role

2.C Please assign DBaaS Administrator role to the user now

2.D Select the user and assign

2.E Please ask user to log into his account again

2.F Now user need to select “Oracle Database Cloud Service” role

2.G Now user has access to “Create Instance”

Oracle DBaaS 1z0-160 part 3:-Best Practise to be followed for cloud deployment

  1. Do not create additional installations of Oracle Database software.Each deployment comes with Oracle Database software already installed.
  2. Do not create additional Oracle databases.
  3. Do not change fundamental characteristics of the database, such as the DB name (SID).
  4. Use only cloud tooling to update the password of the SYS and SYSTEM database users.
  5. Apply only patches that are available through Database Cloud Service.Do not apply patches from any other source unless directed to by Oracle Support.This best practice applies to both database and OS patches.
  6. Apply database and OS patches when they become available through Database Cloud Service.
  7. Update the cloud tooling regularly.
  8. Do not disable or close access to the SSH port (port 22).You can open other ports and protocols.
  9. Do not directly modify a compute node’s user or SSH settings
  10. Do not modify the default administration ports.Do not change the ports for Oracle Cloud DBaaS Monitor, Oracle Application Express, Oracle Net Listener, Enterprise Manager Database Express 12c, or Enterprise Manager 11g Database Control after the deployment is created.
  11. When specifying backups to cloud storage, use a different cloud storage container or bucket for each deployment.
  12. Do not manually remove files from a cloud storage container or bucket that is being used for backups.
  13. Do not detach, change file access permissions for, or change the mount point of any storage volume that was attached to a compute node during the creation of your deployment. In particular, do not unmount or change the file access permissions of /u01 through /u05.
  14. When adding storage to a deployment configured for local backups, be sure add both FRA storage and Data storage to maintain a 1.7-to-1 ratio of FRA storage to Data storage. That is, the FRA storage size should be 1.7 times the Data storage size.
  15. When adding storage to a deployment, especially on Oracle Cloud Infrastructure Classic, avoid adding small amounts (under 10GB) of storage.Oracle Cloud Infrastructure Classic supports a very limited number of storage volumes attached to a compute node.
  16. When adding storage to a deployment on Oracle Cloud Infrastructure Classic, use the Oracle Database Cloud Service cloud tooling. Do not use the Oracle Cloud Infrastructure Compute Classic cloud tooling unless you are adding temporary storage to use for a specific short-term period and then remove.

Oracle DBaaS 1z0-160 part 2:-How to subscribe to Oracle cloud free

Register for free subscriptions

1.Please type url to your favorite browser

https://cloud.oracle.com/home

2.Click on green button

3.Please click on “Create a Free Account”

4.Please fill all details along with your credit card information

 

Note:-Please select among following region(Default Data Region).If you select EMEA or NA you will get more options like RAC with Dataguard options.

 

5.You will get confirmation as below once you get your OTP verified

6.Now you can access oracle cloud pressing blue button

7.Please save the credentials and URL sent in mail to login

 

Oracle DBaaS 1z0-160 part 1:-Oracle DBaaS cloud services overview

Oracle DBaaS cloud services overview

A.Oracle DBaaS cloud services level

A.1 The Oracle Database Cloud Service – Virtual Image


—You have to install this software yourself, and you are responsible for all maintenance operations for this software. You have root privilege, so you can load and run software in the compute environment. You have full administrative privileges for the Oracle database.a compute environment with pre-installed virtual machine images that include all software needed to create and run an Oracle Database. You connect to the virtual machine and run the Oracle Database Configuration Assistant (DBCA) to create your database. All subsequent maintenance operations, including backup, patching and upgrades, are performed by you.

(Not available in accounts that use the Universal Credits payment model)

(Not available on Oracle Cloud Infrastructure)

Release 2 (12.2) and later releases are not available at the Oracle Database Cloud Service – Virtual Image service level.

For more information:-https://blogs.oracle.com/pshuff/database-as-a-virtual-image

https://docs.oracle.com/en/cloud/paas/database-dbaas-cloud/csdbi/create-db-virtual-image-deployment.html#GUID-4851560B-D4B6-4275-9950-9953BB66B040

A.2 The Oracle Database Cloud Service


This level also includes Oracle Database and supporting software. However, the software is installed for you, an Oracle database is created using values you provide when creating the database deployment, and the database is started. Additionally, you can direct Database Cloud Service to set up automatic backups. Finally, the deployment includes cloud tooling that simplifies backup, recovery, patching and upgrade operations. You have root privilege, so you can load and run software in the compute environment.You have full administrative privileges for the Oracle database. You are for making any changes to the automated maintenance setup, and you are responsible for  recovery operations in the event of a failure.

B.Metering Frequency

When creating a database deployment on Oracle Database Cloud Service, you choose one of the following metering frequencies:

Hourly

—Pay only for the number of hours used during your billing period.You cannot switch a deployment from hourly to monthly metering frequency after it is created.

Monthly

—Pay one price for the full month irrespective of the number of hours used.For deployments that are started in the middle of a month, the price is pro-rated;

you pay only for the partial month from the start date

C.Computing Power

When creating a database deployment on Oracle Database Cloud Service, you choose the computing power for the associated compute node or nodes from a list of supported OCPU (Oracle CPU) and processor RAM combinations. The combinations you can choose from depends on the infrastructure you are creating the deployment in:

  •  In Oracle Cloud Infrastructure:

–  VM.Standard1.1 – 1.0 OCPU, 7.0 GB RAM

–  VM.Standard1.2 – 2.0 OCPU, 14.0 GB RAM

–  VM.Standard1.4 – 4.0 OCPU, 28.0 GB RAM

–  VM.Standard1.8 – 8.0 OCPU, 56.0 GB RAM

–  VM.Standard1.16 – 16.0 OCPU, 112.0 GB RAM

–  BM.Standard1.32 – 36.0 OCPU, 256.0 GB RAM

Types and combinations of memory type

OC3 to OC7 denotes General purpose computing power.

OC1m to OC5m denotes High memory computing power.

D.Oracle Database Options

Here is various features in each of these Database Cloud options

A) Standard Edition (SE) —Oracle Database Standard Edition, which delivers database for department-level, and Web applications. It includes all the RDBMS features necessary to build business-critical applications.

B) Enterprise Edition (EE) —Oracle Database Enterprise Edition, includes everything in SE + Database for online transaction processing (OLTP) applications, query-intensive data warehouses, and demanding Internet applications. In simple Terms better then Standard Edition .

C) Enterprise Edition – High Performance (EE-HP) — includes everything in EE  all the features of Enterprise Edition, plus partitioning , multi-tenancy, advanced compression, real application testing, advanced Security, Label Security, Database Vault, Spatial & Graph, Data Masking,  and management packs.

D)Enterprise Edition – Extreme Performance-provides all the features of Enterprise Edition High Performance, plus In-Memory, Active Data Guard and RAC .

So If you need RAC Database or Active Data Guard features then select Enterprise Edition Extreme Performance (EE-EP) option.

E.The following Databases are now supported

Oracle Database 11g Release 2
–>Oracle Database Version 11.2.0.4
Oracle Database 12c Release 1
–>Oracle Database Version 12.1.0.2
Oracle Database 12c Release 2
–>Oracle Database Version 12.2.0.1
Oracle Database 18c
–>Oracle Database Version 18.0.0.0

F.Standard Pricing Model

KBHS-00712: ORA-29024 received from local HTTP service during backup in RAC Oracle cloud

KBHS-00712: ORA-29024 received from local HTTP service during backup in RAC Oracle cloud

The backup of Oracle RAC DBaaS may fail during manual as well automatic backup.
If you manually invoke following command,The backup may not get successful.
Login to opc.
[opc@pocracdemo1 ~]$ raccli describe job 17
{
  “requestStatus” : “SUCCESS”,
  “jobStatus” : “FAILURE”,
  “message” : “Failed to run Rman Backup statement.”,
  “response” : [ {
    “startTime” : “Fri Apr 13 03:28:23 UTC 2018”,
    “endTime” : “Fri Apr 13 03:28:24 UTC 2018”,
    “status” : “SUCCESS”,
    “taskId” : “TaskZJsonRpcExt_2851”,
    “taskResult” : “backup validations done successfully”,
    “taskName” : ” backup validations”
  }, {
    “startTime” : “Fri Apr 13 03:28:24 UTC 2018”,
    “endTime” : “Fri Apr 13 03:28:49 UTC 2018”,
    “status” : “SUCCESS”,
    “taskId” : “TaskZJsonRpcExt_2853”,
    “taskResult” : “DB backup validations done successfully”,
    “taskName” : ” db backup validations”
  }, {
    “startTime” : “Fri Apr 13 03:28:49 UTC 2018”,
    “endTime” : “Fri Apr 13 03:29:07 UTC 2018”,
    “status” : “SUCCESS”,
    “taskId” : “TaskZJsonRpcExt_2855”,
    “taskName” : “cross check database backup”
  }, {
    “startTime” : “Fri Apr 13 03:29:07 UTC 2018”,
    “endTime” : “Fri Apr 13 03:29:57 UTC 2018”,
    “status” : “FAILURE“,
    “taskId” : “TaskZJsonRpcExt_2857”,
    “taskResult” : “Failed to run Rman Backup statement.”,
    “taskName” : “Database Backup”
  } ]
}
Now you need to check RMAN log for exact error:-

tail -100f  /home/oracle/bkup/logs/rman/rman_2018-04-13_02-16-15.0242.log

Starting backup at 04/13/2018 02:16:21
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/13/2018 02:16:21
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27023: skgfqsbi: media manager protocol error
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
KBHS-00715: HTTP error occurred ‘oracle-error’
KBHS-00712: ORA-29024 received from local HTTP service

Recovery Manager complete.

Solution:-
Please refer to below metalink note:-
RMAN Backup to Oracle Database Backup Cloud Service fails with KBHS-00715 ORA-29024 (Doc ID 2360941.1)
Till the bug is fixed, below workaround can be used:
1. Set below parameter in the config file (opcPROD.ora) and retry backup:

vi /u02/app/oracle/admin/orcl/oss_config/opc_orcl.ora

_OPC_VALIDATE_CERT=TRUE

2. If above does not help, re-install the cloud backup module with -trustedCerts option and provide opc.cert file attached in this document i.e.
You need to download opc.cert and opc_install.jar mentioned in above metalink note (Doc ID 2360941.1)
[oracle@pocracdemo1 ~]$ java -jar opc_install.jar -host https://xxx.eu.storage.oraclecloud.com/v1/Storage-xxx -opcId 'xxx@gmail.com' -opcPass 'xxx' -walletDir /home/oracle/opc_wallet -libDir $ORACLE_HOME/lib -libPlatform linux64 -debug -trustedCerts /home/oracle/opc.cert
Oracle Database Cloud Backup Module Install Tool, build 12.2.0.1.0DBBKPCSBP_2017-11-28
Debug: os.name        = Linux
Debug: os.arch        = amd64
Debug: os.version     = 4.1.12-112.14.10.el6uek.x86_64
Debug: file.separator = /
Debug: Platform = PLATFORM_LINUX64
Debug: OPC Account Verification: <?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes”?><account name=”Storage-62b84aec8de8478ba17a6e1f84c3475c”><container><name>DBaaS</name><count>1</count><bytes>279552</bytes><accountId><id>31714</id></accountId><deleteTimestamp>0.0</deleteTimestamp><containerId><id>7665965</id></containerId></container></account>
Oracle Database Cloud Backup Module credentials are valid.
Debug: Certificate Success: file = /home/oracle/opc.cert
Debug: Certificate Success:
       Subject  : CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
       Validity : Fri Nov 10 00:00:00 UTC 2006 – Mon Nov 10 00:00:00 UTC 2031
       Issuer   : CN=DigiCert Global Root CA, OU=www.digicert.com, O=DigiCert Inc, C=US
Oracle Database Cloud Backup Module wallet created in directory /home/oracle/opc_wallet.
Oracle Database Cloud Backup Module initialization file /u01/app/oracle/product/12.2.0.1/dbhome_1/dbs/opcorcl1.ora created.
Downloading Oracle Database Cloud Backup Module Software Library from file opc_linux64.zip.
Debug: Temp zip file = /tmp/opc_linux646570785615594303284.zip
Debug: Downloaded 27314069 bytes in 4 seconds.
Debug: Transfer rate was 6828517 bytes/second.
Download complete.
Debug: Delete RC = true
After that,I faced another issue:-
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
KBHS-01404: See trace file /u01/app/oracle/product/12.1.0/dbhome_1/rdbms/log/sbtio_8654_139790089015904.log for details
KBHS-00719: Error ‘unknown’; You are not allowed to perform a tagging operation on a container that has objects in it, accountName:
KBHS-00700
Recovery Manager complete.
Solution :-
Metalink note:-Backup fails with error ‘KBHS-00719: ERROR ‘UNKNOWN’; YOU ARE NOT ALLOWED TO PERFORM A TAGGING OPERATION’ (Doc ID 2371818.1)
Empty the container by moving the existing files in a different one before taking the first RMAN backup, or just create a new empty container and update the opc parameter file to point to it.
Now the backup succeeds

[opc@pocracdemo1 ~]$ raccli describe job 20

{
“requestStatus” : “SUCCESS”,
“jobStatus” : “SUCCESS”,
“response” : [ {
“startTime” : “Fri Apr 13 06:39:39 UTC 2018”,
“endTime” : “Fri Apr 13 06:39:39 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3885”,
“taskResult” : “backup validations done successfully”,
“taskName” : ” backup validations”
}, {
“startTime” : “Fri Apr 13 06:39:39 UTC 2018”,
“endTime” : “Fri Apr 13 06:40:04 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3887”,
“taskResult” : “DB backup validations done successfully”,
“taskName” : ” db backup validations”
}, {
“startTime” : “Fri Apr 13 06:40:04 UTC 2018”,
“endTime” : “Fri Apr 13 06:41:08 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3889”,
“taskName” : “cross check database backup”
}, {
“startTime” : “Fri Apr 13 06:41:08 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:29 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3891”,
“taskResult” : “Resource { id: 97761124902577, name: rdbaas_backupComponent, type: BackupComponent }”,
“taskName” : “Database Backup”
}, {
“startTime” : “Fri Apr 13 06:49:29 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:33 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskParallel_3893”,
“taskName” : “DB Config files backup”
}, {
“startTime” : “Fri Apr 13 06:49:29 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:33 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3894”,
“taskResult” : “Resource { id: 98261108067814, name: rdbaas_backupComponent, type: BackupComponent }”,
“taskName” : “DB config files backup on node_1”
}, {
“startTime” : “Fri Apr 13 06:49:29 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:33 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3896”,
“taskResult” : “Resource { id: 97712211539712, name: rdbaas_backupComponent, type: BackupComponent }”,
“taskName” : “DB config files backup on node_2”
}, {
“startTime” : “Fri Apr 13 06:49:33 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:45 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskParallel_3899”,
“taskName” : “GI Config files backup”
}, {
“startTime” : “Fri Apr 13 06:49:33 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:45 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskParallel_3904”,
“taskName” : “OS Config files backup”
}, {
“startTime” : “Fri Apr 13 06:49:33 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:38 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3900”,
“taskResult” : “Resource { id: 98265677604650, name: rdbaas_backupComponent, type: BackupComponent }”,
“taskName” : “Gi config files backup on node_1”
}, {
“startTime” : “Fri Apr 13 06:49:33 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:41 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3905”,
“taskResult” : “Resource { id: 98269544616295, name: rdbaas_backupComponent, type: BackupComponent }”,
“taskName” : “Os config files backup on node_1”
}, {
“startTime” : “Fri Apr 13 06:49:33 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:48 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskParallel_3909”,
“taskName” : “Derby DB files backup”
}, {
“startTime” : “Fri Apr 13 06:49:33 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:42 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3902”,
“taskResult” : “Resource { id: 97721137057959, name: rdbaas_backupComponent, type: BackupComponent }”,
“taskName” : “Gi config files backup on node_2”
}, {
“startTime” : “Fri Apr 13 06:49:33 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:45 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3907”,
“taskResult” : “Resource { id: 97725142391225, name: rdbaas_backupComponent, type: BackupComponent }”,
“taskName” : “Os config files backup on node_2”
}, {
“startTime” : “Fri Apr 13 06:49:33 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:42 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3910”,
“taskResult” : “Resource { id: 98272448241014, name: rdbaas_backupComponent, type: BackupComponent }”,
“taskName” : “Derby Db config files backup on node_1”
}, {
“startTime” : “Fri Apr 13 06:49:41 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:48 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3912”,
“taskResult” : “Resource { id: 97728013660122, name: rdbaas_backupComponent, type: BackupComponent }”,
“taskName” : “Derby Db config files backup on node_2”
}, {
“startTime” : “Fri Apr 13 06:49:48 UTC 2018”,
“endTime” : “Fri Apr 13 06:49:48 UTC 2018”,
“status” : “SUCCESS”,
“taskId” : “TaskZJsonRpcExt_3914”,
“taskResult” : “Resource { id: 98279542295230, name: dcs_backup, type: Backu p }”,
“taskName” : “Persisting Backup metadata”
} ]
}