# US 2020/0401312 A1 · Object Storage System with Meta Object Replication

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0401312 A1
- Document ID: US20200401312A1
- Status: Published application
- Kind: A1
- Application number: 16/447,291
- Filed: 2019-06-20
- Published: 2020-12-24
- Earliest claimed: 2019-06-20
- Assignees: Western Digital Technologies, Inc.
- Applicants: Western Digital Technologies, Inc.
- Inventors: Ameet Pyati; Vibhor Patale
- Web page: https://patentgrep.com/patent/US20200401312A1

## CPC

- G06F 3/065: {Replication mechanisms}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors}
- G06F 3/0629: {Configuration or reconfiguration of storage systems}
- G06F 3/0644: {Management of space entities, e.g. partitions, extents, pools}
- G06F 3/0683: {Plurality of storage devices}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Example object storage systems, meta object generators, and methods provide meta objects for replication of configuration data between data object stores. A meta object may be generated that includes configuration data. A meta object identifier may be assigned to the meta object. The meta object may be stored in a first object store with related data objects and may be replicated to a second object data store with the related data objects.

## Claims

### Claim 1

A system, comprising:
a first object data store;
a second object data store;
a metadata store associated with the first object data store and configured to store configuration data for the first object data store, wherein the configuration data includes configuration parameters for rebuilding the configuration data; and
a meta object generator configured to:
generate a meta object, wherein:
the meta object is a data object containing object data; and
the object data includes meta object data selected from the configuration parameters;
assign a meta object identifier to the meta object; and
store the meta object with related data objects in the first object data store, wherein a plurality of data objects replicated to the second object data store include the meta object and the related data objects.

### Claim 2 (depends on 1)

The system of claim 1, wherein:
the first object data store is configured to store the plurality of data objects in a data object bucket;
the meta object data includes bucket configuration data; and
the related data objects include data objects stored in the data object bucket.

### Claim 3 (depends on 1)

The system of claim 1, wherein the meta object identifier includes:
a globally unique identifier for the meta object; and
a meta tag appended to a key value associated with the globally unique identifier.

### Claim 4 (depends on 1)

The system of claim 1, wherein:
the meta object generator is further configured to generate a hidden header value;
the meta object identifier includes the hidden header value; and
the first object data store is further configured to require the hidden header value to access the meta object.

### Claim 5 (depends on 1)

The system of claim 1, wherein the meta object generator is further configured to encrypt the meta object data in the meta object.

### Claim 6 (depends on 1)

The system of claim 1, further comprising:
a replication engine configured to replicate the plurality of data objects from the first object data store to the second object data store.

### Claim 7 (depends on 1)

The system of claim 1, further comprising:
a meta object update handler configured to:
detect changed configuration data in the configuration data; and
initiate the meta object generator to generate an updated meta object including the changed configuration data.

### Claim 8 (depends on 7)

The system of claim 7, wherein the meta object update handler is further configured to periodically initiate the meta object generator at predetermined intervals.

### Claim 9 (depends on 1)

The system of claim 1, further comprising:
a disaster recovery manager configured to:
recover the plurality of data objects from the second object data store to a recovery object data store; and
rebuild, based on the configuration parameters in the meta object, configuration data in a recovery metadata store.

### Claim 10

A computer-implemented method, comprising:
generating a meta object, wherein:
the meta object is a data object containing object data;
the object data includes meta object data selected from configuration data;
the configuration data configures a first object data store; and
the configuration data includes configuration parameters for rebuilding the configuration data;
assigning a meta object identifier to the meta object;
storing the meta object with related data objects in the first object data store; and
replicating a plurality of data objects to a second object data store, wherein the plurality of data objects includes the meta object and the related data objects.

### Claim 11 (depends on 10)

The computer-implemented method of claim 10, further comprising:
configuring the first object data store to store the plurality of data objects in a data object bucket, wherein:
the meta object data is bucket configuration data; and
the related data objects are data objects stored in the data object bucket.

### Claim 12 (depends on 10)

The computer-implemented method of claim 10, wherein the meta object identifier includes:
a globally unique identifier for the meta object; and
a meta tag appended to a key value associated with the globally unique identifier.

### Claim 13 (depends on 10)

The computer-implemented method of claim 10, further comprising:
generating a hidden header value, wherein the meta object identifier includes the hidden header value; and
accessing, using the hidden header value, the meta object, wherein the first object data store is configured to require the hidden header value to access the meta object.

### Claim 14 (depends on 10)

The computer-implemented method of claim 10, further comprising:
encrypting the meta object data in the meta object.

### Claim 15 (depends on 10)

The computer-implemented method of claim 10, further comprising:
selecting the configuration data for the meta object data from a metadata store associated with the first object data store.

### Claim 16 (depends on 10)

The computer-implemented method of claim 10, further comprising:
detecting changed configuration data in the configuration data; and
generating an updated meta object including the changed configuration data.

### Claim 17 (depends on 10)

The computer-implemented method of claim 10, further comprising:
selecting a predetermined interval for meta object updates; and
periodically generating, at the predetermined interval, updated meta objects including changed configuration data.

### Claim 18 (depends on 10)

The computer-implemented method of claim 10, further comprising:
recovering the plurality of data objects from the second object data store to a recovery object data store; and
rebuilding, based on the configuration data in the meta object, configuration data in a recovery metadata store.

### Claim 19

A system, comprising:
a first object data store;
a metadata store associated with the first object data store and configured to store configuration data for the first object data store, wherein the configuration data includes configuration parameters for rebuilding the configuration data;
means for generating a meta object, wherein:
the meta object is a data object containing object data; and
the object data includes meta object data selected from the configuration parameters;
means for assigning a meta object identifier to the meta object;
means for storing the meta object with related data objects in the first object data store; and
means for replicating a plurality of data objects to a second object data store, wherein the plurality of data objects replicated to the second object data store include the meta object and the related data objects.

### Claim 20 (depends on 19)

The system of claim 19, further comprising:
means for configuring the first object data store to store the plurality of data objects in a data object bucket, wherein:
the meta object data is bucket configuration data; and
the related data objects are data objects stored in the data object bucket.