IP Library › Granted Patent US 12,229,582
Granted Patent B2
US 12,229,582 · App. 18/595,719 · Granted Feb 18, 2025

Scalable recovery and/or migration to cloud-based custom-made virtual machines without using failed machines' credentials

Inventors: Amit Mahajan (Bangalore, IN); Ratish Babu Andham Veetil (Bangalore, IN); Venkatesh Maharajan (Bangalore, IN)
Assignee: Commvault Systems, Inc.
G06F9/45558G06F11/1469H04L63/083G06F2009/4557G06F2009/45583G06F2009/45595G06F2201/815
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,229,582
App. No.
18/595,719
Granted
Feb 18, 2025
Kind
B2
Abstract

The disclosed approach works without the individualized credentials of failed machines when setting up recovery VMs in a cloud computing environment. Each recovery VMs is customized to properly correspond to the system state of its failed counterpart. An illustrative data storage management system recovers backup data and system states collected from the counterpart computing devices, custom-configures recovery VMs in the cloud computing environment, and injects the desired drivers into each recovery VM during an enhanced bare-metal restore process. The enhanced bare-metal restore process works without the failed computer's credentials. The system also restores the backed up data to recovery volumes attached to the recovery VMs. The present approach is both scalable and secure. When the enhanced bare-metal restore process completes, each cloud-based recovery VM presents a user interface that, for the first time after the computing device has failed, asks for the individualized credentials of the failed machine.

Claims (47)

1. A system comprising:

one or more computing devices comprising computer hardware processors and computer programming instructions that configure the system to perform a disaster recovery operation of a client computing device,

wherein the client computing device is configured with first password-protected credentials for user access, and

wherein the disaster recovery operation comprises:

(i) by a first computing device that operates in a cloud computing environment, configure a recovery virtual machine in the cloud computing environment according to system state metadata of the client computing device, wherein the system state metadata was previously saved in a backup operation of the client computing device performed by the system,

(ii) add, by the first computing device, into a data storage volume provisioned in the cloud computing environment, a configuration file that comprises instructions for creating second password-protected credentials, which are distinct from the first password-protected credentials of the client computing device, and

(iii) activate, by the first computing device, a configuration tool, which, as guided by the configuration file: establishes the second password-protected credentials in the recovery virtual machine, injects one or more drivers required by the cloud computing environment into the recovery virtual machine while logged in at the recovery virtual machine with the second password-protected credentials, and removes the second password-protected credentials from the recovery virtual machine after logging out therefrom;

wherein the disaster recovery operation configures the recovery virtual machine according to the system state metadata of the client computing device without using the first password-protected credentials of the client computing device; and

wherein after the disaster recovery operation is completed without using the first password-protected credentials of the client computing device, user access to the recovery virtual machine requires the first password-protected credentials, and not the second password-protected credentials.

2. The system of claim 1 , wherein the disaster recovery operation further comprises: restore, to the data storage volume provisioned in the cloud computing environment, data of the client computing device that was previously backed up in the backup operation;

wherein after the disaster recovery operation is completed without using the first password-protected credentials of the client computing device, the recovery virtual machine gains access to the data storage volume, which comprises restored data of the client computing device that was previously backed up in the backup operation, wherein the restored data is in a primary format that is distinct from a backup format generated by the backup operation.

3. The system of claim 1 , wherein the disaster recovery operation further comprises: inject the one or more drivers into the data storage volume before activating the configuration tool.

4. The system of claim 1 , wherein a storage manager among the one or more computing devices is configured to initiate the disaster recovery operation,

wherein the storage manager operates in the cloud computing environment.

5. The system of claim 1 , wherein a storage manager among the one or more computing devices is configured to initiate the disaster recovery operation based on detecting that the client computing device has failed.

6. The system of claim 1 , wherein a storage manager among the one or more computing devices is configured to initiate the disaster recovery operation on demand.

7. The system of claim 1 , wherein a storage manager among the one or more computing devices is configured to initiate the disaster recovery operation,

wherein the storage manager operates outside the cloud computing environment, and

wherein data of the client computing device that was previously backed up in the backup operation is stored outside the cloud computing environment.

