DATA LOCATION MANAGEMENT AGENT USING REMOTE STORAGE

• US 20150039659A1
• Filed: 07/30/2013
• Published: 02/05/2015
• Est. Priority Date: 07/30/2013
• Status: Abandoned Application

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Sauber, William F., Farhan, Munif M.
• Application Number:
  US13/954,450
• Publication Number:
  US 20150039659A1
• Time in Patent Office: Days
• US Class Current: 707/827
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185

Abstract

Methods and systems for offloading data to a remote storage resource from a local storage resource on an information handling system may involve using a data location management agent and an offload mapping. The data location management agent may detect requests for access to files stored on a file system and may offload files to the remote storage resource to maintain a specified available capacity of the local storage resource, based on at least in part on the offload mapping. The data location management agent may classify certain files as pinned files that are excluded from offloading.

Claims

1. A method executed by at least one processor comprising:

detecting, by a data location management agent installed on an information handling system, a request to access a first data file intended for a local storage resource included with the information handling system;

when the first data file is currently stored at a remote storage resource accessible to the information handling system;

offloading at least a second data file to the remote storage resource, including deleting the second data file from the local storage resource; and

loading the first data file from the remote storage resource to the local storage resource.

2. The method of claim 1, further comprising:

prior to detecting the request, enabling configuration of the data location management agent, including;

determining a network location of the remote storage resource; and

determining a reserve capacity of the local storage resource.

3. The method of claim 2, wherein offloading at least the second data file is performed when the available capacity of the local storage resource is less than the specified reserve capacity.

4. The method of claim 1, further comprising:

determining whether the first data file is an offloadable file;

when the data file is an offloadable file;

registering the first data file in an offload mapping; and

restricting offloading of data files to the remote storage resource to files registered in the offload mapping.

5. The method of claim 4, wherein the request to access the first data file is handled by a first file system installed on the local storage resource, and wherein determining whether the first data file is an offloadable file further comprises:

determining, based on one or more file attributes of the first data file whether the first data file is a pinned file, wherein a pinned file is not an offloadable file, and wherein the file attributes are selected from;

whether a file is resident in the local storage resource and is not included in the offload mapping;

a file extension;

a file location in the first file system;

whether a file includes executable code;

attributes of secondary files associated with a file; and

a security attribute assigned by an operating system installed on the information handling system.

6. The method of claim 4, wherein registering the first data file in the offload mapping includes:

when the offload mapping includes a record for the first data file, modifying the record, including updating a timestamp attribute for the first data file; and

when the offload mapping does not include a record for the first data file;

creating a new record for the first data file in the offload mapping;

recording metadata in the new record, the metadata including;

a filename associated with the first data file;

a first location of the first data file on the local storage resource; and

a second location of the first data file on the remote storage resource.

7. The method of claim 1, wherein offloading at least the second data file includes offloading a plurality of data files, including the second data file, and wherein the plurality of data files are selected according to a least-recently-used algorithm.

8. An article of manufacture comprising a non-transitory computer-readable medium storing instructions, that, when executed by a processor subsystem, cause the processor subsystem to:

instantiate a data location management agent on an information handling system, the data location management agent enabled to;

detect a request to access a first data file intended for a local storage resource included with the information handling system;

when the first data file is currently stored at a remote storage resource accessible to the information handling system;

offload at least a second data file to the remote storage resource, including deleting the second data file from the local storage resource; and

load the first data file from the remote storage resource to the local storage resource.

9. The article of manufacture of claim 8, wherein, prior to detecting the request, the data location management agent is enabled to:

determine a network location of the remote storage resource; and

determine a reserve capacity of the local storage resource,

10. The article of manufacture of claim 9, wherein the data location management agent is enabled to offload at least the second data file responsive to determining that an available capacity of the local storage resource is less than the reserve capacity.

11. The article of manufacture of claim 8, wherein the data location management agent is enabled to:

determine whether the first data file is an offloadable file;

when the data file is an offloadable file;

