1. Migrating Infrastructure Classic Workloads to Oracle Cloud Infrastructure
  2. Migrate Object Storage

19 Migrate Object Storage

Currently, migration of Oracle Cloud Infrastructure Object Storage container data is available only for the following scenarios.
  • If you are using the Oracle Cloud Infrastructure Storage Software Appliance, you can use Cloud Sync to migrate data to Oracle Cloud Infrastructure Storage Gateway.
  • If you are not using Oracle Cloud Infrastructure Storage Software Appliance and if the total amount of object storage data does not exceed the guidelines for this type of data migration, then you can use Rclone to migrate data from Oracle Cloud Infrastructure Object Storage Classic to Oracle Cloud Infrastructure Object Storage. For more information on how to determine if your environment is a candidate for this migration strategy, contact your Oracle support or consulting representative.

Migrate Storage Appliance Data to Oracle Cloud Infrastructure Storage Gateway

Oracle Cloud Infrastructure Storage Software Appliance provides a POSIX compliant file system that persists the file data to Oracle Cloud Infrastructure Object Storage Classic.

Oracle Cloud Infrastructure Storage Gateway is the recommended gateway for Oracle Cloud Infrastructure Object Storage. Oracle recommends that you migrate from Oracle Cloud Infrastructure Storage Software Appliance backed by containers in Oracle Cloud Infrastructure Object Storage Classic to Oracle Cloud Infrastructure Storage Gateway that persists data in object storage buckets in Oracle Cloud Infrastructure.

Migration steps can take a considerable amount of time depending upon the number of files/directories and size of files, available resources (CPU, memory, network bandwidth, disk throughput, etc.). While scheduling the migration process, consider the estimated time required to complete the migration. If you abort the migration process for any reason, you can restart the process.

To migrate data from an Archive container, you must first restore the archived objects. For more information, see Restoring Archived Objects in Using Oracle Cloud Infrastructure Object Storage Classic.

Before You Begin

Before you begin migrating your workloads, verify that you have a cloud account with Identity Cloud Service to access Oracle Cloud Infrastructure, and then complete the planning checklist. This section provides information to help you complete the planning checklist.

Identify the following information for each storage software appliance that you want to migrate.

Information Required Details
Is the appliance is running in Compute Classic or in your on-premises environment?  
Version of the storage software appliance running in Compute Classic or in your on-premises environment  
Link to access the management console and password  
Size of the cache storage  
Total number of file systems  

Identify the following information for every file system in the storage software appliance that you want to migrate.

Information Required Details
Number of files in the file system  
Total storage space used  
Is the file system is encrypted? If yes, note down the location where you have downloaded the encryption keys.  
Get Details of the Source Environment

Identify the user name, password, authentication URL, and REST Endpoint URL for the Oracle Cloud Infrastructure Object Storage Classic account from which you want to migrate data.

  1. Note down the user name and password for your Compute Classic instance, which is case-sensitive. The account creation email from Oracle contains this information. If you don't have this information, contact your service administrator.
  2. Sign in to your Cloud Account and navigate to the My Services Dashboard.
    The My Services dashboard is displayed. It lists the services that are assigned to your account.
  3. Look for Oracle Cloud Infrastructure Object Storage Classic.
  4. Select View Details from the Actions menu.
    On the resulting page, the details of your Oracle Cloud Infrastructure Object Storage Classic instance are displayed.
  5. From the Additional Information section, note down the following information:
    • REST Endpoint URL from the REST Endpoint field. For example, https://acme.storage.oraclecloud.com/v1/Storage-acme.
    • The authentication URL from the Auth V1 Endpoint field. For example, https://acme.storage.oraclecloud.com/auth/v1.0.
  6. Also identify the region where the Storage Classic containers are located. This is the region where your Compute Classic account has been provisioned.
Get Details of the Appliance Instance

Before gathering details of the instance on which Oracle Cloud Infrastructure Storage Software Appliance is installed, identify if the appliance is installed on a Compute Classic instance or in your on-premise environment. If you have set up multiple appliance instances, identify the following information for every appliance instance that you want to migrate: the public IP address of the instance that hosts the application, link to access the management console and the password. Use the public IP address to connect to the appliance instance using SSH and to log in to the management console of the appliance.

Get Details of an Appliance Installed on a Compute Classic Instance

