Data is uploaded to OBS using multipart upload. In the event of some situations, data uploads usually fail and generate fragments. You need to clear these fragments to free up storage space. The situations include but are not limited to the following:
With fragment management, you can clear fragments that are generated due to data upload failures.
diff --git a/docs/obs/tool/obs_03_1048.html b/docs/obs/tool/obs_03_1048.html
index f80b40033..d2a228062 100644
--- a/docs/obs/tool/obs_03_1048.html
+++ b/docs/obs/tool/obs_03_1048.html
@@ -2,9 +2,9 @@
An ACL defines grantees and their granted permissions.
-
Bucket and object ACLs are associated with accounts. By default, an ACL is created when a bucket or object is created, authorizing the owner the full control over the bucket or object.
+
Bucket and object ACLs are associated with accounts. By default, an ACL is created when a bucket or object is created, authorizing the owner full control over the bucket or object.
For easy and practical authorization, OBS ACLs have the following features:
-
- An ACL takes effect for both a tenant and users under this tenant.
- If a bucket and its objects have the same owner, the ACL configured on the bucket also applies to the objects in the bucket by default.
- An ACL is created during bucket or object creation by default. You can also configure one after the bucket or object is created.
+
- An ACL takes effect for both a tenant and users under this tenant.
- If a bucket and its objects have the same owner, the bucket's ACL also applies to the objects by default.
- An ACL is created during bucket or object creation by default. You can also configure one after the bucket or object is created.
ACLs control write and read permissions based on accounts, whose permission granularity is not as fine as bucket policies or IAM permissions. Generally, it is recommended that you use IAM permissions and bucket policies for access control.
You can grant bucket access permissions to users or user groups listed in Table 1 by configuring an ACL.
diff --git a/docs/obs/tool/obs_03_1050.html b/docs/obs/tool/obs_03_1050.html
index 1bab67034..d557ac777 100644
--- a/docs/obs/tool/obs_03_1050.html
+++ b/docs/obs/tool/obs_03_1050.html
@@ -4,7 +4,7 @@
Configure a lifecycle rule for a bucket to manage objects in the bucket.
For more information, see Lifecycle Management.
Procedure
- Log in to OBS Browser+.
- Select the bucket you want and choose More > Lifecycle Rules.
- Click Create.
- Configure related parameters.
- Status: Select Enable to enable this lifecycle rule after the configuration.
- Rule Name: Enter a rule name that is no longer than 255 characters.
- Applies To: By selecting Object name prefix, the lifecycle rule will apply to objects with the specified prefix contained in their name. You can also select Bucket for the lifecycle rule to apply to all objects in the bucket.
-
- If Object name prefix is selected and the specified prefix and the prefix in an existing lifecycle rule overlap, OBS regards the two rules as one and forbids you to configure the current rule. For example, if there is a rule with prefix abc in the system, another rule whose prefix contains abc cannot be configured.
- If there is already a lifecycle rule whose Applies To is set to Object name prefix, you are not allowed to configure a new rule whose Applies To is set to Bucket.
- If there is already a lifecycle rule whose Applies To is set to Bucket, you are not allowed to configure a new rule whose Applies To is set to Object name prefix.
+
- If Object name prefix is selected and the specified prefix and the prefix in an existing lifecycle rule overlap, OBS regards the two rules as one and forbids you to configure the current rule. For example, if there is a rule with prefix abc in the system, another rule whose prefix contains abc cannot be configured.
- If there is already a lifecycle rule whose Applies To is set to Object name prefix, you cannot configure a new rule with Applies To set to Bucket.
- If there is already a lifecycle rule whose Applies To is set to Bucket, you cannot configure a new rule with Applies To set to Object name prefix.
- You can use a lifecycle rule to specify the number of days after which objects that have been last updated and meet specified conditions are automatically transitioned to the Warm or Cold storage class, or are automatically deleted upon expiration.
- Transition to Warm: This rule transitions the objects meeting the conditions to the Warm storage class after the specified number of days since the last object update.
- Transition to Cold: This rule transitions the objects meeting the conditions to the Cold storage class after the specified number of days since the last object update.
- Expiration Time: This determines when an object will expire and then be deleted, or the day after which objects matching the rule will be deleted.
diff --git a/docs/obs/tool/obs_03_1055.html b/docs/obs/tool/obs_03_1055.html
index cb20557cc..faa19b80d 100644
--- a/docs/obs/tool/obs_03_1055.html
+++ b/docs/obs/tool/obs_03_1055.html
@@ -3,7 +3,7 @@
Configuring a Bucket Policy
Bucket policies define the access control over resources (buckets and objects) in OBS.
Procedure
- Log in to OBS Browser+.
- Select the bucket you want and choose More > Bucket Policy. The window shown in Figure 1 is displayed.
Figure 1 Configuring a bucket policy
- - Enter a bucket policy in the following format.
- Grant permissions to an account. In the following example, the account (whose account ID is 783fc6652cf246c096ea836694f71855) is granted the permission required to obtain the log management information about bucket logging.bucket3.
{
+ - Enter a bucket policy in the following format.
- Grant permissions to an account. In the following example, the account with ID 783fc6652cf246c096ea836694f71855 is granted permission to obtain log management information for bucket logging.bucket3.
{
"Statement": [
{
"Sid": "testing",
diff --git a/docs/obs/tool/obs_03_1057.html b/docs/obs/tool/obs_03_1057.html
index c368aeafd..2c78aad87 100644
--- a/docs/obs/tool/obs_03_1057.html
+++ b/docs/obs/tool/obs_03_1057.html
@@ -90,7 +90,7 @@
If a custom bucket policy is used to authorize such permissions, the HeadBucket, ListBucket, GetObject, and GetObjectVersion actions must be allowed. More actions can be allowed according to your actual needs.
The following are some restrictions when you (the user who adds the bucket) operate the external bucket:
-
- You cannot restore Archive objects that are not yours in the external bucket. You can view the object restore status only when the owner of those Archive objects grants you the read permission for the objects.
- You can perform only authorized actions on existing objects in the external bucket. If you want to perform additional operations on an object, you need to get corresponding permissions granted by the object owner.
- If you upload an object to the external bucket, the object ACL permissions will be automatically granted to the bucket owner, including the read permission for the object and the read and write permissions for the object ACL.
- The encrypted objects you uploaded to the external bucket cannot be accessed by the bucket owner, because the bucket owner does not have the key.
- To download an object from the external bucket, you must have the read permission for the object. You cannot download encrypted objects from the external bucket.
+
- You cannot restore Archive objects that are not yours in the external bucket. You can view the object restore status only when the owner of those Archive objects grants you the read permission for the objects.
- You can perform only authorized actions on existing objects in the external bucket. To perform any additional operations on an object, you must obtain the corresponding permissions from the object owner.
- If you upload an object to the external bucket, the object ACL permissions will be automatically granted to the bucket owner, including the read permission for the object and the read and write permissions for the object ACL.
- The encrypted objects you uploaded to the external bucket cannot be accessed by the bucket owner, because the bucket owner lacks the key.
- To download an object from the external bucket, you must have read permission for that object. Encrypted objects in the external bucket cannot be downloaded.
diff --git a/docs/obs/tool/obs_03_1058.html b/docs/obs/tool/obs_03_1058.html
index 15228b241..cd1463fa6 100644
--- a/docs/obs/tool/obs_03_1058.html
+++ b/docs/obs/tool/obs_03_1058.html
@@ -5,7 +5,7 @@
Prerequisites
You have been granted the ACL permissions to access buckets of other users.
For example, account A needs to add bucket bucket_share of account B to itself for it to read objects stored in bucket bucket_share. To do this, account B must obtain the Account ID of account A and grant account A the read permission on bucket bucket_share through OBS Console.
Account A can obtain its account ID (same as the owner ID) from the Basic Information page of the bucket.
-
If account B has granted anonymous users the read permission on bucket bucket_share, all users registered with OBS can add bucket bucket_share. For details about how to grant permissions to anonymous users, see Configuring a Bucket ACL.
+
If account B has granted anonymous users the read permission for bucket bucket_share, all OBS-registered users can add bucket bucket_share. For details about how to grant permissions to anonymous users, see Configuring a Bucket ACL.
Procedure
- Log in to OBS Browser+.
- In the navigation pane, choose External Bucket, as shown in Figure 1.
Figure 1 External buckets
- Click Add. In the Add External Bucket dialog box, enter the external bucket name and click OK, as shown in Figure 2.
Figure 2 Adding an external bucket
diff --git a/docs/obs/tool/obs_03_1067.html b/docs/obs/tool/obs_03_1067.html
index 4cec489ab..0310d4d63 100644
--- a/docs/obs/tool/obs_03_1067.html
+++ b/docs/obs/tool/obs_03_1067.html
@@ -6,7 +6,7 @@
Procedure
- Log in to OBS Browser+.
- Locate the object you want to share and click
next to the object.
- - Click Copy Link to copy the object link to a browser and open it. Then you can access the object.
+
- Click Copy Link to copy the object link to a browser and open it. You can then access the object.
diff --git a/docs/obs/tool/obs_03_1068.html b/docs/obs/tool/obs_03_1068.html
index 7b242f357..1e7ee4e71 100644
--- a/docs/obs/tool/obs_03_1068.html
+++ b/docs/obs/tool/obs_03_1068.html
@@ -2,33 +2,32 @@
Restoring a File or Folder
Restore Cold objects before downloading them.
-
Context
Cold storage is secure, durable, and inexpensive for storing data that is rarely accessed (averagely once a year). It is suitable for data archiving and long-term backup. This storage class allows you to safely store your data with low costs. However, it may take hours to restore data stored in this class.
+
Context
Cold storage is secure, durable, and inexpensive for storing data that is rarely accessed (averagely once a year). It is suitable for data archiving and long-term backup. This storage class allows you to safely store your data at low cost. However, it may take hours to restore data stored in this class.
If a Cold object is being restored, you cannot suspend or delete the restore task.
Objects in the Restoring state cannot be restored again.
-
Procedure
- Log in to OBS Browser+.
- Go to the object list in the target bucket.
- Select the file or folder you want to restore and choose More > Restore Object.
Figure 1 Restoring an object
-To restore an object, you must configure the validity period and restore speed. Table 1 describes relevant parameters.
+Procedure
- Log in to OBS Browser+.
- Go to the object list in the target bucket.
- Select the file or folder you want to restore and choose More > Restore.
To restore an object, you must configure the validity period and restore speed. Table 1 describes relevant parameters.
-Table 1 Restoring an objectParameter
+Table 1 Restoring an objectParameter
|
-Description
+ | Description
|
|---|
-Object Name
+ | Object Name
|
-Name of the object or path to be restored.
+ | Name of the object or path to be restored.
|
-Validity Period
+ | Validity Period
|
-Time duration when an object remains in the Restored state after it has been restored. The validity period starts when the object is restored. You can set the validity period to an integer ranging from 1 to 30 (days). The default value is 30.
+ | Time duration when an object remains in the Restored state after it has been restored. The validity period starts when the object is restored. You can set the validity period to an integer ranging from 1 to 30 (days). The default value is 30.
For example, you set Validity Period to 20 when restoring an object. 20 days after the object is restored, its status will change from Restored to Unrestored.
|
-Speed
+ | Speed
|
-How fast an object will be restored.
+ | How fast an object will be restored.
- Expedited: Data smaller than 250 MB can be restored within 1 to 5 minutes.
- Standard: All Cold data can be restored within 3 to 5 hours.
|
@@ -38,9 +37,9 @@
- Click OK to confirm the restored file or folder.
To view the restoration status of the file or folder, click  next to the object and choose Object Properties to view the restoration status. You can download the file only after it has been restored.
-Follow-Up ProcedureWithin the validity period of a restored object, you can restore the object again. Each time the object is restored, its validity period will restart. This prolongs the validity period.
- 1. If a restored object is restored again, its expiration time should be later than the time set for the previous restoration. For example, if an object will expire at 4/12/2021 08:00:00 GMT+08:00 after it is restored for the first time, it should expire later than 4/12/2021 08:00:00 GMT+08:00 after the second restore.
- 2. You are advised not to restore a large number of files in one batch. When more than 10,000 objects are being restored, OBS Browser+ will take a long time to query the restoration progress of such objects. If you indeed need to restore such a large number of files in one batch, you are advised to use SDKs or APIs to query the restoration progress. Alternatively, you can download files after the maximum restoration time that is estimated based on the restoration rate you selected.
+ Follow-Up ProcedureWithin the validity period of a restored object, you can restore the object again. Each time the object is restored, its validity period will restart. This extends the validity period.
+ 1. If a restored object is restored again, its expiration time should be later than the time set for the previous restoration. For example, if an object is scheduled to expire at 4/12/2021 08:00:00 GMT+08:00 after it is restored for the first time, it should expire later than 4/12/2021 08:00:00 GMT+08:00 after the second restore.
+ 2. You are advised not to restore a large number of files in one batch. When more than 10,000 objects are being restored, OBS Browser+ will take a long time to query the restoration progress of such objects. If you indeed need to restore such a large number of files in one batch, you are advised to use SDKs or APIs to query the restoration progress.
@@ -50,10 +49,3 @@
PrerequisitesThere are suspended tasks in the list.
diff --git a/docs/obs/tool/obs_03_1072.html b/docs/obs/tool/obs_03_1072.html
index 2c0d3d73d..548a8107a 100644
--- a/docs/obs/tool/obs_03_1072.html
+++ b/docs/obs/tool/obs_03_1072.html
@@ -6,7 +6,7 @@
Procedure- Log in to OBS Browser+.
- In the navigation pane, choose Task Management.
- Choose the Completed tab.
Figure 1 Completed task list
- (Optional) Select one or more tasks and click Delete (
 ).
-  You are advised to periodically delete the completed tasks from the list. For details, see Why Does the Task Processing Speed Slow After the Number of Tasks Exceeds a Million?
+
diff --git a/docs/obs/tool/obs_03_1077.html b/docs/obs/tool/obs_03_1077.html
index b47a4fa80..28471f00f 100644
--- a/docs/obs/tool/obs_03_1077.html
+++ b/docs/obs/tool/obs_03_1077.html
@@ -3,9 +3,9 @@
Background Running
Scenarios
There are lots of tasks running on OBS Browser+, but you want to close it and perform other operations while the tasks continue in the background.
- How do my tasks enter and end the background running mode?
+ How do I enter and exit background running mode for my tasks?
To enter background running mode, click the close icon in the upper right corner of OBS Browser+ and select Background Running in the Exit OBS Browser+ dialog box. Then, all your tasks will run in the background.
- To end background running mode, double-click the OBS Browser+ icon in the task bar to display its interface again.
+ To exit background running mode, double-click the OBS Browser+ icon in the taskbar to bring the interface back to the foreground.
diff --git a/docs/obs/tool/obs_03_1079.html b/docs/obs/tool/obs_03_1079.html
index cbf6659e9..dfe75b5a2 100644
--- a/docs/obs/tool/obs_03_1079.html
+++ b/docs/obs/tool/obs_03_1079.html
@@ -23,7 +23,7 @@
Auto select part size
|
-This option is selected by default, which automatically sets the size for each part based on the source file or object size.
+ | This option is selected by default. When enabled, OBS Browser+ automatically sets the part size for each multipart upload based on the size of the source file or object.
|
Upload Part Size
@@ -46,7 +46,7 @@
In most cases, multipart tasks not only speed up transfer, but also support resumable transfer of failed tasks. By default, the part size of a multipart task can be automatically adjusted by selecting Auto select part size. In practice, you can adjust the part size based on factors such as the file size and network conditions, to further improve upload and download performance and ensure the efficient and successful completion of tasks.
If you have a large number of small files (each is usually several MB) to be uploaded or downloaded, set Max. Number of Concurrent Tasks to a larger value for better performance. In this case, adjusting the concurrent parts allowed and the part size may be ineffective because the files are too small to reach the threshold of these parameters.
If you want to upload or download large files, set Upload Part Size, Download Part Size, and Max. Concurrent Parts to a larger value for better performance.
- - Due to limiting resources, if there are too many concurrent tasks (calculated from Max. Number of Concurrent Tasks × Max. Concurrent Parts), the upload and download performance may deteriorate because of resource switchover and preemption between threads. To avoid this, adjust the corresponding parameter values based on the actual file size and network condition.
- If the client network is poor, you can reduce the size of parts to be uploaded or downloaded and the total number of concurrent tasks to avoid task failures caused by the network fluctuation.
+ - Because resources are limited, too many concurrent tasks (calculated as Max. Number of Concurrent Tasks × Max. Concurrent Parts) can degrade upload and download performance due to resource switching and contention between threads. To avoid this, adjust the corresponding parameters according to the actual file size and network conditions.
- If the client network is poor, you can reduce the size of parts to be uploaded or downloaded and the total number of concurrent tasks to avoid task failures caused by the network fluctuation.
| |
|---|
