Managing connections in a data storage system

• US 8,769,635 B2
• Filed: 04/30/2013
• Issued: 07/01/2014
• Est. Priority Date: 03/20/2009
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Varadharajan, Prakash, Dornemann, Henry Wallace, Gokhale, Parag
• Primary Examiner(s): Armouche, Hadi
• Assistant Examiner(s): SONG, HEE K
• Application Number:
  US13/874,358
• Publication Number:
  US 20130247154A1
• Time in Patent Office: 427 Days
• Field of Search: 726 2- 7, 726/17, 726 26- 31, 713/189, 713/193, 711/162, 711/163, 709/3, 709/9, 709/202, 709/204, 709/205
• US Class Current: 726/4
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/101 Access control lists [ACL]

Abstract

Described in detail herein are systems and methods for managing connections in a data storage system. For example, the systems and methods may be used to manage connections between two or more computing devices for purposes of performing storage operations on the data of one of the computing devices. The data storage system includes at least two computing devices. A first computing device includes an unauthorized connection data structure and a connection manager component. The connection manager component receives a connection request from a second computing device. If the second computing device is not identified on the unauthorized connection data structure, the connection manager component can request that an authentication manager authenticate the second computing device and/or determine whether the second computing device is properly authorized. If so, the connection manager component can allow the second computing device to connect to the first computing device.

Claims

1. A system for managing connections in a data storage system, wherein the data storage system includes at least one client computing device storing data, the system comprising:

an authentication manager;

a storage device; and

at least one secondary storage computing device configured to receive a request from the client computing device to store the data on the storage device, wherein the secondary storage computing device includes;

a blacklist that includes one or more entries, wherein the entries include an identifier of a computing device;

a connection manager component configured to;

receive, at a first time, from the client computing device a connection request, wherein the connection request includes a identifier identifying the client computing device;

based upon the identifier of the client computing device or the combination of the identifier of the client computing device and the first time, determine from the blacklist whether the connection request from the client computing device should be refused;

refuse the connection request from the client computing device if the connection request from the client computing device should be refused based upon the determination from the blacklist;

if the connection request from the client computing device should not be refused based upon the determination from the blacklist, then determine whether the client computing device is authenticated or authorized to connect to the secondary storage computing device;

if the client computing device is either not authenticated or not authorized to connect to the secondary storage computing device, refuse the connection request from the client computing device; and

if the client computing device is authenticated, or if the client computing device is authorized to connect to the secondary storage computing device, allow the client computing device to connect to the secondary storage computing device,

wherein the secondary storage computing device is located at a friendly side of a firewall, wherein the client computing device is not located at the friendly side of the firewall, and wherein the secondary storage computing device receives the request from the client computing device through the firewall.

2. The system of claim 1 wherein the entries of the blacklist further include a timestamp indicating a time at which the secondary storage computing device received a connection request from the identified computing device.

3. The system of claim 1 wherein the connection manager component is further configured to either:

add an entry to the blacklist that includes the identifier of the client computing device and a timestamp indicating the first time;

or

modify a timestamp of an existing entry of the blacklist that includes the identifier of the client computing device to indicate the first time.

4. The system of claim 1 wherein the secondary storage computing device further includes:

an interface at which the secondary storage computing device receives the connection request; and

an interface blacklist, wherein the interface blacklist includes one or more entries, wherein at least one of the entries is configured to include an identifier of an interface,

wherein the connection manager component is further configured to;

determine an identifier of the interface;

based upon the identifier of the interface, determine from the interface blacklist whether the connection request from the client computing device should be refused; and

refuse the connection request from the client computing device if the connection request from the client computing device should be refused based upon the determination from the interface blacklist.

5. The system of claim 1 wherein the connection manager component is further configured to remove an existing entry that includes the identifier of the client computing device from the blacklist if the client computing device is authorized.

6. The system of claim 1 wherein the connection manager component is further configured to:

receive an identifier of a computing device to which the connection manager component should refuse connection requests; and

add the identifier of the computing device to the blacklist.

7. The system of claim 1 wherein the connection manager component is further configured to receive an indication to enable refusing connection requests from computing devices that are not authorized.

8. The system of claim 1 wherein the blacklist includes at least two entries, wherein a first entry includes an identifier of a computing device, and wherein a second entry includes an identifier of another computing device and a timestamp indicating a time at which the connection manager component received a connection request from the identified other computing device.