register the first data file in an offload mapping; and

restrict offloading of data files to the remote storage resource to files registered in the offload mapping.

12. The article of manufacture of claim 11, wherein the request to access the first data file is handled by a first file system installed on the local storage resource, and wherein the data location management agent enabled to determine whether the first data file is an offloadable file includes the data location management agent enabled to:

determine, based on one or more file attributes of the first data file whether the first data file is a pinned file, wherein a pinned file is not an offloadable file, and wherein the file attributes are selected from;

whether a file is resident in the local storage resource and is not included in the offload mapping;

a file extension;

a file location in the first file system;

whether a file includes executable code;

attributes of secondary files associated with a file; and

a security attribute assigned by an operating system installed on the information handling system.

13. The article of manufacture of claim 11, wherein the data location management agent enabled to register the first data file in the offload mapping includes the data location management agent enabled to:

when the offload mapping includes a record for the first data file, modify the record, including updating a timestamp attribute for the first data file; and

when the offload mapping does not include a record for the first data file;

create a new record for the first data file in the offload mapping;

record metadata in the new record, the metadata including;

a filename associated with the first data file;

a first location of the first data file on the local storage resource; and

a second location of the first data file on the remote storage resource.

14. The article of manufacture of claim 8, wherein the data location management agent enabled to offload at least the second data file includes the data location management agent enabled to offload a plurality of data files, including the second data file, and wherein the plurality of data files are selected according to a least-recently-used algorithm.

15. An information handling system comprising:

a processor subsystem having access to a memory subsystem, wherein the memory subsystem stores instructions executable by the processor subsystem, that, when executed by the processor subsystem, cause the processor subsystem to;

instantiate a data location management agent on an information handling system, the data location management agent enabled to;

detect a request to access a first data file intended for a local storage resource included with the information handling system;

when the first data file is currently stored at a remote storage resource accessible to the information handling system;

offload at least a second data file to the remote storage resource, including deleting the second data file from the local storage resource; and

load the first data file from the remote storage resource to the local storage resource.

16. The information handling system of claim 15, wherein, prior to detecting the request, the data location management agent is enabled to:

determine a network location of the remote storage resource; and

determine a reserve capacity of the local storage resource,

17. The information handling system of claim 16, wherein the data location management agent is enabled to offload at least the second data file responsive to determining that an available capacity of the local storage resource is less than the reserve capacity.

18. The information handling system of claim 15, wherein the data location management agent is enabled to:

determine whether the first data file is an offloadable file;

when the data file is an offloadable file;

register the first data file in an offload mapping; and

restrict offloading of data files to the remote storage resource to files registered in the offload mapping.

19. The information handling system of claim 18, wherein the request to access the first data file is handled by a first file system installed on the local storage resource, and wherein the data location management agent enabled to determine whether the first data file is an offloadable file includes the data location management agent enabled to:

determine, based on one or more file attributes of the first data file whether the first data file is a pinned file, wherein a pinned file is not an offloadable file, and wherein the file attributes are selected from;

whether a file is resident in the local storage resource and is not included in the offload mapping;

a file extension;

a file location in the first file system;

whether a file includes executable code;

attributes of secondary files associated with a file; and

a security attribute assigned by an operating system installed on the information handling system.

20. The information handling system of claim 18, wherein the data location management agent enabled to register the first data file in the offload mapping includes the data location management agent enabled to:

when the offload mapping includes a record for the first data file, modify the record, including updating a timestamp attribute for the first data file; and

when the offload mapping does not include a record for the first data file;

create a new record for the first data file in the offload mapping;

record metadata in the new record, the metadata including;

a filename associated with the first data file;

a first location of the first data file on the local storage resource; and

a second location of the first data file on the remote storage resource.

21. The information handling system of claim 15, wherein the data location management agent enabled to offload at least the second data file includes the data location management agent enabled to offload a plurality of data files, including the second data file, and wherein the plurality of data files are selected according to a least-recently-used algorithm.