8. The system of claim 1 , wherein a storage manager among the one or more computing devices is configured to initiate the disaster recovery operation, and

wherein in the backup operation, the system state metadata was stored in a management database of the storage manager, and

wherein to configure the recovery virtual machine, the first computing device is configured to obtain the system state metadata from the storage manager.

9. The system of claim 1 , wherein the cloud computing environment is an Amazon Web Services (AWS) environment.

10. The system of claim 1 , wherein the configuration file is written in Extensible Markup Language (XML).

11. A computer-implemented method comprising:

by a first computing device operating in a cloud computing environment, wherein the first computing device comprises one or more hardware processors and computer memory carrying programming instructions, which, when executed by the one or more hardware processors, cause the first computing device to perform a disaster recovery operation of a client computing device,

wherein the client computing device is configured with first password-protected credentials for user access, and

wherein performing the disaster recovery operation comprises:

(i) causing a recovery virtual machine to be configured in the cloud computing environment according to system state metadata of the client computing device, wherein the system state metadata was previously saved in a backup operation of the client computing device,

(ii) adding, to a data storage volume provisioned in the cloud computing environment, a configuration file that comprises instructions for creating second password-protected credentials, which are distinct from the first password-protected credentials of the client computing device, and

(iii) activating a configuration tool, which, as guided by the configuration file: establishes the second password-protected credentials in the recovery virtual machine, injects one or more drivers required by the cloud computing environment into the recovery virtual machine while logged in at the recovery virtual machine with the second password-protected credentials, and removes the second password-protected credentials from the recovery virtual machine after logging out therefrom;

wherein the disaster recovery operation configures the recovery virtual machine according to the system state metadata of the client computing device without using the first password-protected credentials of the client computing device; and

wherein after the disaster recovery operation is completed without using the first password-protected credentials of the client computing device, user access to the recovery virtual machine requires the first password-protected credentials, and not the second password-protected credentials.

12. The computer-implemented method of claim 11 , wherein the disaster recovery operation further comprises: restoring, to the data storage volume provisioned in the cloud computing environment, data of the client computing device that was previously backed up in the backup operation;

wherein after the disaster recovery operation is completed without using the first password-protected credentials of the client computing device, the recovery virtual machine gains access to the data storage volume, which comprises restored data of the client computing device that was previously backed up in the backup operation, wherein the restored data is in a primary format that is distinct from a backup format generated by the backup operation.

13. The computer-implemented method of claim 11 , wherein the disaster recovery operation further comprises: injecting the one or more drivers into the data storage volume before activating the configuration tool.

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

by a second computing device operating in the cloud computing environment, wherein the second computing device comprises one or more second hardware processors and computer memory carrying programming instructions, which, when executed by the one or more second hardware processors, cause the second computing device to execute a storage manager, initiating the disaster recovery operation.

15. The computer-implemented method of claim 11 , further comprising: by a second computing device operating outside the cloud computing environment, wherein the second computing device comprises one or more second hardware processors and computer memory carrying programming instructions, which, when executed by the one or more second hardware processors, cause the second computing device to execute a storage manager, initiating the disaster recovery operation; and

wherein data of the client computing device that was previously backed up in the backup operation is stored outside the cloud computing environment.

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

by a second computing device, wherein the second computing device comprises one or more second hardware processors and computer memory carrying programming instructions, which, when executed by the one or more second hardware processors, cause the second computing device to execute a storage manager, initiating the disaster recovery operation; and

by the first computing device, obtaining the system state metadata from the second computing device.

17. The computer-implemented method of claim 16 , wherein the disaster recovery operation is initiated based on the storage manager detecting that the client computing device has failed.

18. The computer-implemented method of claim 16 , wherein the disaster recovery operation is initiated on demand.

19. The computer-implemented method of claim 11 , wherein an operating system of the client computing device and of the recovery virtual machine is a Microsoft Windows operating system, and wherein the configuration tool is based on a system preparation tool for Microsoft Windows operating system deployment.

