# US 10,769,030 B2 · System and method for improved cache performance > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,769,030 B2 - Document ID: US10769030B2 - Status: Granted - Kind: B2 - Application number: 15/962,421 - Filed: 2018-04-25 - Published: 2019-10-31 - Granted: 2020-09-08 - Earliest claimed: 2018-04-25 - Assignees: EMC IP Holding Company LLC - Applicants: EMC IP Holding Company LLC - Inventors: Shelesh Chopra; Gururaj Kulkarni - Web page: https://patentgrep.com/patent/US10769030B2 ## CPC - G06F 11/1448: {Management of the data involved in backup or backup restore} - G06F 11/1464: {for networked environments} - G06F 3/0605: {by facilitating the interaction with a user or administrator} - G06F 3/0631: {by allocating resources to storage systems} - G06F 3/0653: {Monitoring storage devices or systems} - G06F 3/0683: {Plurality of storage devices} - G06F 11/1451: {by selection of backup contents} - G06F 11/1453: {using de-duplication of the data} - G06F 12/0868: Data transfer between cache memory and other subsystems, e.g. storage devices or host systems - G06N 5/04: Inference or reasoning models - G06F 3/065: {Replication mechanisms} - G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]} - G06F 16/10: File systems; File servers - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS ## Abstract A coordination point for assigning clients to remote backup storages includes a persistent storage and a processor. The persistent storage includes client type to remote backup storage mappings. The processor obtains a data storage request for data from a client of the clients; obtains an inferential characterization of the client; identifies a type of the client using the inferential characterization of the client; selects a remote backup storage of the remote backup storages based on the identified type of the client using the client type to remote backup storage mappings; and assigns the selected remote backup storage to service the data storage request. ## Claims ### Claim 1 A coordination point for assigning clients to remote backup storages, comprising: a persistent storage comprising client type to remote backup storage mappings; and a processor programmed to: obtain a data storage request for data from a client of the clients; obtain, without reading the data, an inferential characterization of the client; identify a type of the client using the inferential characterization of the client, wherein, to identify the type of the client using the inferential characterization of the client, the processor is further programmed to: make a prediction of a content of the data based on the inferential characterization of the client, and match the predicted content of the data to one type of a plurality of types, wherein each type of the plurality of types is associated with a different respective contents; select a remote backup storage of the remote backup storages based on the identified type of the client using the client type to remote backup storage mappings; and assign the selected remote backup storage to service the data storage request. ### Claim 2 (depends on 1) The coordination point of claim 1, wherein obtaining the inferential characterization of the client comprises: identifying a file system of the client. ### Claim 3 (depends on 1) The coordination point of claim 1, wherein obtaining the inferential characterization of the client comprises: identifying a state status of the client. ### Claim 4 (depends on 1) The coordination point of claim 1, wherein obtaining the inferential characterization of the client comprises: identifying a size of a storage capacity of the client. ### Claim 5 (depends on 1) The coordination point of claim 1, wherein obtaining the inferential characterization of the client comprises: identifying an operating system of the client. ### Claim 6 (depends on 1) The coordination point of claim 1, wherein the data is unreadable by the coordination point. ### Claim 7 (depends on 1) The coordination point of claim 1, wherein the remote backup storage is selected while the remote backup storage has a higher workload than a second remote backup storage of the remote backup storages. ### Claim 8 (depends on 1) The coordination point of claim 1, wherein the client type to remote backup storage mappings associate clients of different types with different remote backup storages. ### Claim 9 (depends on 1) The coordination point of claim 1, wherein the type of the client comprises at least one selected from a group consisting of a storage capacity of the client, a file system of the client, an operating system of the client, and a state status of the client. ### Claim 10 (depends on 1) The coordination point of claim 1, wherein assigning the selected remote backup storage to service the data storage request comprises: sending an identifier of a gateway of the selected remote backup storage to the client. ### Claim 11 (depends on 1) The coordination point of claim 1, wherein the processor is further programmed to: obtain a second data storage request for second data from a second client of the clients; obtain a second inferential characterization of the second client; identify a second client type of the second client using the second inferential characterization; select a second remote backup storage of the remote backup storages based on the identified second client type of the second client using the client type to remote backup mappings; and assign the selected second remote backup storage to service the second data storage request. ### Claim 12 (depends on 11) The coordination point of claim 11, wherein the data is of a first database type and the second data is of a second database type. ### Claim 13 (depends on 12) The coordination point of claim 12, wherein the client type and the second client type are different. ### Claim 14 (depends on 11) The coordination point of claim 11, wherein the data is of a first database type and the second data is of the first database type. ### Claim 15 (depends on 14) The coordination point of claim 14, wherein the client type and the second client type are different. ### Claim 16 A method of operating a coordination point for assigning clients to remote backup storages, comprising: obtaining a data storage request for data from a client of the clients; without reading the data: obtaining an inferential characterization of the client; identifying a type of the client using the inferential characterization of the client, wherein, identifying the type of the client using the inferential characterization of the client comprises: making a prediction of a content of the data based on the inferential characterization of the client, and matching the predicted content of the data to one type of a plurality of types, wherein each type of the plurality of types is associated with a different respective contents; selecting a remote backup storage of the remote backup storages based on the identified type of the client using client type to remote backup storage mappings; and assigning the selected remote backup storage to service the data storage request. ### Claim 17 A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method for assigning clients to remote backup storages, the method comprising: obtaining a data storage request for data from a client of the clients; without reading the data: obtaining an inferential characterization of the client; identifying a type of the client using the inferential characterization of the client, wherein, identifying the type of the client using the inferential characterization of the client comprises: making a prediction of a content of the data based on the inferential characterization of the client, and matching the predicted content of the data to one type of a plurality of types, wherein each type of the plurality of types is associated with a different respective contents; selecting a remote backup storage of the remote backup storages based on the identified type of the client using client type to remote backup storage mappings; and assigning the selected remote backup storage to service the data storage request.