2024-02-26
|
This is the fourth official release.
diff --git a/docs/obs/tool/obs_03_1034.html b/docs/obs/tool/obs_03_1034.html
deleted file mode 100644
index 10bddef3b..000000000
--- a/docs/obs/tool/obs_03_1034.html
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-How Can I Locate Common Network Errors?
-Accessing OBS using OBS Browser+ is usually affected by your network quality. If there are network fluctuations, your access may time out or your upload/download will fail. If such faults occur, an error message will be displayed in the upper right corner or on the task management page. You can also view log files basic.log and obssdk.log to check whether the network is abnormal. To obtain the log path, choose Settings > Basic Configurations > Log Path. Common errors include connect ETIMEDOUT and premature end of Content-Length delimiter message body (expected: xxxxx, actual:xxxxxx).
- Solutions:
- - Ping the bucket domain name (bucketName.domain name) to check the network connectivity. If the network is disconnected, rectify your local network first.
- If the network is normal, but basic operations such as listing and bucket creation occasionally time out, it may be caused by network fluctuations. In this case, try your operation again.
- premature end of Content-Length delimiter message body (expected: xxxxx, actual:xxxxxx) is a common error during upload and download operations, because there are occasional network fluctuations. OBS Browser+ supports resumable transfer, so you can retry the upload and download tasks that fail due to network errors. If upload and download tasks fail frequently due to network errors, reduce the value of Max. Number of Concurrent Tasks.
 - If you want to further analyze the cause of upload or download failures, capture packets on OBS Browser+ to check whether there is packet loss or other network problems on the entire network link. To capture packets on OBS Browser+, you are advised to select Other object storage services for Service during the login and manually specify an endpoint starting with http://, because network packets will be encrypted for transmission if the HTTPS protocol is used.