If the appliance is installed on a Compute Classic host, then to gather the required information perform the following steps:

  1. On the Compute Classic host go to the directory where you have downloaded the appliance provisioning tool and run the following command: 

    ./fscs.sh -i config_file

    In this command, config_file is the full path and name of the appliance configuration file.

  2. The tool prompts you to enter the password for the Compute Classic user specified in the configuration file. Enter the password.

    The tool validates the password and displays the IP addresses of the instance, as shown in the following example:

    Extracting IP addresses ...
Private IP address: 10.196.35.245
Public IP address: 203.0.113.48

  3. The password for the admin user to access the management console of the appliance.

    If you don’t remember the password, you can reset it. See Changing the Admin Password for the Appliance in Using Oracle Cloud Infrastructure Storage Software Appliance.

  4. Access the management console. In your web browser, go to https://public_IP_address_of_appliance_instance, and then enter the admin password.

    The available filesystems are displayed. Note down the number of the filesystems that you want to migrate.

Get Details of an Appliance Installed in the On-Premises Environment

If the appliance is installed on a Compute Classic host, use the oscsa command-line tool to manage Oracle Cloud Infrastructure Storage Software Appliance. oscsa commands might fail, if you don't run these commands as a root user. To gather the required information, perform the following steps:

  1. If the appliance instance is in your on-premises environment, log in to the appliance host and then run the following commands:

    oscsa info

    Note down the link to access the management console from the output. Example:

    Management Console: https://myApplianceHost.example.com:32775
If you have already configured an OSCSA FileSystem via the Management Console,you can access the NFS share using the following port.
NFS Port: 32774

    Note down the link to access the management console and the NFS port from the output.

    If the appliance instance is not running, then run the following command to bring up the appliance and get the required information.

    oscsa up
  2. Run the following command to identify the version of the storage appliance.
    oscsa version

    Note down the version. While migrating the on-premise storage appliance, you may install a storage appliance on a Compute Classic instance. The version of the storage appliance that you install on the Compute Classic instance must be same as the on-premise storage appliance that you want to migrate.

  3. Access the management console. In your web browser, go to https://myApplianceHost.example.com:32775, and then enter the admin password.

    The available file systems are displayed. Note down the name and number of the file systems that you want to migrate.

Get Details of a File System

Each Oracle Cloud Infrastructure Storage Software Appliance instance can have multiple file systems. Gather the following details for every file system that you want to migrate.

To view the details of a file system, log in to the management console, and click the name of the file system:

  1. The Settings tab displays the enabled file system properties, such as encryption, Archive storage class and deleting old file versions.
  2. If the file system is encrypted, identify encryption key to be used for decrypting the data.
    1. Select the file system for which you want to download encryption keys, and go to the Encryption Keys tab.
    2. Click Download in the Existing Encryption Keys section.
    3. Save the .tar.gz file (that contains the encryption keys) in a location of your choice. Ensure that the file is stored at a secure location. You can delete this file when it is no longer required.
  3. View all the contents in the file system to ensure that the file system contains only files and directories. Special devices, symlink, or hard link cannot be migrated. Run the following command in the NFS client on which you have mounted the appliance file system.
    find source_directory -print
  4. From the details displayed, check if any file name has characters such as '\r' and '\n that are incompatible with Oracle Cloud Infrastructure Storage Gateway. If any file name has characters which are incompatible with storage gateway, you must rename the files before starting the migration process.
  5. If the file system contains any special devices, symlink, or hard link, complete the following tasks:
    1. Create an archive file using tar, cpio, or zip to ensure that you can restore the special files when needed.
    2. Only after the archive file is created, delete all special devices, symlinks or hard links in the source environment before starting the migration.
  6. Run the following command using the Oracle Cloud Infrastructure Object Storage Classic File Transfer Manager command-line interface (FTM CLI) to retrieve metadata of the Oracle Cloud Infrastructure Object Storage Classic container that is associated with the file system:
    java -jar ftmcli.jar describe container_name
    From the details displayed, note down the number of files in the container and the total storage space used by all the objects in the container.
For information about using FTM CLI, see Preparing to Use the FTM CLI in Command-Line Reference for Oracle Cloud Infrastructure Object Storage Classic.

Prepare the Target Environment

