psm analytics restore

Syntax

In the following syntax, line breaks have been added for clarity. Do not include them when entering the command.

psm analytics restore -s|--service-name serviceName 
  -b|--backup-id backupId 
    [-f|--force-scale-in true|false]
    [-n|--notes free form note content]
    [-p|--pause-otd true|false]
    [-r|--reset-binaries true|false]
    [-of|--output-format json|html|short]

Parameters

All parameters are required unless otherwise noted.

Parameter	Description
`-s\|--service-name`	Specifies the name of the service you want to restore.
`-b\|--backup-id`	ID of the backup you want to restore. To retrieve the backup ID, use the `analytics view-restores` command.
`-f\|--force-scale-in`	(Optional) Specifies whether to automatically scale in the service if Managed Servers are configured that aren’t included in the backup being restored. If set to false and the service has Managed Servers configured that aren’t included in the backup being restored, the operation fails and the following error message is displayed : `PAAS-BR-105 : Unable to restore configuration data for managed servers that aren't part of the backup. The affected managedServers are : [managedserver_x, managedserver_y]. Scale in the Oracle Analytics Cloud service to remove these managed servers' nodes and then try to restore the Oracle Analytics Cloud Service again.` Default: `false` (the service shouldn’t be scaled in automatically) This setting is valid only when you are restoring configuration data (`restoreConfig` is set to true).
`-n\|--notesnotes`	(Optional) Free-form text to provide additional information about the restore operation.
`-p\|--pause-otd`	(Optional) Specifies whether to pause the load balancer during the restore process. If set to true, the load balancer pauses and stops forwarding requests to the Managed Servers in the service during the restore process, and responds with an HTTP 503 status code to client requests. After the restore process completes, the load balancer restarts. If pause or restart of the load balancer fails, for example, because the load balancer Administration Server isn’t available, the restore process proceeds. The restore process fails however, if the load balancer health check fails. Don’t rely on this feature if you need to perform any manual tasks once the restore completes. . Default: `false` This setting is valid only if the load balancer is enabled.
`-r\|--reset-binaries`	(Optional) Specifies whether to reset the Oracle WebLogic Server and the JDK software to the versions that correspond to the official patch set update (PSU) level of the software that the service is currently running. Default: `false` (do not replace the binary files) To restore software to an older version, initiate a roll back of the appropriate patch.
`-of\|-–output-format`	(Optional) Desired output format. Accepted values: `json, html, short`

Example

$ psm analytics restore -s Example1Service -b 1386382930068 
{
    "job_id":"34276",
    "operationName":"restore-backup",
    "target_uri":"http://myserver.us.mycorp.com:7103/paas/service/analytics/api/v1.1/instances/myteamabca/Example1Service/restoredbackups/34276"
}
Job ID : 34276

Note that this command returned a job ID. To see the status of your restore operation, use this ID with the psm analytics operation-status command:

$ psm analytics operation-status -j 34276

When you see the message:

    "operationId":364,
    "operationType":"RESTORE",
    "serviceId":364,
    "serviceName":"Example1Service",
    "serviceType":"analytics",
    "startDate":"2016-04-28T19:45:41.907+0000",
    "status":"SUCCEED",
    "summaryMessage":"RESTORE"

the service instance was successfully restored.