Cloud based interface for protecting and managing data stored in networked storage systems
Methods and systems for managing storage is provided. One method includes initializing, a storage service user interface (“SSUI”) within a cloud manager user interface (“CMUI”), the SSUI enables a storage service operation selected from a backup operation, a restore operation and a cloning operation associated with a storage object stored at a cloud volume presented by a cloud layer, the CMUI presented by a cloud provider; transmitting, by the SSUI, an authorization token to a Software As a Service (“SaaS”) layer for authenticating deployment of the SSUI; upon validating the authorization token, initializing a SSUI agent to interface with a deployed storage micro-service layer offered by the cloud layer to execute the storage service operation; transmitting, by the SSUI, an application programming interface (API) request for the SSUI agent for executing the storage service operation; and executing, by the deployed storage micro-service layer, the storage service operation.
1. A method, comprising:
validating, by a Software as a Service (“SaaS”) layer, an authorization message transmitted by a storage service user interface (“SSUI”) for deploying the SSUI, the SSUI configured to provision storage for an application to store a storage object using a cloud volume presented by a cloud layer;
upon successful validation, deploying a SSUI agent within a connector module in the cloud layer for interfacing with a storage micro-service layer offered by the cloud layer to execute a storage service operation selected from a backup operation, a restore operation and a cloning operation associated with the storage object; wherein the connector module stores credentials for authenticating the application to use the storage micro-service layer; and
executing, by the storage micro-service layer, the storage service operation.
2. The method of claim 1 , wherein the SSUI is executed within a cloud manager user interface (“CMUI”).
3. The method of claim 1 , further comprising:
transmitting, by the SSUI, an application programming interface (API) request for the SSUI agent for the storage service operation; and
receiving, by the SaaS layer, the API request and forwarding the API request to the SSUI agent.
4. The method of claim 3 , further comprising:
transmitting, by the SSUI agent, the API request received from the SaaS layer to the storage micro-service layer.
5. The method of claim 4 , further comprising:
utilizing, by the storage micro-service layer, a first plugin to execute the storage service operation.
6. The method of claim 4 , further comprising:
utilizing, by the storage micro-service layer, a second plugin to execute the storage service operation.
7. The method of claim 1 , further comprising:
generating, by the SSUI, a topology view for the application indicating whether a local backup, a remote backup or both the local backup and the remote backup have been taken for the storage object.
8. A non-transitory machine readable storage medium having stored thereon instructions for performing a method, comprising machine executable code which when executed by at least one machine, causes the machine to:
validate, by a Software as a Service (“SaaS”) layer, an authorization message transmitted by a storage service user interface (“SSUI”) for deploying the SSUI, the SSUI configured to provision storage for an application to store a storage object using a cloud volume presented by a cloud layer;
upon successful validation, deploy a SSUI agent within a connector module in the cloud layer for interfacing with a storage micro-service layer offered by the cloud layer to execute a storage service operation selected from a backup operation, a restore operation and a cloning operation associated with the storage object;
wherein the connector module stores credentials for authenticating the application to use the storage micro-service layer; and
execute, by the storage micro-service layer, the storage service operation.
9. The non-transitory machine readable storage medium of claim 8 , wherein the SSUI is executed within a cloud manager user interface (“CMUI”).
10. The non-transitory machine readable storage medium of claim 8 , wherein the machine executable code further causes the machine to:
transmit, by the SSUI, an application programming interface (API) request for the SSUI agent for the storage service operation; and
receive, by the SaaS layer, the API request and forward the API request to the SSUI agent.
11. The non-transitory machine readable storage medium of claim 10 , wherein the machine executable code further causes the machine to:
transmit, by the SSUI agent, the API request received from the SaaS layer to the storage micro-service layer.
12. The non-transitory machine readable storage medium of claim 10 , wherein the machine executable code further causes the machine to:
utilize, by the storage micro-service layer, a first plugin to execute the storage service operation.
13. The non-transitory machine readable storage medium of claim 10 , wherein the machine executable code further causes the machine to:
utilize, by the storage micro-service layer, a second plugin to execute the storage service operation.
14. The non-transitory machine readable storage medium of claim 8 , wherein the machine executable code further causes the machine to:
generate, by the SSUI, a topology view for the application indicating whether a local backup, a remote backup or both the local backup and the remote backup have been taken for the storage object.
15. A system, comprising:
a memory containing machine readable medium comprising machine executable code having stored thereon instructions; and a processor coupled to the memory, the processor configured to execute the machine executable code to:
validate, by a Software as a Service (“SaaS”) layer, an authorization message transmitted by a storage service user interface (“SSUI”) for deploying the SSUI, the SSUI configured to provision storage for an application to store a storage object using a cloud volume presented by a cloud layer;
upon successful validation, deploy a SSUI agent within a connector module in the cloud layer for interfacing with a storage micro-service layer offered by the cloud layer to execute a storage service operation selected from a backup operation, a restore operation and a cloning operation associated with the storage object;
wherein the connector module stores credentials for authenticating the application to use the storage micro-service layer; and
execute, by the storage micro-service layer, the storage service operation.
16. The system of claim 15 , wherein the SSUI is executed within a cloud manager user interface (“CMUI”).
17. The system of claim 15 , wherein the machine executable code further causes to:
transmit, by the SSUI, an application programming interface (API) request for the SSUI agent for the storage service operation; and
receive, by the SaaS layer, the API request and forward the API request to the SSUI agent.
18. The system of claim 17 , wherein the machine executable code further causes to:
transmit, by the SSUI agent, the API request received from the SaaS layer to the storage micro-service layer; and
utilize, by the storage micro-service layer, a first plugin for the application to execute the storage service operation.
19. The system of claim 18 , wherein the machine executable code further causes to:
utilize, by the storage micro-service layer, a second plugin for the application to execute the storage service operation.
20. The system of claim 15 , wherein the machine executable code further causes to:
generate, by the SSUI, a topology view for the application indicating whether a local backup, a remote backup or both the local backup and the remote backup have been taken for the storage object.