Changing the Storage Classes of Buckets and Objects

1. Log in to OBS Console. In the navigation pane, choose Object Storage.
2. In the bucket list, locate the bucket whose storage class you want to change and click Change Storage Class in the Operation column on the right.
3. Choose a new storage class and click OK.
   Figure 1 Manually changing the storage class of a bucket
   

Configuring Storage Class for a Bucket

Command Line Structure

• In Windows

  obsutil stat obs://bucket [-acl] [-bf=xxx] [-config=xxx] [-e=xxx] [-i=xxx] [-k=xxx] [-t=xxx]

• In Linux or macOS

  ./obsutil stat obs://bucket [-acl] [-bf=xxx] [-config=xxx] [-e=xxx] [-i=xxx] [-k=xxx] [-t=xxx]

Examples

• Take the Windows OS as an example. Run the obsutil chattri obs://bucket-test -acl=private command to change the access control policy of the bucket to private read and write.

  obsutil chattri obs://bucket-test -acl=private
  
  Set the acl of bucket [bucket-test] to [private] successfully, request id [04050000016836C5DA6FB21F14A2A0C0]

Parameter Description

1. Log in to OBS Console. In the navigation pane, choose Object Storage.
2. In the bucket list, click the bucket name you want. The Objects page is displayed.
3. Restore objects that are in the Archive or Deep Archive storage class if there are any. For details, see Restoring an Object from Archive or Deep Archive Storage.
4. Change the storage class of objects individually or in a batch.
   1. Individually: In the object list, locate the desired object and choose More > Change Storage Class in the Operation column on the right.
      Figure 2 Changing object storage classes individually
      
   2. In a batch: In the object list, select the desired objects and choose More > Change Storage Class above the object list.
      

      Changing object storage classes in a batch is currently only available in some regions. If you cannot find the button for the batch operation, check whether this operation is supported in your region.

      Figure 3 Changing object storage classes in a batch
      

5. Choose a new storage class and click OK.
   Figure 4 Choosing a new storage class
   

OBS provides two APIs for you to manually change the storage class of objects. You can call an API to:

If you want to change the storage class of Archive or Deep Archive objects, make sure you have restored them before you change their storage classes.

• Modify object metadata (adding the x-obs-storage-class header).
• Copy an object (adding the x-obs-storage-class header). If a bucket has versioning enabled, OBS automatically generates a unique version ID for a new object copy. If a bucket has versioning disabled or suspended, the existing object will be overwritten by a new object copy.

1. Log in to OBS Browser+.
2. Click the name of the bucket that contains the object you want to modify the storage class for. The Objects page is displayed.
3. If the storage class of the object to be modified is Archive or Deep Archive, right-click the object and choose Restore from the shortcut menu. After the restoration is complete, go to 4.
4. Right-click the object to be modified and choose Change Storage Class from the shortcut menu.
5. Select the desired storage class and click OK.

obsutil allows you to change the storage class of an object by modifying its properties.

If you want to change the storage class of objects that are in the Archive or Deep Archive storage, make sure you have restored them before you change their storage classes. For commands for restoring objects, see Restoring Objects.

• In Windows
  • Setting properties of a single object

    obsutil chattri obs://bucket/key [-meta=aaa:bbb#ccc:ddd] [-sc=xxx] [-acl=xxx] [-aclXml=xxx] [-versionId=xxx] [-fr] [-o=xxx] [-config=xxx] [-e=xxx] [-i=xxx] [-k=xxx] [-t=xxx]

  • Setting properties of objects in batches

    obsutil chattri obs://bucket[/key] -r [-f] [-v] [-meta=aaa:bbb#ccc:ddd] [-sc=xxx] [-acl=xxx] [-aclXml=xxx] [-o=xxx] [-j=1] [-config=xxx] [-e=xxx] [-i=xxx] [-k=xxx] [-t=xxx]

