Remove Remote Archive Volume

This section explains how to remove a remote archive volume.

This procedure is carried out using ConfD.

Removing a remote archive volume does not delete any data stored in the remote source.

Prerequisites

A remote archive volume must exist.

Procedure

The following examples use ConfD through the command-line tool confd_client, which is available on all database nodes. You can also access ConfD through XML-RPC in your own Python programs. For more information, see ConfD.

  1. Connect to EXAClusterOS (COS) using c4 connect -t <DEPLOYMENT>[.<NODE>]/cos. For example:

    c4 connect -t 1/cos

    In most cases it does not matter on which node you access ConfD. If you do not specify a node, c4 will connect to the first active node in the deployment. If the cluster is configured with an access node, the first node is the access node (usually n10). The command prompt in COS indicates which node you are connected to: 

    [root@n10 ~]#

    For more information about how to use c4 connect, see How to use c4.

  2. To find the volume name of the archive volume to be removed, use the ConfD job remote_volume_list. 

    confd_client remote_volume_list
    - r0001
    - r0002

    If you cannot identify the correct archive volume to be removed based on the volume name, use remote_volume_info to see the details for a given volume. For example: 

     confd_client remote_volume_info remote_volume_name: r0002
    name: r0002
    owner:
    - 500
    - 500
    password: 123456789
    type: s3
    url: https://my_bucket.s3.eu-west-1.amazonaws.com/db-backup-2/
    username: backup_user
    vid: '10002'

  3. To remove the remote archive volume, use the ConfD job remote_volume_remove. For example:

    confd_client remote_volume_remove remote_volume_name: r0002

Verification

To verify that the volume has been removed, use the ConfD job remote_volume_list.

confd_client remote_volume_list
- r0001