You can stop an ongoing backup job. If automatic backup cleanup is enabled, the backup cleanup job immediately clears incomplete backup data after you stop a backup job.
Prerequisites
Incomplete backup data is generated after you stop an ongoing back job. We recommend that you enable automatic backup cleanup before you perform backup so that incomplete backup data can be cleared as soon as possible without occupying resources. For more information about how to enable automatic backup cleanup, see Automatically clean up expired backup data.
Background information
Assume that the current cluster contains three tenants: sys, mysql_tenant, and oracle_tenant, and that data backup is being performed for the mysql_tenant and oracle_tenant tenants.
Stop data backup from the sys tenant
You can stop data backup for all tenants or a specified tenant in the cluster from the sys tenant.
Log in to the
systenant of the cluster as therootuser.Execute the following statement to stop a data backup job:
Stop data backup for all tenants in the cluster
Execute the following statement to stop the data backup jobs of all tenants in the cluster:
obclient [(none)]> ALTER SYSTEM CANCEL BACKUP;Stop data backup for a specified tenant in the cluster
Execute the following statement to stop an ongoing data backup job of a specified tenant without affecting other tenants in the cluster.
obclient [(none)]> ALTER SYSTEM CANCEL BACKUP TENANT = mysql_tenant;Note
If you specify multiple tenants, separate the tenant names with commas (,).
Stop a backup job of a user tenant
You can stop an ongoing data backup job of a user tenant without affecting other tenants.
Log in to the database as a tenant administrator.
In this example, you can log in to the
mysql_tenanttenant as therootuser, or log in to theoracle_tenanttenant as theSYSuser.Execute the following statement to stop a data backup job:
obclient [(none)]> ALTER SYSTEM CANCEL BACKUP;