Jobs
The
page shows all the details that are related to backup or restore jobs. It shows the history of previous and currently running jobs.The Jobs tab includes following details:
Element | Description |
---|---|
Summary section |
|
Queue section | You can see the number of jobs in progress and pending states. |
Backups tab | You can see the statuses of all jobs (failed, pending, in-progress, canceled,
completed). The Backups table lists all the jobs along with the following details:
|
Search Backups |
|
Restores tab | You can see the all job statuses (failed, pending, in-progress, canceled, completed). The
job Restores table lists all restore jobs along with the following details:
|
Search Restores |
|
Cancel jobs | Cancel jobs by using the Backup or Restore CR. Add the following line to the CR specification
to cancel jobs that are in queue or running state.
If you cancel during backup, the volume snapshots get removed as a part of cleanup. If you issue a cancel during restore, the cleanup happens only when you choose a new
or an existing namespace.
Note: When you cancel a restore job to the original namespace, cleanup does
not happen and can result in a corrupt application after the cancellation
completes.
|
You can scale out the number of transaction manager pods to process more jobs at the same time.
For example, run the following command to increase the number of agent pods to two:
oc scale deployments/transaction-manager --replicas=2 -n ibm-backup-restore
To
the scale out from the OpenShift® Container Platform console, do the
following steps: - Change the project to the Backup & Restore install
namespace. The default is
ibm-backup-restore
. - Search and select the
transaction-manager
deployment. - Click the scale up or down to increase or decrease the scale. It takes about 30 seconds for a replica to start in optimal conditions. Do not click multiple times instead wait for each pod to get to ready status.