• In Linux or macOS
  • Setting properties of a single object

    ./obsutil chattri obs://bucket/key [-meta=aaa:bbb#ccc:ddd] [-sc=xxx] [-acl=xxx] [-aclXml=xxx] [-versionId=xxx] [-fr] [-o=xxx] [-config=xxx] [-e=xxx] [-i=xxx] [-k=xxx] [-t=xxx]

  • Setting properties of objects in batches

    ./obsutil chattri obs://bucket[/key] -r [-f] [-v] [-meta=aaa:bbb#ccc:ddd] [-sc=xxx] [-acl=xxx] [-aclXml=xxx] [-o=xxx] [-j=1] [-config=xxx] [-e=xxx] [-i=xxx] [-k=xxx] [-t=xxx]

Examples

• Take the Windows OS as an example, run the obsutil chattri obs://bucket-test/key -acl=public-read command to set the access permission to an object to public read.

  obsutil chattri obs://bucket-test/key -acl=public-read
  
  Set the acl of object [key] in the bucket [bucket-test] to [public-read] successfully, request id [04050000016836DDFA73B2B5320E2651]

• Take the Windows OS as an example, run the obsutil chattri obs://bucket-test -r -f -acl=public-read command to set the access permission to all objects in the bucket to public read.

  obsutil chattri obs://bucket-test -r -f -acl=public-read
  
  [------------------------------------------------] 100.00% tps:155.15 5/5 233ms
  Succeed count is:   5         Failed count is:    0
  Metrics [max cost:177 ms, min cost:53 ms, average cost:102.40 ms, average tps:20.41]
  Task id is: 9d7f73ff-f747-4fdd-9b2a-815ba2dc3b07

Parameter Description

<AccessControlPolicy>
    <Owner>
        <ID>ownerid</ID>
    </Owner>
    <AccessControlList>
        <Grant>
            <Grantee>
                <ID>userid</ID>
            </Grantee>
            <Permission>[WRITE|WRITE_ACP|READ|READ_ACP|FULL_CONTROL]</Permission>
        </Grant>
        <Grant>
            <Grantee>
                <Canned>Everyone</Canned>
            </Grantee>
            <Permission>[WRITE|WRITE_ACP|READ|READ_ACP|FULL_CONTROL]</Permission>
        </Grant>
    </AccessControlList>
</AccessControlPolicy>

1. In the navigation pane of OBS Console, choose Object Storage.
2. In the bucket list, click the bucket you want to operate. The Objects page is displayed.
3. In the navigation pane, choose Overview.
4. In the Basic Configurations area, click Lifecycle Rules. The Lifecycle Rules page is displayed.

   Alternatively, you can choose Basic Configurations > Lifecycle Rules in the navigation pane.

5. Click Create. A dialog box as shown in Figure 6 is displayed.
   Figure 6 Creating a lifecycle rule
   