20. The computer-implemented method of claim 11 , wherein the configuration file is written in Extensible Markup Language (XML).

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 Mar 28, 2024
From: MAHAJAN, AMIT; ANDHAM VEETIL, RATISH BABU; MAHARAJAN, VENKATESH
To: COMMVAULT SYSTEMS, INC.
Reel/Frame 066927/0161 →
Continuity (2)
Continuation 17389204 · Jul 29, 2021
Related Publication 20240256326A1 · Aug 1, 2024
References Cited (274)
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 8612439B2 · Prahlad · 2013 [cited by applicant]
US 8910155B1 · Sobel · 2014 [cited by examiner]
US 8950009B2 · Vijayan et al. · 2015 [cited by applicant]
US 8954446B2 · Vijayan Retnamma et al. · 2015 [cited by applicant]
US 9020900B2 · Vijayan Retnamma et al. · 2015 [cited by applicant]
US 9032394B1 · Shi · 2015 [cited by applicant]
US 9098495B2 · Gokhale · 2015 [cited by applicant]
US 9116735B2 · Srinivasan · 2015 [cited by applicant]
US 9189170B2 · Kripalani et al. · 2015 [cited by applicant]
US 9239687B2 · Vijayan · 2016 [cited by applicant]
US 9262496B2 · Kumarasamy et al. · 2016 [cited by applicant]
US 9336226B2 · Vibhor et al. · 2016 [cited by applicant]
US 9444811B2 · Nara · 2016 [cited by applicant]
US 9519787B2 · Novak · 2016 [cited by applicant]
US 9633033B2 · Vijayan · 2017 [cited by applicant]
US 9639274B2 · Maranna · 2017 [cited by applicant]
US 9641388B2 · Kripalani · 2017 [cited by applicant]
US 9690936B1 · Malik · 2017 [cited by applicant]
US 10146639B1 · Natanzon · 2018 [cited by examiner]
US 10228962B2 · Dornemann et al. · 2019 [cited by applicant]
US 10255143B2 · Vijayan et al. · 2019 [cited by applicant]
US 10310953B2 · Kumar · 2019 [cited by applicant]
US 10346259B2 · Gokhale et al. · 2019 [cited by applicant]
US 10379598B2 · Muller · 2019 [cited by applicant]
US 10387073B2 · Bhagi et al. · 2019 [cited by applicant]
US 10404799B2 · Mitkar · 2019 [cited by applicant]
US 10552268B1 · Xu · 2020 [cited by examiner]
US 10592145B2 · Bedadala et al. · 2020 [cited by applicant]
US 10592350B2 · Dornemann · 2020 [cited by applicant]
US 10684924B2 · Kilaru et al. · 2020 [cited by applicant]
US 10776329B2 · Ramohalli Gopala Rao et al. · 2020 [cited by applicant]
US 10791025B2 · Kumarasarny et al. · 2020 [cited by applicant]
US 10824375B1 · Natanzon · 2020 [cited by applicant]
US 10891198B2 · Nara et al. · 2021 [cited by applicant]
US 10970179B1 · Ruslyakov · 2021 [cited by applicant]
US 11023329B1 · Per · 2021 [cited by applicant]
US 11032146B2 · Kumarasamy · 2021 [cited by applicant]
US 11113246B2 · Mitkar et al. · 2021 [cited by applicant]
US 11223535B2 · Parvathamvenkatas · 2022 [cited by applicant]
US 11294786B2 · Degaonkar et al. · 2022 [cited by applicant]
US 11314687B2 · Kavaipatti Anantharamakrishnan et al. · 2022 [cited by applicant]
US 11321188B2 · Mitkar · 2022 [cited by applicant]
US 11340824B1 · Yadav · 2022 [cited by applicant]
US 11442896B2 · Agrawal · 2022 [cited by applicant]
US 11461184B2 · Ramohalli Gopala Rao et al. · 2022 [cited by applicant]
US 11494273B2 · Bansod et al. · 2022 [cited by applicant]
US 11500566B2 · Naik et al. · 2022 [cited by applicant]
US 11513922B2 · Kumar · 2022 [cited by applicant]
US 11526403B1 · Ruslyakov · 2022 [cited by applicant]
US 11579681B2 · Mohanty · 2023 [cited by applicant]
US 11604706B2 · Nara · 2023 [cited by applicant]
US 20060224846A1 · Amarendran · 2006 [cited by applicant]
US 20090319534A1 · Gokhale · 2009 [cited by applicant]
US 20110119665A1 · Santos · 2011 [cited by examiner]
US 20120150818A1 · Vijayan Retnamma et al. · 2012 [cited by applicant]
US 20120250686A1 · Vincent · 2012 [cited by examiner]
US 20150312176A1 · Jones · 2015 [cited by applicant]
US 20160099847A1 · Melander · 2016 [cited by applicant]
US 20160350391A1 · Vijayan et al. · 2016 [cited by applicant]
US 20170024260A1 · Chandrasekaran · 2017 [cited by examiner]
US 20170168903A1 · Dornemann et al. · 2017 [cited by applicant]
US 20170185488A1 · Kumarasamy et al. · 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 20180276085A1 · Mitkar · 2018 [cited by examiner]
US 20180285383A1 · Nara et al. · 2018 [cited by applicant]
US 20190068577A1 · Kunjaraman Pillai · 2019 [cited by applicant]
US 20190108341A1 · Bedhapudi et al. · 2019 [cited by applicant]
US 20190220359A1 · Srinivasan · 2019 [cited by applicant]
US 20200351339A1 · Savir · 2020 [cited by applicant]
US 20200364117A1 · Enakiev · 2020 [cited by applicant]
US 20210089215A1 · Ashraf et al. · 2021 [cited by applicant]
US 20210157628A1 · Dornemann et al. · 2021 [cited by applicant]
US 20210357246A1 · Kumar et al. · 2021 [cited by applicant]
US 20210397522A1 · Owen et al. · 2021 [cited by applicant]
US 20220012134A1 · Chatterjee · 2022 [cited by applicant]
US 20220156190A1 · Pradhan · 2022 [cited by applicant]
US 20220222104A1 · Dornemann et al. · 2022 [cited by applicant]
US 20230032790A1 · Mahajan · 2023 [cited by applicant]
CA 2634356A1 · 2007 [cited by applicant]
EP 0259912A1 · 1988 [cited by applicant]
EP 0405926A2 · 1991 [cited by applicant]
EP 0467546A2 · 1992 [cited by applicant]
EP 0541281 · 1993 [cited by applicant]
EP 0774715 · 1997 [cited by applicant]
EP 0809184 · 1997 [cited by applicant]
EP 0899662 · 1999 [cited by applicant]
EP 0981090 · 2000 [cited by applicant]
WO 9513580 · 1995 [cited by applicant]
WO 9912098 · 1999 [cited by applicant]
WO 2006052872 · 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]
Bailey, “When and How to use Sysprep”, Server Room, April 2, 2018, 6 pages. [cited by applicant]
Celesti et al., “Improving Virtual Machine Migration in Federated Cloud Environments”, 2010, pp. 61-67. [cited by applicant]
Chan, et al., “An Approach to High Availability for Cloud Servers with Snapshot Mechanism,” 2012, pp. 1-6. [cited by applicant]
Chervenak, et al., “Protecting File Systems—A Survey of Backup Techniques,” 1998, pp. 17-31. [cited by applicant]
CommVault Systems, Inc., “Enhanced Protection and Manageability of Virtual Servers,” Partner Solution Brief, 2008, 6 pages. [cited by applicant]
Data Protection for Large Vmware and Vblock Environments Using EMC Avamar Applied Technology, Nov. 2010, EMC Corporation, 26 pages. [cited by applicant]
Davis, D., “Understanding VMware VMX Configuration Files,” Petri IT Knowledgebase, <http://www.petri.co.il/virtual_vmware_vmx_configuration_files.htm>, internet accessed on Jun. 19, 2008, 6 pages. [cited by applicant]
Davis, D., “VMware Versions Compared,” Petri IT Knowledgebase, <http://www.petri.co.il/virtual_vmware_versions_compared.htm>, internet accessed on Apr. 28, 2008, 6 pages. [cited by applicant]
Eldos Callback File System product information from https://www.eldos.com/clients/104-345.php retrieved on Dec. 30, 2016 in 2 pages. [cited by applicant]
Eldos Usermode filesystem for your Windows applications—Callback File System® (CBFS®)—Create and manage virtual filesystems and disks from your Windows applications retrieved from https://eldos.com/cbfs on Dec. 30, 2016… [cited by applicant]
Granger, et al., “Survivable Storage Systems”, 2001, pp. 184-195. [cited by applicant]
Haselhorst, et al., “Efficient Storage Synchronization for Live Migration in Cloud Infrastructures”, 2011, pp. 511-518. [cited by applicant]
Hirofuchi, Takahiro et al. “A Live Storage Migration Mechanism Over WAN for Relocatable Virtual Machine Services on Clouds.” Proceedings of the 2009 9th IEEE/ACM International Symposium on Cluster Computing and the Grib… [cited by applicant]
Hu, Wenjin et al., “A Quantitative Study of Virtual Machine Live Migration,” 2013, pp. 1-10. [cited by applicant]
International Search Report and Written Opinion for PCT/US2011/054374, dated May 2, 2012, in 7 pages. [cited by applicant]
Ismail et al., “Architecture of Scalable Backup Service For Private Cloud”, IEEE Conference on Open Systems (ICOS), 2013, pp. 174-179. [cited by applicant]
Jander, “Launching Storage-Area Net,” Data Communications, US, McGraw Hill, NY, vol. 27, No. 4 (Mar. 21, 1998), pp. 64-72. [cited by applicant]
Javaraiah, et al., “Backup for Cloud and Disaster Recovery for Consumers and SMBs,” 2008, pp. 1-3. [cited by applicant]
Kim, et al., “Availability Modeling and Analysis of a Virtualized System,” 2009, pp. 365-371. [cited by applicant]
Kuo, et al., “A Hybrid Cloud Storage Architecture for Service Operational High Availability”, 2013, pp. 487-492. [cited by applicant]
Liang, et al., “A virtual disk environment for providing file system recovery”, 2006, pp. 589-599. [cited by applicant]
Lu et al.. “Virtual Machine Memory Access Tracing with Hypervisor Exclusive Cache”, Usenix Annual Technical Conference, 2007, pp. 29-43. [cited by applicant]
Mao, et al., “Read-Performance Optimization for Deduplication-Based Storage Systems in the Cloud”, 2014, pp. 1-22. [cited by applicant]
Margaret Rouse, “Definition of Availability Zones”, TechTarget, accessed on searchaws.techtarget.com/definition/availability-zones, Apr. 26, 2019, available on https://web.archive.org/web/20180911194556/https://searchaw… [cited by applicant]
Microsoft Corporation, “How NTFS Works,” Windows Server TechCenter, <http://technet2.mircrosoft.com/windowsserver/en/library/8cc5891d-bf8e-4164-862d-dac5418c5948 . . . >, updated Mar. 28, 2003, internet accessed Mar. 26… [cited by applicant]
Reingold, B. et al., “Cloud Computing: The Intersection of Massive Scalability, Data Security and Privacy (Part I),” LegalWorks, 2009, 5 pages. [cited by applicant]
Sanbarrow.com, “Files Used by a VM,” <http://sanbarrow.com/vmx/vmx-files-used-by-a-vm.html>, internet accessed on Jul. 22, 2008, 2 pages. [cited by applicant]
Somasundaram et al., Information Storage and Management. 2009, pp. 251-281. [cited by applicant]
Tran, et al., “Efficient Cooperative Backup with Decentralized Trust Management”, 2012, pp. 1-25. [cited by applicant]
Travostino, et al., “Seamless live migration of virtual machines over the MAN/WAN”, 2006, pp. 901-907. [cited by applicant]
Vaghani, “Virtual Machine File System”, 2010, pp. 57-70. [cited by applicant]
VMware, Inc., “The Open Virtual Machine Format Whitepaper for OVF Specification, version 0.9,” White Paper, <http://www.vmware.com>, 2007, 16 pages. [cited by applicant]
VMware, Inc., “Understanding VMware Consolidated Backup,” White Paper, <http://www.vmware.com>, accessed Apr. 30, 2014, 11 pages. [cited by applicant]
VMware, Inc., “Virtual Disk Format 1.1,” VMware Technical Note, <http://www.vmware.com>, Revision 20071113, Version 1.1, 2007, 18 pages. [cited by applicant]
VMware, Inc., “Virtualized iSCSI SANS: Flexible, Scalable Enterprise Storage for Virtual Infrastructures,” White Paper, <http://www.vmware.com>, Mar. 2008, 13 pages. [cited by applicant]
VMware, Inc., “VMware ESX 3.5,” Product Datasheet, <http://www.vmware.com>, 2008, 4 pages. [cited by applicant]
VMware, Inc., “VMware GSX Server 3.2, Disk Types: Virtual and Physical,” <http://www.vmware.com/support/gsx3/doc/disks.sub.--types.sub.--gsx.ht- ml>, internet accessed on Mar. 25, 2008, 2 pages. [cited by applicant]
VMware, Inc., “VMware Solution Exchange (VSX)” <http://www.vmware.com/appliances/learn/ovf.html>, 2014, 3 pages. [cited by applicant]
VMware, Inc., “VMware Workstation 5.0, Snapshots in a Process Tree,” <http://www.vmware.com/support/ws5/doc/ws.sub.--preserve.sub.--sshot.s- ub.--tree.html>, internet accessed on Mar. 25, 2008, 1 page. [cited by applicant]
VMware, Inc., “VMware Workstation 5.5, What Files Make Up a Virtual Machine?” <http://www.vmware.com/support/ws55/doc/ws.sub.--learning.su- b.--files.sub.--in.sub.--a.sub.-- vm.html>, internet accessed on Mar. 25, 2008,… [cited by applicant]
Vrable, et al., “Cumulus: Filesystem Backup to the Cloud”, 2009, pp. 1-28. [cited by applicant]
Wikipedia, “File Allocation Table,” <http://en.wikipedia.org/wiki/File.sub.--Allocation.sub.--Table>, internet accessed on Jul. 25, 2008, 19 pages. [cited by applicant]
Wikipedia, “Logical vol. Management,” <http://en.wikipedia.org/wiki/Logical_volume_management>, internet accessed on Mar. 26, 2008, 5 pages. [cited by applicant]
Wikipedia, “Storage Area Network,” <http://en.wikipedia.org/wiki/Storage_area_network>, internet accessed on Oct. 24, 2008, 5 pages. [cited by applicant]
Wikipedia, “Virtualization,” <http://en.wikipedia.org/wikiNirtualization>, internet accessed Mar. 18, 2008, 7 pages. [cited by applicant]
Wikipedia, Cloud Computing, en.wikipedia.org/wiki/Cloud_computing, accessed on Apr. 26, 2019, 13 Pages. [cited by applicant]
Yang, et al., “Toward Reliable Data Delivery for Highly Dynamic Mobile Ad Hoc Networks,” 2012, pp. 111-124. [cited by applicant]
Yoshida et al., “Orthros: A High-Reliability Operating System with Transmigration of Processes,” 2013, pp. 318-327. [cited by applicant]
Zhao, et al., “Adaptive Distributed Load Balancing Algorithm based on Live Migration of Virtual Machines in Cloud”, 2009, pp. 170-175. [cited by applicant]
Google Cloud Regions and Zones, accessed on https://cloud.google.com/compute/docs/regions-zones/, Apr. 26, 2019, available on https://web.archive.org/web/20190415102759/cloud.google.com/compute/docs/regions-zones/, Dec.… [cited by applicant]
Mell et al., The NIST Definition of Cloud Computing, 800-145, Sep. 2011. [cited by applicant]
Wikipedia, Sysprep, http://en.wikipedia.org/wiki/Sysprep (accessed Jul. 14, 2021). [cited by applicant]
Armstead et al., “Implementation of a Campus-wide Distributed Mass Storage Service: The Dream vs. Reality,” IEEE, Sep. 11-14, 1995, pp. 190-199. [cited by applicant]
Brandon, J., “Virtualization Shakes Up Backup Strategy,” <http://www.computerworld.com>, internet accessed on Mar. 6, 2008, 3 pages. [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]
Chen et al., “When Virtual Is Better Than Real”, IEEE 2001, pp. 133-138. [cited by applicant]
Chiappetta, Marco, “ESA Enthusiast System Architecture,” <http://hothardware.com/Articles/NVIDIA_ESA_Enthusiast_System_Architecture/>, Nov. 5, 2007, 2 pages. [cited by applicant]
CommVault Systems, Inc., “A CommVault White Paper: VMware Consolidated Backup (VCB) Certification Information Kit,” 2007, 23 pages. [cited by applicant]
CommVault Systems, Inc., “CommVault Solutions—VMware,” <http://www.commvault.com/solutions/vmware/>, accessed Apr. 30, 2014, 1 page. [cited by applicant]
Cully, et al., “Remus: High Availability via Asynchronous Virtual Machine Replication”, 2008, pp. 161-174. [cited by applicant]
Davis, D., “3 VMware Consolidated Backup (VCB) Utilities You Should Know,” Petri IT Knowlegebase, <http://www.petri.co.il/vmware-consolidated-backup-utilities.htm>, internet accessed on Jul. 14, 2008, 7 pages. [cited by applicant]
Davis, D., “VMware Server & Workstation Disk Files Explained,” Petri IT Knowledgebase, <http://www.petri.co.il/virtual_vmware_files_explained.htm>, internet accessed on Jun. 19, 2008, 5 pages. [cited by applicant]
Deng, et al., “Fast Saving and Restoring Virtual Machines with Page Compression”, 2011, pp. 150-157. [cited by applicant]
Eitel, “Backup and Storage Management in Distributed Heterogeneous Environments,” IEEE, Jun. 12-16, 1994, pp. 124-126. [cited by applicant]
Fraser et al., “Safe Hardware Access With the Xen Virtual Machine Monitor”, 1st Workshop on Operating System and Architectural Support for the demand IT Infrastructure (OASIS), 2004, pp. 1-10. [cited by applicant]
Galan et al. “Service Specification in Cloud Environments Based on Extension to Oper Standards” COMSWARE 09 Jun. 16-19, Dublin, Ireland ACM, 12 Pages. [cited by applicant]
Gibson, et al., “Implementing Preinstallation Environment Media for Use in User Support,” 2007, pp. 129-130. [cited by applicant]
Gupta, et al., “GPFS-SNC: An enterprise storage framework for virtual-machine clouds”, 2011, pp. 1-10. [cited by applicant]
Hirofuchi, et al., “Enabling Instantaneous Relocation of Virtual Machines with a Lightweight VMM Extension”, 2010, pp. 73-83. [cited by applicant]
Hu, et al., “Virtual Machine based Hot-spare Fault-tolerant System”, 2009, pp. 429-432. [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]
Ibrahim, Shadi et al., “Cloudlet: Towards MapReduce Implementation on Virtual Machines,” 2009, pp. 65-66. [cited by applicant]
International Preliminary Report on Patentability and Written Opinion for PCT/US2011/054374, dated Apr. 11, 13, 6 pages. [cited by applicant]
Jhawar et al., “Fault Tolerance Management in Cloud Computing: A System-Level Perspective”, IEEE Systems Journal, vol. 7, No. 2, 2013, pp. 288-297. [cited by applicant]
Jo, et al., “Efficient Live Migration of Virtual Machines Using Shared Storage”, 2013, pp. 1-10. [cited by applicant]
Kashyap “RLC—A Reliable approach to Fast and Efficient Live Migration of Virtual Machines in the Clouds” IEEE 2014 IEEE Computer Society, pp. 360-367. [cited by applicant]
Li et al. “Comparing Containers versus Virtual Machines for Achieving High Availability” 2015 IEEE, pp. 353-358. [cited by applicant]
Migrate a Virtual Machine with Storage vMotion in the vSphere Client. http://pubs.vmware.com/vsphere-51/advanced/ print/jsp?topic=/com.vmware.vsphere.vcent . . . Retrieved Aug. 12, 2014; 2 pages. [cited by applicant]
Nance et al., “Virtual Machine Introspection: Observation or Interference?”, 2008 IEEE, pp. 32-37. [cited by applicant]
Ng, Chun-Ho et al., “Live Deduplication Storage of Virtual Machine Images in an Open-Source Cloud,” 2011, pp. 80-99. [cited by applicant]
Nicolae, Bogdan et al., “A Hybrid Local Storage Transfer Scheme for Live Migration of 1/0 Intensive Workloads,” 2012, pp. 85-96. [cited by applicant]
Reingold, B et al., “Cloud Computing: Industry and Government Developments (Part II),” LegalWorks, Sep. 2009, 5 pages. [cited by applicant]
Reingold, B. et al., “Cloud Computing: Whose Law Governs the Cloud? (Part III),” LegalWorks, Jan.-Feb. 2010, 6 pages. [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-15. [cited by applicant]
Sanbarrow.com, “Disktype-table,” <http://sanbarrow.com/vmdk/disktypes.html>, internet accessed on Jul. 22, 2008, 4 pages. [cited by applicant]
Sanbarrow.com, “Monolithic Versus Split Disks,” <http://sanbarrow.com/vmdk/monolithicversusspllit.html>, internet accessed on Jul. 14, 2008, 2 pages. [cited by applicant]
Tudoran, Radu et al., “Adaptive File Management for Scientific Workflows on the Azure Cloud,” 2013, pp. 273-281. [cited by applicant]
VMware Storage VMotion—Non-Disruptive Live Migration for Virtual Machine Storage Disk Files. Copyright 2009 VMware, Inc.; 2 pages. [cited by applicant]
VMware, Inc., “OVF, Open Virtual Machine Format Specification, version 0.9,” White Paper, <http://www.vmware.com>, 2007, 50 pages. [cited by applicant]
VMware, Inc., “Using VMware Infrastructure for Backup and Restore,” Best Practices, <http://www.vmware.com>, accessed Apr. 30, 2014, 2006, 20 pages. [cited by applicant]
VMware, Inc., “Virtual Disk API Programming Guide,” <http://www.vmware.com>, Revision 20080411, 2008, 44 pages. [cited by applicant]
VMware, Inc., “VMware Consolidated Backup, Improvements in Version 3.5,” Information Guide, <http://www.vmware.com>, 2007, 11 pages. [cited by applicant]
VMware, Inc., “VMware Consolidated Backup,” Product Datasheet, <http://www.vmware.com>, 2007, 2 pages. [cited by applicant]
VMware, Inc., “VMware OVF Tool,” Technical Note, <http://www.vmware.com>, 2007, 4 pages. [cited by applicant]
VMware, Inc., “VMware Workstation 5.0, Snapshots in a Linear Process,” <http:/www.vmware.com/support/ws5/doc/ws.sub.--preserve.sub.--sshot.su- b.--linear.html>, internet accessed on Mar. 25, 2008, 1 page. [cited by applicant]
VSphere Storage vMotion: Storage Management & Virtual Machine Migration. http://www.vmware.com/products /vsphere/features/storage-vmotion. Retrieved Aug. 12, 2014; 6 pages. [cited by applicant]
Wikipedia, “Cluster (file system),” <http://en.wikipedia.org/wiki/Cluster.sub.--%,28file.sub.--system%29>-;, internet accessed Jul. 25, 2008, 1 page. [cited by applicant]
Wikipedia, “Cylinder-head-sector,” <http://en.wikipedia.org/wiki/Cylinder-head-sector>, Jan. 4, 2009, 6 pages. [cited by applicant]
Wikipedia, “Logical Disk Manager,” <http://en.wikipedia.org/wiki/Logical_Disk_Manager>, internet accessed Mar. 26, 2008, 3 pages. [cited by applicant]
Wood, et al., “Disaster Recovery as a Cloud Service: Economic Benefits & Deployment Challenges”, 2010, pp. 1-7. [cited by applicant]
Yang, et al., “TRAP-Array: A Disk Array Architecture Providing Timely Recovery to Any Point-in-time,” 2006, pp. 1-12. [cited by applicant]
Zhao, et al., “Supporting Application-Tailored Grid File System Sessions with WSRF-Based Services”, Advanced Computing and Information Systems Laboratory (ACIS), 2005, pp. 24-33. [cited by applicant]
Posey, “What is Sysprep and How Does It Work?”, Sysprep (System Preparation Tool), https://searchenterprisedesktop.techtarget.com/definition.Sysprep-System-Preperation-Tool, 4 pages. [cited by applicant]
Sysprep (Generalize) a Windows installation, Microsoft Does, May 2, 2017, https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep-generalize-a-window-installation in 6 pages. [cited by applicant]