Browse Prior Art Database

A system and method of recovering and migrating expansion data automatically

IP.com Disclosure Number: IPCOM000236724D
Publication Date: 2014-May-13
Document File: 7 page(s) / 72K

Publishing Venue

The IP.com Prior Art Database

Abstract

This invention provides a method of the expansion enclosure can be recovered and migrated data more efficiently and automatically. Thus we don't need to start copy services or system migrations again.Once user connects the expansion to controller, the configuration will be detected and analyzed, and a judgment will be made if the required information is in these expansions, then the virtual volumes can be identified by the storage system. This article first describes the background and problem existed now, and then raises the solution accroding to this problem. At last, this invention provides a detail implemetation, user can define a data redundancy configuration(eg:Tables,txt file,etc) in each expansion enclosure to record the configuration information which tell other system which Raid and Virtual Volumes can be recovered and identified when this expansion need to recover or migrate data.

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

Page 01 of 7

A system and method of recovering and migrating expansion data automatically

Current storage systems are using expansion drivers to extend the system capacity to satisfy the continuous growing product data. And data migration and integration is becoming very common requirement for users.

The traditional expansion data recovery or migration is dependent on the base controller, with only expansions will not help at all. What's more, traditional method is using copy services or system synchronization to recover and migrate data, users have to provide extra backup space and start copy services or synchronization and what's more, this is very time consuming.

Here are two situations:

1) The storage system is physically destroyed by accident, but the expansions are fine. If unfortunately there is no data backup all the data should be lost.

2) For some reason the data needs to be merged together between storage system A and storage system B. In other words, the data in storage system A needs to be migrated to storage system B. Usually users will use the copy services or system synchronization.

Basing on the current solutions, this invention brings up a direct and efficiency method to migrate or merge the expansion data among storage systems.

To implement the invention, we bring up two tables on each expansion enclosure.

The tables contain the expansion information, Raid information, drive information and virtual volume information, which will tell other system which Raid and virtual volumes can be recovered and identified when this expansion is connected to a new storage system.

With this invention we'll solve the two problems above very easily. For case 1), user could connect the expansions to a new storage system, from which the previous data (virtual volumes) storing in the expansions can be recovered. For case 2), user could easily migrate the data from storage system A to storage system B by connecting the expansions of storage system A to storage system B, and the data correctness and integrity could be ensured.

1


Page 02 of 7

By connecting one or more expansions to an existing storage system or new system, the tables on each expansion will be analyzed by the storage system, and if the required virtual volumes information is all in these expansions, then the virtual volumes can be identified by the storage system. Thus the expansion data can be recovered to the storage system and merged to the new storage system.

Below table will be stored on each expansion:

Table 1:

Name

Description

Expansion UID

The unified ID for this expansion, e.g. 0, 1, 2.

Raid ID

The ID for each Raid on this expansion, e.g. 0, 1, 2.

Raid level

The level of this Raid, e.g. 10, 5, 6.

Drive number

The count of drives the Raid contains, e.g. 6, 7, 8.

Drive slot number

The drive slot number, e.g. 1, 2, 3.

Drive expansion UID_Drive
ID The Raid may use drives from different expansions, this property it mark the drive's expansion ID and the drive ID, e.g. {0_0, 0_1,...