Nearline Storage

Nearline Storage enables you to store data that is long-lived but infrequently accessed. Nearline data has the same durability and comparable availability as Standard storage but with lower storage costs. You can read more about it in the Nearline Storage White Paper.

Nearline Storage is appropriate for storing data in scenarios where slightly lower availability and slightly higher latency (typically just a few seconds) is an acceptable trade-off for lowered storage costs. For example:

• Cold Data Storage - Infrequently accessed data, for example, data stored for legal or regulatory reasons, that should be stored at low cost but be available when needed.

• Disaster recovery - In the event of a Disaster Recovery (DR) event, recovery time is key. Google Cloud Storage provides low latency access to data stored in the Nearline Storage class.

You enable Nearline at the bucket level, during bucket creation. Once a Nearline bucket is created, all bucket and object operations are exactly the same as with the standard storage class. New objects in the bucket are transparently stored with the Nearline configuration, and your billing for these objects will automatically reflect the lowered prices.

To change a bucket from Nearline Storage to another class, see Changing storage class. Note that because Nearline Storage is designed for data that is not frequently accessed, there are associated retrieval costs for accessing the data and early deletion. For more information, see pricing.

Creating a Nearline bucket

You enable Nearline Storage at the bucket level.

$ gsutil mb -c NEARLINE gs://<bucket-name>/

curl -X POST --data-binary @nearline.json \
     -H 'Content-Type: application/json' \
     -H "Authorization: Bearer <auth token>" \
     https://www.googleapis.com/storage/v1/b?project=<project-id>

{
 "name": "<bucket-name>",
 "storageClass": "NEARLINE"
}

curl -X PUT --data-binary @nearline.xml \
     -H "Authorization: Bearer <auth token>" \
     -H "x-goog-project-id: <project-id>" \
     https://storage.googleapis.com/<bucket-name>

<CreateBucketConfiguration>
   <LocationConstraint>US</LocationConstraint>
   <StorageClass>NEARLINE</StorageClass>
</CreateBucketConfiguration>

Verifying a Nearline bucket

gsutil ls -L -b gs://<bucket-name>/

gs://<bucketname>/ :
     Storage class:         NEARLINE
     Location constraint:   US
     ...

curl -X GET -H "Authorization: Bearer <auth token>" \
     https://www.googleapis.com/storage/v1/b/<bucket-name>?fields=storageClass

{
 "storageClass": "NEARLINE"
}

curl -X GET -H "Authorization: Bearer <auth token>" \
     -H "x-goog-project-id: <project-id>" \
     https://storage.googleapis.com/<bucket-name>?storageClass

<StorageClass>NEARLINE</StorageClass>

Using a Nearline bucket

You can access data in a Nearline bucket in the same way you access data in a Standard bucket. The same APIs, tools, and UI that are used for Standard Storage are also used for Nearline Storage including the XML API and JSON API, the command-line gsutil tool, the Google Developers Console, and the client libraries.

Because Nearline Storage is designed for data that is not frequently accessed, there are associated retrieval costs for accessing the data and early deletion. For more information, see the pricing page.

特に記載のない限り、このページのコンテンツはクリエイティブ・コモンズの表示 3.0 ライセンスにより使用許諾されます。サンプル コードは Apache 2.0 ライセンス（リンク先は英語）により使用許諾されます。詳しくは、Google のサイトに関するポリシーをご覧ください。