Before migrating the file systems, set up the target environment. To prepare the target environment, install and configure an instance of the Oracle Cloud Infrastructure Storage Gateway. You will use this instance after you complete the migration process. Test the target environment and resolve issues, if any. You have to test the environment only once before migrating the first file system. Mount a test file system on the storage gateway instance, and then check if you can successfully read and write to object storage.

  1. Install and configure Oracle Cloud Infrastructure Storage Gateway in Oracle Cloud Infrastructure. See Installing Storage Gateway in Oracle Cloud Infrastructure documentation.
    If the source appliance instance runs in the cloud, create the storage gateway instance in the cloud. If the source appliance instance runs on-premises, create the storage gateway instance in your on-premises environment.
  2. Create a storage gateway file system to test the connection. See Creating Your First File System in Oracle Cloud Infrastructure documentation.
    You can also use the source file system that you are migrating from the Oracle Cloud Infrastructure Storage Software Appliance instance.
  3. Connect the file system to an Oracle Cloud Infrastructure Object Storage bucket. See Connecting a File System in Oracle Cloud Infrastructure documentation.
  4. Mount the test file system on a Linux NFS client. See Mounting File Systems on Clients in Oracle Cloud Infrastructure documentation.
  5. Use the Oracle Cloud Infrastructure Console to verify that you can read and write files to this file system. Create files in the file system and then read the content of the uploaded files to check that the files were uploaded successfully to the object storage.
  6. Unmount the test file system from NFS client. SSH to the client instance, and then run the following command:
    umount /mnt/myFileSystem1

    Where, myFileSystem1 is the name of the filesystem that you want to unmount.

  7. Disconnect the test file system. See Disconnecting a File System in Oracle Cloud Infrastructure documentation.
  8. Delete the test file system. See Deleting a File System in Oracle Cloud Infrastructure documentation.

Additional Steps to Prepare the On-Premises Environments

If you are migrating object storage data from a storage appliance in the cloud to a storage gateway in the cloud, you don't need to perform any additional steps to prepare the environments. However, if you are migrating object storage data from a storage appliance in your on-premises environment to a storage gateway in your on-premises environment, consider performing the following additional steps to prepare the environment.

Even if the appliance instance is available on-premises, you don't need to perform these additional steps if you are connecting to Oracle Cloud through a low latency, high throughput connectivity, such as Oracle Cloud Infrastructure FastConnect. In such a scenario, you can use the appliance instance in your on-premises environment to perform the migration.

Prepare Source Appliance for Migration

  1. Install and configure an Oracle Cloud Infrastructure Storage Software Appliance instance on a Compute Classic instance.
  2. Create a file system with the same name and properties (such as storage tier, encryption, and other options) as the file system being migrated. Set appropriate NFS options, which is available in advanced options, to ensure security.
  3. Do not connect the file system. Before connecting the file system you must ensure that all pending uploads to the appliance are complete. You'll also need to disconnect the existing appliance instance. You'll connect the file system later in the migration process.

Prepare Target Gateway for Migration

  1. Install and configure Oracle Cloud Infrastructure Storage Gateway on a compute instance in Oracle Cloud Infrastructure.

    You 'll use this Oracle Cloud Infrastructure Storage Gateway instance during the migration process. Create this instance only if you want to use an Oracle Cloud Infrastructure instance to complete the migration instead of using an instance in your on-premises environment.

  2. Create a file system with the same name and properties as the file system being migrated. Use standard tier bucket along with object life cycle policy and not the archive tier bucket.
  3. Set appropriate NFS options, which is available in advanced options, to ensure security.
  4. Connect the Oracle Cloud Infrastructure Storage Gateway file system.

Start Migrating a File System

