Netapp, Inc.

Vasantha Sadananda Prabhu

Rushi Srinivas Surla

Gaurab Paul

Ritesh Tiwari

Ramanathan Padinjarel Somanathan

Pratik Murali

Amarnath Rachapudi

Priyanka Kasinath Surakanti

Karkala Pallavi Puranik

Kumar Dawani

Konstantinos Roussos

Boris Teterin

Nikhil Kaplingat

Girish Kumar

Anurag Kumar

Uttam Singh

Ebin Varghese Kadavy

Yogesh Basavani Suresh

Shivananda Kn

Backup of application data associated with an application executing in a virtual machine managed by a hypervisor is performed. Backup of the application data includes retrieving a Logical Unit Number (LUN) identification (ID) used by the application to store the application data in a storage volume. Backup of the application data also includes performing a virtual storage resolution for the LUN ID to determine whether the application data is stored in the storage volume identified by the LUN ID based on a first virtual mapping or a physical mapping. Backup also includes storing in metadata for the backup the LUN ID and whether the LUN ID is based on the first virtual mapping or the physical mapping. Backup includes creating a backup of the application data stored in the storage volume. Application data can subsequently be restored based on the application data that is backed up.

Backup and recovery of application data of an application executing in a virtual machine

Methods and systems for restoring a tenant database of a multitenant database system with multiple tenant databases is provided. In response to a request to restore a first tenant database, a system verifies that the first tenant database is present in the multitenant system database system with a same identifier when a backup of the first tenant database was taken during a backup operation and when the restore request was received. A restore method is selected based on a storage type used for storing the first tenant database. The selected restore method is executed for restoring the first tenant database utilizing an internal file associated with the first tenant database, while processing requests for other tenant databases.

Methods and systems for protecting multitenant databases in networked storage systems

Methods and systems for protecting a multitenant database system with multiple tenant databases are provided. One method includes accessing, by a processor, a backup of a source container database of a multitenant database system, the source container database hosting a plurality of tenant databases; generating, by the processor, a clone of the source container database from the backup, the clone of the source container database including clones of the plurality of tenant databases; exporting, by the processor, configuration information of a clone of a first tenant database from the clone of the source container database to a target container database; importing, by the processor, the clone of the first tenant database into the target container database; and removing, by the processor, the clone of the first tenant database from the cloned source container database, while retaining data files associated with the first tenant database.

Exemplary embodiments relate to techniques that allow for file system support to be rapidly deployed for new or updated operating system distributions. In some embodiments, a management component is provided perform data management on file systems. When a data management operation on a file system is requested, an operation component searches in a predetermined location for a named module that implements certain types of operations. The operation component then calls these operations (including validate, build and deport operations for the file system) to implement data management procedures in the file system. Implementing support for a new operating system or file system does not require that the management entity be rebuilt. Upon release of a new operating system or file system, a new named module can be written and placed in the predetermined location where the operation module is configured to search.

Data management of UNIX file systems

Method and system is provided to perform a plurality of checks before performing a volume based snapshot restore ('VBSR') operation. The checks may be performed by an application executed at a computing system that interfaces with a storage system. The application may determine if there are any inconsistent LUNS and foreign mapped LUNs. The application may also determine if there are any new LUNs or any new snapshots since the snapshot, which is the basis of the restore operation was created. The application may further determine if there are any backup relationships with respect to a volume that is being restored. The application takes the information and provides a report to a user. The report allows a user to ascertain the consequences of proceeding with the VBSR operation.

Method and system for volume based snapshot restore

A method, apparatus, and system of exclusive access during a critical sub-operation to enable simultaneous operations are disclosed. In one embodiment, a method of a host device includes identifying a critical sub-operation of an operation associated with a storage system, applying a lock associated with the critical sub-operation based on a type of the sub-operation, providing exclusive access of the critical sub-operation to a first instance requiring the critical sub-operation, denying other instances access to the critical sub-operation during an interval comprising a period when the first instance executes the critical sub-operation, and releasing the lock when the critical sub-operation is no longer required by the first instance. The first instance and the other instances may originate on different host devices.

Exclusive access during a critical sub-operation to enable simultaneous operations

Techniques introduced herein allow writeable PPIs to be re-used. A writeable PPI manager can make use of existing writeable PPIs to offer logical units to clients without creating additional writeable PPIs. The writeable PPI manager can determine which writeable PPIs to re-use by testing the writeable PPIs for a variety of conditions. Advantageously, re-use of remaining logical units reduces unnecessary replication of data and increased overhead costs. Resources can thereby be conserved.

System and method for re-use of writeable PPIs

According to one or more of the provisions set forth herein, data can be managed in a data storage system in an efficient manner. In one example, a first flexible copy volume of data is generated based on a snapshot copy volume of a flexible volume containing the data. The first flexible copy volume is configured to be operated upon according to a first set of operations. A second flexible copy of the data is also generated based on the snapshot copy volume. The second flexible copy volume is configured to be operated upon according to a second set of operations that differs from the first set of operations. Having a second copy of the data allows testing or other operations to be performed on the data while also maintaining an original version of the data.

Flexible copies having different sub-types

A method and system for generating authorization settings that indicate whether host administrators using a host-based storage-management application are authorized to perform provisioning operations on data storage entities residing on a data storage system are disclosed. Accordingly, a storage-management application receives from an administrator an authorization setting indicating on a per-user basis a set of provisioning operations which can be performed with a data storage entity via the storage-management application. The authorization settings are then communicated from the host-based storage-management application to the storage system where the data storage entity resides, and the authorization settings are stored. A storage-management application executing on any host can then utilize the authorization settings to control which users are allowed to interact with certain data storage entities, and what specific interactions (e.g., provisioning operations) are allowed.

Provisioning data storage entities with authorization settings

Method and system are provided for managing inactive snapshot blocks. Information regarding inactive blocks is collected and placed in a queue. After the queue reaches a threshold number of inactive blocks, the inactive blocks are compressed and stored as a compressed segment. The compressed segment may include inactive blocks for different snapshot data structures. A compression map structure stores information regarding a plurality of compressed segments, including identifiers identifying different snapshot files which may point to one or more inactive blocks. For each compressed segment, a compression information map identifies the location of each inactive block within the compressed segment and the compression state for each inactive block.

Method and system for managing inactive snapshot blocks

Techniques introduced herein allow writeable PPIs to be analyzed prior to deletion to determine whether or not the writeable PPIs have reached the end of their life cycle. Prior to deletion a writeable PPI manager can inspect the writeable PPI to determine whether or not the writeable PPI has reached the end of the writeable PPI life cycle. If various criteria are not met, then the writeable PPI can be determined to have not yet reached the end of its life cycle and the deletion can be prevented.

Growing community of inventors

Bengaluru, India

Vasantha Sadananda Prabhu