Browse Prior Art Database

Define virtual storage pool attributes based on storage volumes to be migrated

IP.com Disclosure Number: IPCOM000234650D
Publication Date: 2014-Jan-24
Document File: 6 page(s) / 213K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to automate the parameters needed for migrating storage subsystem volumes to a cloud environment and use these to successfully automate migration of the storage subsystem volumes to virtual pools. Described herein are the calculations and methods needed to move storage subsystem volumes to a desired virtual storage pool with the size and characteristics determined by the underlying storage subsystem volumes.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 50% of the total text.

Page 01 of 6

Define virtual storage pool attributes based on storage volumes to be migrated

Storage Subsystem virtualization is the preferred way to provision storage to cloud environments. A lot of legacy storage is not

virtualized, and movement of this legacy storage to a virtual environment is time consuming; it requires manual steps to add the virtualization layer between the storage subsystem storage and the services that use the storage. In order to gain the benefits of full virtualization, a storage administrator must understand the type and size of the storage meant for virtualization and develop the commands or scripts to convert this storage. This can be a very time consuming task, especially if there are many different volumes of different types and sizes that need virtualization.

Existing virtualizers require a storage administrator to copy data from different storage environments to a virtual environment with no awareness of the size and type of virtual pools needed for the migration. No known Storage Resource Management (SRM) applications leverage the awareness of the storage environments to derive the virtual pools needed for the migration.

A method is needed that enables storage administrators to automate the steps to determine the size and type of virtual pools

needed for the migration of storage subsystem volumes to a virtual environment.

The novel contribution is a method to automate the parameters needed for migrating storage subsystem volumes to a cloud environment and use these to successfully automate migration of the storage subsystem volumes to virtual pools. Described herein are the calculations and methods needed to move storage subsystem volumes to a desired virtual storage pool with the size and characteristics determined by the underlying storage subsystem volumes.

This method performs a number of functions. It calculates virtual storage pool size based on desired shortfall percentage, size, and number of storage volumes to be migrated from any storage device to virtual storage device. It calculates intermediate minimum pool size based on size of storage volumes and desired number of concurrent storage volumes to be migrated from any storage device to virtual storage device. The method provides suggested attributes based on attributes of storage volumes to be migrated from any storage device to virtual storage device, and facilitates the automation of migrating any storage volumes to virtual storage

The initial step is to identify the storage subsystem volumes that are surfaced to services that require virtualization. The storage subsystem volumes are either fully allocated volumes, known as thick volumes, or partially allocated volumes, known as thin volumes. Each storage subsystem volume has a specific allocated size, unallocated size, and total size. The additional storage parameters for consideration are Redundant Array of Independent Disk (RAID) level, encryption, and compression.

1


Page 02 of 6

Figure 1: Th...