Data Synchronization

Learn how to manage the transmission of object storage data between buckets on your Roving Edge devices and your Oracle Cloud Infrastructure tenancy.

Roving Edge devices are built to function connected, semi-connected, or disconnected from the cloud for extended periods. While data syncing with your Oracle Cloud Infrastructure tenancy is optional, if you choose to use this feature, it’s essential to perform syncing regularly according to your use case.

You can perform syncing in the following ways:

  • Roving Edge device bucket-to-Oracle Cloud Infrastructure bucket: Upload data to your Oracle Cloud Infrastructure object storage buckets for processing and long-term storage. To maximize available storage on your device, delete the data from the Roving Edge device after the upload is finished.

  • Oracle Cloud Infrastructure bucket-to-Roving Edge device bucket: Download data residing in the object storage buckets in your Oracle Cloud Infrastructure tenancy to the devices. Also update system files for the device and its browser-based user interface.

Note

You can't set up a bi-directional sync using two tasks and the same object storage buckets used by Oracle Cloud Infrastructure and the Roving Edge devices.

Note

The maximum size of an object you can use with Roving Edge devices is 10 TiB. Any objects in your object store workload or any custom images greater than 10 TiB in size are not included in the data synchronization.

The following are the prerequisite tasks for performing a bi-directional data synchronization:

  • Connect your Roving Edge device to your local site network, such as a site headquarters using the internet or FastConnect.

  • Provide routing using the internet or FastConnect to an Oracle Cloud Infrastructure region.

  • Provide an IAM policy for data synchronization that grants a user group (or dynamic group for services) permissions to create, read, update, delete, and manage data synchronization tasks and interact with Oracle Cloud Infrastructure Object Storage within a specified compartment or across the tenancy. For more information, see Creating and Managing User Groups, Creating and Managing Dynamic Groups, and Managing Policies.

    For example, to configure the Resource Prinicpal Policies:

    Create a dynamic group:

    Create dynamic group "cccinfrastructure-datasync-grp" with Matching Rules:
    All {resource.type='cccinfrastructure'}
    
    Then create a policy for that dynamic group in the tenancy:
    
    allow dynamic-group cccinfrastructure-datasync-grp to manage objectstorage-namespaces
    allow dynamic-group cccinfrastructure-datasync-grp to manage object-family 

    To configure the API policy:

    Create a user group and add the appropriate users.

    Create a compartment-specific or tenancy-wide policy granting this group necessary permissions to manage data sync API actions and object storage. For example:

    Allow group data-sync-group to {DATA_SYNC_TASK_DEF_CREATE, DATA_SYNC_TASK_DEF_UPDATE, DATA_SYNC_TASK_DEF_READ, ...} in compartment <identifier>
    Allow group data-sync-group to manage object-family in compartment <identifier>

You can perform the following data sync tasks: