CA1319758C - Centralized management in an sna network - Google Patents
Centralized management in an sna networkInfo
- Publication number
- CA1319758C CA1319758C CA000607307A CA607307A CA1319758C CA 1319758 C CA1319758 C CA 1319758C CA 000607307 A CA000607307 A CA 000607307A CA 607307 A CA607307 A CA 607307A CA 1319758 C CA1319758 C CA 1319758C
- Authority
- CA
- Canada
- Prior art keywords
- focal point
- node
- nodes
- message
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
Abstract
ABSTRACT
An improved method for dynamically and centrally managing a teleprocessing network partitions the network into Focal Point (FP) nodes and non-FP (NFP) or serviced nodes. Each FP node provides management services to an assigned group of non-FP nodes. The names of the non-FP nodes are maintained in a table called a "sphere of control" (SOC) table at the FP node that services those NFP nodes.
As NFP nodes in the SOC table become active, the FP establishes a session with the NFP node and sends it a "Request to be Your FP" message. If the NFP node supports the keys (bit pattern identifying a particular category of management services data) for which authorization is being requested, the NFP node replies positively acknowledging the requestor as its focal point for the specified key.
Thereafter, problem messages which are related to the particular type of man-agement services are forwarded to the FP node.
An improved method for dynamically and centrally managing a teleprocessing network partitions the network into Focal Point (FP) nodes and non-FP (NFP) or serviced nodes. Each FP node provides management services to an assigned group of non-FP nodes. The names of the non-FP nodes are maintained in a table called a "sphere of control" (SOC) table at the FP node that services those NFP nodes.
As NFP nodes in the SOC table become active, the FP establishes a session with the NFP node and sends it a "Request to be Your FP" message. If the NFP node supports the keys (bit pattern identifying a particular category of management services data) for which authorization is being requested, the NFP node replies positively acknowledging the requestor as its focal point for the specified key.
Thereafter, problem messages which are related to the particular type of man-agement services are forwarded to the FP node.
Description
RA988013 Pase 1 131~758 CENTRALIZED MANAGEMENT I~ A~ SNA N~TWOR~
CROSS ~EFEREHCE TO RELATE~ R~TENT
U.S. Patent No. 5,109,48~, issued APril 28, 1992 to A.E. Baratz et al, entitled 'Method for Dissemina-ting Network S-tate Information , discloses a method for dissemina-ting network state information between network nodes. The subject patent is assigned to the assignee of the present invention.
Ba_kyround of_the Invention 1. Field of_the Inven _on The present invention relates to computer networks in general and more particularlY to improved me-thods For managing said networks.
CROSS ~EFEREHCE TO RELATE~ R~TENT
U.S. Patent No. 5,109,48~, issued APril 28, 1992 to A.E. Baratz et al, entitled 'Method for Dissemina-ting Network S-tate Information , discloses a method for dissemina-ting network state information between network nodes. The subject patent is assigned to the assignee of the present invention.
Ba_kyround of_the Invention 1. Field of_the Inven _on The present invention relates to computer networks in general and more particularlY to improved me-thods For managing said networks.
2. Pri_r_Art The~ proliferation in computer nPtworlcs creates a need for more afficient methods to manage and control saiel networks. The need is particularly pressing for large mesh networks wherein the toPologY of the network is constantly changing by addition and~or deletie~n of network nodes. Such deletions and~or additions may be the result of expansion or contraction in -the network and~or communications failures in a node or link. Because of -the dynamic characteristics of these networks, a dynamic management approach which adjusts and provides manc7gement services For -the changing network is desirable.
~J~ ~
A communications network typically consists of a plurality of nodes and communications links interconnecting the nodes. The nodes can act as informa-tion accepting locations (origin nodes), information sink locations (destina-tion nodes) or an intermediate node which passes a message from the origin to the destination. Each node is provided with a plurality of functions which interact and enable the node to perform an assigned task.
Among the many functions which are provided is the so-called "Management Service (MS) Function." This function usually resides in the System Support Control Point (SSCP) of a node. It gathers management information about the network and reports it to an operator. For example, one type of management service may handle error conditions in a network. On the occurrence of a net-work error condition, the management service is made aware of the condition.
The management service in turn notifies a network operator who can take appro-priate steps to correct the error condition.
Currently, networks are managed on a "domain" basis. This means that a network is partitioned into different domains and each SSCP provides management services for resources in its own domain. There are no provisions for cross-domain management. However, there are times when cross-domain management is desirable to effectuate better management of the network. For example, cross domain management is p~eferred where the network is comprised o a relatively large number of domains with each domain requiring an operator.
SUMMARY OF T~IE INVENTION
It is therefore the general object of the present invention to provide an apparatus and method which manage a network more efficiently than was heretofore possible.
1 31 ~758 It is a more specific object of the present invention to provide cross-domain management.
It is still another object of the present invention to provide dynamic management service functions which adapt to compensate for changes in the net-work.
The objectives are achieved by partitioning the network into control nodes which are called focal point nodes (FP nodes) and managed nodes called non-focal point nodes or "NFP Nodes." Each FP node is provided with a "Sphere of Control"
(SOC) table that lists the NFP nodes which are managed by the FP node. As nodes become active in the network, the FP node is made aware of them. The FP node searches its SOC table to see if the node is listed. If the node is listed, the FP node generates and transmits a request message asking it to be its "focal point." If accepted, the NFP node issues a favorable response. The FP node that explicity lists the NFP nodes is called the primary FP. Thereafter, in-formational messages relative to authorized types of management services are exchanged freely between the FP node and the NFP node.
There are at least three types of Request Messages, namely: (a) Request to be your Primary FP, (b) Request to be your Secondary FP, and (c) Requast to be your Backup FP. The Request to be your Backup FP is used between FP nodes.
; In one feature of this invention, an FP node can be designated to provide management services for NFP nodes not listed in the SOC table of other FP nodes.
This FP node is called the secondary FP. The secondary FP issues to an NFP node - a "request to be your secondary FP" message even though the NFP node is not in its SOC table. In this case message (b) is the selected one. This message provides management services for NFP nodes that are not assigned to a Primary FP.
RA988013 Page h The foregoing and other objects and features of this invention will be more fully described in the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 shows a schematic of a network partitioned in accordance with the teachings of the present invention.
Fig. 2 shows a functional diagram of structures for an FP node.
Fig. 3 shows a functional diagram of structures for an NFP node.
Fig. 4 shows FP Management Services (~IS) tables.
Fig. 5 shows NFP (MS) tables.
Figs. 6A-6E show MS Message Formats.
Figs. 7A & B show a flow chart of a program used a~ FP node.
Fig. 8 shows a flow chart of a program used at an NFP Node.
Fig. 9 shows flows demonstrating an NFP Node changing its FP Node.
Fig. 10 shows flows illustrating communications involved in establishing a "backup" FP Node.
DESCRIPTION OF T~IE PREFERRED EMBODIMENT
Fig. 1 shows a block diagram of a communications network which includes the teachings of the present invention. The network of Fig. 1 is merely exemplary as to the number of nodes and is not intended in any way to limit the scope or teaching of the present invention. The network includes a plurality of end nodes (EN) 10', 16', 16", 18', 18" and 20' coupled by respective com-munications link to network nodes ~NN~. The end nodes may include devices such as personal computers, printers, word processing stations, computers, etc.
Computers and other data processing equipment which are end nodes usually do RA988013 Paye 5 not participate in network functions such as routin~, etc. The network nodes ParticiPate in providins ne-twork functions to at-tached end nodes.
Still referring to Fig. 1, the network nodes include focal points (FP) nodes 10 and 14 and non--Focal points (NFP) nodes 12, 16, 18 and 20. The networl< nodes are interconnected by communications links A, B, C, D, E, F and G. As will he explained subsequently, the Focal point nodes provide manasement services for the non-focal point nodes. Stated another way, -the non-focal poin-t nodes such as 16, 18, 20 and 12 are managed or serviced by -focal point nodes 10 and 14. In particular, FP 10 manages or services NFP 12, NFP 1~ and NFP 18. To show that NFP 12, NFP 16 and NFP 18 are manased by FP 10, this srouP
of nodes i9 interconnected by broken lines 22, 24 ancl 26. SimilarlY, Focal POint 14 manages non-focal point node 20 and is interconnected by broken line 28. Thus, in Ficm l tl)e solid interconnecting lines represent communications links while the hroken interconnecting lines represent managemen-t links. I-t should he no-ted -that manasement links are not physical lines in -the ne-twork. rhey are onlY used to show the relationship between managed and manac1ins network nodes. They are also called sessions.
Fig. 2 shows a functional s-truc-t-lre for a focal point node. The structure of the focal POint node is similar to the structure of the well-known APPN nodes. De-tails oF the APPN nodes are set Forth in:
1. "Advallced Program -to Program Communication and Advanced Peer-to-Peer Networking Users Guide", a manual For IBM~ AS~400 system, SC21-9598.
2. "Advanced Peer to Peer Networking (APPN) for AS~400 System, GC24-3287.
131~758 Since the functional structure of the node is well defined, only those components which are necessary to practice and understand the present invention will be described. To that end, the focal point node includes a control point (CP), application (APPL) programs, logical unit (LU), path control, SOC tabls and a plurality of data link control (DLC) modules. The data link control modules provide protocol functions so that messages leàving from a focal point node can be arranged in a desired protocol for transmission over a communication link. Multiple DLC indicates that the FP supports different types of protocols.
The path control module provides the routing function to enable messages to be exchanged between two nodes. The CP provides the control function for the node.
For example, it controls sessions, calculates routes, directory services, etc.
Finally, the LU provides the interface which allows an application program ac-cess into the network. The present invention impacts the conventionaI APPN node and provides improved management services by adding the application programs, and focal point management service (FP~IS) tables. It also makes use of the APPN's topology data base (TDB). Details on each of these components will be given subsequently. Suffice it to say at this point that the addition of these components provides improved methods for managing a network.
Fig. 3 is a functional block diagram for a non-focal point (NFP) node.
The non-focal point node is structurally similar to an APPN node and the focal point node previously described in Fig. 2. This being the case, only the functions which have been added by the present invention will be described.
The added functions include an application program called here a non-focal point managsment services (NFP-MS) program, and the FP authorized table. Details of the added function will be described subsequently. Suffice it to say at this RA988013 1 3 1 q 7 5 8 Page 7 point that the adcded -function causes a non focal point node to respond to -the focal Point nocle and exchange messages whieh eause the non-foeal point node to transmit mallasement services information including error conditions, alerts, etc. -to the focal point node which controls or services the non-Focal point node.
Fig. q shows the tables which are used by the CP of the focal point node. The tables include a Sphere Or Control (SOC) and FP
table. These tahles are used by a Focal Point mana~ement services program. The figure also shows an examPle of topologY data base (TDB~
corresponding to -the ne-twork example sllown in Figure l. The topology data base (TDB) identiFies the topologY o-F network nodes. This ineludes a listing of nodes and links between them with a status indicating whether or not an in-tereonnecting link is eurrently aetive or inaetive. It should be noted tha-t the TDB table is present in all network nodes whether it is a foeal po;nt node or a non-foeal Point node. From this TDB table a node can determine whether or not there is an active connectivi-ty to a c1iverl network node. By way of example, the TDB of Fig. 4 lists the rlocles ancl connectivity For the network in Fig. l. Thus, as can be seen From the table, network node FP lO is connected by links A and C -to network nodes NFP lZ and NFP 16.
Similarly, network node NFP 12 i.5 couplecl via communication links A, B and D to network nodes FP lO, FP 1~l ancl NFP 18, respectively, and so forth. As stated previously, a similar TDB -table i5 provided in a non-foeal point node. An example of a topology data base table whieh can be used irl the present invention is set forth in US Patent 4,644,532.
Still referring to Fi~. 4, the FP managemen-t serviees ~odule includes a sphere of control (SOC) table and a focal point (FP) table. The SOC table ~,~
, contains a list of all network nodes for which this focal point is responsible.
The network operator can dynamically add or delete network node to the SOC table and also display current status for all nodes defined in the SOC table. The table also contains a status (STAT) for each node. Thus, by way of example, MFP 12 is active. Similarly, NFP 20 is revoked (REVOK), etc. Table 1 below shows a listing of status for network nodes and an interpretation for each one.
These will be described more fully in later sections of this document.
-STATUS INTERPRETATION
Active The node is in the sphere of control, connectivity to the nod2 exists and the focal point is actively providing focal point services to this node.
Inactive, Not in Network The FP does not have connectivity to the node.
Inactive, Session Down The FP has lost its management services session with the node and is attempting to re-establish that session.
Rejected The node has rejected FP services. .
Revoked Another FP has taken over as the active FP.
131q758 As can be seen from the above Table 1, when a non-focal point node is marked active in the table, the responsible focal point is providing active focal point services to that node. The other possible states that a non-focal point node may be in are set forth in Table 1 and the associated interpretations are clearly explained. Thus, no further description of Table 1 will be given.
A focal point can be responsible for different management services func-tions for different spheres of control. That is, a single focal point may maintain multiple sphere of control tables, one for each management services focal point function it provides. Associated with each sphere of control table, the focal point management services module contains a record called FP-Table.
This table contains a focal point type field and a list of management services (MS) key fields. This record is transmitted from a focal point node to a non-focal point node in a request focal point authorization message. The FP type field tells what type of focal point the node is and the MS key list identifies the network management services provided by this focal point. Each MS key identifies a specific management service. The present invention defines the following FP types: primary, secondary and backup.
Primary FP- is the FP for the network management category identified by the management services keys (MS-keys), and it provides services for network nodes identified explicitly in the SOC table.
Secondary FP- is the FP for network nodes that were not assigned to a primary FP (not defined in SOC table of any primary FP).
Backup FP- is the FP that backs up another FP. It acts as an FP when the primary FP is not operational.
Table II below shows an example of possible codings for an FP-Table in which the associated FP node is a Primary and Secondary for the management .
1 31 ~75~
services listed in the management services key field. Hex (X) notations are used to code the management services which the node supports. In the preferred embodiment of this invention X'0000' identifies that the FP supports the re-ceiving of Alerts sent by the non focal point nodes, and X'0025' identifies that the FP supports receiving the problem determination stat-stical information.
As is indicated by the dots, other management service keys can be listed in the key field.
TABLE II
FP-TABLE
¦FP-Type ¦List Of MS-Keys ¦bit 1 2 3 ¦X'0000', X'0025' (1 is Primary; 2 is Secondary; 3 is backup) As will be explained subsequently, this focal point record is transmitted with the request message to a non-focal point node;
Fig. 5 shows the focal point authorization table which is present in the non-focal point management service (NFP-MS) node of Fig. 3. The TDB table of Fig. 3 is identical to the previously-described TDB table and therefore further description will not be repeated. The focal point authorization table (Fig.
5) lists focal point names, management services (MS) keys and focal point typ~s.
As will be explained subsequently, when a focal point node sends out a request RA98~013 Page 12 1 31 ~158 message to a non-focal point node, the message includes a focal point name, MS
keys and the Focal Point type.
The non-focal point node uses the information received in the request to update the FP Authorization Table. The non-focal point node uses the informa-tion in the FP Authorization Table to route specific management services data, defined by the specific Management Services key (MS key) -to the appropriate FP
node. The same table also informs the non-focal point node if the management services are provided by the primary or secondary focal point node. The non-focal point node will reject a request received from a secondary FP if the non-FP node is already receiving services from a primary FP for the specific MS Key.
Figs. 6A-6E show formats for the messages which are exchanged between a focal point and a non-focal point node. Figs. 6A-6C show the general management services message format. This message format includes a prefix field, a routing header field, a CP-MSU (management service unit) field, and a suffix field.
The routing header field includes the origin and destination name of the stations involved. By way of example, the origin name would be the name of the station which originates the message while the destination name is the name of the node to which the message is sent. The CP-MSU field (Fig. 6B) is further divided into a length field, general data stream (GDS) ID field and a management service major vector field. In the preferred embodiment of this invention, the GDS ID field carries the notation Hex or X'1212'. This notation indicates that the message is a management services type message. The management services major vector field is further divided into a length field, an MS key field and a data field. As stated before, each of the keys indicate the type of management services which an FP node supports. By way of example, the following MS keys ~A988013 Page 13 are defined: X'OOOO'- indicates an alert, X'0025'- indicates problem determi-nation statistics, X'80FO' indicates MS capabilities request and X'OOFO' indi-cates MS capabilities reply. It should be understood that these keys are merely exemplary and do not limit the invention in any way.
Referring to Figs. 6D and 6E, specific formats which are used for estab-lishing communications between focal point nodes and nodes in the sphere of control table are shown. The format in Fig. 6D is a request format while the format in Fig. 6E is a reply format. Stated another way, the format of Fig.
6D is generated and transmitted to a non-focal point node entering (i.~., be-coming active) in the network. The same format is used for a ;;Request to Be Your Primary FP" or a "Request to Be Your Secondary FP." The message format in Fig. 6E is generated and returned to the focal point node. The format in Fig. 6D includes a length field, MS key field, a length field, a request iden-tifier field, a length field, an FP type field, and a list of MS keys. The request field carries a code indicating that the message is a request. In the preferred embodiment of this invention the code is X'61'. Of course, other codes can be used without deviating from the scope of the present invention.
Each length (L) field in the message indicates the number of bytes which imme-diately follow. The other fields such as the MS key, FP type and list of MS
keys field have already been described and will not be repeated here. Suffice it to say that in a preferred embodiment of the invention the FP-type field (Fig. 6D) includes the following coding X'lO' for Primary FP, X'20' for Sec-ondary FP and X'30' for Backup FP. Likewise, the list of MS-keys includes X'OOOO' and X'0025'. Of course, other codings can be placed in either or both fields without departing from the teachings of thé present invention.
RA98~013 Page 14 The reply message (Fig. 6E) has a structure similar to the request message.
The code X'62' is used to identify that the message is a reply. The reply message also includes a result field which carries information to inform the FP node if the request is accepted, rejected, revoked, etc. In a preferred embodiment of the invention X'10' is an accept, X'20' is a reject and X'30' is a revoke. The list of MS keys is a record of the keys for the services which the non-focal point node accepts.
As described previously, both the non-focal point node and the focal point node carry respective application programs which cause the node to perform functions necessary to provide management services of the present invention.
It is those programs that this document will now describe.
Figs. 7A and 7B show a flow chart of the algorithm or program that xesides at the focal point node. Execution of the program causes the FP node to perform the steps necessary to effectuate the teachings of the present invention. The program comprises of an entry point called a start. From the start, the program descends into block 30 where it waits until the focal point node receives a topology data base update. message or session outage notification or "FP Au-thorization Revoked" message. The topology data base update message (TDU) is regularly provided to update the topology data table that resides in each net-work node. The program then descends into block 31, where it checks to see if a TDU message has been received. If the result is "yes" (Y), the program then descends into block 32. In block 32 the focal point updates the topology data base and checks if a new node has joined the network. The program then descends into decisional block 34. In block 34 the program checks to see if the node which recently became active is defined in its sphere of control table. If it is not defined in the table, the program enters the decisional block 36. In block 36 the program checks to see if the FP type equals secondary for some ~IS
keys. If it is not equal to secondary, the program loops back into block 30.
With reference to block 36, if the focal point type is secondary, the program descends into block 40. In block 40 the program generates and sends a "request to be your secondary focal point" message and descends into block 42 where it waits for a response from the non-focal point node.
Still referring to Figs. 7A and 7B, and with respect to block 34, if the recently active node is defined in the sphere of control table, the program descends into decisional block 44. In block 44 the program checks to see if focal point type equals primary. If it does not, the program ioops back into block 30. Otherwise, the program descends into block 46 where it sends out a "request to be your primary focal point" message. From block 46 the program descents into block 42 where it waits for a response from the non-focal point node and continues when received. The program then descends into decisional block 48. In decisional block 48 the program checks to see if the non-focal point node accepts the focal point. Whether or not the node accepts the focal point (FP) depends on the information carried in the request. Specifically, it depends on the FP-type field and list of MS-key field of the Request Message (Fig. 6D). If the message is a "request to be your secondary FP" and the non-FP
node already has another FP as a primary for the same MS-keys, the node will not accept the request. If the node rejects the request, the program enters block 50 where it checks its table to see if it is a secondary focal point.
If it is, the program loops back to block 30. If it is not, the program then descends into block 52. In block 52 the program notifies the network operator of the rejection and enters rejected in the status column of the sphere of control table (Fig. 4). From block 52 the program then gocs back co start.
,:
131~758 Still referring to Figs. 7A and 7B, and with respect to decisional block 48, if the non-focal point node accepts the focal point as its focal point for the particular type of service, the program descends into block 54. In block 54 the program changes the status in the SOC table to "active" and descends into block 56. In block 56 the focal point can now receive unsolicited management services data from the node. The focal point can also send messages to retrieve data from the serviced network node.
This algorithm is also used initially when an FP program becomes active or when a node is dynamically added to the SOC. When an FP program becomes active, it will first check the TDB and for each non-focal point node defined in the SOC table for which connectivity exists, the FP will use the same algo-rithm as if the node has just joined the network. When a node is added to the SOC table, the FP program first determines if connectivity to that node exists and proceeds from box 41.
Still referring to Figs. 7A and 7B, and with respect to block 31, if a TDU
message has not been received, the program exits along the NO (N) path into block 33. In block 33 the program checks if a "Session Outage Notification"
has been received. If a "Session Outage Notification" has been received, the program descends into block 35 where it updates the status of an NFP node, in the SOC Table, to "Inactive-Session Down" and descends into block 37. In block 37, the program notifies the network operator and returns to start. With ref-erence to block 33, if a "Session Outage Notification" was not received, the program descends into blocl~ 39 where it updates the status of an NFP node, in the SOC table, to "Revoked" and descends into block 37 where it performs the previously described functions.
Fig. 8 shows a flow chart for the algorithm used in a non-focal point node.
From the start block, the program descends into block 60. In block 60 the non-focal point node receives a request message from a focal point node. The program descends into block 62 where it checks to see if the message is a "re^
quest to be your primary focal point" message. If it is, the program checks its FP authorization table (Fig. 5) to see if the node already has a session with another focal point for the same MS- key (block 64). If it does not, the program enters block 66. In block 66 the node sends a "focal point accepted"
reply message to the focal point.
With reference to block 64, if the node has a session with another focal point for the same MS key, the program descends into block 72. In block 72 the program sends "focal point authorization (AUTH) revoked" in the reply message to the current focal point. The program then descends into block 74 where it terminates the session with the current focal point. It should be noted that all sessions are set up and controlled by the LU function in each network node (NN). The program then descends into block 76 where it updates its focal point authorization table (Fig. 5) with the focal point name, MS key, and focal point type from information received in the focal point request message. Thereafter, the node (block 78~ can start sending unsolicited network management information for the category identified by the MS key.
Still referring to Fig. 8 and decisional block 62 in particular, if the answer to the question in block 62 is no, the program descends into decisional block 80. In block 80 the program checks to see if it is a "Request to be Your Secondary Focal Point." If it is not, the program descends into block 70 where it sends the "focal point rejected" reply to the focal point node. Otherwise, from block 80 the program descends into decisional block 82. In decisional 1 31 q758 block 82 the program checks to see if the node has a session with another primary focal point. If the response is yes, the program descends into block 70. If the answer is no, the program descends into block 66. When a non-focal point node loses a session with the FP node, it deletes entries in the FP Authori zation Table associated with this FP node. This completes the description of the programs which are used to implement the present invention.
One of the unique characteristics of the present invention is that non-focal point nodes which are in the SOC of an FP Node can be changed dynamically.
This is illustrated by the flow control schematic in Fig. 9. The network nodes are captioned at the top of the drawing as focal point A, focal point B and node C. Each arrow in this flow diagram shows the direction in which information flows between the nodes. Thus, in step 1 focal point A issues a "request to be your primary focal point" message to node C. This comes about because node C is listed in the sphere of control table of focal point A which establishes a session between itself and node C and then issues the request message. Step 2, noda C accepts the request and issues the "authorization accepted" message to focal point A. In the preferred embodiment of this invention, node A accepts by issuing a control vector X'62' code in the reply message. Step 3 shows focal point B issuing a "request to be your primary focal point" message to node C.
This occurs because node C has just been defined in the SOC table at focal point B. Focal point B establishes a session with node C and issues a "Request to be Your Primary FP" message. Node C accepts the request and issues two mes-sages, one to focal point B accepting the request and one to focal point A (Step 5) revoking the previous authorization. In this particular example~ it shculd be noted that the order of the request from the primary focal point A or B to node C deter:ines which focal poiDt h~s t,e authorization and which authori;
,, 13197~8 zation will be revoked. In this particular example, the focal point which is-sues the second request is deemed to take precedence over an earlier request.
Of course, some other types of priority succession can be arranged without de-viating from the SCOp8 or teachings of the present invention.
One of the request messages that a focal point can generate and ~ransmit to another focal point is a "Request to Be Your Backup Focal Point" message.
The communica~ions which are exchanged between backup focal point B, the primary focal point A and a serviced node such as node X is illustrated in Fig. 10.
If a focal point is defined to provide backup function for another or other focal points, that focal point such as B in the figure, establishes a session with those it backs up. The backup focal point sends a "request to back you up as a focal point" message. The receiving focal point, such as focal point AJ indicates if it supports having that focal point as a backup focal point.
The authori~ation is rejected if the focal point is not a focal point for the keys specified by the backup focal point. With respect to Fig. 9, node X is in the sphere of control table of focal point A. Focal point B, as a backup for focal point A, will attempt to establish a session with node X when the session between A and B is lost and cannot be re-established.
In order for the backup focal point to establish a session with the nodes that are serviced by the primary focal point A, the backup focal point B must have knowledge of the sphere of control of the focal point being backed up (or perhaps a portion of that sphere of control if backup is provided by multiple focal points). When the session between a focal point and its backup fails, the backup focal point attempts to re-establish a session. If that session is re-established, the communications set forth in both 80 and 82 (Fig. 10) are allowed to occur. That is, "the request to back you up as a focal point" message is sent and replied to by the served focal point. However, if the session be-tween a focal point and its backup cannot be re-established, the backup focal point notifies the local operator of this condition, and allows the operator to decide if the backup focal point should attempt to establish sessions with all nodes in that portion of the sphere of control of the lost focal point being backed up. Operator intervention is preferred since the operator may have knowledge of why connectivity to the primary focal point was lost and thus may know if the backup is needed.
If sessions between the backup focal point and node in the backed up sphere of control are established, the "request to be your secondary focal point"
message is sent to each node in the sphere of control of the primary focal point.
The node will accept the secondary as its focal point if it does not have a focal point, otherwise it will reject the request.
Operation In operation, names for a set of managed or serviced network nodes are defined in a sphere of control table at each focal point ncde. Names can be added or deleted dynamically by the focal point operator. As nodes, in an FP
SOC table, become active, the focal point establishes a session with the node and sends it a "Request to be Your Primary Focal Point Message." If the node supports the key for which authorization is being requested, the node replies positively (acknowledging the requestor as its focal point for the specified keys). These keys can identify a particular category of management ser~ices data. If the authorization request is accepted, the node creates an entry in its directory of focal points ~Fig. 5). The entry or entries in the directory of focal points can be used to determine the destination focal point for unso-131q758 licited messages or to determine if a particular focal point is authorized tosend the specific management service request to the node. A password may be included in the request.
If the focal point is not accepted as a foc~l point from the node, the focal point may modify the request to be your focal point message and resubmit it, that is, change the key for which this focal point is requesting authorization, or indicate in its sphere of control table that the node has rejected the focal point request and notify the operator. If the focal point is accepted as a focal point for the node, the focal point receives ali unsolicited management services data as sent by the node for the authorized key or keys.
A focal point is responsible for establishing sessions with each node name appearing in its user defined sphere of control table. The only exceptions are:
nodes to which connectivity does not exist, nodes which reject the "request to be your primary focal point" message and nodes serviced by another focal point.
When a node accepts a new focal point, it notifies the previous focal point that it is served by another focal point. When a session between a focal point and the node in its sphere of control is lost, if connectivity to that node exists, the focal point will establish a new session with that node. When that session is lost, the non-focal point node purges all entries in the FP Authorization Table associated with this FP node.
Several advantages accrue to the user of the present invention. Among the advantages are ~1) management of a communication system can be performed at the site or sites specified by personnel responsible for the operation of the sys-tem, (2) the sites can be defined locally without a coordinated system defi-nition, (3) structuring the network among management services focal points can be done by management services discipline (that is, problem management, per-rZ~ ~
.~,, formance, accounting management, configuration management, change management)or within discipline (example, within problem management Alerts of a certain type can be handled at one management services focal point, while all other Alerts are handled at another), (4) the set of nodes for which a management services focal point is responsible for a specific management services function can be changed dynamically without system redefinition, (S) backing up of focal points can be done dynamically, (6) nodes not assigned to a primary focal point can receive focal point services from a secondary, or default, focal point.
While the invention has been particularly shown and described with refer-ence to a preferred embodiment thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.
. .
~J~ ~
A communications network typically consists of a plurality of nodes and communications links interconnecting the nodes. The nodes can act as informa-tion accepting locations (origin nodes), information sink locations (destina-tion nodes) or an intermediate node which passes a message from the origin to the destination. Each node is provided with a plurality of functions which interact and enable the node to perform an assigned task.
Among the many functions which are provided is the so-called "Management Service (MS) Function." This function usually resides in the System Support Control Point (SSCP) of a node. It gathers management information about the network and reports it to an operator. For example, one type of management service may handle error conditions in a network. On the occurrence of a net-work error condition, the management service is made aware of the condition.
The management service in turn notifies a network operator who can take appro-priate steps to correct the error condition.
Currently, networks are managed on a "domain" basis. This means that a network is partitioned into different domains and each SSCP provides management services for resources in its own domain. There are no provisions for cross-domain management. However, there are times when cross-domain management is desirable to effectuate better management of the network. For example, cross domain management is p~eferred where the network is comprised o a relatively large number of domains with each domain requiring an operator.
SUMMARY OF T~IE INVENTION
It is therefore the general object of the present invention to provide an apparatus and method which manage a network more efficiently than was heretofore possible.
1 31 ~758 It is a more specific object of the present invention to provide cross-domain management.
It is still another object of the present invention to provide dynamic management service functions which adapt to compensate for changes in the net-work.
The objectives are achieved by partitioning the network into control nodes which are called focal point nodes (FP nodes) and managed nodes called non-focal point nodes or "NFP Nodes." Each FP node is provided with a "Sphere of Control"
(SOC) table that lists the NFP nodes which are managed by the FP node. As nodes become active in the network, the FP node is made aware of them. The FP node searches its SOC table to see if the node is listed. If the node is listed, the FP node generates and transmits a request message asking it to be its "focal point." If accepted, the NFP node issues a favorable response. The FP node that explicity lists the NFP nodes is called the primary FP. Thereafter, in-formational messages relative to authorized types of management services are exchanged freely between the FP node and the NFP node.
There are at least three types of Request Messages, namely: (a) Request to be your Primary FP, (b) Request to be your Secondary FP, and (c) Requast to be your Backup FP. The Request to be your Backup FP is used between FP nodes.
; In one feature of this invention, an FP node can be designated to provide management services for NFP nodes not listed in the SOC table of other FP nodes.
This FP node is called the secondary FP. The secondary FP issues to an NFP node - a "request to be your secondary FP" message even though the NFP node is not in its SOC table. In this case message (b) is the selected one. This message provides management services for NFP nodes that are not assigned to a Primary FP.
RA988013 Page h The foregoing and other objects and features of this invention will be more fully described in the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 shows a schematic of a network partitioned in accordance with the teachings of the present invention.
Fig. 2 shows a functional diagram of structures for an FP node.
Fig. 3 shows a functional diagram of structures for an NFP node.
Fig. 4 shows FP Management Services (~IS) tables.
Fig. 5 shows NFP (MS) tables.
Figs. 6A-6E show MS Message Formats.
Figs. 7A & B show a flow chart of a program used a~ FP node.
Fig. 8 shows a flow chart of a program used at an NFP Node.
Fig. 9 shows flows demonstrating an NFP Node changing its FP Node.
Fig. 10 shows flows illustrating communications involved in establishing a "backup" FP Node.
DESCRIPTION OF T~IE PREFERRED EMBODIMENT
Fig. 1 shows a block diagram of a communications network which includes the teachings of the present invention. The network of Fig. 1 is merely exemplary as to the number of nodes and is not intended in any way to limit the scope or teaching of the present invention. The network includes a plurality of end nodes (EN) 10', 16', 16", 18', 18" and 20' coupled by respective com-munications link to network nodes ~NN~. The end nodes may include devices such as personal computers, printers, word processing stations, computers, etc.
Computers and other data processing equipment which are end nodes usually do RA988013 Paye 5 not participate in network functions such as routin~, etc. The network nodes ParticiPate in providins ne-twork functions to at-tached end nodes.
Still referring to Fig. 1, the network nodes include focal points (FP) nodes 10 and 14 and non--Focal points (NFP) nodes 12, 16, 18 and 20. The networl< nodes are interconnected by communications links A, B, C, D, E, F and G. As will he explained subsequently, the Focal point nodes provide manasement services for the non-focal point nodes. Stated another way, -the non-focal poin-t nodes such as 16, 18, 20 and 12 are managed or serviced by -focal point nodes 10 and 14. In particular, FP 10 manages or services NFP 12, NFP 1~ and NFP 18. To show that NFP 12, NFP 16 and NFP 18 are manased by FP 10, this srouP
of nodes i9 interconnected by broken lines 22, 24 ancl 26. SimilarlY, Focal POint 14 manages non-focal point node 20 and is interconnected by broken line 28. Thus, in Ficm l tl)e solid interconnecting lines represent communications links while the hroken interconnecting lines represent managemen-t links. I-t should he no-ted -that manasement links are not physical lines in -the ne-twork. rhey are onlY used to show the relationship between managed and manac1ins network nodes. They are also called sessions.
Fig. 2 shows a functional s-truc-t-lre for a focal point node. The structure of the focal POint node is similar to the structure of the well-known APPN nodes. De-tails oF the APPN nodes are set Forth in:
1. "Advallced Program -to Program Communication and Advanced Peer-to-Peer Networking Users Guide", a manual For IBM~ AS~400 system, SC21-9598.
2. "Advanced Peer to Peer Networking (APPN) for AS~400 System, GC24-3287.
131~758 Since the functional structure of the node is well defined, only those components which are necessary to practice and understand the present invention will be described. To that end, the focal point node includes a control point (CP), application (APPL) programs, logical unit (LU), path control, SOC tabls and a plurality of data link control (DLC) modules. The data link control modules provide protocol functions so that messages leàving from a focal point node can be arranged in a desired protocol for transmission over a communication link. Multiple DLC indicates that the FP supports different types of protocols.
The path control module provides the routing function to enable messages to be exchanged between two nodes. The CP provides the control function for the node.
For example, it controls sessions, calculates routes, directory services, etc.
Finally, the LU provides the interface which allows an application program ac-cess into the network. The present invention impacts the conventionaI APPN node and provides improved management services by adding the application programs, and focal point management service (FP~IS) tables. It also makes use of the APPN's topology data base (TDB). Details on each of these components will be given subsequently. Suffice it to say at this point that the addition of these components provides improved methods for managing a network.
Fig. 3 is a functional block diagram for a non-focal point (NFP) node.
The non-focal point node is structurally similar to an APPN node and the focal point node previously described in Fig. 2. This being the case, only the functions which have been added by the present invention will be described.
The added functions include an application program called here a non-focal point managsment services (NFP-MS) program, and the FP authorized table. Details of the added function will be described subsequently. Suffice it to say at this RA988013 1 3 1 q 7 5 8 Page 7 point that the adcded -function causes a non focal point node to respond to -the focal Point nocle and exchange messages whieh eause the non-foeal point node to transmit mallasement services information including error conditions, alerts, etc. -to the focal point node which controls or services the non-Focal point node.
Fig. q shows the tables which are used by the CP of the focal point node. The tables include a Sphere Or Control (SOC) and FP
table. These tahles are used by a Focal Point mana~ement services program. The figure also shows an examPle of topologY data base (TDB~
corresponding to -the ne-twork example sllown in Figure l. The topology data base (TDB) identiFies the topologY o-F network nodes. This ineludes a listing of nodes and links between them with a status indicating whether or not an in-tereonnecting link is eurrently aetive or inaetive. It should be noted tha-t the TDB table is present in all network nodes whether it is a foeal po;nt node or a non-foeal Point node. From this TDB table a node can determine whether or not there is an active connectivi-ty to a c1iverl network node. By way of example, the TDB of Fig. 4 lists the rlocles ancl connectivity For the network in Fig. l. Thus, as can be seen From the table, network node FP lO is connected by links A and C -to network nodes NFP lZ and NFP 16.
Similarly, network node NFP 12 i.5 couplecl via communication links A, B and D to network nodes FP lO, FP 1~l ancl NFP 18, respectively, and so forth. As stated previously, a similar TDB -table i5 provided in a non-foeal point node. An example of a topology data base table whieh can be used irl the present invention is set forth in US Patent 4,644,532.
Still referring to Fi~. 4, the FP managemen-t serviees ~odule includes a sphere of control (SOC) table and a focal point (FP) table. The SOC table ~,~
, contains a list of all network nodes for which this focal point is responsible.
The network operator can dynamically add or delete network node to the SOC table and also display current status for all nodes defined in the SOC table. The table also contains a status (STAT) for each node. Thus, by way of example, MFP 12 is active. Similarly, NFP 20 is revoked (REVOK), etc. Table 1 below shows a listing of status for network nodes and an interpretation for each one.
These will be described more fully in later sections of this document.
-STATUS INTERPRETATION
Active The node is in the sphere of control, connectivity to the nod2 exists and the focal point is actively providing focal point services to this node.
Inactive, Not in Network The FP does not have connectivity to the node.
Inactive, Session Down The FP has lost its management services session with the node and is attempting to re-establish that session.
Rejected The node has rejected FP services. .
Revoked Another FP has taken over as the active FP.
131q758 As can be seen from the above Table 1, when a non-focal point node is marked active in the table, the responsible focal point is providing active focal point services to that node. The other possible states that a non-focal point node may be in are set forth in Table 1 and the associated interpretations are clearly explained. Thus, no further description of Table 1 will be given.
A focal point can be responsible for different management services func-tions for different spheres of control. That is, a single focal point may maintain multiple sphere of control tables, one for each management services focal point function it provides. Associated with each sphere of control table, the focal point management services module contains a record called FP-Table.
This table contains a focal point type field and a list of management services (MS) key fields. This record is transmitted from a focal point node to a non-focal point node in a request focal point authorization message. The FP type field tells what type of focal point the node is and the MS key list identifies the network management services provided by this focal point. Each MS key identifies a specific management service. The present invention defines the following FP types: primary, secondary and backup.
Primary FP- is the FP for the network management category identified by the management services keys (MS-keys), and it provides services for network nodes identified explicitly in the SOC table.
Secondary FP- is the FP for network nodes that were not assigned to a primary FP (not defined in SOC table of any primary FP).
Backup FP- is the FP that backs up another FP. It acts as an FP when the primary FP is not operational.
Table II below shows an example of possible codings for an FP-Table in which the associated FP node is a Primary and Secondary for the management .
1 31 ~75~
services listed in the management services key field. Hex (X) notations are used to code the management services which the node supports. In the preferred embodiment of this invention X'0000' identifies that the FP supports the re-ceiving of Alerts sent by the non focal point nodes, and X'0025' identifies that the FP supports receiving the problem determination stat-stical information.
As is indicated by the dots, other management service keys can be listed in the key field.
TABLE II
FP-TABLE
¦FP-Type ¦List Of MS-Keys ¦bit 1 2 3 ¦X'0000', X'0025' (1 is Primary; 2 is Secondary; 3 is backup) As will be explained subsequently, this focal point record is transmitted with the request message to a non-focal point node;
Fig. 5 shows the focal point authorization table which is present in the non-focal point management service (NFP-MS) node of Fig. 3. The TDB table of Fig. 3 is identical to the previously-described TDB table and therefore further description will not be repeated. The focal point authorization table (Fig.
5) lists focal point names, management services (MS) keys and focal point typ~s.
As will be explained subsequently, when a focal point node sends out a request RA98~013 Page 12 1 31 ~158 message to a non-focal point node, the message includes a focal point name, MS
keys and the Focal Point type.
The non-focal point node uses the information received in the request to update the FP Authorization Table. The non-focal point node uses the informa-tion in the FP Authorization Table to route specific management services data, defined by the specific Management Services key (MS key) -to the appropriate FP
node. The same table also informs the non-focal point node if the management services are provided by the primary or secondary focal point node. The non-focal point node will reject a request received from a secondary FP if the non-FP node is already receiving services from a primary FP for the specific MS Key.
Figs. 6A-6E show formats for the messages which are exchanged between a focal point and a non-focal point node. Figs. 6A-6C show the general management services message format. This message format includes a prefix field, a routing header field, a CP-MSU (management service unit) field, and a suffix field.
The routing header field includes the origin and destination name of the stations involved. By way of example, the origin name would be the name of the station which originates the message while the destination name is the name of the node to which the message is sent. The CP-MSU field (Fig. 6B) is further divided into a length field, general data stream (GDS) ID field and a management service major vector field. In the preferred embodiment of this invention, the GDS ID field carries the notation Hex or X'1212'. This notation indicates that the message is a management services type message. The management services major vector field is further divided into a length field, an MS key field and a data field. As stated before, each of the keys indicate the type of management services which an FP node supports. By way of example, the following MS keys ~A988013 Page 13 are defined: X'OOOO'- indicates an alert, X'0025'- indicates problem determi-nation statistics, X'80FO' indicates MS capabilities request and X'OOFO' indi-cates MS capabilities reply. It should be understood that these keys are merely exemplary and do not limit the invention in any way.
Referring to Figs. 6D and 6E, specific formats which are used for estab-lishing communications between focal point nodes and nodes in the sphere of control table are shown. The format in Fig. 6D is a request format while the format in Fig. 6E is a reply format. Stated another way, the format of Fig.
6D is generated and transmitted to a non-focal point node entering (i.~., be-coming active) in the network. The same format is used for a ;;Request to Be Your Primary FP" or a "Request to Be Your Secondary FP." The message format in Fig. 6E is generated and returned to the focal point node. The format in Fig. 6D includes a length field, MS key field, a length field, a request iden-tifier field, a length field, an FP type field, and a list of MS keys. The request field carries a code indicating that the message is a request. In the preferred embodiment of this invention the code is X'61'. Of course, other codes can be used without deviating from the scope of the present invention.
Each length (L) field in the message indicates the number of bytes which imme-diately follow. The other fields such as the MS key, FP type and list of MS
keys field have already been described and will not be repeated here. Suffice it to say that in a preferred embodiment of the invention the FP-type field (Fig. 6D) includes the following coding X'lO' for Primary FP, X'20' for Sec-ondary FP and X'30' for Backup FP. Likewise, the list of MS-keys includes X'OOOO' and X'0025'. Of course, other codings can be placed in either or both fields without departing from the teachings of thé present invention.
RA98~013 Page 14 The reply message (Fig. 6E) has a structure similar to the request message.
The code X'62' is used to identify that the message is a reply. The reply message also includes a result field which carries information to inform the FP node if the request is accepted, rejected, revoked, etc. In a preferred embodiment of the invention X'10' is an accept, X'20' is a reject and X'30' is a revoke. The list of MS keys is a record of the keys for the services which the non-focal point node accepts.
As described previously, both the non-focal point node and the focal point node carry respective application programs which cause the node to perform functions necessary to provide management services of the present invention.
It is those programs that this document will now describe.
Figs. 7A and 7B show a flow chart of the algorithm or program that xesides at the focal point node. Execution of the program causes the FP node to perform the steps necessary to effectuate the teachings of the present invention. The program comprises of an entry point called a start. From the start, the program descends into block 30 where it waits until the focal point node receives a topology data base update. message or session outage notification or "FP Au-thorization Revoked" message. The topology data base update message (TDU) is regularly provided to update the topology data table that resides in each net-work node. The program then descends into block 31, where it checks to see if a TDU message has been received. If the result is "yes" (Y), the program then descends into block 32. In block 32 the focal point updates the topology data base and checks if a new node has joined the network. The program then descends into decisional block 34. In block 34 the program checks to see if the node which recently became active is defined in its sphere of control table. If it is not defined in the table, the program enters the decisional block 36. In block 36 the program checks to see if the FP type equals secondary for some ~IS
keys. If it is not equal to secondary, the program loops back into block 30.
With reference to block 36, if the focal point type is secondary, the program descends into block 40. In block 40 the program generates and sends a "request to be your secondary focal point" message and descends into block 42 where it waits for a response from the non-focal point node.
Still referring to Figs. 7A and 7B, and with respect to block 34, if the recently active node is defined in the sphere of control table, the program descends into decisional block 44. In block 44 the program checks to see if focal point type equals primary. If it does not, the program ioops back into block 30. Otherwise, the program descends into block 46 where it sends out a "request to be your primary focal point" message. From block 46 the program descents into block 42 where it waits for a response from the non-focal point node and continues when received. The program then descends into decisional block 48. In decisional block 48 the program checks to see if the non-focal point node accepts the focal point. Whether or not the node accepts the focal point (FP) depends on the information carried in the request. Specifically, it depends on the FP-type field and list of MS-key field of the Request Message (Fig. 6D). If the message is a "request to be your secondary FP" and the non-FP
node already has another FP as a primary for the same MS-keys, the node will not accept the request. If the node rejects the request, the program enters block 50 where it checks its table to see if it is a secondary focal point.
If it is, the program loops back to block 30. If it is not, the program then descends into block 52. In block 52 the program notifies the network operator of the rejection and enters rejected in the status column of the sphere of control table (Fig. 4). From block 52 the program then gocs back co start.
,:
131~758 Still referring to Figs. 7A and 7B, and with respect to decisional block 48, if the non-focal point node accepts the focal point as its focal point for the particular type of service, the program descends into block 54. In block 54 the program changes the status in the SOC table to "active" and descends into block 56. In block 56 the focal point can now receive unsolicited management services data from the node. The focal point can also send messages to retrieve data from the serviced network node.
This algorithm is also used initially when an FP program becomes active or when a node is dynamically added to the SOC. When an FP program becomes active, it will first check the TDB and for each non-focal point node defined in the SOC table for which connectivity exists, the FP will use the same algo-rithm as if the node has just joined the network. When a node is added to the SOC table, the FP program first determines if connectivity to that node exists and proceeds from box 41.
Still referring to Figs. 7A and 7B, and with respect to block 31, if a TDU
message has not been received, the program exits along the NO (N) path into block 33. In block 33 the program checks if a "Session Outage Notification"
has been received. If a "Session Outage Notification" has been received, the program descends into block 35 where it updates the status of an NFP node, in the SOC Table, to "Inactive-Session Down" and descends into block 37. In block 37, the program notifies the network operator and returns to start. With ref-erence to block 33, if a "Session Outage Notification" was not received, the program descends into blocl~ 39 where it updates the status of an NFP node, in the SOC table, to "Revoked" and descends into block 37 where it performs the previously described functions.
Fig. 8 shows a flow chart for the algorithm used in a non-focal point node.
From the start block, the program descends into block 60. In block 60 the non-focal point node receives a request message from a focal point node. The program descends into block 62 where it checks to see if the message is a "re^
quest to be your primary focal point" message. If it is, the program checks its FP authorization table (Fig. 5) to see if the node already has a session with another focal point for the same MS- key (block 64). If it does not, the program enters block 66. In block 66 the node sends a "focal point accepted"
reply message to the focal point.
With reference to block 64, if the node has a session with another focal point for the same MS key, the program descends into block 72. In block 72 the program sends "focal point authorization (AUTH) revoked" in the reply message to the current focal point. The program then descends into block 74 where it terminates the session with the current focal point. It should be noted that all sessions are set up and controlled by the LU function in each network node (NN). The program then descends into block 76 where it updates its focal point authorization table (Fig. 5) with the focal point name, MS key, and focal point type from information received in the focal point request message. Thereafter, the node (block 78~ can start sending unsolicited network management information for the category identified by the MS key.
Still referring to Fig. 8 and decisional block 62 in particular, if the answer to the question in block 62 is no, the program descends into decisional block 80. In block 80 the program checks to see if it is a "Request to be Your Secondary Focal Point." If it is not, the program descends into block 70 where it sends the "focal point rejected" reply to the focal point node. Otherwise, from block 80 the program descends into decisional block 82. In decisional 1 31 q758 block 82 the program checks to see if the node has a session with another primary focal point. If the response is yes, the program descends into block 70. If the answer is no, the program descends into block 66. When a non-focal point node loses a session with the FP node, it deletes entries in the FP Authori zation Table associated with this FP node. This completes the description of the programs which are used to implement the present invention.
One of the unique characteristics of the present invention is that non-focal point nodes which are in the SOC of an FP Node can be changed dynamically.
This is illustrated by the flow control schematic in Fig. 9. The network nodes are captioned at the top of the drawing as focal point A, focal point B and node C. Each arrow in this flow diagram shows the direction in which information flows between the nodes. Thus, in step 1 focal point A issues a "request to be your primary focal point" message to node C. This comes about because node C is listed in the sphere of control table of focal point A which establishes a session between itself and node C and then issues the request message. Step 2, noda C accepts the request and issues the "authorization accepted" message to focal point A. In the preferred embodiment of this invention, node A accepts by issuing a control vector X'62' code in the reply message. Step 3 shows focal point B issuing a "request to be your primary focal point" message to node C.
This occurs because node C has just been defined in the SOC table at focal point B. Focal point B establishes a session with node C and issues a "Request to be Your Primary FP" message. Node C accepts the request and issues two mes-sages, one to focal point B accepting the request and one to focal point A (Step 5) revoking the previous authorization. In this particular example~ it shculd be noted that the order of the request from the primary focal point A or B to node C deter:ines which focal poiDt h~s t,e authorization and which authori;
,, 13197~8 zation will be revoked. In this particular example, the focal point which is-sues the second request is deemed to take precedence over an earlier request.
Of course, some other types of priority succession can be arranged without de-viating from the SCOp8 or teachings of the present invention.
One of the request messages that a focal point can generate and ~ransmit to another focal point is a "Request to Be Your Backup Focal Point" message.
The communica~ions which are exchanged between backup focal point B, the primary focal point A and a serviced node such as node X is illustrated in Fig. 10.
If a focal point is defined to provide backup function for another or other focal points, that focal point such as B in the figure, establishes a session with those it backs up. The backup focal point sends a "request to back you up as a focal point" message. The receiving focal point, such as focal point AJ indicates if it supports having that focal point as a backup focal point.
The authori~ation is rejected if the focal point is not a focal point for the keys specified by the backup focal point. With respect to Fig. 9, node X is in the sphere of control table of focal point A. Focal point B, as a backup for focal point A, will attempt to establish a session with node X when the session between A and B is lost and cannot be re-established.
In order for the backup focal point to establish a session with the nodes that are serviced by the primary focal point A, the backup focal point B must have knowledge of the sphere of control of the focal point being backed up (or perhaps a portion of that sphere of control if backup is provided by multiple focal points). When the session between a focal point and its backup fails, the backup focal point attempts to re-establish a session. If that session is re-established, the communications set forth in both 80 and 82 (Fig. 10) are allowed to occur. That is, "the request to back you up as a focal point" message is sent and replied to by the served focal point. However, if the session be-tween a focal point and its backup cannot be re-established, the backup focal point notifies the local operator of this condition, and allows the operator to decide if the backup focal point should attempt to establish sessions with all nodes in that portion of the sphere of control of the lost focal point being backed up. Operator intervention is preferred since the operator may have knowledge of why connectivity to the primary focal point was lost and thus may know if the backup is needed.
If sessions between the backup focal point and node in the backed up sphere of control are established, the "request to be your secondary focal point"
message is sent to each node in the sphere of control of the primary focal point.
The node will accept the secondary as its focal point if it does not have a focal point, otherwise it will reject the request.
Operation In operation, names for a set of managed or serviced network nodes are defined in a sphere of control table at each focal point ncde. Names can be added or deleted dynamically by the focal point operator. As nodes, in an FP
SOC table, become active, the focal point establishes a session with the node and sends it a "Request to be Your Primary Focal Point Message." If the node supports the key for which authorization is being requested, the node replies positively (acknowledging the requestor as its focal point for the specified keys). These keys can identify a particular category of management ser~ices data. If the authorization request is accepted, the node creates an entry in its directory of focal points ~Fig. 5). The entry or entries in the directory of focal points can be used to determine the destination focal point for unso-131q758 licited messages or to determine if a particular focal point is authorized tosend the specific management service request to the node. A password may be included in the request.
If the focal point is not accepted as a foc~l point from the node, the focal point may modify the request to be your focal point message and resubmit it, that is, change the key for which this focal point is requesting authorization, or indicate in its sphere of control table that the node has rejected the focal point request and notify the operator. If the focal point is accepted as a focal point for the node, the focal point receives ali unsolicited management services data as sent by the node for the authorized key or keys.
A focal point is responsible for establishing sessions with each node name appearing in its user defined sphere of control table. The only exceptions are:
nodes to which connectivity does not exist, nodes which reject the "request to be your primary focal point" message and nodes serviced by another focal point.
When a node accepts a new focal point, it notifies the previous focal point that it is served by another focal point. When a session between a focal point and the node in its sphere of control is lost, if connectivity to that node exists, the focal point will establish a new session with that node. When that session is lost, the non-focal point node purges all entries in the FP Authorization Table associated with this FP node.
Several advantages accrue to the user of the present invention. Among the advantages are ~1) management of a communication system can be performed at the site or sites specified by personnel responsible for the operation of the sys-tem, (2) the sites can be defined locally without a coordinated system defi-nition, (3) structuring the network among management services focal points can be done by management services discipline (that is, problem management, per-rZ~ ~
.~,, formance, accounting management, configuration management, change management)or within discipline (example, within problem management Alerts of a certain type can be handled at one management services focal point, while all other Alerts are handled at another), (4) the set of nodes for which a management services focal point is responsible for a specific management services function can be changed dynamically without system redefinition, (S) backing up of focal points can be done dynamically, (6) nodes not assigned to a primary focal point can receive focal point services from a secondary, or default, focal point.
While the invention has been particularly shown and described with refer-ence to a preferred embodiment thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.
. .
Claims (16)
1. An improved method for managing a computer network including a plurality of nodes interconnected by a communications network, said method comprising the steps of:
(a) partitioning the network into at least one Focal Point (FP) node and a plurality of Non-Focal Point (NFP) nodes;
(b) at the Focal Point node, maintaining a sphere of control (SOC) table than includes a listing of names of the Non-Focal Point nodes;
(c) at each Non-Focal Point node, maintaining a Focal Point authorization table with said table at least containing indicia which identifies the Focal Point node;
(d) generating and sending from the Focal Point node to active Non-Focal Point nodes a "Request to be Your Focal Point" message;
(e) for each Non-Focal Point node receiving the message of step (d), responding with an "Accept Request" message only if a Non-Focal Point node ascertains that the Focal Print node is its primary Focal Point node; and (f) thereafter, said each Non Focal Point node generating and forwarding information messages to the Focal Point node.
(a) partitioning the network into at least one Focal Point (FP) node and a plurality of Non-Focal Point (NFP) nodes;
(b) at the Focal Point node, maintaining a sphere of control (SOC) table than includes a listing of names of the Non-Focal Point nodes;
(c) at each Non-Focal Point node, maintaining a Focal Point authorization table with said table at least containing indicia which identifies the Focal Point node;
(d) generating and sending from the Focal Point node to active Non-Focal Point nodes a "Request to be Your Focal Point" message;
(e) for each Non-Focal Point node receiving the message of step (d), responding with an "Accept Request" message only if a Non-Focal Point node ascertains that the Focal Print node is its primary Focal Point node; and (f) thereafter, said each Non Focal Point node generating and forwarding information messages to the Focal Point node.
2. The improved method of claim 1 wherein the information message includes error reports.
3. The improved method of claim 2 further including the step of displaying the error reports at the Focal Point node.
4. In a computer network having a plurality of nodes interconnected by a plurality of communications links an improved method for managing said network comprising the steps of:
(a) partitioning the network into a plurality of Focal Point and a plurality of Non-Focal Point nodes, with each Focal Point node assigned to provide management services to a selected group of Non-Focal Point nodes;
(b) at each Focal Point node, maintaining a sphere of control (SOC) table that includes the names of the Non-Focal Point nodes which are being serviced by that Focal Point node;
(c) at each Non-Focal Point node, maintaining a Focal Point authorization table that includes indicia that identifies Focal Point nodes and the type of management services that the nodes provide;
(d) generating and sending a Focal Point node to active Non-Focal Point nodes a "Request to be Your Focal Point" message;
(e) for selected ones of Non-Focal Point node receiving the message of step (d), responding with an "Accept Request" message only if a Non-Focal Point node determines that the Focal Point node is its servicing node; and (f) thereafter, said selected ones of Non Focal Point node generating and sending to the Focal Point node information messages.
(a) partitioning the network into a plurality of Focal Point and a plurality of Non-Focal Point nodes, with each Focal Point node assigned to provide management services to a selected group of Non-Focal Point nodes;
(b) at each Focal Point node, maintaining a sphere of control (SOC) table that includes the names of the Non-Focal Point nodes which are being serviced by that Focal Point node;
(c) at each Non-Focal Point node, maintaining a Focal Point authorization table that includes indicia that identifies Focal Point nodes and the type of management services that the nodes provide;
(d) generating and sending a Focal Point node to active Non-Focal Point nodes a "Request to be Your Focal Point" message;
(e) for selected ones of Non-Focal Point node receiving the message of step (d), responding with an "Accept Request" message only if a Non-Focal Point node determines that the Focal Point node is its servicing node; and (f) thereafter, said selected ones of Non Focal Point node generating and sending to the Focal Point node information messages.
5. The improved method of claim 4 wherein the "Request to be Your Focal Point" message includes an identification code, and a type of service code which identifies the service the Focal Point node provides.
6. The improved method of claim 4 wherein the Focal Point authorization table includes Focal Point name field containing names of Focal Point nodes and type of service field with indicia indicating the type of service which a named Focal Point node provides to the node.
7. The improved method of claim 6 wherein a responding Non-Focal Point node in step (e) determines that the requesting Focal Point node is the primary servicing node if a type of service code indicia in the "Request to be Your Focal Point" message indicates that the Focal Point is primary.
8. The improved method of claim 6 wherein responding Non-Focal Point nodes of step (e) determine that the requesting Focal Point node is a servicing node if selected indicia in said "Request to be Your Focal Point" message matches selected indicia in said Focal Point authorization table.
9. In a communications network having a plurality of network nodes interconnected by a Plurality of communications links an improved method for exchanging selected information between network nodes comprising the steps of:
(a) selecting at least one network node as a control node;
(b) maintaining in said one control node a list of network nodes which are being controlled by said control node;
(c) maintaining in said one control node; a topology data base which indicates changes in said network;
(d) maintaining in said one control node the list of network nodes and the topology data base; and (e) as a network node becomes active node, issuing a "Request to be Your Focal Point" message to said active node.
(a) selecting at least one network node as a control node;
(b) maintaining in said one control node a list of network nodes which are being controlled by said control node;
(c) maintaining in said one control node; a topology data base which indicates changes in said network;
(d) maintaining in said one control node the list of network nodes and the topology data base; and (e) as a network node becomes active node, issuing a "Request to be Your Focal Point" message to said active node.
10. The method set Forth in claim 9 further including the steps of:
(f) receiving the message at the active node;
(g) examining the message at the active node to determine if the control node is providing primary or secondary management service functions; and (h) generating and transmitting a reply message at the active node accepting or denying the request from said control node.
(f) receiving the message at the active node;
(g) examining the message at the active node to determine if the control node is providing primary or secondary management service functions; and (h) generating and transmitting a reply message at the active node accepting or denying the request from said control node.
11. An improved method for managing a computer network including a plurality of nodes interconnected by a communications network, said method comprising the steps of:
(a) partitioning the network into at least one Focal Point (FP) node and a plurality of Non-Focal Point (NFP) nodes;
(b) at the Focal Point node, maintaining a sphere of control (SOC) table that includes a listing of names of the Non-Focal Point nodes and a set of Management Service (MS) keys identifying services provided by the Focal Point node;
(c) at each Non-Focal Point node, maintaining a Focal Point authorization table with said Focal Point authorization table at least containing indicia which identifies the Focal Point node and Management Service keys;
(d) generating and sending from the Focal Point node to active Non-Focal Point nodes a "Request to be Your Focal Point" message;
(e) for selected ones of Non-Focal Point nodes receiving the message of step (d) responding with an "Accept Request" message only if a Non-Focal Point node ascertains that the Focal Point node is its primary focal point node or if the node lacks a Focal point for specified Management Service keys; and (f) thereafter said selected ones of Non-Focal Point nodes, generating and forwarding informational messages with the specified Management Service keys to the Focal Point node.
(a) partitioning the network into at least one Focal Point (FP) node and a plurality of Non-Focal Point (NFP) nodes;
(b) at the Focal Point node, maintaining a sphere of control (SOC) table that includes a listing of names of the Non-Focal Point nodes and a set of Management Service (MS) keys identifying services provided by the Focal Point node;
(c) at each Non-Focal Point node, maintaining a Focal Point authorization table with said Focal Point authorization table at least containing indicia which identifies the Focal Point node and Management Service keys;
(d) generating and sending from the Focal Point node to active Non-Focal Point nodes a "Request to be Your Focal Point" message;
(e) for selected ones of Non-Focal Point nodes receiving the message of step (d) responding with an "Accept Request" message only if a Non-Focal Point node ascertains that the Focal Point node is its primary focal point node or if the node lacks a Focal point for specified Management Service keys; and (f) thereafter said selected ones of Non-Focal Point nodes, generating and forwarding informational messages with the specified Management Service keys to the Focal Point node.
12. The improved method set forth in claim 11 wherein the network of step (a) is being partitioned into at least two Focal Point nodes.
13. The improved method set forth in claim 12 further including the steps of designating one of the two Focal Point nodes as a Backup Focal Point node; and establishing communications between the Backup Focal Point node, another Focal Point node and the Non-Focal Point nodes so that the Backup Focal Point node assumes responsibility for servicing the Non-Focal Point nodes if said another Focal Point node is disabled.
14. In a computer network having a plurality of computer nodes interconnected by communications links an improved apparatus for managing said network comprising at least one of the computer nodes providing management services to selected ones of said computer nodes; said at least one of the computer nodes including a storage means with a topology data base (TDB) table containing information about structures or activities of said computer nodes or a Focal Point management services table listing the selected ones of said computer nodes or codes representative of management services provided by said one computer node; and a control means located in said one computer node for monitoring said topology data base table or the Focal Point management services table and as the selected ones of said nodes become active, generate and transmit a "Request to he Your Focal Point" message to said nodes.
15. The improved apparatus of claim 14 wherein the "Request to be Your Focal Point" message includes a data Field with coded signals identifying the management services which said at least one of the computer nodes provides.
16. The improved apparatus of claim 14 further including:
means located at the selected ones of said computer nodes for receiving the "Request to be Your Focal Point" message;
means provided in said selected ones of said computer nodes for correlating information contained in the "Request to be Your Focal Point" message with information contained in Focal Point authorization table and for generating and transmitting to said at least one of the computer nodes an "Accept Request" message only if the selected ones of said computer nodes determine that said at least one of the computer nodes is its servicing node.
means located at the selected ones of said computer nodes for receiving the "Request to be Your Focal Point" message;
means provided in said selected ones of said computer nodes for correlating information contained in the "Request to be Your Focal Point" message with information contained in Focal Point authorization table and for generating and transmitting to said at least one of the computer nodes an "Accept Request" message only if the selected ones of said computer nodes determine that said at least one of the computer nodes is its servicing node.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US265,104 | 1988-10-31 | ||
| US07/265,104 US4995035A (en) | 1988-10-31 | 1988-10-31 | Centralized management in a computer network |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA1319758C true CA1319758C (en) | 1993-06-29 |
Family
ID=23009015
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA000607307A Expired - Fee Related CA1319758C (en) | 1988-10-31 | 1989-08-02 | Centralized management in an sna network |
Country Status (7)
| Country | Link |
|---|---|
| US (1) | US4995035A (en) |
| EP (1) | EP0367699B1 (en) |
| JP (1) | JPH0685521B2 (en) |
| BR (1) | BR8905539A (en) |
| CA (1) | CA1319758C (en) |
| DE (1) | DE68915246T2 (en) |
| ES (1) | ES2054078T3 (en) |
Families Citing this family (443)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH0468457A (en) * | 1990-07-09 | 1992-03-04 | Matsushita Electric Ind Co Ltd | Manager device for network control system |
| US5424724A (en) * | 1991-03-27 | 1995-06-13 | International Business Machines Corporation | Method and apparatus for enhanced electronic mail distribution |
| US5457689A (en) * | 1991-04-10 | 1995-10-10 | California Institute Of Technology | High speed polling protocol for multiple node network with sequential flooding of a polling message and a poll-answering message |
| US5321812A (en) * | 1991-04-29 | 1994-06-14 | International Business Machines Corp. | Loop detection and dissolution in a focal point network |
| EP0511925A3 (en) * | 1991-04-30 | 1994-10-19 | Ibm | Dynamic backup and recovery of focal points in a computer network |
| EP0520709A3 (en) * | 1991-06-28 | 1994-08-24 | Digital Equipment Corp | A method for providing a security facility for remote systems management |
| EP0520749B1 (en) * | 1991-06-28 | 1996-12-18 | Digital Equipment Corporation | A method and apparatus for network computer systems management group administration |
| US5272702A (en) * | 1991-08-05 | 1993-12-21 | Fisher Controls International, Inc. | Integrity mapping in data communication system |
| US5758052A (en) * | 1991-10-02 | 1998-05-26 | International Business Machines Corporation | Network management method using redundant distributed control processors |
| US5491796A (en) * | 1992-10-23 | 1996-02-13 | Net Labs, Inc. | Apparatus for remotely managing diverse information network resources |
| US5355364A (en) * | 1992-10-30 | 1994-10-11 | International Business Machines Corporation | Method of routing electronic messages |
| GB2272551B (en) * | 1992-11-14 | 1996-01-17 | Siemens Measurements Ltd | A polled communications network |
| US5701120A (en) * | 1992-12-13 | 1997-12-23 | Siemens Business Communication Systems, Inc. | Partitioned point-to-point communications networks |
| US5574914A (en) * | 1993-01-04 | 1996-11-12 | Unisys Corporation | Method and apparatus for performing system resource partitioning |
| US5574860A (en) * | 1993-03-11 | 1996-11-12 | Digital Equipment Corporation | Method of neighbor discovery over a multiaccess nonbroadcast medium |
| US5515501A (en) * | 1994-01-21 | 1996-05-07 | Unisys Corporation | Redundant maintenance architecture |
| US5586261A (en) * | 1994-11-10 | 1996-12-17 | International Business Machines Corporation | Method and apparatus for interconnecting similar networks using a network of a diffrent type as a virtual link |
| US5603005A (en) * | 1994-12-27 | 1997-02-11 | Unisys Corporation | Cache coherency scheme for XBAR storage structure with delayed invalidates until associated write request is executed |
| US5717942A (en) * | 1994-12-27 | 1998-02-10 | Unisys Corporation | Reset for independent partitions within a computer system |
| US5732086A (en) * | 1995-09-21 | 1998-03-24 | International Business Machines Corporation | System and method for determining the topology of a reconfigurable multi-nodal network |
| US5675768A (en) * | 1996-02-01 | 1997-10-07 | Unisys Corporation | Store software instrumentation package instruction |
| US5793951A (en) * | 1996-05-10 | 1998-08-11 | Apple Computer, Inc. | Security and report generation system for networked multimedia workstations |
| US5909549A (en) * | 1996-11-12 | 1999-06-01 | International Business Machines Corporation | Network management system wherein the managed device reestablishes a connection to a management station after detecting a broken connection |
| US6279098B1 (en) | 1996-12-16 | 2001-08-21 | Unisys Corporation | Method of and apparatus for serial dynamic system partitioning |
| US5960455A (en) * | 1996-12-30 | 1999-09-28 | Unisys Corporation | Scalable cross bar type storage controller |
| US5822766A (en) * | 1997-01-09 | 1998-10-13 | Unisys Corporation | Main memory interface for high speed data transfer |
| US5970253A (en) * | 1997-01-09 | 1999-10-19 | Unisys Corporation | Priority logic for selecting and stacking data |
| US6097727A (en) * | 1997-04-29 | 2000-08-01 | International Business Machines Corporation | Methods, systems and computer program products for end-to-end route selection in compound wide/local area networks |
| US6012092A (en) * | 1997-04-30 | 2000-01-04 | International Business Machines Corp. | Method and system for managing multi-user data flows in environments having minimal bandwidth and computational resources |
| US6112249A (en) | 1997-05-30 | 2000-08-29 | International Business Machines Corporation | Non-disruptively rerouting network communications from a secondary network path to a primary path |
| DE59809429D1 (en) | 1997-07-28 | 2003-10-02 | Siemens Ag | METHOD AND ARRANGEMENT FOR OPERATING A COMMUNICATION NETWORK |
| GB2328352A (en) * | 1997-08-12 | 1999-02-17 | Lucent Technologies Uk Limited | Redundant communication network |
| US7581077B2 (en) * | 1997-10-30 | 2009-08-25 | Commvault Systems, Inc. | Method and system for transferring data in a storage operation |
| US6418478B1 (en) * | 1997-10-30 | 2002-07-09 | Commvault Systems, Inc. | Pipelined high speed data transfer mechanism |
| US7209972B1 (en) | 1997-10-30 | 2007-04-24 | Commvault Systems, Inc. | High speed data transfer mechanism |
| US7277941B2 (en) | 1998-03-11 | 2007-10-02 | Commvault Systems, Inc. | System and method for providing encryption in a storage network by storing a secured encryption key with encrypted archive data in an archive storage device |
| US7739381B2 (en) | 1998-03-11 | 2010-06-15 | Commvault Systems, Inc. | System and method for providing encryption in storage operations in a storage network, such as for use by application service providers that provide data storage services |
| US6976093B2 (en) * | 1998-05-29 | 2005-12-13 | Yahoo! Inc. | Web server content replication |
| US6442592B1 (en) | 1998-12-11 | 2002-08-27 | Micro Computer Systems, Inc. | Message center system |
| US6600727B1 (en) | 1999-05-27 | 2003-07-29 | Cisco Technology, Inc. | Distributed network repeater system |
| US7035880B1 (en) * | 1999-07-14 | 2006-04-25 | Commvault Systems, Inc. | Modular backup and retrieval system used in conjunction with a storage area network |
| US7395282B1 (en) * | 1999-07-15 | 2008-07-01 | Commvault Systems, Inc. | Hierarchical backup and retrieval system |
| US7389311B1 (en) | 1999-07-15 | 2008-06-17 | Commvault Systems, Inc. | Modular backup and retrieval system |
| US7434219B2 (en) * | 2000-01-31 | 2008-10-07 | Commvault Systems, Inc. | Storage of application specific profiles correlating to document versions |
| US7003641B2 (en) | 2000-01-31 | 2006-02-21 | Commvault Systems, Inc. | Logical view with granular access to exchange data managed by a modular data and storage management system |
| US7155481B2 (en) | 2000-01-31 | 2006-12-26 | Commvault Systems, Inc. | Email attachment management in a computer system |
| US6658436B2 (en) * | 2000-01-31 | 2003-12-02 | Commvault Systems, Inc. | Logical view and access to data managed by a modular data and storage management system |
| JP4025501B2 (en) * | 2000-03-03 | 2007-12-19 | 株式会社ソニー・コンピュータエンタテインメント | Music generator |
| US20020161698A1 (en) * | 2000-10-04 | 2002-10-31 | Wical Kelly J. | Caching system using timing queues based on last access times |
| US7539154B1 (en) * | 2000-10-17 | 2009-05-26 | Cisco Technology, Inc. | Method and apparatus to detect and break loop configuration |
| US20020138302A1 (en) * | 2001-03-21 | 2002-09-26 | David Bodnick | Prepaid telecommunication card for health care compliance |
| JP2005505039A (en) * | 2001-09-28 | 2005-02-17 | コムヴォールト・システムズ・インコーポレーテッド | Apparatus and method for archiving objects in an information storage device |
| EP1436873B1 (en) | 2001-09-28 | 2009-04-29 | Commvault Systems, Inc. | System and method for generating and managing quick recovery volumes |
| US8346733B2 (en) | 2006-12-22 | 2013-01-01 | Commvault Systems, Inc. | Systems and methods of media management, such as management of media to and from a media storage library |
| US7603518B2 (en) | 2005-12-19 | 2009-10-13 | Commvault Systems, Inc. | System and method for improved media identification in a storage device |
| US20050033913A1 (en) * | 2003-04-03 | 2005-02-10 | Rajiv Kottomtharayil | Method and system for controlling a robotic arm in a storage device |
| AU2002365580A1 (en) * | 2001-11-23 | 2003-06-10 | Commvault Systems, Inc. | Selective data replication system and method |
| US20030101155A1 (en) * | 2001-11-23 | 2003-05-29 | Parag Gokhale | Method and system for scheduling media exports |
| US7584227B2 (en) * | 2005-12-19 | 2009-09-01 | Commvault Systems, Inc. | System and method for containerized data storage and tracking |
| DE60220375T2 (en) | 2002-04-03 | 2008-02-14 | Alcatel Lucent | Specific data registration server in a telecommunication system operating and management center |
| AU2003270482A1 (en) * | 2002-09-09 | 2004-03-29 | Commvault Systems, Inc. | Dynamic storage device pooling in a computer system |
| US7162496B2 (en) * | 2002-09-16 | 2007-01-09 | Commvault Systems, Inc. | System and method for blind media support |
| US8370542B2 (en) * | 2002-09-16 | 2013-02-05 | Commvault Systems, Inc. | Combined stream auxiliary copy system and method |
| CA2508089A1 (en) * | 2002-10-07 | 2004-04-22 | Commvault Systems, Inc. | System and method for managing stored data |
| WO2004090789A2 (en) | 2003-04-03 | 2004-10-21 | Commvault Systems, Inc. | System and method for extended media retention |
| US7246207B2 (en) | 2003-04-03 | 2007-07-17 | Commvault Systems, Inc. | System and method for dynamically performing storage operations in a computer network |
| WO2004090675A2 (en) * | 2003-04-03 | 2004-10-21 | Commvault Systems, Inc. | System and method for performing storage operations through a firewall |
| US20050039069A1 (en) * | 2003-04-03 | 2005-02-17 | Anand Prahlad | Remote disaster data recovery system and method |
| US7574431B2 (en) * | 2003-05-21 | 2009-08-11 | Digi International Inc. | Remote data collection and control using a custom SNMP MIB |
| DE60309451T2 (en) * | 2003-06-11 | 2007-03-15 | Siemens Ag | Method and apparatus for resolving catastrophic failures of an IP network by providing geographic redundancy |
| US7454569B2 (en) * | 2003-06-25 | 2008-11-18 | Commvault Systems, Inc. | Hierarchical system and method for performing storage operations in a computer network |
| US7440982B2 (en) * | 2003-11-13 | 2008-10-21 | Commvault Systems, Inc. | System and method for stored data archive verification |
| CA2544064C (en) | 2003-11-13 | 2012-02-07 | Commvault Systems, Inc. | System and method for performing integrated storage operations |
| US7613748B2 (en) * | 2003-11-13 | 2009-11-03 | Commvault Systems, Inc. | Stored data reverification management system and method |
| WO2005048085A2 (en) | 2003-11-13 | 2005-05-26 | Commvault Systems, Inc. | System and method for performing an image level snapshot and for restoring partial volume data |
| WO2005050381A2 (en) * | 2003-11-13 | 2005-06-02 | Commvault Systems, Inc. | Systems and methods for performing storage operations using network attached storage |
| WO2005065084A2 (en) * | 2003-11-13 | 2005-07-21 | Commvault Systems, Inc. | System and method for providing encryption in pipelined storage operations in a storage network |
| GB2424297B (en) * | 2003-11-13 | 2007-06-27 | Commvault Systems Inc | System and method for data storage and tracking |
| US8266406B2 (en) | 2004-04-30 | 2012-09-11 | Commvault Systems, Inc. | System and method for allocation of organizational resources |
| US7343356B2 (en) | 2004-04-30 | 2008-03-11 | Commvault Systems, Inc. | Systems and methods for storage modeling and costing |
| WO2006052872A2 (en) | 2004-11-05 | 2006-05-18 | Commvault Systems, Inc. | System and method to support single instance storage operations |
| US7490207B2 (en) * | 2004-11-08 | 2009-02-10 | Commvault Systems, Inc. | System and method for performing auxillary storage operations |
| US8775823B2 (en) | 2006-12-29 | 2014-07-08 | Commvault Systems, Inc. | System and method for encrypting secondary copies of data |
| US8140786B2 (en) * | 2006-12-04 | 2012-03-20 | Commvault Systems, Inc. | Systems and methods for creating copies of data, such as archive copies |
| US8832706B2 (en) | 2006-12-22 | 2014-09-09 | Commvault Systems, Inc. | Systems and methods of data storage management, such as dynamic data stream allocation |
| US8959299B2 (en) | 2004-11-15 | 2015-02-17 | Commvault Systems, Inc. | Using a snapshot as a data source |
| US8112605B2 (en) * | 2005-05-02 | 2012-02-07 | Commvault Systems, Inc. | System and method for allocation of organizational resources |
| US7602906B2 (en) * | 2005-08-25 | 2009-10-13 | Microsoft Corporation | Cipher for disk encryption |
| US20070185926A1 (en) * | 2005-11-28 | 2007-08-09 | Anand Prahlad | Systems and methods for classifying and transferring information in a storage network |
| US8271548B2 (en) * | 2005-11-28 | 2012-09-18 | Commvault Systems, Inc. | Systems and methods for using metadata to enhance storage operations |
| EP1974296B8 (en) | 2005-12-19 | 2016-09-21 | Commvault Systems, Inc. | Systems and methods for performing data replication |
| US8930496B2 (en) | 2005-12-19 | 2015-01-06 | Commvault Systems, Inc. | Systems and methods of unified reconstruction in storage systems |
| US7651593B2 (en) | 2005-12-19 | 2010-01-26 | Commvault Systems, Inc. | Systems and methods for performing data replication |
| US7620710B2 (en) * | 2005-12-19 | 2009-11-17 | Commvault Systems, Inc. | System and method for performing multi-path storage operations |
| WO2007097826A2 (en) * | 2005-12-19 | 2007-08-30 | Commvault Systems, Inc. | System and method for providing a flexible licensing system for digital content |
| US7606844B2 (en) | 2005-12-19 | 2009-10-20 | Commvault Systems, Inc. | System and method for performing replication copy storage operations |
| US7617262B2 (en) | 2005-12-19 | 2009-11-10 | Commvault Systems, Inc. | Systems and methods for monitoring application data in a data replication system |
| US7962709B2 (en) * | 2005-12-19 | 2011-06-14 | Commvault Systems, Inc. | Network redirector systems and methods for performing data replication |
| US8572330B2 (en) | 2005-12-19 | 2013-10-29 | Commvault Systems, Inc. | Systems and methods for granular resource management in a storage network |
| US7636743B2 (en) * | 2005-12-19 | 2009-12-22 | Commvault Systems, Inc. | Pathname translation in a data replication system |
| US7543125B2 (en) * | 2005-12-19 | 2009-06-02 | Commvault Systems, Inc. | System and method for performing time-flexible calendric storage operations |
| US8655850B2 (en) | 2005-12-19 | 2014-02-18 | Commvault Systems, Inc. | Systems and methods for resynchronizing information |
| US20070166674A1 (en) * | 2005-12-19 | 2007-07-19 | Kochunni Jaidev O | Systems and methods for generating configuration metrics in a storage network |
| US7457790B2 (en) * | 2005-12-19 | 2008-11-25 | Commvault Systems, Inc. | Extensible configuration engine system and method |
| US20110010518A1 (en) | 2005-12-19 | 2011-01-13 | Srinivas Kavuri | Systems and Methods for Migrating Components in a Hierarchical Storage Network |
| US20200257596A1 (en) | 2005-12-19 | 2020-08-13 | Commvault Systems, Inc. | Systems and methods of unified reconstruction in storage systems |
| US8248916B2 (en) * | 2005-12-30 | 2012-08-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Recovery methods for restoring service in a distributed radio access network |
| US8248915B2 (en) * | 2005-12-30 | 2012-08-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Redundant session information for a distributed network |
| US8315172B2 (en) * | 2005-12-30 | 2012-11-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Monitoring access nodes in a distributed radio access network |
| US8726242B2 (en) | 2006-07-27 | 2014-05-13 | Commvault Systems, Inc. | Systems and methods for continuous data replication |
| US7539783B2 (en) | 2006-09-22 | 2009-05-26 | Commvault Systems, Inc. | Systems and methods of media management, such as management of media to and from a media storage library, including removable media |
| CN101529419B (en) | 2006-10-17 | 2013-05-01 | 慷孚系统公司 | Method and system for offline indexing of content and classifying stored data |
| US7882077B2 (en) | 2006-10-17 | 2011-02-01 | Commvault Systems, Inc. | Method and system for offline indexing of content and classifying stored data |
| US8655914B2 (en) | 2006-10-17 | 2014-02-18 | Commvault Systems, Inc. | System and method for storage operation access security |
| US8370442B2 (en) | 2008-08-29 | 2013-02-05 | Commvault Systems, Inc. | Method and system for leveraging identified changes to a mail server |
| US20080147878A1 (en) * | 2006-12-15 | 2008-06-19 | Rajiv Kottomtharayil | System and methods for granular resource management in a storage network |
| US8677091B2 (en) | 2006-12-18 | 2014-03-18 | Commvault Systems, Inc. | Writing data and storage system specific metadata to network attached storage device |
| US7840537B2 (en) | 2006-12-22 | 2010-11-23 | Commvault Systems, Inc. | System and method for storing redundant information |
| US8719809B2 (en) * | 2006-12-22 | 2014-05-06 | Commvault Systems, Inc. | Point in time rollback and un-installation of software |
| US8312323B2 (en) | 2006-12-22 | 2012-11-13 | Commvault Systems, Inc. | Systems and methods for remote monitoring in a computer network and reporting a failed migration operation without accessing the data being moved |
| US7831566B2 (en) * | 2006-12-22 | 2010-11-09 | Commvault Systems, Inc. | Systems and methods of hierarchical storage management, such as global management of storage operations |
| US20080155205A1 (en) * | 2006-12-22 | 2008-06-26 | Parag Gokhale | Systems and methods of data storage management, such as dynamic data stream allocation |
| US7734669B2 (en) | 2006-12-22 | 2010-06-08 | Commvault Systems, Inc. | Managing copies of data |
| US20080228771A1 (en) | 2006-12-22 | 2008-09-18 | Commvault Systems, Inc. | Method and system for searching stored data |
| US8290808B2 (en) * | 2007-03-09 | 2012-10-16 | Commvault Systems, Inc. | System and method for automating customer-validated statement of work for a data storage environment |
| US8707070B2 (en) | 2007-08-28 | 2014-04-22 | Commvault Systems, Inc. | Power management of data processing resources, such as power adaptive management of data storage operations |
| US8706976B2 (en) | 2007-08-30 | 2014-04-22 | Commvault Systems, Inc. | Parallel access virtual tape library and drives |
| US8396838B2 (en) * | 2007-10-17 | 2013-03-12 | Commvault Systems, Inc. | Legal compliance, electronic discovery and electronic document handling of online and offline copies of data |
| US8296301B2 (en) | 2008-01-30 | 2012-10-23 | Commvault Systems, Inc. | Systems and methods for probabilistic data classification |
| US7836174B2 (en) * | 2008-01-30 | 2010-11-16 | Commvault Systems, Inc. | Systems and methods for grid-based data scanning |
| US8769048B2 (en) | 2008-06-18 | 2014-07-01 | Commvault Systems, Inc. | Data protection scheduling, such as providing a flexible backup window in a data protection system |
| US8352954B2 (en) | 2008-06-19 | 2013-01-08 | Commvault Systems, Inc. | Data storage resource allocation by employing dynamic methods and blacklisting resource request pools |
| US9128883B2 (en) | 2008-06-19 | 2015-09-08 | Commvault Systems, Inc | Data storage resource allocation by performing abbreviated resource checks based on relative chances of failure of the data storage resources to determine whether data storage requests would fail |
| US8484162B2 (en) | 2008-06-24 | 2013-07-09 | Commvault Systems, Inc. | De-duplication systems and methods for application-specific data |
| US8219524B2 (en) * | 2008-06-24 | 2012-07-10 | Commvault Systems, Inc. | Application-aware and remote single instance data management |
| US9098495B2 (en) | 2008-06-24 | 2015-08-04 | Commvault Systems, Inc. | Application-aware and remote single instance data management |
| US8335776B2 (en) | 2008-07-02 | 2012-12-18 | Commvault Systems, Inc. | Distributed indexing system for data storage |
| US8166263B2 (en) | 2008-07-03 | 2012-04-24 | Commvault Systems, Inc. | Continuous data protection over intermittent connections, such as continuous data backup for laptops or wireless devices |
| US8307177B2 (en) | 2008-09-05 | 2012-11-06 | Commvault Systems, Inc. | Systems and methods for management of virtualization data |
| US8725688B2 (en) | 2008-09-05 | 2014-05-13 | Commvault Systems, Inc. | Image level copy or restore, such as image level restore without knowledge of data object metadata |
| US20100070474A1 (en) | 2008-09-12 | 2010-03-18 | Lad Kamleshkumar K | Transferring or migrating portions of data objects, such as block-level data migration or chunk-based data migration |
| US20100070466A1 (en) * | 2008-09-15 | 2010-03-18 | Anand Prahlad | Data transfer techniques within data storage devices, such as network attached storage performing data migration |
| US9015181B2 (en) * | 2008-09-26 | 2015-04-21 | Commvault Systems, Inc. | Systems and methods for managing single instancing data |
| AU2009296695B2 (en) | 2008-09-26 | 2013-08-01 | Commvault Systems, Inc. | Systems and methods for managing single instancing data |
| US9178842B2 (en) | 2008-11-05 | 2015-11-03 | Commvault Systems, Inc. | Systems and methods for monitoring messaging applications for compliance with a policy |
| US8412677B2 (en) * | 2008-11-26 | 2013-04-02 | Commvault Systems, Inc. | Systems and methods for byte-level or quasi byte-level single instancing |
| US8204859B2 (en) | 2008-12-10 | 2012-06-19 | Commvault Systems, Inc. | Systems and methods for managing replicated database data |
| US9495382B2 (en) * | 2008-12-10 | 2016-11-15 | Commvault Systems, Inc. | Systems and methods for performing discrete data replication |
| US8943183B2 (en) | 2008-12-10 | 2015-01-27 | Commvault Systems, Inc. | Decoupled installation of data management systems |
| US8434131B2 (en) | 2009-03-20 | 2013-04-30 | Commvault Systems, Inc. | Managing connections in a data storage system |
| US8401996B2 (en) | 2009-03-30 | 2013-03-19 | Commvault Systems, Inc. | Storing a variable number of instances of data objects |
| US8209307B2 (en) | 2009-03-31 | 2012-06-26 | Commvault Systems, Inc. | Systems and methods for data migration in a clustered file system |
| US8315981B2 (en) * | 2009-03-31 | 2012-11-20 | Commvault Systems, Inc. | Data mining systems and methods for heterogeneous data sources |
| CN101551736B (en) * | 2009-05-20 | 2010-11-03 | 杭州华三通信技术有限公司 | Cache management device and method based on address pointer linked list |
| US8578120B2 (en) | 2009-05-22 | 2013-11-05 | Commvault Systems, Inc. | Block-level single instancing |
| US8849955B2 (en) | 2009-06-30 | 2014-09-30 | Commvault Systems, Inc. | Cloud storage and networking agents, including agents for utilizing multiple, different cloud storage sites |
| US8930306B1 (en) | 2009-07-08 | 2015-01-06 | Commvault Systems, Inc. | Synchronized data deduplication |
| US8706867B2 (en) | 2011-03-31 | 2014-04-22 | Commvault Systems, Inc. | Realtime streaming of multimedia content from secondary storage devices |
| US9092500B2 (en) | 2009-09-03 | 2015-07-28 | Commvault Systems, Inc. | Utilizing snapshots for access to databases and other applications |
| US8719767B2 (en) | 2011-03-31 | 2014-05-06 | Commvault Systems, Inc. | Utilizing snapshots to provide builds to developer computing devices |
| US8433682B2 (en) | 2009-12-31 | 2013-04-30 | Commvault Systems, Inc. | Systems and methods for analyzing snapshots |
| US8442983B2 (en) | 2009-12-31 | 2013-05-14 | Commvault Systems, Inc. | Asynchronous methods of data classification using change journals and other data structures |
| EP2519872A4 (en) | 2009-12-31 | 2015-08-26 | Commvault Systems Inc | Systems and methods for performing data management operations using snapshots |
| US8202205B2 (en) * | 2010-02-09 | 2012-06-19 | GoBe Healthy, LLC | Omni-directional exercise device |
| US8504517B2 (en) * | 2010-03-29 | 2013-08-06 | Commvault Systems, Inc. | Systems and methods for selective data replication |
| US8352422B2 (en) | 2010-03-30 | 2013-01-08 | Commvault Systems, Inc. | Data restore systems and methods in a replication environment |
| US8725698B2 (en) | 2010-03-30 | 2014-05-13 | Commvault Systems, Inc. | Stub file prioritization in a data replication system |
| US8504515B2 (en) | 2010-03-30 | 2013-08-06 | Commvault Systems, Inc. | Stubbing systems and methods in a data replication environment |
| US8572719B2 (en) | 2010-05-28 | 2013-10-29 | Commvault Systems, Inc. | Firewall proxy systems and methods in a backup environment |
| US8589347B2 (en) | 2010-05-28 | 2013-11-19 | Commvault Systems, Inc. | Systems and methods for performing data replication |
| US11449394B2 (en) | 2010-06-04 | 2022-09-20 | Commvault Systems, Inc. | Failover systems and methods for performing backup operations, including heterogeneous indexing and load balancing of backup and indexing resources |
| US8504526B2 (en) | 2010-06-04 | 2013-08-06 | Commvault Systems, Inc. | Failover systems and methods for performing backup operations |
| US8504869B2 (en) | 2010-07-16 | 2013-08-06 | Commvault Systems, Inc. | Kernel swapping systems and methods for recovering a network device |
| US8495420B2 (en) | 2010-07-16 | 2013-07-23 | Commvault Systems, Inc. | Registry key federation systems and methods |
| WO2012045021A2 (en) | 2010-09-30 | 2012-04-05 | Commvault Systems, Inc. | Efficient data management improvements, such as docking limited-feature data management modules to a full-featured data management system |
| US8577851B2 (en) | 2010-09-30 | 2013-11-05 | Commvault Systems, Inc. | Content aligned block-based deduplication |
| US8935492B2 (en) | 2010-09-30 | 2015-01-13 | Commvault Systems, Inc. | Archiving data objects using secondary copies |
| US8578109B2 (en) | 2010-09-30 | 2013-11-05 | Commvault Systems, Inc. | Systems and methods for retaining and using data block signatures in data protection operations |
| US9244779B2 (en) | 2010-09-30 | 2016-01-26 | Commvault Systems, Inc. | Data recovery operations, such as recovery from modified network data management protocol data |
| KR20120050367A (en) * | 2010-11-10 | 2012-05-18 | 삼성전자주식회사 | Method and apparatus for providing service using personal network |
| US8954446B2 (en) | 2010-12-14 | 2015-02-10 | Comm Vault Systems, Inc. | Client-side repository in a networked deduplicated storage system |
| US9020900B2 (en) | 2010-12-14 | 2015-04-28 | Commvault Systems, Inc. | Distributed deduplicated storage system |
| US9021198B1 (en) | 2011-01-20 | 2015-04-28 | Commvault Systems, Inc. | System and method for sharing SAN storage |
| US9680567B2 (en) | 2011-03-03 | 2017-06-13 | Acacia Communications, Inc. | Fault localization and fiber security in optical transponders |
| US8719264B2 (en) | 2011-03-31 | 2014-05-06 | Commvault Systems, Inc. | Creating secondary copies of data based on searches for content |
| US8849762B2 (en) | 2011-03-31 | 2014-09-30 | Commvault Systems, Inc. | Restoring computing environments, such as autorecovery of file systems at certain points in time |
| US9323466B2 (en) | 2011-04-27 | 2016-04-26 | Commvault Systems, Inc. | System and method for client policy assignment in a data storage system |
| US9372827B2 (en) | 2011-09-30 | 2016-06-21 | Commvault Systems, Inc. | Migration of an existing computing system to new hardware |
| US9461881B2 (en) | 2011-09-30 | 2016-10-04 | Commvault Systems, Inc. | Migration of existing computing systems to cloud computing sites or virtual machines |
| US9116633B2 (en) | 2011-09-30 | 2015-08-25 | Commvault Systems, Inc. | Information management of virtual machines having mapped storage devices |
| US20130227352A1 (en) | 2012-02-24 | 2013-08-29 | Commvault Systems, Inc. | Log monitoring |
| US9471578B2 (en) | 2012-03-07 | 2016-10-18 | Commvault Systems, Inc. | Data storage system utilizing proxy device for storage operations |
| US9298715B2 (en) | 2012-03-07 | 2016-03-29 | Commvault Systems, Inc. | Data storage system utilizing proxy device for storage operations |
| US20130253977A1 (en) | 2012-03-23 | 2013-09-26 | Commvault Systems, Inc. | Automation of data storage activities |
| US9262496B2 (en) | 2012-03-30 | 2016-02-16 | Commvault Systems, Inc. | Unified access to personal data |
| US8950009B2 (en) | 2012-03-30 | 2015-02-03 | Commvault Systems, Inc. | Information management of data associated with multiple cloud services |
| US9020890B2 (en) | 2012-03-30 | 2015-04-28 | Commvault Systems, Inc. | Smart archiving and data previewing for mobile devices |
| WO2013148096A1 (en) | 2012-03-30 | 2013-10-03 | Commvault Systems, Inc. | Informaton management of mobile device data |
| US9063938B2 (en) | 2012-03-30 | 2015-06-23 | Commvault Systems, Inc. | Search filtered file system using secondary storage, including multi-dimensional indexing and searching of archived files |
| US9286327B2 (en) | 2012-03-30 | 2016-03-15 | Commvault Systems, Inc. | Data storage recovery automation |
| US9639297B2 (en) | 2012-03-30 | 2017-05-02 | Commvault Systems, Inc | Shared network-available storage that permits concurrent data access |
| US10157184B2 (en) | 2012-03-30 | 2018-12-18 | Commvault Systems, Inc. | Data previewing before recalling large data files |
| US9342537B2 (en) | 2012-04-23 | 2016-05-17 | Commvault Systems, Inc. | Integrated snapshot interface for a data storage system |
| US9189167B2 (en) | 2012-05-31 | 2015-11-17 | Commvault Systems, Inc. | Shared library in a data storage system |
| US8892523B2 (en) | 2012-06-08 | 2014-11-18 | Commvault Systems, Inc. | Auto summarization of content |
| US8977672B2 (en) | 2012-06-08 | 2015-03-10 | Commvault Systems, Inc. | Intelligent scheduling for remote computers |
| US9189170B2 (en) | 2012-06-12 | 2015-11-17 | Commvault Systems, Inc. | External storage manager for a data storage cell |
| US20130339298A1 (en) | 2012-06-13 | 2013-12-19 | Commvault Systems, Inc. | Collaborative backup in a networked storage system |
| US20140025796A1 (en) | 2012-07-19 | 2014-01-23 | Commvault Systems, Inc. | Automated grouping of computing devices in a networked data storage system |
| US9275086B2 (en) | 2012-07-20 | 2016-03-01 | Commvault Systems, Inc. | Systems and methods for database archiving |
| US20140040580A1 (en) | 2012-07-31 | 2014-02-06 | Commvault Systems, Inc. | Administering a shared, on-line pool of data storage resources for performing data storage operations |
| US9026498B2 (en) | 2012-08-13 | 2015-05-05 | Commvault Systems, Inc. | Lightweight mounting of a secondary copy of file system data |
| US8938481B2 (en) | 2012-08-13 | 2015-01-20 | Commvault Systems, Inc. | Generic file level restore from a block-level secondary copy |
| US9747169B2 (en) | 2012-12-21 | 2017-08-29 | Commvault Systems, Inc. | Reporting using data obtained during backup of primary storage |
| US10379988B2 (en) | 2012-12-21 | 2019-08-13 | Commvault Systems, Inc. | Systems and methods for performance monitoring |
| US9223597B2 (en) | 2012-12-21 | 2015-12-29 | Commvault Systems, Inc. | Archiving virtual machines in a data storage system |
| US20140181085A1 (en) | 2012-12-21 | 2014-06-26 | Commvault Systems, Inc. | Data storage system for analysis of data across heterogeneous information management systems |
| US9201906B2 (en) | 2012-12-21 | 2015-12-01 | Commvault Systems, Inc. | Systems and methods to perform data backup in data storage systems |
| US20140181047A1 (en) | 2012-12-21 | 2014-06-26 | Commvault Systems, Inc. | Systems and methods to protect deleted files |
| US9740702B2 (en) | 2012-12-21 | 2017-08-22 | Commvault Systems, Inc. | Systems and methods to identify unprotected virtual machines |
| US9633216B2 (en) | 2012-12-27 | 2017-04-25 | Commvault Systems, Inc. | Application of information management policies based on operation with a geographic entity |
| US9069799B2 (en) | 2012-12-27 | 2015-06-30 | Commvault Systems, Inc. | Restoration of centralized data storage manager, such as data storage manager in a hierarchical data storage system |
| US9021452B2 (en) | 2012-12-27 | 2015-04-28 | Commvault Systems, Inc. | Automatic identification of storage requirements, such as for use in selling data storage management solutions |
| US9378035B2 (en) | 2012-12-28 | 2016-06-28 | Commvault Systems, Inc. | Systems and methods for repurposing virtual machines |
| US10346259B2 (en) | 2012-12-28 | 2019-07-09 | Commvault Systems, Inc. | Data recovery using a cloud-based remote data recovery center |
| US9633022B2 (en) | 2012-12-28 | 2017-04-25 | Commvault Systems, Inc. | Backup and restoration for a deduplicated file system |
| US20140196038A1 (en) | 2013-01-08 | 2014-07-10 | Commvault Systems, Inc. | Virtual machine management in a data storage system |
| US9760444B2 (en) | 2013-01-11 | 2017-09-12 | Commvault Systems, Inc. | Sharing of secondary storage data |
| US9846620B2 (en) | 2013-01-11 | 2017-12-19 | Commvault Systems, Inc. | Table level database restore in a data storage system |
| US9804930B2 (en) | 2013-01-11 | 2017-10-31 | Commvault Systems, Inc. | Partial file restore in a data storage system |
| US9886346B2 (en) | 2013-01-11 | 2018-02-06 | Commvault Systems, Inc. | Single snapshot for multiple agents |
| US9495404B2 (en) | 2013-01-11 | 2016-11-15 | Commvault Systems, Inc. | Systems and methods to process block-level backup for selective file restoration for virtual machines |
| US9665591B2 (en) | 2013-01-11 | 2017-05-30 | Commvault Systems, Inc. | High availability distributed deduplicated storage system |
| US9262435B2 (en) | 2013-01-11 | 2016-02-16 | Commvault Systems, Inc. | Location-based data synchronization management |
| US9286110B2 (en) | 2013-01-14 | 2016-03-15 | Commvault Systems, Inc. | Seamless virtual machine recall in a data storage system |
| US9483489B2 (en) | 2013-01-14 | 2016-11-01 | Commvault Systems, Inc. | Partial sharing of secondary storage files in a data storage system |
| US9459968B2 (en) | 2013-03-11 | 2016-10-04 | Commvault Systems, Inc. | Single index to query multiple backup formats |
| US20140281516A1 (en) | 2013-03-12 | 2014-09-18 | Commvault Systems, Inc. | Automatic file decryption |
| US9934103B2 (en) | 2013-04-16 | 2018-04-03 | Commvault Systems, Inc. | Managing multi-source restore operations in an information management system |
| US9483361B2 (en) | 2013-05-08 | 2016-11-01 | Commvault Systems, Inc. | Information management cell with failover management capability |
| US9483558B2 (en) | 2013-05-29 | 2016-11-01 | Commvault Systems, Inc. | Assessing user performance in a community of users of data storage resources |
| US9939981B2 (en) | 2013-09-12 | 2018-04-10 | Commvault Systems, Inc. | File manager integration with virtualization in an information management system with an enhanced storage manager, including user control and storage management of virtual machines |
| US9590886B2 (en) | 2013-11-01 | 2017-03-07 | Commvault Systems, Inc. | Systems and methods for differential health checking of an information management system |
| US10949382B2 (en) | 2014-01-15 | 2021-03-16 | Commvault Systems, Inc. | User-centric interfaces for information management systems |
| US9639426B2 (en) | 2014-01-24 | 2017-05-02 | Commvault Systems, Inc. | Single snapshot for multiple applications |
| US9495251B2 (en) | 2014-01-24 | 2016-11-15 | Commvault Systems, Inc. | Snapshot readiness checking and reporting |
| US9753812B2 (en) | 2014-01-24 | 2017-09-05 | Commvault Systems, Inc. | Generating mapping information for single snapshot for multiple applications |
| US9632874B2 (en) | 2014-01-24 | 2017-04-25 | Commvault Systems, Inc. | Database application backup in single snapshot for multiple applications |
| US10324897B2 (en) | 2014-01-27 | 2019-06-18 | Commvault Systems, Inc. | Techniques for serving archived electronic mail |
| US9798596B2 (en) | 2014-02-27 | 2017-10-24 | Commvault Systems, Inc. | Automatic alert escalation for an information management system |
| US9648100B2 (en) | 2014-03-05 | 2017-05-09 | Commvault Systems, Inc. | Cross-system storage management for transferring data across autonomous information management systems |
| US9633026B2 (en) | 2014-03-13 | 2017-04-25 | Commvault Systems, Inc. | Systems and methods for protecting email data |
| US10380072B2 (en) | 2014-03-17 | 2019-08-13 | Commvault Systems, Inc. | Managing deletions from a deduplication database |
| US9633056B2 (en) | 2014-03-17 | 2017-04-25 | Commvault Systems, Inc. | Maintaining a deduplication database |
| US9811427B2 (en) | 2014-04-02 | 2017-11-07 | Commvault Systems, Inc. | Information management by a media agent in the absence of communications with a storage manager |
| US9823978B2 (en) | 2014-04-16 | 2017-11-21 | Commvault Systems, Inc. | User-level quota management of data objects stored in information management systems |
| US9740574B2 (en) | 2014-05-09 | 2017-08-22 | Commvault Systems, Inc. | Load balancing across multiple data paths |
| US9848045B2 (en) | 2014-05-27 | 2017-12-19 | Commvault Systems, Inc. | Offline messaging between a repository storage operation cell and remote storage operation cells via an intermediary media agent |
| US9760446B2 (en) | 2014-06-11 | 2017-09-12 | Micron Technology, Inc. | Conveying value of implementing an integrated data management and protection system |
| US20160004605A1 (en) | 2014-07-01 | 2016-01-07 | Commvault Systems, Inc. | Lightweight data reconstruction based on backup data |
| US20160019317A1 (en) | 2014-07-16 | 2016-01-21 | Commvault Systems, Inc. | Volume or virtual machine level backup and generating placeholders for virtual machine files |
| US20160019117A1 (en) | 2014-07-16 | 2016-01-21 | Commvault Systems, Inc. | Creating customized bootable image for client computing device from backup copy |
| US20160019224A1 (en) | 2014-07-18 | 2016-01-21 | Commvault Systems, Inc. | File system content archiving based on third-party application archiving rules and metadata |
| US10031917B2 (en) | 2014-07-29 | 2018-07-24 | Commvault Systems, Inc. | Efficient volume-level replication of data via snapshots in an information management system |
| US9641388B2 (en) | 2014-07-29 | 2017-05-02 | Commvault Systems, Inc. | Customized deployment in information management systems |
| US10360110B2 (en) | 2014-08-06 | 2019-07-23 | Commvault Systems, Inc. | Point-in-time backups of a production application made accessible over fibre channel and/or iSCSI as data sources to a remote application by representing the backups as pseudo-disks operating apart from the production application and its host |
| US11249858B2 (en) | 2014-08-06 | 2022-02-15 | Commvault Systems, Inc. | Point-in-time backups of a production application made accessible over fibre channel and/or ISCSI as data sources to a remote application by representing the backups as pseudo-disks operating apart from the production application and its host |
| US9852026B2 (en) | 2014-08-06 | 2017-12-26 | Commvault Systems, Inc. | Efficient application recovery in an information management system based on a pseudo-storage-device driver |
| US10042716B2 (en) | 2014-09-03 | 2018-08-07 | Commvault Systems, Inc. | Consolidated processing of storage-array commands using a forwarder media agent in conjunction with a snapshot-control media agent |
| US9774672B2 (en) | 2014-09-03 | 2017-09-26 | Commvault Systems, Inc. | Consolidated processing of storage-array commands by a snapshot-control media agent |
| US9405928B2 (en) | 2014-09-17 | 2016-08-02 | Commvault Systems, Inc. | Deriving encryption rules based on file content |
| US9710465B2 (en) | 2014-09-22 | 2017-07-18 | Commvault Systems, Inc. | Efficiently restoring execution of a backed up virtual machine based on coordination with virtual-machine-file-relocation operations |
| US9436555B2 (en) | 2014-09-22 | 2016-09-06 | Commvault Systems, Inc. | Efficient live-mount of a backed up virtual machine in a storage management system |
| US9417968B2 (en) | 2014-09-22 | 2016-08-16 | Commvault Systems, Inc. | Efficiently restoring execution of a backed up virtual machine based on coordination with virtual-machine-file-relocation operations |
| US10204010B2 (en) | 2014-10-03 | 2019-02-12 | Commvault Systems, Inc. | Intelligent protection of off-line mail data |
| US9609058B2 (en) | 2014-10-13 | 2017-03-28 | Commvault Systems, Inc. | Storage management operations based on executable files served on demand to storage management components |
| US9444811B2 (en) | 2014-10-21 | 2016-09-13 | Commvault Systems, Inc. | Using an enhanced data agent to restore backed up data across autonomous storage management systems |
| US9575673B2 (en) | 2014-10-29 | 2017-02-21 | Commvault Systems, Inc. | Accessing a file system using tiered deduplication |
| US10776209B2 (en) | 2014-11-10 | 2020-09-15 | Commvault Systems, Inc. | Cross-platform virtual machine backup and replication |
| US9848046B2 (en) | 2014-11-13 | 2017-12-19 | Commvault Systems, Inc. | Archiving applications in information management systems |
| US9448731B2 (en) | 2014-11-14 | 2016-09-20 | Commvault Systems, Inc. | Unified snapshot storage management |
| US9648105B2 (en) | 2014-11-14 | 2017-05-09 | Commvault Systems, Inc. | Unified snapshot storage management, using an enhanced storage manager and enhanced media agents |
| US20160142485A1 (en) | 2014-11-19 | 2016-05-19 | Commvault Systems, Inc. | Migration to cloud storage from backup |
| US9983936B2 (en) | 2014-11-20 | 2018-05-29 | Commvault Systems, Inc. | Virtual machine change block tracking |
| US20160162364A1 (en) | 2014-12-03 | 2016-06-09 | Commvault Systems, Inc. | Secondary storage pruning |
| US9632713B2 (en) | 2014-12-03 | 2017-04-25 | Commvault Systems, Inc. | Secondary storage editor |
| US9645891B2 (en) | 2014-12-04 | 2017-05-09 | Commvault Systems, Inc. | Opportunistic execution of secondary copy operations |
| US9753816B2 (en) | 2014-12-05 | 2017-09-05 | Commvault Systems, Inc. | Synchronization based on filtered browsing |
| US20160210044A1 (en) | 2015-01-15 | 2016-07-21 | Commvault Systems, Inc. | Intelligent hybrid drive caching |
| US20160210306A1 (en) | 2015-01-15 | 2016-07-21 | Commvault Systems, Inc. | Managing structured data in a data storage system |
| US9952934B2 (en) | 2015-01-20 | 2018-04-24 | Commvault Systems, Inc. | Synchronizing selected portions of data in a storage management system |
| US9588849B2 (en) | 2015-01-20 | 2017-03-07 | Commvault Systems, Inc. | Synchronizing selected portions of data in a storage management system |
| US10108687B2 (en) | 2015-01-21 | 2018-10-23 | Commvault Systems, Inc. | Database protection using block-level mapping |
| US9898213B2 (en) | 2015-01-23 | 2018-02-20 | Commvault Systems, Inc. | Scalable auxiliary copy processing using media agent resources |
| US9904481B2 (en) | 2015-01-23 | 2018-02-27 | Commvault Systems, Inc. | Scalable auxiliary copy processing in a storage management system using media agent resources |
| US10313243B2 (en) | 2015-02-24 | 2019-06-04 | Commvault Systems, Inc. | Intelligent local management of data stream throttling in secondary-copy operations |
| US10956299B2 (en) | 2015-02-27 | 2021-03-23 | Commvault Systems, Inc. | Diagnosing errors in data storage and archiving in a cloud or networking environment |
| US9575804B2 (en) | 2015-03-27 | 2017-02-21 | Commvault Systems, Inc. | Job management and resource allocation |
| US9928144B2 (en) | 2015-03-30 | 2018-03-27 | Commvault Systems, Inc. | Storage management of data using an open-archive architecture, including streamlined access to primary data originally stored on network-attached storage and archived to secondary storage |
| US10339106B2 (en) | 2015-04-09 | 2019-07-02 | Commvault Systems, Inc. | Highly reusable deduplication database after disaster recovery |
| US9934265B2 (en) | 2015-04-09 | 2018-04-03 | Commvault Systems, Inc. | Management of log data |
| US10311150B2 (en) | 2015-04-10 | 2019-06-04 | Commvault Systems, Inc. | Using a Unix-based file system to manage and serve clones to windows-based computing clients |
| US9710253B2 (en) | 2015-04-16 | 2017-07-18 | Commvault Systems, Inc. | Managing a software-patch submission queue |
| US9904598B2 (en) | 2015-04-21 | 2018-02-27 | Commvault Systems, Inc. | Content-independent and database management system-independent synthetic full backup of a database based on snapshot technology |
| US9639286B2 (en) | 2015-05-14 | 2017-05-02 | Commvault Systems, Inc. | Restore of secondary data using thread pooling |
| US10324914B2 (en) | 2015-05-20 | 2019-06-18 | Commvalut Systems, Inc. | Handling user queries against production and archive storage systems, such as for enterprise customers having large and/or numerous files |
| US20160350391A1 (en) | 2015-05-26 | 2016-12-01 | Commvault Systems, Inc. | Replication using deduplicated secondary copy data |
| US9563514B2 (en) | 2015-06-19 | 2017-02-07 | Commvault Systems, Inc. | Assignment of proxies for virtual-machine secondary copy operations including streaming backup jobs |
| US10084873B2 (en) | 2015-06-19 | 2018-09-25 | Commvault Systems, Inc. | Assignment of data agent proxies for executing virtual-machine secondary copy operations including streaming backup jobs |
| US10275320B2 (en) | 2015-06-26 | 2019-04-30 | Commvault Systems, Inc. | Incrementally accumulating in-process performance data and hierarchical reporting thereof for a data stream in a secondary copy operation |
| US9766825B2 (en) | 2015-07-22 | 2017-09-19 | Commvault Systems, Inc. | Browse and restore for block-level backups |
| US10192065B2 (en) | 2015-08-31 | 2019-01-29 | Commvault Systems, Inc. | Automated intelligent provisioning of data storage resources in response to user requests in a data storage management system |
| US10101913B2 (en) | 2015-09-02 | 2018-10-16 | Commvault Systems, Inc. | Migrating data to disk without interrupting running backup operations |
| EP3350728B1 (en) | 2015-09-18 | 2022-04-06 | Commvault Systems, Inc. | Data storage management operations in a secondary storage subsystem using image recognition and image-based criteria |
| US10514986B2 (en) | 2015-09-30 | 2019-12-24 | Commvault Systems, Inc. | Dynamic triggering of block-level backups based on block change thresholds and corresponding file identities in a data storage management system |
| US10176036B2 (en) | 2015-10-29 | 2019-01-08 | Commvault Systems, Inc. | Monitoring, diagnosing, and repairing a management database in a data storage management system |
| US10353994B2 (en) | 2015-11-03 | 2019-07-16 | Commvault Systems, Inc. | Summarization of email on a client computing device based on content contribution to an email thread using classification and word frequency considerations |
| US10228962B2 (en) | 2015-12-09 | 2019-03-12 | Commvault Systems, Inc. | Live synchronization and management of virtual machines across computing and virtualization platforms and using live synchronization to support disaster recovery |
| US10387266B2 (en) | 2015-12-23 | 2019-08-20 | Commvault Systems, Inc. | Application-level live synchronization across computing platforms including synchronizing co-resident applications to disparate standby destinations and selectively synchronizing some applications and not others |
| US20170192868A1 (en) | 2015-12-30 | 2017-07-06 | Commvault Systems, Inc. | User interface for identifying a location of a failed secondary storage device |
| US10684924B2 (en) | 2016-02-18 | 2020-06-16 | Commvault Systems, Inc. | Data restoration operations based on network path information |
| US10296368B2 (en) | 2016-03-09 | 2019-05-21 | Commvault Systems, Inc. | Hypervisor-independent block-level live browse for access to backed up virtual machine (VM) data and hypervisor-free file-level recovery (block-level pseudo-mount) |
| US10452490B2 (en) | 2016-03-09 | 2019-10-22 | Commvault Systems, Inc. | Data management and backup of distributed storage environment |
| US10592350B2 (en) | 2016-03-09 | 2020-03-17 | Commvault Systems, Inc. | Virtual server cloud file system for virtual machine restore to cloud operations |
| US10503753B2 (en) | 2016-03-10 | 2019-12-10 | Commvault Systems, Inc. | Snapshot replication operations based on incremental block change tracking |
| US10248174B2 (en) | 2016-05-24 | 2019-04-02 | Hedvig, Inc. | Persistent reservations for virtual disk using multiple targets |
| US10664447B2 (en) | 2016-07-12 | 2020-05-26 | Commvault Systems, Inc. | Dynamic management of expandable cache storage for multiple network shares configured in a file server |
| US10417102B2 (en) | 2016-09-30 | 2019-09-17 | Commvault Systems, Inc. | Heartbeat monitoring of virtual machines for initiating failover operations in a data storage management system, including virtual machine distribution logic |
| US10540516B2 (en) | 2016-10-13 | 2020-01-21 | Commvault Systems, Inc. | Data protection within an unsecured storage environment |
| US10152251B2 (en) | 2016-10-25 | 2018-12-11 | Commvault Systems, Inc. | Targeted backup of virtual machine |
| US10210048B2 (en) | 2016-10-25 | 2019-02-19 | Commvault Systems, Inc. | Selective snapshot and backup copy operations for individual virtual machines in a shared storage |
| US10162528B2 (en) | 2016-10-25 | 2018-12-25 | Commvault Systems, Inc. | Targeted snapshot based on virtual machine location |
| US10389810B2 (en) | 2016-11-02 | 2019-08-20 | Commvault Systems, Inc. | Multi-threaded scanning of distributed file systems |
| US10922189B2 (en) | 2016-11-02 | 2021-02-16 | Commvault Systems, Inc. | Historical network data-based scanning thread generation |
| US11106632B2 (en) | 2016-11-16 | 2021-08-31 | Commvault Systems, Inc. | Dynamically configuring a proxy server using containerization for concurrent and/or overlapping backup, restore, and/or test operations |
| US10678758B2 (en) | 2016-11-21 | 2020-06-09 | Commvault Systems, Inc. | Cross-platform virtual machine data and memory backup and replication |
| US10838821B2 (en) | 2017-02-08 | 2020-11-17 | Commvault Systems, Inc. | Migrating content and metadata from a backup system |
| US10740193B2 (en) | 2017-02-27 | 2020-08-11 | Commvault Systems, Inc. | Hypervisor-independent reference copies of virtual machine payload data based on block-level pseudo-mount |
| US10459666B2 (en) | 2017-03-03 | 2019-10-29 | Commvault Systems, Inc. | Using storage managers in respective data storage management systems for license distribution, compliance, and updates |
| US10949308B2 (en) | 2017-03-15 | 2021-03-16 | Commvault Systems, Inc. | Application aware backup of virtual machines |
| US11032350B2 (en) | 2017-03-15 | 2021-06-08 | Commvault Systems, Inc. | Remote commands framework to control clients |
| US10877851B2 (en) | 2017-03-24 | 2020-12-29 | Commvault Systems, Inc. | Virtual machine recovery point selection |
| US10891069B2 (en) | 2017-03-27 | 2021-01-12 | Commvault Systems, Inc. | Creating local copies of data stored in online data repositories |
| US10776329B2 (en) | 2017-03-28 | 2020-09-15 | Commvault Systems, Inc. | Migration of a database management system to cloud storage |
| US11108858B2 (en) | 2017-03-28 | 2021-08-31 | Commvault Systems, Inc. | Archiving mail servers via a simple mail transfer protocol (SMTP) server |
| US10613939B2 (en) | 2017-03-28 | 2020-04-07 | Commvault Systems, Inc. | Backup index generation process |
| US11074138B2 (en) | 2017-03-29 | 2021-07-27 | Commvault Systems, Inc. | Multi-streaming backup operations for mailboxes |
| US10949398B2 (en) | 2017-03-29 | 2021-03-16 | Commvault Systems, Inc. | Synchronization operations for network-accessible folders |
| US10387073B2 (en) | 2017-03-29 | 2019-08-20 | Commvault Systems, Inc. | External dynamic virtual machine synchronization |
| US10599527B2 (en) | 2017-03-29 | 2020-03-24 | Commvault Systems, Inc. | Information management cell health monitoring system |
| US11074140B2 (en) | 2017-03-29 | 2021-07-27 | Commvault Systems, Inc. | Live browsing of granular mailbox data |
| US11294786B2 (en) | 2017-03-31 | 2022-04-05 | Commvault Systems, Inc. | Management of internet of things devices |
| US10853195B2 (en) | 2017-03-31 | 2020-12-01 | Commvault Systems, Inc. | Granular restoration of virtual machine application data |
| US11221939B2 (en) | 2017-03-31 | 2022-01-11 | Commvault Systems, Inc. | Managing data from internet of things devices in a vehicle |
| US10552294B2 (en) | 2017-03-31 | 2020-02-04 | Commvault Systems, Inc. | Management of internet of things devices |
| US11010261B2 (en) | 2017-03-31 | 2021-05-18 | Commvault Systems, Inc. | Dynamically allocating streams during restoration of data |
| US10984041B2 (en) | 2017-05-11 | 2021-04-20 | Commvault Systems, Inc. | Natural language processing integrated with database and data storage management |
| US10664352B2 (en) | 2017-06-14 | 2020-05-26 | Commvault Systems, Inc. | Live browsing of backed up data residing on cloned disks |
| US10846180B2 (en) | 2017-09-14 | 2020-11-24 | Commvault Systems, Inc. | Distributed framework for task splitting and task assignments in a content indexing system |
| US11086834B2 (en) | 2017-09-14 | 2021-08-10 | Commvault Systems, Inc. | Distributed framework for data proximity-based task splitting in a content indexing system |
| US11263088B2 (en) | 2017-09-14 | 2022-03-01 | Commvault Systems, Inc. | Distributed architecture for tracking content indexing |
| US11036592B2 (en) | 2017-09-14 | 2021-06-15 | Commvault Systems, Inc. | Distributed content indexing architecture with separately stored file previews |
| US10846266B2 (en) | 2017-09-14 | 2020-11-24 | Commvault Systems, Inc. | Distributed architecture for content indexing emails |
| US10635546B2 (en) | 2017-12-07 | 2020-04-28 | Commvault Systems, Inc. | Synthesizing a restore image from one or more secondary copies to facilitate data restore operations to a file server |
| US10740300B1 (en) | 2017-12-07 | 2020-08-11 | Commvault Systems, Inc. | Synchronization of metadata in a distributed storage system |
| US10742735B2 (en) | 2017-12-12 | 2020-08-11 | Commvault Systems, Inc. | Enhanced network attached storage (NAS) services interfacing to cloud storage |
| US10831591B2 (en) | 2018-01-11 | 2020-11-10 | Commvault Systems, Inc. | Remedial action based on maintaining process awareness in data storage management |
| US10795927B2 (en) | 2018-02-05 | 2020-10-06 | Commvault Systems, Inc. | On-demand metadata extraction of clinical image data |
| US10642886B2 (en) | 2018-02-14 | 2020-05-05 | Commvault Systems, Inc. | Targeted search of backup data using facial recognition |
| US10592145B2 (en) | 2018-02-14 | 2020-03-17 | Commvault Systems, Inc. | Machine learning-based data object storage |
| US10732885B2 (en) | 2018-02-14 | 2020-08-04 | Commvault Systems, Inc. | Block-level live browsing and private writable snapshots using an ISCSI server |
| US10848468B1 (en) | 2018-03-05 | 2020-11-24 | Commvault Systems, Inc. | In-flight data encryption/decryption for a distributed storage platform |
| US10877928B2 (en) | 2018-03-07 | 2020-12-29 | Commvault Systems, Inc. | Using utilities injected into cloud-based virtual machines for speeding up virtual machine backup operations |
| US10761942B2 (en) | 2018-03-12 | 2020-09-01 | Commvault Systems, Inc. | Recovery point objective (RPO) driven backup scheduling in a data storage management system using an enhanced data agent |
| US10789387B2 (en) | 2018-03-13 | 2020-09-29 | Commvault Systems, Inc. | Graphical representation of an information management system |
| US10673943B2 (en) | 2018-05-02 | 2020-06-02 | Commvault Systems, Inc. | Network storage backup using distributed media agents |
| US11321183B2 (en) | 2018-05-02 | 2022-05-03 | Commvault Systems, Inc. | Multi-tiered backup indexing |
| US11249863B2 (en) | 2018-05-02 | 2022-02-15 | Commvault Systems, Inc. | Backup-based media agent configuration |
| US10893103B2 (en) | 2018-07-25 | 2021-01-12 | Commvault Systems, Inc. | Distributed and scalable storage management using a storage-microservices server |
| US10891304B2 (en) | 2018-07-25 | 2021-01-12 | Commvault Systems, Inc. | Distributed and scalable client-based storage management |
| US10891198B2 (en) | 2018-07-30 | 2021-01-12 | Commvault Systems, Inc. | Storing data to cloud libraries in cloud native formats |
| US11159469B2 (en) | 2018-09-12 | 2021-10-26 | Commvault Systems, Inc. | Using machine learning to modify presentation of mailbox objects |
| US11016696B2 (en) | 2018-09-14 | 2021-05-25 | Commvault Systems, Inc. | Redundant distributed data storage system |
| US11010258B2 (en) | 2018-11-27 | 2021-05-18 | Commvault Systems, Inc. | Generating backup copies through interoperability between components of a data storage management system and appliances for data storage and deduplication |
| US11200124B2 (en) | 2018-12-06 | 2021-12-14 | Commvault Systems, Inc. | Assigning backup resources based on failover of partnered data storage servers in a data storage management system |
| US10860443B2 (en) | 2018-12-10 | 2020-12-08 | Commvault Systems, Inc. | Evaluation and reporting of recovery readiness in a data storage management system |
| US20200192572A1 (en) | 2018-12-14 | 2020-06-18 | Commvault Systems, Inc. | Disk usage growth prediction system |
| US11698727B2 (en) | 2018-12-14 | 2023-07-11 | Commvault Systems, Inc. | Performing secondary copy operations based on deduplication performance |
| US11012508B2 (en) | 2018-12-14 | 2021-05-18 | Commvault Systems, Inc. | Region-based distributed information management system |
| US10872069B2 (en) | 2019-01-22 | 2020-12-22 | Commvault Systems, Inc. | File indexing for virtual machine backups in a data storage management system |
| US11347707B2 (en) | 2019-01-22 | 2022-05-31 | Commvault Systems, Inc. | File indexing for virtual machine backups based on using live browse features |
| US10768971B2 (en) | 2019-01-30 | 2020-09-08 | Commvault Systems, Inc. | Cross-hypervisor live mount of backed up virtual machine data |
| US10996974B2 (en) | 2019-01-30 | 2021-05-04 | Commvault Systems, Inc. | Cross-hypervisor live mount of backed up virtual machine data, including management of cache storage for virtual machine data |
| US11126365B2 (en) | 2019-03-11 | 2021-09-21 | Commvault Systems, Inc. | Skipping data backed up in prior backup operations |
| US11269732B2 (en) | 2019-03-12 | 2022-03-08 | Commvault Systems, Inc. | Managing structured data in a data storage system |
| US11321184B2 (en) | 2019-03-26 | 2022-05-03 | Commvault Systems, Inc. | Streamlined secondary copy operations for data stored on shared file storage |
| US20200327017A1 (en) | 2019-04-10 | 2020-10-15 | Commvault Systems, Inc. | Restore using deduplicated secondary copy data |
| US11100064B2 (en) | 2019-04-30 | 2021-08-24 | Commvault Systems, Inc. | Automated log-based remediation of an information management system |
| US11366723B2 (en) | 2019-04-30 | 2022-06-21 | Commvault Systems, Inc. | Data storage management system for holistic protection and migration of serverless applications across multi-cloud computing environments |
| US11442623B2 (en) | 2019-05-02 | 2022-09-13 | Commvault Systems, Inc. | Faster browse of secondary copies of block-level data volumes |
| US11463264B2 (en) | 2019-05-08 | 2022-10-04 | Commvault Systems, Inc. | Use of data block signatures for monitoring in an information management system |
| US11269734B2 (en) | 2019-06-17 | 2022-03-08 | Commvault Systems, Inc. | Data storage management system for multi-cloud protection, recovery, and migration of databases-as-a-service and/or serverless database management systems |
| US11308034B2 (en) | 2019-06-27 | 2022-04-19 | Commvault Systems, Inc. | Continuously run log backup with minimal configuration and resource usage from the source machine |
| US11561866B2 (en) | 2019-07-10 | 2023-01-24 | Commvault Systems, Inc. | Preparing containerized applications for backup using a backup services container and a backup services container-orchestration pod |
| US11042318B2 (en) | 2019-07-29 | 2021-06-22 | Commvault Systems, Inc. | Block-level data replication |
| US20210037112A1 (en) | 2019-07-29 | 2021-02-04 | Commvault Systems, Inc. | Data storage system with rapid restore capability |
| US11263173B2 (en) | 2019-07-30 | 2022-03-01 | Commvault Systems, Inc. | Transaction log index generation in an enterprise backup system |
| US11513922B2 (en) | 2019-08-14 | 2022-11-29 | Commvault Systems, Inc. | Systems and methods for change block tracking for backing up changed data |
| US11237935B2 (en) | 2019-09-11 | 2022-02-01 | Commvault Systems, Inc. | Anomaly detection in data protection operations |
| US11218450B2 (en) | 2019-09-11 | 2022-01-04 | Commvault Systems, Inc. | Data protection component scaling in a cloud-based data storage system |
| US11256673B2 (en) | 2019-09-11 | 2022-02-22 | Commvault Systems, Inc. | Anomaly detection in deduplication pruning operations |
| US20210133150A1 (en) | 2019-11-04 | 2021-05-06 | Commvault Systems, Inc. | Efficient implementation of multiple deduplication databases in a heterogeneous data storage system |
| US11442896B2 (en) | 2019-12-04 | 2022-09-13 | Commvault Systems, Inc. | Systems and methods for optimizing restoration of deduplicated data stored in cloud-based storage resources |
| US11237924B2 (en) | 2019-12-11 | 2022-02-01 | Commvault Systems, Inc. | Dynamic resizing and re-distribution of destination data storage resources for bare metal restore operations in a data storage management system |
| US11223535B2 (en) | 2019-12-31 | 2022-01-11 | Commvault Systems, Inc. | Smart network topology systems and methods |
| US11467753B2 (en) | 2020-02-14 | 2022-10-11 | Commvault Systems, Inc. | On-demand restore of virtual machine data |
| US11321188B2 (en) | 2020-03-02 | 2022-05-03 | Commvault Systems, Inc. | Platform-agnostic containerized application data protection |
| US11422900B2 (en) | 2020-03-02 | 2022-08-23 | Commvault Systems, Inc. | Platform-agnostic containerized application data protection |
| US11334442B2 (en) | 2020-03-10 | 2022-05-17 | Commvault Systems, Inc. | Management database long-term archiving to a recovery manager |
| US11005935B1 (en) | 2020-03-10 | 2021-05-11 | Commvault Systems, Inc. | Using multiple streams with network data management protocol to improve performance and granularity of backup and restore operations from/to a file server |
| US11442768B2 (en) | 2020-03-12 | 2022-09-13 | Commvault Systems, Inc. | Cross-hypervisor live recovery of virtual machines |
| US11099956B1 (en) | 2020-03-26 | 2021-08-24 | Commvault Systems, Inc. | Snapshot-based disaster recovery orchestration of virtual machine failover and failback operations |
| US11500669B2 (en) | 2020-05-15 | 2022-11-15 | Commvault Systems, Inc. | Live recovery of virtual machines in a public cloud computing environment |
| US11687424B2 (en) | 2020-05-28 | 2023-06-27 | Commvault Systems, Inc. | Automated media agent state management |
| US11327663B2 (en) | 2020-06-09 | 2022-05-10 | Commvault Systems, Inc. | Ensuring the integrity of data storage volumes used in block-level live synchronization operations in a data storage management system |
| US11537959B2 (en) | 2020-06-16 | 2022-12-27 | Commvault Systems, Inc. | Dynamic computing progress tracker |
| US11614883B2 (en) | 2020-07-17 | 2023-03-28 | Commvault Systems, Inc. | Distributed data storage system using erasure coding on storage nodes fewer than data plus parity fragments |
| US11494417B2 (en) | 2020-08-07 | 2022-11-08 | Commvault Systems, Inc. | Automated email classification in an information management system |
| US11513708B2 (en) | 2020-08-25 | 2022-11-29 | Commvault Systems, Inc. | Optimized deduplication based on backup frequency in a distributed data storage system |
| US11108861B1 (en) | 2020-08-26 | 2021-08-31 | Commvault Systems, Inc. | System for managing multiple information management cells |
| US11789830B2 (en) | 2020-09-22 | 2023-10-17 | Commvault Systems, Inc. | Anti-entropy-based metadata recovery in a strongly consistent distributed data storage system |
| US11647075B2 (en) | 2020-09-22 | 2023-05-09 | Commvault Systems, Inc. | Commissioning and decommissioning metadata nodes in a running distributed data storage system |
| US11656951B2 (en) | 2020-10-28 | 2023-05-23 | Commvault Systems, Inc. | Data loss vulnerability detection |
| US11474753B2 (en) | 2020-10-30 | 2022-10-18 | Commvault Systems, Inc. | Systems and methods for backing up to a virtual tape library |
| US11323513B1 (en) | 2021-01-22 | 2022-05-03 | Commvault Systems, Inc. | Geo-location-based data replication |
| US11604706B2 (en) | 2021-02-02 | 2023-03-14 | Commvault Systems, Inc. | Back up and restore related data on different cloud storage tiers |
| US11645175B2 (en) | 2021-02-12 | 2023-05-09 | Commvault Systems, Inc. | Automatic failover of a storage manager |
| US11574050B2 (en) | 2021-03-12 | 2023-02-07 | Commvault Systems, Inc. | Media agent hardening against ransomware attacks |
| US11561978B2 (en) | 2021-06-29 | 2023-01-24 | Commvault Systems, Inc. | Intelligent cache management for mounted snapshots based on a behavior model |
| US11954513B2 (en) | 2021-07-29 | 2024-04-09 | Commvault Systems, Inc. | Scalable recovery and/or migration to cloud- based custom-made virtual machines without using failed machines' credentials |
| US11615147B2 (en) | 2021-08-23 | 2023-03-28 | Commvault Systems, Inc. | Mobile storage manager control application for managing a storage manager of an information management system |
| US11593223B1 (en) | 2021-09-02 | 2023-02-28 | Commvault Systems, Inc. | Using resource pool administrative entities in a data storage management system to provide shared infrastructure to tenants |
| US11809285B2 (en) | 2022-02-09 | 2023-11-07 | Commvault Systems, Inc. | Protecting a management database of a data storage management system to meet a recovery point objective (RPO) |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| IT1108325B (en) * | 1978-04-10 | 1985-12-09 | Cselt Centro Studi Lab Telecom | ROAD PROCEDURE AND DEVICE FOR A PACKAGE SWITCHING COMMUNICATION NETWORK |
| US4654656A (en) * | 1984-09-17 | 1987-03-31 | International Business Machines Corp. | Off-line notification and communication network |
| GB8528892D0 (en) * | 1985-11-23 | 1986-01-02 | Int Computers Ltd | Multi-node data processing system |
| US4805134A (en) * | 1986-01-09 | 1989-02-14 | International Business Machines Corporation | Electronic system for accessing graphical and textual information |
| NL8601712A (en) * | 1986-07-01 | 1988-02-01 | Koninkl Philips Electronics Nv | COMMUNICATION NETWORK, IN PARTICULAR A TELEPHONE NETWORK AND DATA COMMUNICATION NETWORK COMPOSED OF A COLLECTION OF BUTTON UNITS, WHICH FOLLOWS SPECIFIC FACILITIES UNDER DUTIES. |
| US4847830A (en) * | 1987-12-02 | 1989-07-11 | Network Equipment Technologies, Inc. | Method and apparatus for automatic loading of a data set in a node of a communication network |
-
1988
- 1988-10-31 US US07/265,104 patent/US4995035A/en not_active Expired - Fee Related
-
1989
- 1989-08-02 CA CA000607307A patent/CA1319758C/en not_active Expired - Fee Related
- 1989-09-06 DE DE68915246T patent/DE68915246T2/en not_active Expired - Fee Related
- 1989-09-06 EP EP89480131A patent/EP0367699B1/en not_active Expired - Lifetime
- 1989-09-06 ES ES89480131T patent/ES2054078T3/en not_active Expired - Lifetime
- 1989-10-26 JP JP1277335A patent/JPH0685521B2/en not_active Expired - Lifetime
- 1989-10-30 BR BR898905539A patent/BR8905539A/en not_active Application Discontinuation
Also Published As
| Publication number | Publication date |
|---|---|
| ES2054078T3 (en) | 1994-08-01 |
| US4995035A (en) | 1991-02-19 |
| JPH02166943A (en) | 1990-06-27 |
| DE68915246D1 (en) | 1994-06-16 |
| BR8905539A (en) | 1990-05-29 |
| DE68915246T2 (en) | 1994-11-24 |
| JPH0685521B2 (en) | 1994-10-26 |
| EP0367699A2 (en) | 1990-05-09 |
| EP0367699B1 (en) | 1994-05-11 |
| EP0367699A3 (en) | 1991-10-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA1319758C (en) | Centralized management in an sna network | |
| CA2094410C (en) | Distributed management communications network | |
| EP0348331B1 (en) | Method of efficiently updating the topology databases of the nodes in a data communications network | |
| EP1517508B1 (en) | Method and apparatus for representing and applying network topological data | |
| US5355371A (en) | Multicast communication tree creation and control method and apparatus | |
| EP0221360B1 (en) | Digital data message transmission networks and the establishing of communication paths therein | |
| JPS61284144A (en) | Topology data base maintenance for network | |
| AU678219B2 (en) | System and method for automatic segment resolution on a local area network | |
| CA2094409C (en) | Multicast communication tree creation and control method and apparatus | |
| JPH06112938A (en) | Communication network | |
| EP1880512A1 (en) | Optimal path routing method in wireless network | |
| EP1009130A1 (en) | Distributed directory services for locating network resources in a very large packet switching network | |
| JP2003060715A (en) | Method and device for routing osi tunnel | |
| US6067573A (en) | Technique for reducing the flow of topology information in a computer network to only nodes that require the information | |
| CA2246818C (en) | Geographic redundancy protection method and apparatus for a communications network | |
| JP3589709B2 (en) | Hierarchical communication network and components for the communication network | |
| EP0511925A2 (en) | Dynamic backup and recovery of focal points in a computer network | |
| CN1898903B (en) | Method and apparatus for performing routing operations in communications network | |
| JP3255238B2 (en) | Communication control processor | |
| KR100621733B1 (en) | Connection Method for parallel processing in a ATM network | |
| KR100299061B1 (en) | Routing method in heterogeneous wide area networks | |
| KR100846562B1 (en) | Codesystem and Data translation method in NMS using that | |
| EP0901295B1 (en) | Method for routing messages in a communication network and device therefor | |
| EP1009131A1 (en) | Method and system for optimizing the end to end path selection in very large packet switching networks | |
| JPH04313138A (en) | Computer network system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| MKLA | Lapsed |