6. Configure a lifecycle rule.
   Basic Information:

   • Status: Select Enable to enable this lifecycle rule after the configuration.
   • Rule Name: It identifies a lifecycle rule. The rule name must be no longer than 255 characters.
   • Prefix: It is optional.
     • If this field is configured, objects with the specified prefix will be managed by the lifecycle rule. The prefix cannot start with a slash (/) or contain two consecutive slashes (//), and cannot contain the following special characters: \:*?"<>|
     • If this field is not configured, all objects in the bucket will be managed by the lifecycle rule.

   

   • 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 already a rule with prefix abc in OBS, you cannot configure another rule whose prefix starts with abc.
   • If there is already a lifecycle rule based on an object prefix, you are not allowed to configure another rule that is applied to the entire bucket.

   Current Version or Historical Version:

   

   • Current Version and Historical Version are two concepts related to Versioning. If versioning is enabled for a bucket, uploading objects with the same name to the bucket creates different object versions. An object uploaded most recently is called Current Version, while an object uploaded previously is called Historical Version. For details, see Versioning.
   • Either the Current Version or Historical Version must be configured, or you can configure both of them.
   • Transition to Infrequent Access After (Days): After a specified number of days have passed since the last update, objects meeting specified conditions will be transitioned to Infrequent Access. This number must be at least 30.
   • Transition to Archive After (Days): After a specified number of days have passed since the last update, objects meeting specified conditions will be transitioned to Archive. If you configure objects to transition first to Infrequent Access and then to Archive, make sure the objects stay in Infrequent Access at least 30 days before they are transitioned to Archive. There are, however, no such constraints on time if you configure objects to transition to only Archive.
   • Transition to Deep Archive After (Days): After a specified number of days have passed since the last update, objects meeting specified conditions will be transitioned to Deep Archive. If you configure objects to transition first to Infrequent Access and then to Deep Archive, make sure the objects stay in Infrequent Access at least 30 days before they are transitioned to Deep Archive. If you configure objects to transition first to Archive and then to Deep Archive, make sure the objects stay in Archive at least 90 days before they are transitioned to Deep Archive. There are, however, no such constraints on time if you configure objects to transition to only Deep Archive.
   • Expiration Time: After a specified number of days have passed since the last update, objects meeting specified rules will be automatically expired and deleted. This number must be an integer larger than that specified for any of the transition operations.
   • Delete Fragments After (Days): After a specified number of days have passed since the fragment generation, OBS will automatically delete fragments in the bucket.
   Assume you stored the following files in OBS on January 7, 2015:

   • log/test1.log
   • log/test2.log
   • doc/example.doc
   • doc/good.txt
   Then, you stored the following files in OBS on January 10, 2015:

   • log/clientlog.log
   • log/serverlog.log
   • doc/work.doc
   • doc/travel.txt

   If you created a rule to delete the objects prefixed with log one day after the last update on January 10, 2015, the following situations may occur:

   • Objects log/test1.log and log/test2.log uploaded on January 7, 2015 might be deleted upon the next system scan. The deletion could happen on January 10, 2015 or January 11, 2015, depending on the time of the system scan.
   • For objects log/clientlog.log and log/serverlog.log uploaded on January 10, 2015, each system scan would determine whether one full day had passed since their last update. If any scan determined one full day had passed, those objects would be deleted upon that scan. The deletion might happen on January 11, 2015 or January 12, 2015.

   Suppose you configured the objects with the log prefix to be transitioned to Infrequent Access 30 days and to Archive 60 days and to be deleted 100 days after their last update. OBS would perform those actions on log/clientlog.log, log/serverlog.log, log/test1.log, and log/test2.log as you defined.

   

   After an object is uploaded, OBS calculates its lifecycle from 00:00 UTC the next day. It takes 24 hours at most to execute a lifecycle rule. As a result, there may be a delay in transitioning objects between storage classes and deleting expired objects. Generally, the delay does not exceed 48 hours. If you make changes to an existing lifecycle rule, when the changed rule takes effect will be recalculated.

7. Click OK to complete the lifecycle rule configuration.

Configuring Bucket Lifecycle Rules

1. Log in to OBS Browser+.
2. Select the bucket you want to configure a lifecycle rule and choose More > Lifecycle Rules.
   Figure 7 Lifecycle Rules
   

3. Click Create. The window shown in Figure 8 is displayed.
   Figure 8 Creating a lifecycle rule
   

4. 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 based on an object prefix, you are not allowed to configure another rule that is applied to the entire 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 the last update objects that meet specified criteria are automatically transitioned to the Infrequent Access or Archive storage class, or are automatically deleted.
     • Transition to Infrequent Access: This rule transitions the objects meeting the conditions to the Infrequent Access storage class the specified number of days after the last update.
     • Transition to Archive: This rule transitions the objects meeting the conditions to the Archive storage class the specified number of days after the last 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.

   Assume you stored the following files in OBS on January 7, 2022:

   • log/test1.log
   • log/test2.log
   • doc/example.doc
   • doc/good.txt

   On January 10, 2022, you stored the following files in OBS:

   • log/clientlog.log
   • log/serverlog.log
   • doc/work.doc
   • doc/travel.txt

     Suppose you configured a rule on January 10, 2022 to expire and delete objects with the log/ prefix one day after their upload, objects log/test1.log, log/test2.log, log/clientlog.log, and log/serverlog.log would deleted on January 12, 2022.

     If you configure lifecycle rules that transition objects with the log prefix to Infrequent Access 30 days and to Archive 60 days after the upload and delete them 100 days after the upload. OBS performs those actions on log/clientlog.log, log/serverlog.log, log/test1.log, and log/test2.log one day after the defined transition periods end.

5. Click OK to save the lifecycle rule.