Veritas Technologies LLC

Symantec Corporation

Soumya Tripathy

Subhadeep Ghosh

Aditya Deshpande

Mohini Rahalkar

Mahendra Karmuse

Amit Gupte

Selvaraj M

Disclosed are methods and systems that include receiving updated operating system information, encrypting the updated operating system information, and updating a map file. The updated operating system information is received at an encryption virtual machine. The encrypting the updated operating system information results in the encrypted updated operating system information. The encrypting the updated operating system information is managed by the encryption virtual machine. The updated operating system information is encrypted in response to receipt of the updated operating system information. The updated operating system information is encrypted using an encryption key. In certain embodiments, the updating includes storing operating system metadata in the map file (where the operating system metadata is associated with the encrypted updated operating system information) and storing the encryption key in the map file (where the storing the encryption key in the map file associates the encryption key with the operating system metadata).

Protecting virtual machine data in cloud environments

Various systems, methods, and processes to protect virtual machine data in cloud computing environments are disclosed. A request for application data is received. The application data is encrypted, the request is received at an encryption virtual machine, and the encryption virtual machine is configured to receive the request from application virtual machines via loaders. A map file is accessed to identify an application virtual machine for which the application data is requested and the application data is accessed in a storage volume. The storage volume is communicatively coupled to the encryption virtual machine, and the encryption virtual machine is coupled between the application virtual machines and the storage volume. The application data is received from the storage volume and decrypted at the encryption virtual machine. The decrypted application data is sent to the loaders.

A computer-implemented method for automated delivery and identification of virtual drives may include (1) creating a drive-template archive that contains a collection of virtual-drive templates, each of which contains a unique burned-in configuration identifier, (2) receiving, a provision request to provision a virtual drive for a requesting virtual machine, (3) fulfilling the provision request by (A) creating a copy of an appropriate virtual-drive template that matches the specification of the provision request and (B) providing the copy of the appropriate virtual-drive template to the requesting virtual machine, and (4) utilizing, at the requesting virtual machine, the copy of the appropriate virtual-drive template in response to determining that the burned-in configuration identifier of the copy of the appropriate virtual-drive template corresponds to a drive configuration that fulfills the provision request. Various other methods, systems, and computer-readable media are also disclosed.

Systems and methods for automated delivery and identification of virtual drives

Various systems, methods, and processes to protect virtual machine data in a cloud environment are disclosed. A request for requested data is received at an encryption virtual machine. The requested data is encrypted, and the encryption virtual machine is configured to receive the request from an application virtual machine via a loader. The requested data includes one or more operating system modules, and the operating system modules are configured to be used by the application virtual machine. The requested data is accessed in a storage volume, which is communicatively coupled to the encryption virtual machine. The requested data is then retrieved from the storage volume and decrypted at the encryption virtual machine. The decrypted data is then sent to the loader.

A computer-implemented method for performing fast failovers may include 1) identifying an application to fail over from a first computing system to a second computing system, 2) identifying a first component of the application to fail over, the first component depending on a second component of the application and a third component of the application, the second component and third component being mutually independent, and 3) failing the application over from the first computing system to the second computing system by, based on a determination that the second component and third component are mutually independent, (i) taking the second component offline on the first computing system after taking the first component offline on the first computing system and (ii) taking the third component offline on the first computing system while bringing the second component online on the second computing system. Various other methods, systems, and computer-readable media are also disclosed.

Growing community of inventors

West Bengal, India

Soumya Tripathy