Delete a cleanup policy

After a cleanup policy is created, you can delete the policy to stop automatic cleanup of expired backups or to change the cleanup policy.

Considerations and notes

• When all cleanup policies under a tenant are deleted, the automatic cleanup feature for that tenant is effectively disabled.

• Deleting a cleanup policy does not affect any cleanup tasks that are currently in progress. It only means that the next time the system schedules automatic cleanup, the deleted policy will not generate any new cleanup tasks.

Delete a cleanup policy for a specified user tenant

1. Log in to the cluster as the root user in the sys tenant.

2. Execute the following statement to delete the cleanup policy.

   ALTER SYSTEM DROP DELETE BACKUP POLICY policy_name TENANT [=] tenant_name;
   

   Where:

   • policy_name: the name of the cleanup policy to be deleted. You can obtain this name from the CDB_OB_BACKUP_DELETE_POLICY view.

   • tenant_name: the name of the user tenant. When deleting a cleanup policy in the system tenant, you must specify the name of the user tenant, and only one user tenant name can be specified.

   Here are some examples:

   • Delete the cleanup policy for the mysql001 tenant.

     obclient(root@sys)[(none)]> ALTER SYSTEM DROP DELETE BACKUP POLICY 'default' TENANT mysql001;
     

   • Delete the cleanup policy for the oracle001 tenant.

     obclient(root@sys)[(none)]> ALTER SYSTEM DROP DELETE BACKUP POLICY 'log_only' TENANT oracle001;
     

3. Confirm whether the cleanup policy has been deleted.

   obclient(root@sys)[(none)]> SELECT * FROM oceanbase.CDB_OB_BACKUP_DELETE_POLICY WHERE tenant_id = 1002;
   

   If the query result shows no records for the specified tenant, it indicates that the cleanup policy has been successfully deleted.

Delete a cleanup strategy of the current user tenant

1. Log in to the database as a tenant administrator.

   Note

   The administrator of a MySQL-compatible tenant is the root user, and the administrator of an Oracle-compatible tenant is the SYS user.

2. Execute the following statement to delete the cleanup strategy.

   The statement is as follows:

   ALTER SYSTEM DROP DELETE BACKUP POLICY policy_name;
   

   Here, policy_name specifies the name of the cleanup strategy to be deleted. You can query the oceanbase.DBA_OB_BACKUP_DELETE_POLICY or SYS.DBA_OB_BACKUP_DELETE_POLICY view to obtain the cleanup strategy of the current tenant.

   Here is an example:

   MySQL-compatible mode

   Oracle-compatible mode

   Delete the cleanup strategy default of the current tenant in MySQL-compatible mode.

   obclient(root@mysql001)[(none)]> ALTER SYSTEM DROP DELETE BACKUP POLICY 'default';
   

   Delete the cleanup strategy log_only of the current tenant in Oracle-compatible mode.

   obclient(SYS@oracle001)[SYS]> ALTER SYSTEM DROP DELETE BACKUP POLICY 'log_only';
   

3. Check whether the cleanup strategy has been deleted.

   You can query the oceanbase.DBA_OB_BACKUP_DELETE_POLICY view in MySQL-compatible mode or the SYS.DBA_OB_BACKUP_DELETE_POLICY view in Oracle-compatible mode to check whether the cleanup strategy of the current tenant has been deleted.

   Here are some examples:

   MySQL-compatible mode

   Oracle-compatible mode

   In MySQL-compatible mode, execute the following statement:

   obclient(root@mysql001)[oceanbase]> SELECT * FROM oceanbase.DBA_OB_BACKUP_DELETE_POLICY;
   

   In Oracle-compatible mode, execute the following statement:

   obclient(SYS@oracle001)[SYS]> SELECT * FROM SYS.DBA_OB_BACKUP_DELETE_POLICY;
   

   If the query result does not contain the corresponding cleanup strategy, the cleanup strategy of the tenant has been deleted.

What to do next

After you delete the cleanup strategy, we recommend that you set a new cleanup strategy to avoid the disk space being filled up due to the failure to clean up backup files, which may affect the backup operation. For more information about how to set a cleanup strategy, see Automatically clean up expired backups.