The following steps are required for migrating a single file system. Repeat these steps for each file system that you want to migrate. Depending upon the availability of resources, you may migrate multiple file systems in parallel.

  1. Quiesce the source file system that you want to migrate. Complete the following tasks in the source storage appliance.
    1. Access the management console of the storage appliance.
    2. Click the name of the file system to view its details.
    3. The Activity tab shows the ongoing and pending upload activity. If there is any ongoing activity, wait for the activity to complete.
    4. Unmount the filesystem from the client instances. SSH to the client instance, and then run the following command:
      umount /mnt/myFileSystem1

      Where, myFileSystem1 is the name of the filesystem that you want to unmount.

    5. Wait for pending uploads, if any, to complete.
    6. On the Dashboard tab of the management console, select the filesystem that you want to disconnect, and then click Disconnect.
  2. If you are using the source storage appliance instance to perform the migration, then perform the following tasks in the source storage appliance. If you have configured a Oracle Cloud Infrastructure Storage Gateway on a compute instance in Oracle Cloud Infrastructure to perform the migration, then perform the following steps in the instance that you have created.
    1. In the Settings tab, set the NFS Export Options to read-only (ro) for the file system, and then click Save.
    2. For the changes to take effect, reconnect the file system. On the Dashboard tab of the management console, select the filesystem that you want to connect, and then click Connect.
    3. If the FileSystem: Claim Ownership window is displayed, re-enter your Oracle Cloud Infrastructure Object Storage Classic password and then select Claim Ownership.
  3. Set up the destination file system for the copy operation.
    1. On the host running the Oracle Cloud Infrastructure Storage Gateway, mount the source file system that is available on the appliance instance. To transfer the files using Cloud Sync, you must mount the file system under /cloudsync/mounts.
      # mount -t nfs <mount_options> <storage_appliance_server>:<filesystem> <mountpoint>
    2. Connect the new file system in the Oracle Cloud Infrastructure Storage Gateway instance. See Connecting a File System in Oracle Cloud Infrastructure documentation.
  4. Create a Cloud Sync job that syncs all files and directories between the source and the destination file system. See Using Storage Gateway Cloud Sync in Oracle Cloud Infrastructure documentation.
    Use Storage Gateway management console to create, manage, and monitor Cloud Sync jobs.
  5. Run the Cloud Sync job that you have created. See Using Storage Gateway Cloud Sync in Oracle Cloud Infrastructure documentation.
  6. Get the status of the Cloud Sync job to monitor status of the process. See Using Storage Gateway Cloud Sync in Oracle Cloud Infrastructure documentation.
    The management console displays the status of the job (Created, Running, Completed, Failed, or Canceled) just below the job name. View the output of this command to determine if any files have changed on the storage appliance after you copied files to the storage gateway. If any files have been modified, rerun the job to copy only the modified files.

Validate

After object storage data migration is complete, perform the following steps to determine if the migration was completed successfully.

  1. After the migration is complete, check if any errors occurred during the migration process. Cloud Sync records error messages in a file. You can download this file from the management console.
  2. Compare the file inventory in the source and target environments. You can list the files in the source and target environment and compare them.
When you get the status of a Cloud Sync job, it also reports any mismatch in the files on the source and target. If there is a discrepancy between files in the source and target, try restarting the cloud sync job first. If that doesn't work, restart the migration process to reconcile the differences. If that does not resolve the issue, contact My Oracle Support to complete the migration.

Post Migration Requirements for On-premises Environment

Perform the following steps only if you are migrating an appliance instance which is installed in your on-premises environment and you have used a temporary storage gateway instance which is installed in the cloud for the purpose of migration. After migrating the file system to the temporary storage gateway instance in the cloud, connect the file system to an on-premises storage gateway instance.

  1. Disconnect the file system on the temporary Oracle Cloud Infrastructure Storage Gateway instance that you had set up in the cloud and used for migration. See Disconnecting a File System in Oracle Cloud Infrastructure documentation.
  2. Connect the file system to the Oracle Cloud Infrastructure Storage Gateway instance that you have installed in the on-premises environment. See Connecting a File System in Oracle Cloud Infrastructure documentation.
    This results in a file system takeover and requires you to provide credentials to access your Oracle Cloud Infrastructure account. It might take a while to connect the migrated file system. The time taken for this operation depends on the number of files and directories in the file system.
  3. (Optional.) Perform additional validation by mounting the file system and performing a dry run with relevant application and workload.

Delete the Source File System and Appliance

After the migration is complete and you've validated the Oracle Cloud Infrastructure Storage Gateway file system, you can clean up unused resources.

  1. Delete the file system from the Oracle Cloud Infrastructure Storage Software Appliance instance.
    1. Log in to the management console.
    2. On the Dashboard tab, identify the file system that you want to delete.
    3. Make sure that the file system is disconnected. If it’s still connected, then click Disconnect.
    4. After the file system is disconnected, click its name.
    5. On the page that displays the details of the file system, click Delete.
  2. Delete the storage classic container after removing the objects in the container. The delete option is available only for empty containers.
    1. Sign in to the Oracle Cloud Infrastructure Object Storage Classic console.
    2. Identify the container that you want to delete.
    3. Click delete on the left side of the container name.
    4. Click OK to delete the container.
  3. After migrating all the file systems, you can uninstall the Oracle Cloud Infrastructure Storage Software Appliance instance.

    To uninstall an Oracle Cloud Infrastructure Storage Software Appliance instance in the cloud, see Deleting the Appliance in Using Oracle Cloud Infrastructure Storage Software Appliance.

    To uninstall an Oracle Cloud Infrastructure Storage Software Appliance instance in your on-premises environment, see Uninstalling the Appliance in Using Oracle Cloud Infrastructure Storage Software Appliance.

