IP Library Granted Patent US 12,380,001
Granted Patent B2
US 12,380,001 · App. 18/885,883 · Granted Aug 5, 2025

Management database long-term archiving to a recovery manager

Inventor: Prasad Nara (Manalapan, NJ)
Assignee: Commvault Systems, Inc.
G06F11/1464G06F11/1435G06F11/1448G06F11/1461G06F16/21
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,380,001
App. No.
18/885,883
Granted
Aug 5, 2025
Kind
B2
Abstract

A storage manager for an information management system determines whether one or more predetermined conditions have been met for transferring metadata of previously performed backup jobs stored in a first management database. A backup job may correspond to a backup operation of a primary storage device of a first client computing device. In response to a determination that one or more of the predetermined conditions have been met, the storage manager may transfer metadata for a second plurality of backup jobs to a second management database of a recovery manager. The recovery manager may receive a request to restore data to the primary storage device of the first client computing device based on the metadata of the second plurality of backup jobs. A media agent managed by the recovery manager may then restore the requested data to the primary storage device of the first client computing device.

Claims (63)

1. A system comprising:

a first computing device comprising one or more hardware processors; and

a second computing device comprising one or more hardware processors, wherein the second computing device is configured to:

based on a criterion that has been satisfied, receive first metadata from the first computing device,

wherein the first metadata was generated by, and is associated with, one or more first backup jobs that were previously managed by the first computing device,

wherein the one or more first backup jobs generated first backup copies that are stored in secondary storage, and

wherein the second computing device is configured to manage restore jobs of the first backup copies from the secondary storage, and

store the first metadata at the second computing device;

wherein the first computing device is configured to:

remove the first metadata from the first computing device after transferring the first metadata to the second computing device,

after having removed the first metadata, receive a request to restore at least one of the first backup copies, and

based on determining that the first metadata has been transferred to the second computing device, redirect the request to the second computing device; and

wherein the second computing device is further configured to:

responsive to the request, manage a restore job that restores the at least one of the first backup copies to a primary storage device,

wherein the second computing device is further configured to lack authorization to back up data stored at the primary storage device.

2. The system of claim 1 wherein the second computing device is further configured to determine that the criterion has been satisfied and causes the first computing device to transfer the first metadata.

3. The system of claim 1 wherein the first computing device is further configured to determine that the criterion has been satisfied and initiates transferring of the first metadata to the second computing device.

4. The system of claim 1 , wherein the criterion is based on one or more of: a size threshold of a first management database configured at the first computing device, and a threshold number of records of the first management database, wherein the first management database comprises the first metadata.

5. The system of claim 1 , wherein the criterion is based on an age threshold of the one or more first backup jobs.

6. The system of claim 1 , wherein the criterion is based on a frequency.

7. The system of claim 1 , wherein the first computing device is further configured to cause one or more client computing devices that are associated with the first metadata to register as restore-only clients of the second computing device; and

wherein the second computing device is further configured to lack access to primary data of any client computing device that is registered as a restore-only client at the second computing device as a data source for backup jobs.

8. The system of claim 1 , wherein the first computing device is further configured to identify one or more data agents that are associated with the first metadata, wherein the one or more data agents execute at one or more client computing devices, and

cause the one or more data agents to register as restore-only clients of the second computing device; and

wherein the second computing device is configured to lack access to primary data associated with the one or more data agents as a data source for backup jobs.

9. The system of claim 1 wherein the second computing device is further configured to cause a media agent to be populated with at least some of the first metadata, wherein the media agent is hosted by a third computing device that comprises one or more hardware processors; and

wherein the third computing device hosting the media agent is configured to perform the restore job.

10. A computer-implemented method comprising:

based on a criterion that has been satisfied, transferring, by a storage manager to a recovery manager, first metadata that is stored at the storage manager,

wherein the first metadata was generated by one or more first backup jobs that were previously managed by the storage manager,

wherein the one or more first backup jobs generated first backup copies that are stored in secondary storage;

wherein the recovery manager is configured to manage restore jobs of the first backup copies from the secondary storage,

wherein the storage manager executes on a first computing device that comprises one or more hardware processors, and

wherein the recovery manager executes on a second computing device, which is distinct from the first computing device, and which comprises one or more hardware processors;

by the recovery manager, storing the first metadata at the recovery manager;

by the storage manager, removing the first metadata from the storage manager after transferring the first metadata to the recovery manager;

after having removed the first metadata, receiving, by the storage manager, a request to restore at least one of the first backup copies;

