# US 2017/0257420 A1 · Saas network-based backup system

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

- Number: US 2017/0257420 A1
- Document ID: US20170257420A1
- Status: Published application
- Kind: A1
- Application number: 15/391,646
- Filed: 2016-12-27
- Published: 2017-09-07
- Earliest claimed: 2013-02-11
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Ketan Bengali; Kaniska Mandal; Alex J. Chen
- Web page: https://patentgrep.com/patent/US20170257420A1

## CPC

- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- G06F 11/1448: {Management of the data involved in backup or backup restore}
- H04L 67/5682: Policies or rules for updating, deleting or replacing the stored data
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system fetches consistent datasets in batches for a given period of time and provides the ability to retrieve each batch. Batches of data may be fetched for an interval of time. The present system may fetch new or changed data from different cloud/on-premise applications. It will store this data in the cloud or on-premise to build data history. As the system fetches new data, existing batches of data will not be overwritten. New batches of data are created as new versions so that change history is preserved. Past batches of data for a past time period may be provided to one or more tenants.

## Claims

### Claim 1

(canceled)

### Claim 2

A method for managing data, the method comprising:
collecting a plurality of data batches from at least one tenant device over a network interface at different time intervals, each collected data batch associated with the tenant application at a respective time interval;
storing each of the collected data batches in a data store in memory in association with the respective time interval, wherein previous data batches from the tenant device are not overwritten by current data batches from the tenant device;
receiving a request from a computing device regarding the tenant device during a specified time period that includes one or more of the different time intervals;
retrieving one or more of the stored data batches associated with the tenant device, wherein each retrieved data batches is associated with a respective time interval that is within the specified time period; and
sending the retrieved data batches to the computing device in response to receiving the request.

### Claim 3 (depends on 2)

The method of claim 2, wherein the data store comprises a database that is remote from the tenant device.

### Claim 4 (depends on 2)

The method of claim 2, wherein the request further specifies a portion of the data batch, and wherein sending the retrieved data batches comprises sending only the specified portion of the retrieved data batches to the computing device.

### Claim 5 (depends on 4)

The method of claim 4, wherein the specified portion refers to data identified as new or changed during the specified time period.

### Claim 6 (depends on 2)

The method of claim 2, wherein collecting the plurality of data batches comprises identifying that a failure has occurred for one of the data batches.

### Claim 7 (depends on 6)

The method of claim 6, wherein identifying that the failure has occurred is based on identifying that a portion of the failed batch is not loaded into the data store.

### Claim 8 (depends on 7)

The method of claim 7, further comprising removing the failed batch and collecting a new data batch for a same time interval as the failed data batch.

### Claim 9 (depends on 2)

The method of claim 2, wherein the stored plurality of batches are associated with a batch log that tracks characteristics of each stored batch.

### Claim 10 (depends on 2)

The method of claim 2, wherein a next data batch is not collected from the tenant device until a change to a current data batch is detected.

### Claim 11

A system for managing data, the system comprising:
a data collection server that collects a plurality of data batches from at least one tenant device over a network interface at different time intervals, each collected data batch associated with the tenant application at a respective time interval;
data store memory that stores each of the collected data batches in association with the respective time interval, wherein previous data batches from the tenant device are not overwritten by current data batches from the tenant device; and
an integration server that:
receives a request from a computing device regarding the tenant device during a specified time period that includes one or more of the different time intervals;
retrieves one or more of the stored data batches associated with the tenant device via the data collection server, wherein each retrieved data batches is associated with a respective time interval that is within the specified time period; and
sends the retrieved data batches to the computing device in response to receiving the request.

### Claim 12 (depends on 11)

The system of claim 11, wherein the data store memory is remote from the tenant device.

### Claim 13 (depends on 11)

The method of claim 11, wherein the request further specifies a portion of the data batch, and wherein the integration server sends only the specified portion of the retrieved data batches to the computing device.

### Claim 14 (depends on 13)

The system of claim 13, wherein the specified portion refers to data identified as new or changed during the specified time period.

### Claim 15 (depends on 11)

The system of claim 11, wherein the data collection server further identifies that a failure has occurred for one of the data batches.

### Claim 16 (depends on 15)

The system of claim 15, wherein the data collection server identifies that the failure has occurred based on identifying that a portion of the failed batch is not loaded into the data store memory.

### Claim 17 (depends on 16)

The system of claim 16, wherein the data collection server removesthe failed batch and collects a new data batch for a same time interval as the failed data batch.

### Claim 18 (depends on 11)

The system of claim 11, wherein the stored plurality of batches are associated with a batch log that tracks characteristics of each stored batch.

### Claim 19 (depends on 11)

The system of claim 11, wherein the data collection server does not collect a next data batch from the tenant device until a change to a current data batch is detected.

### Claim 20

A non-transitory computer readable storage medium having embodied thereon a program for performing a method for managing data, the method comprising:
collecting a plurality of data batches from at least one tenant device over a network interface at different time intervals, each collected data batch associated with the tenant application at a respective time interval;
storing each of the collected data batches in a data store in memory in association with the respective time interval, wherein previous data batches from the tenant device are not overwritten by current data batches from the tenant device;
receiving a request from a computing device regarding the tenant device during a specified time period that includes one or more of the different time intervals;
retrieving one or more of the stored data batches associated with the tenant device, wherein each retrieved data batches is associated with a respective time interval that is within the specified time period; and
sending the retrieved data batches to the requesting computing device in response to receiving the request.