You can also delete any instances that you have created for migrating the workloads as well as any associated resources, including block volumes.

Migrate Object Storage Using Rclone

If you don't use the Oracle Cloud Infrastructure Storage Software Appliance, then you can use Rclone to migrate data from Oracle Cloud Infrastructure Object Storage Classic to Oracle Cloud Infrastructure Object Storage.

Note:

Before you use the procedures in this document, review the amount of object storage data to be migrated. Consult with your Oracle representative to be sure the amount of data you want to migrate is supported by this migration method.

Considerations for Data Migration Using Rclone

Before you start your migration, consider the following factors that could have an impact on your migration process.

  • You can't copy multiple containers at a time. You can copy only one container at a time. However, you can copy one or more objects at a time.
  • Metadata and policies aren't copied. This includes:
    • Custom metadata on objects and containers
    • Cross-Origin Resource Sharing (CORS) settings
    • Object immutability
    • ACLs on containers
    • Container quotas
    • Container replication policies
  • Server side encryption can be enabled on containers. Rclone can successfully copy containers where server side encryption is enabled.
  • If you have large objects in your Oracle Cloud Infrastructure Object Storage Classic account, then you should check if the object as well as its segments are stored in the same container. When the same container has the object and as well as its segments, Rclone detects this and copies the object correctly without duplicating data. However, when the segments are in one container and the object manifest is in a different container (for example, if you upload a large object using the File Transfer Manager command-line interface), then Rclone can't detect the duplicate object. In such cases, ensure that you don't copy the container that has the segments or if you copy it, you delete it later to avoid duplicating data.
  • There are some differences in the rules for naming containers in Oracle Cloud Infrastructure Object Storage Classic versus buckets in Oracle Cloud Infrastructure Object Storage. Container names can include UTF-8 characters subject to a maximum of 1061 bytes, while bucket names can include only upper or lower case letters, numbers, hyphens, underscores, and periods. Bucket names are also subject to a maximum of 256 characters. Due to these differences, you might need to rename some containers before you copy them.
  • There are also some differences in the rules for naming objects in Oracle Cloud Infrastructure Object Storage Classic versus Oracle Cloud Infrastructure Object Storage. In Oracle Cloud Infrastructure Object Storage Classic you can specify object names with UTF-8 characters subject to a maximum of 1061 bytes, while in Oracle Cloud Infrastructure Object Storage you can specify object names with UTF-8 characters subject to a maximum of 1024 bytes and up to 1024 characters.

Consider using the following rclone options in the following scenarios:

  • dry-run: Use this option to validate a migration before start to copy data. Amongst other benefits, this option allows you to check that the specified bucket name is valid.
  • includes, excludes, or filtering: Use these options to include or exclude files to be copied, based on patterns or size.
  • s3-upload-cutoff: Use this option to copy large objects.
  • progress: Use this option to generate a real-time overview of the transfer.
  • transfers: Use this option to utilize your network bandwidth better and increase throughput. You will need to tune this value based on the available bandwidth for your compute shape.

For more information about Oracle Cloud Infrastructure Object Storage Classic, see https://docs.oracle.com/en/cloud/iaas/storage-cloud/index.html and for information about Oracle Cloud Infrastructure Object Storage see https://docs.cloud.oracle.com/iaas/Content/Object/Concepts/objectstorageoverview.htm.

Before You Begin

Before you begin, complete the following prerequisites.

  • Validate the existing object storage data and back up the object storage data in the source environment.
  • Create a new object storage destination in your target environment. For information about creating a bucket, see Managing Buckets in Oracle Cloud Infrastructure documentation. You cannot change the name of the bucket after you create it, so carefully consider the naming conventions and if you want the bucket name to match the name of the container available at the source.
  • To migrate data from an Archive container, you must first restore the archived objects. For more information, see Restoring Archived Objects in Using Oracle Cloud Infrastructure Object Storage Classic.

Get Details of Your Source Environment

Identify the user name, password, authentication URL, and REST Endpoint URL for the Oracle Cloud Infrastructure Object Storage Classic account from which you want to migrate data.