based on determining that the first metadata has been transferred to the recovery manager, redirecting the request to the recovery manager; and

responsive to the request, managing, by the recovery manager, a restore job that restores the at least one of the first backup copies to a primary storage device,

wherein the recovery manager is further configured to lack access to data stored at the primary storage device as a data source for backup jobs.

11. The computer-implemented method of claim 10 wherein the recovery manager determines that the criterion has been satisfied and causes the storage manager to transfer the first metadata.

12. The computer-implemented method of claim 10 wherein the storage manager determines that the criterion has been satisfied and initiates transferring of the first metadata to the recovery manager.

13. The computer-implemented method of claim 10 further comprising:

by the recovery manager, informing the storage manager that the first metadata has been validated;

based on the first metadata having been validated by the recovery manager, identifying, by the storage manager, storage media within the secondary storage that comprises the first backup copies, and adding the storage media to an overwrite protection pool.

14. The computer-implemented method of claim 10 further comprising:

by the recovery manager, informing the storage manager that the first metadata has been validated;

based on the first metadata having been validated by the recovery manager, identifying, by the storage manager, storage media within the secondary storage that comprises the first backup copies, and indicating at the storage manager that the storage media are read-only.

15. The computer-implemented method of claim 10 further comprising:

receiving, by the storage manager, a second request to restore a second backup copy, which is distinct from the first backup copies;

based on determining that second metadata associated with the second backup copy resides at the storage manager, managing, by the storage manager, a restore job that restores the second backup copy to a primary storage device.

16. The computer-implemented method of claim 10 further comprising:

identifying, by the storage manager, one or more client computing devices that are associated with the first metadata;

causing, by the storage manager, the one or more client computing devices to register as restore-only clients of the recovery manager; and

wherein the recovery manager is configured not to manage backup jobs of primary data of any client computing device that is registered as a restore-only client at the recovery manager.

17. The computer-implemented method of claim 10 , further comprising:

identifying, by the storage manager, one or more data agents that are associated with the first metadata, wherein the one or more data agents execute at one or more client computing devices;

causing, by the storage manager, the one or more data agents to register as restore-only clients of the recovery manager; and

wherein the recovery manager is configured not to manage backup jobs of primary data associated with the one or more data agents that are registered as restore-only clients at the recovery manager.

18. The computer-implemented method of claim 10 , wherein the recovery manager is configured not to manage backup jobs.

19. The computer-implemented method of claim 10 further comprising: causing, by the recovery manager, a media agent to be populated with at least some of the first metadata; and

by the media agent, performing the restore job that restores the at least one of the first backup copies, wherein the media agent executes on a third computing device that comprises one or more hardware processors.

20. The computer-implemented method of claim 10 , wherein the criterion is based on one or more of: a frequency, a size threshold of a first management database configured at the first computing device, a threshold number of records of the first management database, and an age threshold of the one or more first backup jobs.