-
- How Can I Permanently Share Files or Folders with Other Users?
-You can use OBS Browser+ to share files or folders with other users through URLs. These URLs are valid for only a certain period. Once they expire, files or folders will not be accessed. If you want to share a file permanently, configure this file to be accessible from anonymous users, so anonymous users can access the file through the URL you shared. To share a folder permanently, configure a bucket policy that makes the objects prefixed with a certain folder readable for the public, so anonymous users can access all objects under that folder.
+ You can use OBS Browser+ to share files or folders with other users through URLs. These URLs are valid for only a certain period. Once they expire, files or folders will not be accessed.
+ - To share a file permanently, configure this file to be accessible from anonymous users, so anonymous users can access the file through the URL you shared.
- To share a folder permanently, configure a bucket policy that makes the objects prefixed with a certain folder readable for the public, so anonymous users can access all objects under that folder.
diff --git a/docs/obs/tool/obs_03_1036.html b/docs/obs/tool/obs_03_1036.html
index 5f76f5393..88c747378 100644
--- a/docs/obs/tool/obs_03_1036.html
+++ b/docs/obs/tool/obs_03_1036.html
@@ -1,7 +1,10 @@
How Can I Access a Specific Bucket or Directory?
- In some scenarios, when you try to log in to OBS Browser+ using access keys (AK and SK) that have only the permission to access a specific bucket or a specific directory in a bucket, the login will fail because of the lack of listing and other permissions. To address this issue, you can specify an access path (in the obs://bucketName/folder format) on the login page.
+ Background:
+ When you log in to OBS Browser+ using access keys (AK and SK) that only have the permissions to access a specific bucket or a specific directory in a bucket, a message indicating insufficient permissions is displayed.
+ Solution:
+ You can specify an access path (in the obs://bucketName/folder format) on the login page.
diff --git a/docs/obs/tool/obs_03_1037.html b/docs/obs/tool/obs_03_1037.html
index 3dff62c5b..2ff3cdf6e 100644
--- a/docs/obs/tool/obs_03_1037.html
+++ b/docs/obs/tool/obs_03_1037.html
@@ -1,7 +1,9 @@
Can I Cancel the Directory Sharing After a Directory Has Been Shared with Others?
- No. URLs for sharing objects or directories through OBS Browser+ have a validity period. During the validity period, the sharing cannot be canceled. Therefore, exercise caution when selecting a URL validity period and when selecting the objects or directories you want to share.
+ No.
+ URLs for sharing objects or directories through OBS Browser+ have a validity period. During the validity period, the sharing cannot be canceled.
+ Therefore, exercise caution when selecting a URL validity period and when selecting the objects or directories you want to share.
diff --git a/docs/obs/tool/obs_03_1041.html b/docs/obs/tool/obs_03_1041.html
index 15294075d..973aa4cc1 100644
--- a/docs/obs/tool/obs_03_1041.html
+++ b/docs/obs/tool/obs_03_1041.html
@@ -2,47 +2,49 @@
Creating a Bucket
Buckets are containers that store objects in OBS. To store data in OBS, you must first create a bucket.
- Procedure- Log in to OBS Browser+.
- In the upper part of the page, click Create Bucket.
- In the displayed dialog box, configure bucket parameters, as shown in Figure 1.
Figure 1 Creating a bucket
-
-
-
-
+Procedure- Log in to OBS Browser+.
- In the upper part of the page, click Create Bucket.
- In the displayed dialog box, configure bucket parameters, as shown in Figure 1.
Figure 1 Creating a bucket
-Table 1 Bucket creation parametersParameter
+Table 1 Bucket creation parametersParameter
|
-Description
+ | Description
|
|---|
-Region
+ | Region
|
-Enter the region where you want to create a bucket. Once the bucket is created, its region cannot be changed.
+ | Enter the region where you want to create a bucket.
+- Once the bucket is created, its region cannot be changed.
- For lower latency and faster access, create a bucket in the region nearest to you.
|
-Storage Class
+ | Storage Class
|
-Storage class of the bucket. Different storage classes meet customers' needs for storage performance and costs.
+ | Storage class of the bucket.
+Different storage classes meet customers' needs for storage performance and costs.
- Standard: applicable to scenarios where a large number of hot files or small files need to be accessed frequently (multiple times per month on average) and require fast access response.
- Warm: ideal for storing data that is not frequently accessed (less than 12 times per year on average) but requires fast access response.
- Cold: suitable for archiving data that is rarely accessed (averagely once a year) and has no requirements for quick response.
+ NOTE: During the object upload, an object inherits its bucket's storage class by default, and you can also specify a different storage class for the object.
+
|
-Bucket ACL
+ | Bucket ACL
|
-Controls read and write permissions on buckets.
+ | Controls read and write permissions on buckets.
- Private: Only users granted permissions by the ACL can access the bucket.
- Public Read: Anyone can read objects in the bucket.
- Public Read and Write: Anyone can read, write, or delete objects in the bucket.
|
-Bucket Name
+ | Bucket Name
|
-Name of the bucket you want to create, which must be globally unique. A bucket name:
+ | Name of the bucket you want to create, which must be globally unique.
+A bucket name:
- Must be 3 to 63 characters long and start with a digit or letter. Only lowercase letters, digits, hyphens (-), and periods (.) are allowed.
- Cannot be formatted as an IP address.
- Cannot start or end with a hyphen (-) or period (.).
- Cannot contain two consecutive periods (..), for example, my..bucket.
- Cannot contain a period (.) and a hyphen (-) adjacent to each other, for example, my-.bucket or my.-bucket.
+After a bucket is created, its name cannot be changed.
+A user can create a maximum of 100 buckets in OBS.
+ NOTE: - You can click
 next to the Bucket Name text box to view the bucket naming rules. - When a URL is used to access a bucket, the bucket name will become part of the URL. According to the DNS rule, URLs do not support uppercase letters and cannot recognize buckets whose name contains uppercase letters. Therefore, a bucket name can contain only lowercase letters, digits, hyphens (-), and periods (.). For example, if you attempt to access bucket MyBucket using a URL, the URL will parse MyBucket as mybucket. This results in an access error.
- DNS naming rules can standardize bucket names globally, facilitating the resolution during bucket access. With the DNS naming rules used, you can benefit from new functions and optimized features, and configure static website hosting for buckets.
+
|
You can click  next to the bucket name to learn about the bucket naming rules. A user can create a maximum of 100 buckets in OBS.
- - When a URL is used to access a bucket, the bucket name will become part of the URL. According to the DNS rule, URLs do not support uppercase letters and cannot recognize buckets whose name contains uppercase letters. Therefore, a bucket name can contain only lowercase letters, digits, hyphens (-), and periods (.) For example, if you attempt to access bucket MyBucket using a URL, the URL will parse MyBucket as mybucket. This results in an access error.
- DNS naming rules can standardize bucket names globally, facilitating the resolution during bucket access. With the DNS naming rules used, you can benefit from new functions and optimized features, and configure static website hosting for buckets.
- Once a bucket is created, its name cannot be changed. Make sure that the bucket name you set is appropriate.
-
- Click OK. If the bucket is successfully created, it is displayed in the bucket list. If the creation fails, an error message will be displayed.
diff --git a/docs/obs/tool/obs_03_1042.html b/docs/obs/tool/obs_03_1042.html
index efef906d5..ed1f3a62a 100644
--- a/docs/obs/tool/obs_03_1042.html
+++ b/docs/obs/tool/obs_03_1042.html
@@ -2,17 +2,9 @@
Searching for a Bucket
Search for a bucket on OBS Browser+ by using a string contained in the bucket name.
- Procedure- Log in to OBS Browser+.
- In the upper right corner of the page, enter a string contained in the bucket name in the search box, as shown in Figure 1.
-
-
-
-
+Procedure- Log in to OBS Browser+.
- In the upper right corner of the page, enter a string contained in the bucket name in the search box, as shown in Figure 1.
Figure 1 Search box
- Click
 .Matching buckets are displayed in the list. If you want to search for other buckets, click  in the search box to delete the keyword you have entered and enter a new one, as shown in Figure 2.
-Figure 2 Searching for buckets
-
-
-
-
+Figure 2 Searching for buckets
diff --git a/docs/obs/tool/obs_03_1043.html b/docs/obs/tool/obs_03_1043.html
index 35733f5b7..c9b539c09 100644
--- a/docs/obs/tool/obs_03_1043.html
+++ b/docs/obs/tool/obs_03_1043.html
@@ -1,62 +1,58 @@
Viewing a Bucket's Basic Information
- View the basic information about a bucket, such as the bucket type, account ID, region, and storage usage.
- Procedure- Log in to OBS Browser+.
- Right-click the bucket you want to view and choose Basic Information from the shortcut menu.
- In the displayed Basic Information window, view your required information, as shown in Figure 1.
Figure 1 Bucket's basic information
-
-
-
-
+View the basic information about a bucket, such as the bucket type, account ID, region, and used capacity.
+ Procedure- Log in to OBS Browser+.
- Right-click the bucket you want to view and choose Basic Information from the shortcut menu.
- In the displayed Basic Information window, view your required information, as shown in Figure 1.
Figure 1 Bucket's basic information
-Table 1 Parameter descriptionParameter
+Table 1 Parameter descriptionParameter
|
-Description
+ | Description
|
|---|
-Bucket Name
+ | Bucket Name
|
-Name of the bucket.
+ | Name of the bucket.
|
-Bucket Type
+ | Bucket Type
|
-Object storage.
+ | Object storage.
|
-Region
+ | Region
|
-Region where the bucket is located.
+ | Region where the bucket is located.
|
-Storage Class
+ | Storage Class
|
-Storage class of the bucket. It can be Standard, Warm, or Cold.
+ | Storage class of the bucket. It can be Standard, Warm, or Cold.
|
-Bucket Version
+ | Bucket Version
|
-Version number of the bucket.
+ | Version number of the bucket.
|
-Used Capacity
+ | Used Capacity
|
-Total capacity used by objects in the bucket.
+ | Total capacity used by objects in the bucket.
|
-Objects
+ | Objects
|
-Number of objects in the bucket.
+ | Number of objects in the bucket.
|
-Account ID
+ | Account ID
|
-Unique identity of the bucket owner. It is the same as Account ID on the My Credentials page.
+ | Unique identity of the bucket owner. It is the same as Account ID on the My Credentials page.
|
-Created
+ | Created
|
-Time when the bucket was created.
+ | Time when the bucket was created.
|
diff --git a/docs/obs/tool/obs_03_1044.html b/docs/obs/tool/obs_03_1044.html
index b008f64b9..d9c44ad96 100644
--- a/docs/obs/tool/obs_03_1044.html
+++ b/docs/obs/tool/obs_03_1044.html
@@ -7,12 +7,8 @@
 Deleted fragments cannot be recovered. Before deleting fragments, ensure that all multipart uploads are complete, or deleting fragments may cause uploads to fail.
Procedure- Log in to OBS Browser+.
- Select the bucket you want and click Fragments.
- In the Fragments window, select the unwanted fragments and click Delete above the list. You can also click Delete All above the list to delete all fragments. Click
 in the upper right corner to refresh the fragment list, as shown in Figure 1.Figure 1 Fragment management
-
-
-
-
- - In the displayed Warning dialog box, confirm the delete information and click OK.
- Click OK.
The Fragments window is displayed. You can close this window to go back to the OBS Browser+ homepage.
+Procedure- Log in to OBS Browser+.
- Select the bucket you want and click Fragments.
- In the Fragments window, select the unwanted fragments and click Delete above the list. You can also click Delete All above the list to delete all fragments. Click in the upper right corner to refresh the fragment list, as shown in Figure 1.
Figure 1 Fragment management
+ - In the displayed Warning dialog box, confirm the delete information and click Yes.
- Click Yes.
The Fragments window is displayed. You can close this window to go back to the OBS Browser+ homepage.
Procedure- Log in to OBS Browser+.
- Select the bucket you want to delete and click Delete.
The name of a deleted bucket can be reused for another bucket or a parallel file system at least 30 minutes after the deletion.
- - Click OK to delete the bucket.
+ - Click Yes to delete the bucket.
diff --git a/docs/obs/tool/obs_03_1046.html b/docs/obs/tool/obs_03_1046.html
index e4ae87376..459ee0d1c 100644
--- a/docs/obs/tool/obs_03_1046.html
+++ b/docs/obs/tool/obs_03_1046.html
@@ -1,13 +1,13 @@
Advanced Bucket Settings
- This chapter describes how to manage bucket attributes, including bucket ACL permissions, bucket policies, and external bucket adding.
+ This chapter describes how to manage bucket attributes, including bucket ACL permissions, lifecycle rules, bucket policies, and external bucket adding.
- Bucket ACLs
-- Lifecycle Management
+ - Configuring a Lifecycle Rule
- Bucket Policies
diff --git a/docs/obs/tool/obs_03_1048.html b/docs/obs/tool/obs_03_1048.html
index a04fe8d91..f80b40033 100644
--- a/docs/obs/tool/obs_03_1048.html
+++ b/docs/obs/tool/obs_03_1048.html
@@ -5,7 +5,7 @@
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.
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.
-ACLs control write and read permissions based on accounts, whose permission granularity is not as fine as bucket policies or IAM policies. Generally, it is recommended that you use IAM permissions and bucket policies for access control.
+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.
Table 1 Authorized users supported by OBSPrincipal
@@ -22,7 +22,7 @@
|
|---|
Owner
|
-The owner of a bucket is the account that created the bucket. A bucket owner has all access permissions on the bucket by default. The read and write permissions for the bucket ACL are permanently available to the bucket owner, and cannot be modified.
+ | The owner of a bucket is the account that created the bucket. By default, a bucket owner has full control over the bucket ACL. The read and write permissions for the bucket ACL are permanently available to the bucket owner, and cannot be modified.
An object owner is the account that uploads the object, but may not be the owner of the bucket that stores the object. The object owner has the read permission on the object, as well as the read and write permissions on the object ACL by default, and such permissions cannot be modified.
NOTICE: Do not modify the bucket owner's read and write permissions for the bucket.
diff --git a/docs/obs/tool/obs_03_1049.html b/docs/obs/tool/obs_03_1049.html
index 1ce27891b..f85728204 100644
--- a/docs/obs/tool/obs_03_1049.html
+++ b/docs/obs/tool/obs_03_1049.html
@@ -2,11 +2,7 @@
Configuring a Bucket ACL
Configure ACL permissions for owners, anonymous users, or specific users.
- Procedure- Log in to OBS Browser+.
- Select the bucket you want and click Bucket ACLs.
- Configure the bucket ACL as needed and click OK, as shown in Figure 1.
Figure 1 Configuring an ACL
-
-
-
-
+Procedure- Log in to OBS Browser+.
- Select the bucket you want and click Bucket ACLs.
- Configure the bucket ACL as needed and click OK, as shown in Figure 1.
Figure 1 Configuring an ACL
If no ACL permissions are configured for a new bucket, OBS Browser+ automatically disables the access to the bucket and its objects by any other users except the bucket owner.
Lifecycle Management
-Lifecycle management allows you to configure rules to periodically delete objects from a bucket or transition objects between storage classes (for example, transition to the Cold or Warm storage class). This section describes lifecycle management and how to configure lifecycle rules.
+ Configuring a Lifecycle Rule
+ 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.
+
+- 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.
+
+ - Click OK to save the lifecycle rule.
+
+ Related OperationsAfter the configuration is complete, you can edit, delete, enable, or disable the configured rule if necessary.
+
-
-
diff --git a/docs/obs/tool/obs_03_1051.html b/docs/obs/tool/obs_03_1051.html
deleted file mode 100644
index ea965f715..000000000
--- a/docs/obs/tool/obs_03_1051.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
- Overview
- Lifecycle management for OBS includes periodically deleting objects from buckets and transitioning between object storage classes based on pre-defined rules.
- You may configure lifecycle management rules to: - Periodically delete files that are only meant to be retained for specified periods of time.
- Transition documents that are seldom accessed to the Warm or Cold storage class or delete them.
-
- You can define lifecycle rules to identify objects in the scenarios above and further manage their lifecycles.
- Using lifecycle rules to transition objects that are no longer frequently accessed to the Cold or Warm storage class can save costs. Transition basically means that the object storage class is altered without copying the object. You can also manually change the storage class of an object on the Objects page. For details, see Uploading a File or Folder.
- Lifecycle management rules have two key elements:
- - Policy: You can configure a lifecycle rule for it to apply to a set of objects with the specified prefix, or to apply to the entire bucket (that is, apply to all the objects in the bucket).
- Time: 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 defines the number of days since the last object update after which objects meeting specified conditions are automatically transitioned to the Warm storage class.
- Transition to Cold: This defines the number of days since the last object update after which objects meeting specified conditions are automatically transitioned to the Cold storage class.
- Expiration Time: This defines the number of days since the last object update after which objects meeting specified conditions are automatically expired and then deleted.
-
- Objects can be transitioned to Warm at least 30 days after their last update. If you configure to transition objects first to Warm and then Cold, the objects must stay Warm at least 30 days before they can be transitioned to Cold. For example, if you configure to transition objects to Warm 33 days after their last update, the objects can be transitioned to Cold at least 63 days after their last update. If only transition to Cold is used, but transition to Warm is not, there is no limit on the number of days for transition. The number of days for objects to expire must be greater than the two transition times.
-
-
-
diff --git a/docs/obs/tool/obs_03_1052.html b/docs/obs/tool/obs_03_1052.html
deleted file mode 100644
index 9eddbd72f..000000000
--- a/docs/obs/tool/obs_03_1052.html
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
- Configuring a Lifecycle Rule
- Configure a lifecycle rule for a bucket to manage objects in the bucket.
- 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.
-
-- 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.
-
-For example, on January 7, 2022, you saved the following files in OBS:
-- log/test1.log
- log/test2.log
- doc/example.doc
- doc/good.txt
-On January 10, 2022, you saved the following files in OBS:
-- log/clientlog.log
- log/serverlog.log
- doc/work.doc
- doc/travel.txt
If you configure a rule on January 10, 2022 and the rule will make the objects with log/ as their prefix expired and deleted one day later, objects log/test1.log, log/test2.log, log/clientlog.log, and log/serverlog.log will be deleted from the files above on January 12, 2022.
-
- - Click OK to save the lifecycle rule.
-
- Related OperationsAfter the configuration is complete, you can edit, delete, enable, or disable the configured rule if necessary.
-
-
-
-
diff --git a/docs/obs/tool/obs_03_1055.html b/docs/obs/tool/obs_03_1055.html
index 1fecc96ac..cb20557cc 100644
--- a/docs/obs/tool/obs_03_1055.html
+++ b/docs/obs/tool/obs_03_1055.html
@@ -2,25 +2,22 @@
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
-
-
-
+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.
{
"Statement": [
{
- "Sid": "testing",
+ "Sid": "testing",
"Effect": "Allow",
"Principal": {
"ID": [
- "domain/783fc6652cf246c096ea836694f71855:user/*"
+ "domain/783fc6652cf246c096ea836694f71855:user/*"
]
},
"Action": [
"GetBucketLogging"
],
"Resource": [
- "logging.bucket3"
+ "logging.bucket3"
]
}
]
@@ -59,18 +56,18 @@
- Grant permissions to an IAM user. In the following example, the user (whose ID is 71f3901173514e6988115ea2c26d1999) under the account (whose ID is 219d520ceac84c5a98b237431a2cf4c2) is assigned the permission required to set log management for bucket logging.bucket3.
{
"Statement": [
{
- "Sid": "testing",
+ "Sid": "testing",
"Effect": "Allow",
"Principal": {
"ID": [
- "domain/219d520ceac84c5a98b237431a2cf4c2:user/71f3901173514e6988115ea2c26d1999"
+ "domain/219d520ceac84c5a98b237431a2cf4c2:user/71f3901173514e6988115ea2c26d1999"
]
},
"Action": [
- "PutBucketLogging"
+ "PutBucketLogging"
],
"Resource": [
- "logging.bucket3"
+ "logging.bucket3"
]
}
]
@@ -99,12 +96,14 @@
|
219d520ceac84c5a98b237431a2cf4c2
|
-ID of an account. You can change it as needed. You can click  next to the target bucket to obtain the Account ID on the Basic Information page.
+ | ID of an account. You can change it as needed.
+You can click next to the target bucket to obtain the Account ID on the Basic Information page.
|
71f3901173514e6988115ea2c26d1999
|
-ID of a user under the account. You can change it as needed. You can choose My Credentials from the username in the upper right corner of OBS Console to obtain the IAM User ID.
+ | ID of a user under the account. You can change it as needed.
+You can choose My Credentials from the username in the upper right corner of OBS Console to obtain the IAM User ID.
|
@@ -112,7 +111,7 @@
-For details about the fields in a bucket policy, see Bucket Policy Overview.
+For details about bucket policy parameters, see Bucket Policy Overview.
diff --git a/docs/obs/tool/obs_03_1057.html b/docs/obs/tool/obs_03_1057.html
index b1008e44f..bda2e57cd 100644
--- a/docs/obs/tool/obs_03_1057.html
+++ b/docs/obs/tool/obs_03_1057.html
@@ -3,6 +3,94 @@
Overview
If you have ACL permissions on buckets of other users, you can add them through OBS Browser+ as external buckets. By doing so, you can access these external buckets locally using your account.
By default, after user A has added a bucket of user B and uploaded an object to the bucket, user B cannot download the object.
+ You can grant read and write permissions to a bucket through the bucket ACL or bucket policy. Permissions controlled by a bucket ACL are as follows:
+
+ Table 1 Permissions controlled by a bucket ACLBucket ACL Permission
+ |
+Option
+ |
+Mapped Action in a Custom Bucket Policy
+ |
+
|---|
+
+Access to bucket
+ |
+Read
+ |
+- HeadBucket
- ListBucket
- ListBucketVersions
- ListBucketMultipartUploads
+ |
+
+Write
+ |
+- PutObject
- DeleteObject
- DeleteObjectVersion
+ |
+
+Access to ACL
+ |
+Read
+ |
+GetBucketAcl
+ |
+
+Write
+ |
+PutBucketAcl
+ |
+
+
+
+
+ Permissions controlled by a standard bucket policy are as follows:
+
+ Table 2 Permissions controlled by a standard bucket policyParameter
+ |
+Public Read
+ |
+Public Read and Write
+ |
+
|---|
+
+Effect
+ |
+Select Allow.
+ |
+Select Allow.
+ |
+
+Principal
+ |
+* (Any user)
+ |
+* (Any user)
+ |
+
+Resources
+ |
+* (All objects in a bucket)
+ |
+* (All objects in a bucket)
+ |
+
+Actions
+ |
+- GetObject
- GetObjectVersion
- HeadBucket
- ListBucket
+ |
+- GetObject
- GetObjectVersion
- PutObject
- DeleteObject
- DeleteObjectVersion
- HeadBucket
- ListBucket
+ |
+
+Conditions
+ |
+N/A
+ |
+N/A
+ |
+
+
+
+
+ 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.
diff --git a/docs/obs/tool/obs_03_1058.html b/docs/obs/tool/obs_03_1058.html
index 6e6a71856..15228b241 100644
--- a/docs/obs/tool/obs_03_1058.html
+++ b/docs/obs/tool/obs_03_1058.html
@@ -7,16 +7,8 @@
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.
- 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
-
-
-
+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
An external bucket name must be globally unique and:
- Must be 3 to 63 characters long and start with a digit or letter. Only lowercase letters, digits, hyphens (-), and periods (.) are allowed.
- Cannot be formatted as an IP address.
- Cannot start or end with a hyphen (-) or period (.).
- Cannot contain two consecutive periods (..), for example, my..bucket.
- Cannot contain a period (.) and a hyphen (-) adjacent to each other, for example, my-.bucket or my.-bucket.
After external buckets are added, you can see them in the bucket list and have ACL access permissions for them.
diff --git a/docs/obs/tool/obs_03_1059.html b/docs/obs/tool/obs_03_1059.html
index c2f3bef6a..d213bad04 100644
--- a/docs/obs/tool/obs_03_1059.html
+++ b/docs/obs/tool/obs_03_1059.html
@@ -2,7 +2,7 @@
Object Operations
Objects are basic data units that you operate in OBS. This chapter describes how to manage objects.
- Right-click in the blank area of the object list and choose Create Folder or Upload from the shortcut menu to manage the object.
+ Right-click in the blank area of the object list and choose Create Folder or Upload from the shortcut menu to manage objects.
Create a folder on OBS Browser+.
ContextUnlike a file system, OBS does not involve the concepts of file and folder. For easy data management, OBS allows you to simulate a folder by adding a slash (/) to the name of an object.
- Procedure- Log in to OBS Browser+.
- Click the bucket where you want to create a folder and click Create Folder.
- In the displayed dialog box, enter a folder name and click OK, as shown in Figure 1.
Figure 1 Creating a folder
-
-
-
- - A folder name cannot contain the following special characters: \ : * ? ' < > |
- A folder name cannot start or end with a period (.) or slash (/).
- A folder name cannot exceed 1,023 bytes. The length of a folder name is the sum of the length of its own and the length of its upper-level directories. The total length cannot exceed 1,023 bytes. Directories of different levels are automatically separated by slashes (/). For example, if the upper-level directory of folder01 is folder02, the name length of folder folder01 is the length of folder02/folder01/.
- A single slash (/) separates and creates multiple levels of folders.
+ Procedure- Log in to OBS Browser+.
- Click the bucket where you want to create a folder and click Create Folder.
- In the displayed dialog box, enter a folder name and click OK, as shown in Figure 1.
Figure 1 Creating a folder
+- A folder name cannot contain the following special characters: \ : * ? ' < > |
- A folder name cannot start or end with a period (.) or slash (/).
- A folder name cannot exceed 1,023 bytes. The length of a folder name is the sum of the length of its own name and the length of its upper-level directory names. The total length cannot exceed 1,023 bytes. Directories of different levels are automatically separated by slashes (/). For example, if the upper-level directory of folder01 is folder02, the name length of folder folder01 is the length of folder02/folder01/.
- A single slash (/) separates and creates multiple levels of folders.
- Click OK.
diff --git a/docs/obs/tool/obs_03_1061.html b/docs/obs/tool/obs_03_1061.html
index 6752de9ed..39eb0dabb 100644
--- a/docs/obs/tool/obs_03_1061.html
+++ b/docs/obs/tool/obs_03_1061.html
@@ -3,13 +3,9 @@
Uploading a File or Folder
Upload local files or folders to OBS. If you do not specify a storage class during file or folder upload, any file or folder you upload will inherit the storage class of the bucket by default.
ContextFiles are uploaded using multipart upload on OBS Browser+. With multipart upload, you can upload a single file with the maximum size of 48.8 TB.
- A file or folder name cannot exceed 1,023 bytes. The length of a file name is the sum of the length of its own and the length of its upper-level directories. The total length cannot exceed 1,023 bytes. Directories of different levels are automatically separated by slashes (/). For example, if the upper-level folder of file file01 is folder01, the name length of file file01 is the length of folder01/file01.
+ A file or folder name cannot exceed 1,023 bytes. The length of a file name is the sum of the length of its own name and the length of its upper-level directory names. The total length cannot exceed 1,023 bytes. Directories of different levels are automatically separated by slashes (/). For example, if the upper-level folder of file file01 is folder01, the name length of file file01 is the length of folder01/file01.
- Procedure- Log in to OBS Browser+.
- Click the bucket where you want to upload files or folders.
- Click Upload and then Add File or Folder, as shown in Figure 1.
Figure 1 Uploading a file or folder
-
-
-
-
+Procedure- Log in to OBS Browser+.
- Click the bucket where you want to upload files or folders.
- Click Upload and then Add File or Folder, as shown in Figure 1.
Figure 1 Uploading a file or folder
For better experience when using the Add File function, you are advised to upload a maximum of 100 files at a time. If you need to upload more, place all the files in a folder and upload them by adding a folder.
 You must have access to the file you want to upload, or the file upload will fail.
Searching for a File or Folder
Search for a file or folder by name prefix on OBS Browser+.
- Procedure- Log in to OBS Browser+.
- Click the bucket that stores the target file or folder.
- In the upper right corner of the page, enter the name prefix of the file or folder you want in the search box.
- Click
 , as shown in Figure 1.Figure 1 Searching for a file or folder
-
-
-
-
-Matching files or folders are displayed in the list. If you want to search for other files or folders, click  in the search box to delete the keyword you have entered and enter a new one.
-For example, if you want to search for files or folders whose name prefix is testobject in bucket mybucket, go to the object management page of bucket mybucket, enter testobject in the search box in the upper right corner, and click  . Files or folders with testobject as the name prefix are displayed in the list.
+Procedure- Log in to OBS Browser+.
- Click the bucket that stores the target file or folder.
- In the upper right corner of the page, enter the name prefix of the file or folder you want in the search box.
- Click , as shown in Figure 1.
Figure 1 Searching for a file or folder
+Matching files or folders are displayed in the list. If you want to search for other files or folders, click in the search box to delete the keyword you have entered and enter a new one.
+For example, if you want to search for files or folders whose name prefix is testobject in bucket mybucket, go to the object management page of bucket mybucket, enter testobject in the search box in the upper right corner, and click . Files or folders with testobject as the name prefix are displayed in the list.
diff --git a/docs/obs/tool/obs_03_1063.html b/docs/obs/tool/obs_03_1063.html
index f27d0982c..f470cdfd5 100644
--- a/docs/obs/tool/obs_03_1063.html
+++ b/docs/obs/tool/obs_03_1063.html
@@ -2,10 +2,10 @@
Downloading a File or Folder
Download a file or folder from OBS to your local computer.
- Procedure- Log in to OBS Browser+.
- Go to the target bucket, select the file or folder you want to download, and click Download.
You can hold down Ctrl or Shift to select multiple files or folders and batch download them. You can also press Ctrl+A to select all the files or folders. The operations are consistent with those in Windows operating systems.
- To download Cold files, you must restore them first. For more information, see Restoring a File.
+ Procedure- Log in to OBS Browser+.
- Go to the target bucket, select the file or folder you want to download, and click Download.
You can select multiple files or folders and batch download them.
+ - To download Cold files, you must restore them first. For details, see Restoring a File or Folder.
- Only files or folders that have been listed can be downloaded in batches. You can drag the scroll bar to the bottom to update the number of listed files or folders. 100 files or folders can be updated at a time.
- - In the displayed dialog box, select a path for saving the file or folder and click OK.
+ - In the displayed dialog box, select a path for saving the file or folder and click Select Folder.
diff --git a/docs/obs/tool/obs_03_1064.html b/docs/obs/tool/obs_03_1064.html
index eeb2ba216..25fb25c01 100644
--- a/docs/obs/tool/obs_03_1064.html
+++ b/docs/obs/tool/obs_03_1064.html
@@ -2,9 +2,9 @@
Copying a File or Folder
Copy a file or folder stored in OBS from one path to another path.
- Procedure- Log in to OBS Browser+.
- Go to the target bucket. Right-click the file or folder and choose Copy from the shortcut menu.
- Right-click the path for saving the file or folder and choose Paste from the shortcut menu.
- Files or folders in external buckets cannot be copied.
- The restore status of Archive objects cannot be copied.
- The source path and target path must be different.
-
-
+ Constraints- Files or folders in external buckets cannot be copied.
- The restore status of Archive objects cannot be copied.
- The source path and target path must be different.
+
+ Procedure- Log in to OBS Browser+.
- Go to the target bucket. Right-click the file or folder and choose Copy from the shortcut menu.
- Right-click the path for saving the file or folder and choose Paste from the shortcut menu.
diff --git a/docs/obs/tool/obs_03_1066.html b/docs/obs/tool/obs_03_1066.html
index c583ef13c..4b0a3bb8a 100644
--- a/docs/obs/tool/obs_03_1066.html
+++ b/docs/obs/tool/obs_03_1066.html
@@ -4,12 +4,13 @@
Delete an existing file or folder as needed.
ContextDeleting a folder will also delete all files in it. Ensure that all files in a folder can be deleted before deleting the folder.
Deleting unwanted files or folders saves space and costs.
- You can use lifecycle management to periodically delete some unwanted files or batch delete all files or folders in OBS.
+ You can use lifecycle management to periodically delete some unwanted files or batch delete all files or folders in OBS buckets.
- Procedure- Log in to OBS Browser+.
- Go to the target bucket. Select the file or folder you want to delete and click Delete.
You can hold down Ctrl or Shift to select multiple files or folders and batch delete them. You can also press Ctrl+A to select all the files or folders. The operations are consistent with those in Windows operating systems.
- - In the displayed dialog box, click OK.
+ Procedure- Log in to OBS Browser+.
- Go to the target bucket. Select the file or folder you want to delete and click Delete.
- In the displayed dialog box, click Yes.
- Important NotesIn big data scenarios, parallel file systems usually have deep directory levels and each directory has a large number of files. In such case, deleting directories from parallel file systems may fail due to timeout. To address this problem, you are advised to delete directories in either of the following ways:
+ Important NotesIn big data scenarios, parallel file systems usually have deep directory levels and each directory has a large number of files. In such case, deleting directories from parallel file systems may fail due to timeout.
+
+ To address this problem, you are advised to delete directories in either of the following ways:
- On the Hadoop client that has OBSA, an OBS client plugin, embedded, run the hadoop fs - rmr obs://{Name of a parallel file system}/{Directory name} command.
- Configure a lifecycle rule for directories so that they can be deleted in background based on the preset lifecycle rule.
diff --git a/docs/obs/tool/obs_03_1068.html b/docs/obs/tool/obs_03_1068.html
index d3f8186e6..7b242f357 100644
--- a/docs/obs/tool/obs_03_1068.html
+++ b/docs/obs/tool/obs_03_1068.html
@@ -1,46 +1,46 @@
- Restoring a File
+ Restoring a File or Folder
Restore Cold objects before downloading them.
ContextCold 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.
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 you want to restore and choose More > Restore Object.
-
+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.
-Table 1 Restoring an objectParameter
+Table 1 Restoring an objectParameter
|
-Description
+ | Description
|
|---|
-Object Name
+ | Object Name
|
-Name of the object 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.
|
- Click OK to confirm the restored file.
To view the file restore status, 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.
+ - 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.
- If a restored object is restored again, its expiration time should be later than the time set for the previous restore. 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.
+ 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.
diff --git a/docs/obs/tool/obs_03_1070.html b/docs/obs/tool/obs_03_1070.html
index 157214bad..0e380cde3 100644
--- a/docs/obs/tool/obs_03_1070.html
+++ b/docs/obs/tool/obs_03_1070.html
@@ -3,10 +3,7 @@
Managing Running and Queued Tasks
PrerequisitesThere are running tasks in the list.
- Procedure- Log in to OBS Browser+.
- In the navigation pane, choose Task Management.
- The Queuing tab is displayed by default, as shown in Figure 1.
Figure 1 Running and queued task list
-
-
-
+
diff --git a/docs/obs/tool/obs_03_1071.html b/docs/obs/tool/obs_03_1071.html
index 8efc1bdd4..362f4c39c 100644
--- a/docs/obs/tool/obs_03_1071.html
+++ b/docs/obs/tool/obs_03_1071.html
@@ -3,14 +3,9 @@
Managing Suspended Tasks
PrerequisitesThere are suspended tasks in the list.
- Procedure- Log in to OBS Browser+.
- In the navigation pane, choose Task Management.
- Choose the Suspended tab, as shown in Figure 1.
Figure 1 Suspended task List
-
-
-
-
+
-
diff --git a/docs/obs/tool/obs_03_1072.html b/docs/obs/tool/obs_03_1072.html
index 5949579aa..2c0d3d73d 100644
--- a/docs/obs/tool/obs_03_1072.html
+++ b/docs/obs/tool/obs_03_1072.html
@@ -3,11 +3,7 @@
Managing Completed Tasks
PrerequisitesThere are completed tasks in the list.
- Procedure- Log in to OBS Browser+.
- In the navigation pane, choose Task Management.
- Choose the Completed tab, as shown in Figure 1.
Figure 1 Completed task list
-
-
-
-
+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_1073.html b/docs/obs/tool/obs_03_1073.html
index 15a9d66cc..5eaefb88f 100644
--- a/docs/obs/tool/obs_03_1073.html
+++ b/docs/obs/tool/obs_03_1073.html
@@ -3,11 +3,7 @@
Managing Tasks Being Restored
PrerequisitesThere are tasks being restored in the list.
- Procedure- Log in to OBS Browser+.
- In the navigation pane, choose Task Management.
- Choose the Restoring tab, as shown in Figure 1.
Figure 1 List of tasks being restored
-
-
-
-
+Procedure- Log in to OBS Browser+.
- In the navigation pane, choose Task Management.
- Choose the Restoring tab.
Figure 1 List of tasks being restored
- (Optional) Select one or more tasks and click Delete (
 ).
- If a Cold object is being restored, you cannot suspend or delete the restore task.
- Objects in the Restoring state cannot be restored again.
- The Delete function can delete only local task data.
diff --git a/docs/obs/tool/obs_03_1074.html b/docs/obs/tool/obs_03_1074.html
index e52efc7ff..d6d649a2c 100644
--- a/docs/obs/tool/obs_03_1074.html
+++ b/docs/obs/tool/obs_03_1074.html
@@ -3,11 +3,7 @@
Managing Failed Tasks
PrerequisitesThere are failed tasks in the list.
- Procedure- Log in to OBS Browser+.
- In the navigation pane, choose Task Management.
- Choose the Failed tab, as shown in Figure 1.
Figure 1 Failed task list
-
-
-
-
+
- A failed task will be automatically retried three times.
diff --git a/docs/obs/tool/obs_03_1077.html b/docs/obs/tool/obs_03_1077.html
index 0359c48cb..b47a4fa80 100644
--- a/docs/obs/tool/obs_03_1077.html
+++ b/docs/obs/tool/obs_03_1077.html
@@ -1,7 +1,11 @@
Background Running
- If there are lots of tasks running on OBS Browser+, but you want to perform other operations outside OBS Browser+, you can close OBS Browser+ while tasks are still running in the background. Specifically, 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. You can also double-click the OBS Browser+ icon in the task bar to display its interface again.
+ 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?
+ 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.
diff --git a/docs/obs/tool/obs_03_1079.html b/docs/obs/tool/obs_03_1079.html
index f8ac7882a..cbf6659e9 100644
--- a/docs/obs/tool/obs_03_1079.html
+++ b/docs/obs/tool/obs_03_1079.html
@@ -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 x 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.
+ - 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.
diff --git a/docs/obs/tool/obs_03_1082.html b/docs/obs/tool/obs_03_1082.html
index acd0b6777..3b1655dc9 100644
--- a/docs/obs/tool/obs_03_1082.html
+++ b/docs/obs/tool/obs_03_1082.html
@@ -1,7 +1,7 @@
Can OBS Browser+ List Objects with Special Characters in Their Names?
- No. You can use OBS SDKs to list such objects.
+ No. You can use OBS SDKs to list such objects.
|
|---|
|
|---|
|
|---|
|
