IP Library › Granted Patent US 12,737,127
Granted Patent B2
US 12,737,127 · App. 19/015,297 · Granted Sep 15, 2026

Cloud based interface for protecting and managing data stored in networked storage systems

Inventors: Anu O. Mangaly (Bangalore, IN); Deen Dayal Pareta (Bangalore, IN); Sumeet Kumar Sethy (Bangalore, IN); Khaja Hussain Surajuddin (Coimbatore, IN)
Assignee: NetApp, Inc.
G06F3/0619G06F3/0605G06F3/0622G06F3/0659G06F3/067G06F9/547G06F11/1464G06F11/1469G06F21/44H04L67/1097H04L67/51
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,737,127
App. No.
19/015,297
Filed
Jan 9, 2025
Granted
Sep 15, 2026
Kind
B2
Art Unit
2443
USPC
709/226
Abstract

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.

Claims (44)

1 . A method, comprising:

deploying a storage service user interface (“SSUI”), the SSUI being configured to provision storage for an application to store a storage object using a cloud volume presented by a cloud layer;

initiating, by the SSUI, a storage service operation selected from a backup operation, a restore operation and a cloning operation associated with the storage object;

deploying, by the SSUI, 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 the storage service operation, wherein the connector module stores credentials for authenticating the application to use the storage micro-service layer;

tracking, by the SSUI, a protection status of the storage object for the application; and

generating, by the SSUI, an overview of the application, wherein the overview includes the protection status of the storage object for the application.

2 . The method of claim 1 , wherein the protection status of the storage object includes a status selected from a protected status, an unprotected status and a need attention status.

3 . The method of claim 1 , wherein deploying the SSUI includes validating, by a Software as a Service (“SaaS”) layer, an authorization message transmitted by the SSUI for deploying the SSUI.

4 . The method of claim 1 , wherein the SSUI is executed within a cloud manager user interface (“CMUI”).

5 . The method of claim 3 , 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.

6 . The method of claim 5 , further comprising:

transmitting, by the SSUI agent, the API request received from the SaaS layer to the storage micro-service layer; and

utilizing, by the storage micro-service layer, a plugin for the application 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 computer-readable storage medium containing program instructions, wherein execution of the program instructions by one or more processors of a computer causes the one or more processors to perform steps comprising:

deploying a storage service user interface (“SSUI”), the SSUI being configured to provision storage for an application to store a storage object using a cloud volume presented by a cloud layer;

initiating, by the SSUI, a storage service operation selected from a backup operation, a restore operation and a cloning operation associated with the storage object;

deploying, by the SSUI, an 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 the storage service operation, wherein the connector module stores credentials for authenticating the application to use the storage micro-service layer;

tracking, by the SSUI, a protection status of the storage object for the application; and

generating, by the SSUI, an overview of the application, wherein the overview includes the protection status of the storage object for the application.

9 . The non-transitory computer-readable storage medium of claim 8 , wherein the protection status of the storage object includes a status selected from a protected status, an unprotected status and a need attention status.

10 . The non-transitory computer-readable storage medium of claim 8 , wherein deploying the SSUI includes validating, by a Software as a Service (“SaaS”) layer, an authorization message transmitted by the SSUI for deploying the SSUI.

11 . The non-transitory computer-readable storage medium of claim 8 , wherein the SSUI is executed within a cloud manager user interface (“CMUI”).

12 . The non-transitory computer-readable storage medium of claim 10 , wherein the steps further comprise:

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.

13 . The non-transitory computer-readable storage medium of claim 12 , wherein the steps further comprise:

transmitting, by the SSUI agent, the API request received from the SaaS layer to the storage micro-service layer; and

utilizing, by the storage micro-service layer, a plugin for the application to execute the storage service operation.

14 . The non-transitory computer-readable storage medium of claim 8 , wherein the steps further comprise:

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.

15 . A system comprising:

a memory; and

one or more processors coupled to the memory, the one or more processors configured to execute machine executable code to;

deploy a storage service user interface (“SSUI”), the SSUI being configured to provision storage for an application to store a storage object using a cloud volume presented by a cloud layer;

initiate, by the SSUI, a storage service operation selected from a backup operation, a restore operation and a cloning operation associated with the storage object;

deploy, by the SSUI, an 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 the storage service operation, wherein the connector module stores credentials for authenticating the application to use the storage micro-service layer;

track, by the SSUI, a protection status of the storage object for the application; and

generate, by the SSUI, an overview of the application, wherein the overview includes the protection status of the storage object for the application.

16 . The system of claim 15 , wherein the protection status of the storage object includes a status selected from a protected status, an unprotected status and a need attention status.

17 . The system of claim 15 , wherein the machine executable code further causes the one or more processors to validate, by a Software as a Service (“SaaS”) layer, an authorization message transmitted by the SSUI for deploying the SSUI.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 9, 2025
From: MANGALY, ANU O.; PARETA, DEEN DAYAL; SETHY, SUMEET KUMAR; SURAJUDDIN, KHAJA HUSSAIN
To: NETAPP, INC.
Reel/Frame 069807/0378 →
Continuity (3)
Continuation 18207466 · Jun 8, 2023
Continuation 17242816 · Apr 28, 2021
Related Publication 20250348231A1 · Nov 13, 2025
References Cited (13)
US 9740568B2 · Karinta et al. · 2017 [cited by applicant]
US 9804929B2 · Karinta et al. · 2017 [cited by applicant]
US 10387263B2 · Karinta et al. · 2019 [cited by applicant]
US 10496488B2 · Karinta et al. · 2019 [cited by applicant]
US 11726664B2 · Mangaly et al. · 2023 [cited by applicant]
US 20160188417A1 · Karinta · 2016 [cited by examiner]
US 20200379781A1 · Rachapudi · 2020 [cited by examiner]
US 20220350496A1 · Mangaly et al. · 2022 [cited by applicant]
US 20230325095A1 · Mangaly et al. · 2023 [cited by applicant]
NETAPP., “SnapCenter® Software 4.2 Release Notes,” Aug. 2019, 41 pages. [cited by applicant]
NETAPP., “SnapCenter® Software 4.3.1 Release Notes,” Mar. 2020, 41 pages. [cited by applicant]
Non-Final Office Action mailed on Jun. 4, 2024 for U.S. Appl. No. 18/207,466, filed Jun. 8, 2023, 07 pages. [cited by applicant]
Notice of Allowance mailed on Sep. 11, 2024 for U.S. Appl. No. 18/207,466, filed Jun. 8, 2023, 07 pages. [cited by applicant]