9. The system of claim 1 wherein the data storage system includes at least two different hierarchical tiers of data storage, wherein the client computing device is at a first hierarchical tier of data storage, and wherein the secondary storage computing device is at a second hierarchical tier of data storage.

10. The system of claim 1, wherein the authentication manager performs both authentication of the client computing device and determining whether the client computing device is authorized to access the secondary storage computing device.

11. A method of managing connections in a data storage system, wherein the data storage system includes at least two computing devices, the method comprising:

receiving, at a local computing device, a connection request from a remote computing device,

wherein the connection request includes an identifier that identifies the remote computing device,

wherein the local computing device is located at a friendly side of a firewall, and

accessing a blacklist, wherein the blacklist includes one or more entries, wherein the entries include an identifier of a computing device;

receiving an indication to enable refusing connection requests at the local computing device to computing devices that are not at the friendly side of the firewall;

based upon the identifier of the remote computing device, determining from the blacklist whether the connection request from the remote computing device should be refused; and

,

if the connection request from the remote computing device should be refused based upon the determination from the blacklist, then refusing the connection request from the remote computing device;

if the remote computing device is either not authenticated or not authorized to connect to the local computing device, refusing the connection request from the remote computing device; and

if the remote computing device is authenticated, or if the remote computing device is authorized to connect to the local computing device, allowing the remote computing device to connect to the local computing device.

12. The method of claim 11, further comprising, if the connection request from the remote computing device is refused, then either:

adding an entry to the blacklist that includes the identifier of the remote computing device and a timestamp indicating the first time;

or

modifying a timestamp of an existing entry of the blacklist that includes the identifier of the remote computing device to indicate the first time.

13. The method of claim 11 wherein the local computing device receives the connection request at an interface, and further comprising:

determining an identifier of the interface at which the connection request is received;

accessing an interface blacklist data structure, wherein the interface blacklist data structure includes one or more entries, wherein at least one of the entries is configured to store an identifier of an interface;

based upon the identifier of the interface, determining from the interface blacklist data structure whether the connection request from the remote computing device should be refused; and

if the connection request from the remote computing device should be refused based upon the determination from the interface blacklist data structure, then refusing the connection request from the remote computing device.

14. The method of claim 11 further comprising:

requesting that an authorization computing device determine whether the remote computing device is authorized to connect to the local computing device; and

receiving an indication from the authorization computing device whether the remote computing device is authorized to connect to the local computing device,

wherein, if the remote computing device is authorized to connect to the local computing device, then removing an existing entry from the blacklist that includes the identifier of the remote computing device.

15. The method of claim 11, further comprising:

receiving an identifier of a computing device to which the local computing device should refuse connection requests; and

adding the identifier of the computing device to the blacklist.

16. The method of claim 11, wherein the entries of the blacklist further include a timestamp indicating a time at which the secondary storage computing device received a connection request from the identified computing device.

17. The method of claim 11 wherein the blacklist includes at least two entries, wherein a first entry includes only an identifier of a computing device, and wherein a second entry includes an identifier of another computing device and a timestamp indicating a time at which the local computing device received a connection request from the identified other computing device.

18. The method of claim 11 wherein at least one of the entries included in the blacklist includes an identifier of a computing device that is not licensed in the data storage system.

19. A computer-readable, non-transitory medium including instructions for managing connections in a data storage system, comprising:

receiving, at a first time at a first computing device, a connection request from a second computing device,

wherein the connection request includes an identifier that identifies the second computing device;

accessing a blacklist,

wherein the blacklist includes zero or more entries, and,

wherein the entries are configured to include an identifier of a computing device;

receiving an indication to enable refusing connection requests at the first computing device to computing devices that are not on a friendly side of a firewall and that are not authenticated;

based upon the combination of the identifier of the second computing device and the first time, determining from the blacklist whether the connection request should be refused; and

,

if the connection request from the second computing device should be refused based upon the determination from the blacklist, then refusing the connection request from the second computing device;

if the second computing device is either not authenticated or not authorized to connect to the secondary storage computing device, refuse the connection request; and

if the second computing device is authenticated, or if the second computing device is authorized to connect to the first computing device, allowing the second computing device to connect to the first storage computing device.

20. The computer-readable medium of claim 19 further comprising, if the connection request from the second computing device is refused, then either:

adding an entry to the blacklist that includes the identifier of the second computing device and a timestamp indicating the first time;

or

modifying a timestamp of an existing entry of the blacklist that includes the identifier of the second computing device to indicate the first time.