Updated on 2026-10-28 GMT+08:00
Indexes Cannot Be Backed Up
Index backup is implemented by creating cluster snapshots. If index backup fails, perform the following steps to troubleshoot this problem:
Check Whether the Account or IAM User Has the Index Backup Permissions
- In the cluster list, click the name of the target cluster. The cluster information page is displayed.
- Click the Cluster Snapshots tab.
- Click the IAM agency name under IAM Agency to go to the agency details page.
- On the Basic Information tab, check that Cloud Service is Cloud Search Service (CSS).
- On the Permissions tab, click a permission name. On the displayed page, check that Policy Content contains the following actions:
"obs:bucket:GetBucketLocation", "obs:object:GetObjectVersion", "obs:object:GetObject", "obs:object:DeleteObject", "obs:bucket:HeadBucket", "obs:bucket:GetBucketStoragePolicy", "obs:object:DeleteObjectVersion", "obs:bucket:ListBucketVersions", "obs:bucket:ListBucket", "obs:object:PutObject"
- If SSE-KMS encryption is enabled for the selected OBS bucket, check whether the agency has the following KMS permissions:
"kms:cmk:create", "kms:dek:create", "kms:cmk:get", "kms:dek:decrypt", "kms:cmk:list"
- If the agency has insufficient permissions, modify its permissions.
- If a custom agency is used, you can modify the agency to add the missing actions.
- If the default CSS agency is used, click Modify Settings on the Cluster Snapshots page, and click Automatically Create IAM Agency or One-click Authorization in the IAM Agency area to modify the agency.
- If indexes still cannot be backed up after the agency permissions are modified, contact technical support.
Parent topic: Functions
What is your overall rating for this page?
0
1
2
3
4
5
6
7
8
9
10
Very dissatisfiedVery satisfied
Thank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.