You can find out the user name and password from the New Account Information email that you received from Oracle Cloud when your account was set up. If you don't have your New Account Information email, ask your account administrator for your Oracle Cloud user name and password.

To identify the authentication URL and REST Endpoint URL:

  1. Sign in to the Oracle Cloud My Services application.
    The My Services dashboard is displayed. It lists the services that are assigned to your account.
  2. Look for Oracle Cloud Infrastructure Object Storage Classic.
  3. Select View Details from the Actions menu. Alternatively, click the Oracle Cloud Infrastructure Object Storage Classic link on the Dashboard page.
    On the resulting page, the details of your Oracle Cloud Infrastructure Object Storage Classic instance are displayed.
  4. If your account was created after November 2017, then note down the following information that is displayed under the Additional Information section:
    • The authentication URL from the Auth V1 Endpoint field field. For example: 
      https://acme.storage.oraclecloud.com/auth/v1.0

      If your authentication URL is not available, then you must construct the authentication URL. See Authenticating Access When Using the REST API in Using Oracle Cloud Infrastructure Object Storage Classic. You must specify this value while sending a request for an authentication token.

    • The REST Endpoint URL from the REST Endpoint field. For example: 
      https://acme.storage.oraclecloud.com/v1/Storage-acme

Use Rclone to Migrate Your Object Storage Data

To migrate your object storage data, install and run rclone.

  1. Install rclone.

    You can install rclone on any virtual machine or system that has network access to both the source and destination environments. Rclone supports Windows, Linux, and other operating systems. The procedure in this document has been tested using version 1.48 of the rclone tool against Windows and Macintosh operating systems. For more information about supported operating systems, downloading the installer, and installation instructions, see https://rclone.org/downloads/.

  2. Create the rclone.conf file in the ~/.config/rclone folder if the file doesn't already exist.
  3. Add the following information to the ~/.config/rclone/rclone.conf file to create the remote device configuration for the source. 
    [classic-source]
type = swift
env_auth = false
user = Storage-acme:myuserName
key = pas$word
storage_url = https://acme.storage.oraclecloud.com/v1/Storage-acme
auth = https://acme.storage.oraclecloud.com/auth/v1.0
auth_token = AUTH_xxxx

    Replace the values for the user, key, storage_url, auth, and auth_token parameters with the values specific to your source environment. Where:

    • user: Specify the value you that you passed to the X-Storage-User header while requesting an authentication token to access Oracle Cloud Infrastructure Object Storage Classic.
    • key: Specify the password to access your Oracle Cloud Infrastructure Object Storage Classic account.
    • storage_url: Specify the REST Endpoint URL.
    • auth: Specify the authentication URL that you had passed while requesting an authentication token to access Oracle Cloud Infrastructure Object Storage Classic.
    • auth_token: Optionally, specify the value of a valid authentication token. This is not a required field when the user name, password, and authentication URL are specified.
  4. To create the remote device configuration for the destination, add the following information to the ~/.config/rclone/rclone.conf file: 
    [oci-dest]
type = s3
env_auth = false
access_key_id = YOUR_ACCESS_KEY
secret_access_key = YOUR_ACCESS_SECRET_KEY
region = YOUR_REGION_IDENTIFIER
endpoint = https://YOUR_NAMESPACE.compat.objectstorage.YOUR_REGION_IDENTIFIER.oraclecloud.com

    Replace the values for the access_key_id, secret_access_key, region and endpoint parameters with the values specific to your target environment. Where:

  5. Run the following commands to ensure that you can access the Oracle Cloud Infrastructure Compute Classic and the Oracle Cloud Infrastructure environments using the information that you have entered in the configuration file. The following command returns a list of containers that exist in your Oracle Cloud Infrastructure Object Storage Classic account.
    rclone -v lsd classic-source:

    Note down the name of the container from which you want to copy the data.

  6. The following command returns a list of buckets that exist in your Oracle Cloud Infrastructure account.
    rclone -v lsd oci-dest:

    Note down the name of the bucket to which you want to copy the data.

  7. Start copying the data. The following command copies files from the source to destination and skips the files that have already been copied.
    rclone copy classic-source:<containername> oci-dest:<containername>

    To monitor the progress, you can add a debug option. For example:

    rclone -I --log-level DEBUG copy classic-source:<containername> oci-dest:<containername>
  8. Optional. The following command modifies the destination to make it identical with source.
    rclone sync classic-source:<containername> oci-dest:<containername>