Skip to content

Data Forwarding to Volcengine TOS

  1. Complete the setup for rule name and filter conditions.
  2. Continue to configure the backup.

Start Configuration

  1. Select Volcengine TOS as the backup type, which means saving the matched data to this object storage.
  2. Choose the storage format.
  3. Choose whether to encrypt storage.
  4. Select the storage type.
  5. Select the access type.
  6. Click Confirm to successfully create the rule.
Note

If there are changes to the backup type information, ensure that the configurations on the associated platform are updated accordingly to avoid data write failures due to configuration changes. New configuration rules will take effect within 5 minutes.

Storage Type

Storage Type
 Use Cases
Standard Storage High availability, high reliability, high-performance storage type, suitable for frequently accessed data.
Infrequent Access Storage Suitable for data that is not frequently accessed, with a minimum storage period of 30 days.
Archive Flashback Storage Suitable for data that is rarely accessed, with a minimum storage period of 90 days. Supports direct reading (flashback) and direct conversion to other storage types without additional restoration or thawing.
Archive Storage Suitable for business scenarios where data is rarely accessed and needs to be stored long-term, with a minimum storage period of 90 days. Data must be restored before accessing Archive Storage.
Cold Archive Storage A cold data type suitable for business scenarios where data is extremely rarely accessed and needs to be stored long-term. Minimum storage period is 180 days. Data must be restored before accessing Cold Archive Storage.

Access Type

Role Authorization

  1. After configuring the authorization policy in the Volcengine Cloud console, fill in the backup information, including the Volcengine Cloud account ID, TOS role name, region, and bucket name.

  2. Enter the storage path to facilitate further distinction and location of the forwarded data.

  3. Click "Test Connection". If the above information meets the specifications, a successful connection test message will be displayed. Click Confirm to save the current rule.

If the test fails:

You need to confirm:

  • Whether the authorization was successful.
  • Whether the account ID is correct.
  • Whether the bucket exists.
  • Whether the Region is inconsistent.

Access Keys

  1. Configure the Guance RAM policy in Volcengine Cloud. After configuration is complete, enter the Volcengine Cloud AK & SK, region, and bucket name.

  2. Enter the storage path to facilitate further distinction and location of the forwarded data.

  3. Click "Test Connection". If the above information meets the specifications, a successful connection test message will be displayed. Click Confirm to save the current rule.

If the test fails:

You need to confirm:

  • Whether the AK / SK exist.
  • Whether the bucket exists.
  • Whether the Region is inconsistent.

Account Authorization

  1. Volcengine Cloud provides cross-account authorization capability. You need to use the Guance specific account ID and follow the configuration instructions to add a cross-account access authorization policy.

  2. After configuration, select the region and enter the bucket name.

  3. Enter the storage path to facilitate further distinction and location of the forwarded data.

  4. Click "Test Connection". If the above information meets the specifications, a successful connection test message will be displayed. Click Confirm to save the current rule.

If the test fails:

You need to confirm:

  • Whether the account ID is correct.
  • Whether the bucket exists.
  • Whether the Region is inconsistent.
Storage Path Naming Convention
  1. Create a single folder or multi-level folders. A slash (/) indicates creating multi-level folders.
  2. Folder names cannot start or end with a slash (/).
  3. Cannot contain two or more consecutive slashes (/).
  4. Applicable to all access types.
Note
  • If the entered folder does not exist, the system will create it directly, and data will still be saved to that path.
  • Please be cautious when changing the storage path. Due to a delay of approximately 5 minutes for configuration updates, some data might still be forwarded to the original directory after the change.

Next Steps

Continue to configure the data viewing permissions for the current forwarding rule.

Feedback

Is this page helpful? ×