Assignments (2)
SUPPLEMENTAL CONFIRMATORY GRANT OF SECURITY INTEREST IN UNITED STATES PATENTS Recorded Apr 16, 2025
From: COMMVAULT SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 070864/0344 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 26, 2024
From: NARA, PRASAD
To: COMMVAULT SYSTEMS, INC.
Reel/Frame 068703/0502 →
Continuity (5)
Continuation 18486201 · Oct 13, 2023
Continuation 18127569 · Mar 28, 2023
Continuation 17714391 · Apr 6, 2022
Continuation 16814718 · Mar 10, 2020
Related Publication 20250013540A1 · Jan 9, 2025
References Cited (118)
US 4084231A · Capozzi et al. · 1978 [cited by applicant]
US 4267568A · Dechant et al. · 1981 [cited by applicant]
US 4283787A · Chambers · 1981 [cited by applicant]
US 4417321A · Chang et al. · 1983 [cited by applicant]
US 4641274A · Swank · 1987 [cited by applicant]
US 4654819A · Stiffler et al. · 1987 [cited by applicant]
US 4686620A · Ng · 1987 [cited by applicant]
US 4912637A · Sheedy et al. · 1990 [cited by applicant]
US 4995035A · Cole · 1991 [cited by applicant]
US 5005122A · Griffin · 1991 [cited by applicant]
US 5093912A · Dong et al. · 1992 [cited by applicant]
US 5133065A · Cheffetz et al. · 1992 [cited by applicant]
US 5193154A · Kitajima et al. · 1993 [cited by applicant]
US 5212772A · Masters · 1993 [cited by applicant]
US 5226157A · Nakano et al. · 1993 [cited by applicant]
US 5239647A · Anglin et al. · 1993 [cited by applicant]
US 5241668A · Eastridge et al. · 1993 [cited by applicant]
US 5241670A · Eastridge et al. · 1993 [cited by applicant]
US 5276860A · Fortier et al. · 1994 [cited by applicant]
US 5276867A · Kenley et al. · 1994 [cited by applicant]
US 5287500A · Stoppani, Jr. · 1994 [cited by applicant]
US 5301286A · Rajani · 1994 [cited by applicant]
US 5321816A · Rogan et al. · 1994 [cited by applicant]
US 5347653A · Flynn et al. · 1994 [cited by applicant]
US 5410700A · Fecteau et al. · 1995 [cited by applicant]
US 5420996A · Aoyagi · 1995 [cited by applicant]
US 5454099A · Myers et al. · 1995 [cited by applicant]
US 5559991A · Kanfi · 1996 [cited by applicant]
US 5642496A · Kanfi · 1997 [cited by applicant]
US 6418478B1 · Ignatius et al. · 2002 [cited by applicant]
US 6542972B2 · Ignatius et al. · 2003 [cited by applicant]
US 6658436B2 · Oshinsky et al. · 2003 [cited by applicant]
US 6721767B2 · DeMeno et al. · 2004 [cited by applicant]
US 6760723B2 · Oshinsky et al. · 2004 [cited by applicant]
US 7003641B2 · Prahlad · 2006 [cited by applicant]
US 7035880B1 · Crescenti · 2006 [cited by applicant]
US 7107298B2 · Prahlad · 2006 [cited by applicant]
US 7130970B2 · Devassy · 2006 [cited by applicant]
US 7162496B2 · Amarendran et al. · 2007 [cited by applicant]
US 7174433B2 · Kottomtharayil et al. · 2007 [cited by applicant]
US 7246207B2 · Kottomtharayil · 2007 [cited by applicant]
US 7315923B2 · Retnamma · 2008 [cited by applicant]
US 7343453B2 · Prahlad · 2008 [cited by applicant]
US 7389311B1 · Crescenti et al. · 2008 [cited by applicant]
US 7395282B1 · Crescenti · 2008 [cited by applicant]
US 7440982B2 · Lu · 2008 [cited by applicant]
US 7454569B2 · Kavuri · 2008 [cited by applicant]
US 7490207B2 · Amarendran et al. · 2009 [cited by applicant]
US 7500053B1 · Kavuri · 2009 [cited by applicant]
US 7529782B2 · Prahlad · 2009 [cited by applicant]
US 7536291B1 · Vijayan Retnamma et al. · 2009 [cited by applicant]
US 7543125B2 · Gokhale · 2009 [cited by applicant]
US 7546324B2 · Prahlad et al. · 2009 [cited by applicant]
US 7603386B2 · Amarendran et al. · 2009 [cited by applicant]
US 7606844B2 · Kottomtharayil · 2009 [cited by applicant]
US 7613752B2 · Prahlad · 2009 [cited by applicant]
US 7617253B2 · Prahlad et al. · 2009 [cited by applicant]
US 7617262B2 · Prahlad · 2009 [cited by applicant]
US 7620710B2 · Kottomtharayil · 2009 [cited by applicant]
US 7636743B2 · Erofeev · 2009 [cited by applicant]
US 7651593B2 · Prahlad · 2010 [cited by applicant]
US 7657550B2 · Prahlad · 2010 [cited by applicant]
US 7660807B2 · Prahlad · 2010 [cited by applicant]
US 7661028B2 · Erofeev · 2010 [cited by applicant]
US 7734669B2 · Kottomtharayil · 2010 [cited by applicant]
US 7747579B2 · Prahlad · 2010 [cited by applicant]
US 7801864B2 · Prahlad · 2010 [cited by applicant]
US 7809914B2 · Kottomtharayil · 2010 [cited by applicant]
US 8156086B2 · Lu et al. · 2012 [cited by applicant]
US 8170995B2 · Prahlad · 2012 [cited by applicant]
US 8229954B2 · Kottomtharayil · 2012 [cited by applicant]
US 8230195B2 · Amarendran · 2012 [cited by applicant]
US 8285681B2 · Prahlad · 2012 [cited by applicant]
US 8307177B2 · Prahlad · 2012 [cited by applicant]
US 8364652B2 · Vijayan · 2013 [cited by applicant]
US 8370542B2 · Lu et al. · 2013 [cited by applicant]
US 8578120B2 · Attarde · 2013 [cited by applicant]
US 8954446B2 · Vijayan Retnamma et al. · 2015 [cited by applicant]
US 9020900B2 · Vijayan Retnamma et al. · 2015 [cited by applicant]
US 9098495B2 · Gokhale · 2015 [cited by applicant]
US 9239687B2 · Vijayan · 2016 [cited by applicant]
US 9633033B2 · Vijayan · 2017 [cited by applicant]
US 9639274B2 · Maranna · 2017 [cited by applicant]
US 10474388B2 · Nara et al. · 2019 [cited by applicant]
US 11334442B2 · Nara · 2022 [cited by applicant]
US 11645168B2 · Nara · 2023 [cited by applicant]
US 20060224846A1 · Amarendran et al. · 2006 [cited by applicant]
US 20090319534A1 · Gokhale · 2009 [cited by applicant]
US 20120150818A1 · Vijayan Retnamma et al. · 2012 [cited by applicant]
US 20140006357A1 · Davis et al. · 2014 [cited by applicant]
US 20160350391A1 · Vijayan et al. · 2016 [cited by applicant]
US 20170168903A1 · Dornemann et al. · 2017 [cited by applicant]
US 20170185488A1 · Kumarasamy et al. · 2017 [cited by applicant]
US 20170192866A1 · Kumar · 2017 [cited by applicant]
US 20170193003A1 · Vijayan et al. · 2017 [cited by applicant]
US 20170235647A1 · Kilaru et al. · 2017 [cited by applicant]
US 20170242871A1 · Kilaru et al. · 2017 [cited by applicant]
US 20190182322A1 · Kumar et al. · 2019 [cited by applicant]
EP 0259912A1 · 1988 [cited by applicant]
EP 0405926A2 · 1991 [cited by applicant]
EP 0467546A2 · 1992 [cited by applicant]
EP 0541281A2 · 1993 [cited by applicant]
EP 0774715A1 · 1997 [cited by applicant]
EP 0809184A1 · 1997 [cited by applicant]
EP 0899662A1 · 1999 [cited by applicant]
EP 0981090A1 · 2000 [cited by applicant]
WO 9513580A1 · 1995 [cited by applicant]
WO 9912098A1 · 1999 [cited by applicant]
WO 2006052872A2 · 2006 [cited by applicant]
Arneson, “Mass Storage Archiving in Network Environments,” Digest of Papers, Ninth IEEE Symposium on Mass Storage Systems, Oct. 31, 1988Nov. 3, 1988, pp. 45-50, Monterey, CA. [cited by applicant]
Arneson, David A., “Development of Omniserver,” Control Data Corporation, Tenth IEEE Symposium on Mass Storage Systems, May 1990, ‘Crisis in Mass Storage’ Digest of Papers, pp. 88-93, Monterey, CA. [cited by applicant]
Cabrera et al., “ADSM: A Multi-Platform, Scalable, Backup and Archive Mass Storage System,” Digest of Papers, Compcon '95, Proceedings of the 40th IEEE Computer Society International Conference, Mar. 5, 1995-Mar. 9, 199… [cited by applicant]
Case No. 1:21-cv-00537, Complaint WDTX-1-21-cv-00537-1_WDTX-6-21-cv-00634-1, filed Jun. 18, 2021, in 44 pages. [cited by applicant]
Case No. 6:21-cv-00634-ADA, Order Dismissing with Prejudice WDTX-6-21-cv-00634-22, filed Sep. 1, 2021, in 1 page. [cited by applicant]
Case No. No. 6:21-CV-00634-ADA, Answer WDTX-6-21-cv-00634-19, filed Aug. 27, 2021, in 23 pages. [cited by applicant]
Eitel, “Backup and Storage Management in Distributed Heterogeneous Environments,” IEEE, Jun. 12-16, 1994, pp. 124-126. [cited by applicant]
Huff, KL, “Data Set Usage Sequence Number,” IBM Technical Disclosure Bulletin, vol. 24, No. 5, Oct. 1981 New York, US, pp. 2404-2406. [cited by applicant]
Rosenblum et al., “The Design and Implementation of a Log-Structure File System,” Operating Systems Review SIGOPS, vol. 25, No. 5, May 1991, New York, US, pp. 1-14. [cited by applicant]