CN115373597A - Method, device and equipment for removing double live volumes of storage system and storage medium - Google Patents

Method, device and equipment for removing double live volumes of storage system and storage medium Download PDF

Info

Publication number
CN115373597A
CN115373597A CN202210901665.4A CN202210901665A CN115373597A CN 115373597 A CN115373597 A CN 115373597A CN 202210901665 A CN202210901665 A CN 202210901665A CN 115373597 A CN115373597 A CN 115373597A
Authority
CN
China
Prior art keywords
volume
identification information
slave
master
storage system
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210901665.4A
Other languages
Chinese (zh)
Inventor
蒋米传
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Inspur Intelligent Technology Co Ltd
Original Assignee
Suzhou Inspur Intelligent Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Suzhou Inspur Intelligent Technology Co Ltd filed Critical Suzhou Inspur Intelligent Technology Co Ltd
Priority to CN202210901665.4A priority Critical patent/CN115373597A/en
Publication of CN115373597A publication Critical patent/CN115373597A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G06F3/0607—Improving or facilitating administration, e.g. storage management by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629—Configuration or reconfiguration of storage systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application relates to a method, a device, equipment and a storage medium for dismantling double live volumes of a storage system, wherein the method comprises the following steps: receiving a primary volume deleting command; releasing the binding relationship between the main volume and the auxiliary volume in response to the main volume deleting command, and recovering the capacity space of the main volume; changing the identification information of the slave volume to the identification information of the master volume so that the host accesses the slave volume based on the identification information of the master volume. According to the method and the device, the replacement of the identification information of the secondary volume can be completed when the primary volume is deleted, and the accessed volume becomes the secondary volume when the host side continues to access the volume through the identification information. Because the dual activities are synchronous in real time and complete data exists in the secondary volume, the service is not influenced before and after switching, the application of the host end does not need to be reconfigured, and the host application is not sensed in the process of switching the identification information.

Description

Method, device and equipment for removing double live volumes of storage system and storage medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for removing dual live volumes of a storage system.
Background
Currently, in the storage system, the dual active storage system plays an important role. Active storage may enable information to be shared, accessed, or moved within a data center as well as between data centers, thereby consolidating various storage systems into a single resource. The storage system between two geographically separated data centers is allowed to simultaneously access data, professional virtual storage software runs on a cluster-type hardware engine, a host cluster can simultaneously access the same double live volumes through storage at two sides, and the double centers simultaneously provide external services, so that the resource utilization rate can be improved. That is, dual active storage is a disaster recovery backup scheme for a storage system, and the implementation mode is to let the master and slave data sites simultaneously undertake the services of users. The master data center and the slave data center are mutually backed up and perform real-time backup.
The double live volumes are formed by virtually integrating a master volume and a slave volume into one at a storage end, and mapping the master volume to a host bearer service. Because the host side accesses the dual live volumes by identifying the ID of the host volume, if the dual live volumes are not wanted to be used, only the entire dual live volumes can be deleted, or only the slave volumes can be deleted, and deletion of only the primary volumes of the dual live volumes is not allowed. When the primary volume has an unrecoverable problem, how to delete only the primary volume and ensure that the host service is not affected is a problem that needs to be solved.
Disclosure of Invention
Based on this, the application provides a storage system dual live volume dismounting method, device, equipment and storage medium, so as to solve the problems existing in the prior art.
In a first aspect, a storage system dual live volume teardown method is provided, where the method includes:
receiving a primary volume deleting command;
releasing the binding relationship between the master volume and the slave volume in response to the master volume deleting command, and recovering the capacity space of the master volume;
changing the identification information of the slave volume to the identification information of the master volume so that the host accesses the slave volume based on the identification information of the master volume.
According to an implementable manner in an embodiment of the present application, the unbinding of the primary volume and the secondary volume includes:
releasing the synchronous remote copy relationship of the primary volume and the secondary volume;
recovering the identification information of the slave volume.
According to an implementable aspect of an embodiment of the present application, before the changing the identification information of the slave volume to the identification information of the master volume, the method further includes:
and acquiring the identification information of the primary volume and the identification information of the secondary volume.
According to an implementation manner in an embodiment of the present application, the acquiring the identification information of the master volume and the identification information of the slave volume includes:
acquiring the identification information of the main volume, wherein the identification information of the main volume is first identification information;
and acquiring the identification information of the secondary volume, and acquiring the identification information of the secondary volume as second identification information.
According to an implementable aspect of an embodiment of the present application, the changing the identification information of the slave volume to the identification information of the master volume so that the host accesses the slave volume based on the identification information of the master volume includes:
changing the identification information of the slave volume to the first identification information, and recovering the second identification information so that the host accesses the slave volume based on the first identification information.
According to an implementable manner in an embodiment of the present application, the identification information includes: a universal unique identification code.
According to an implementation manner of the embodiment of the present application, the reclaiming the capacity space of the primary volume includes:
setting the capacity space allocated to the primary volume to zero.
In a second aspect, a storage system dual live volume dismounting device is provided, the device comprising:
a receiving unit: for receiving a primary volume delete command;
dismantling the unit: the system is used for responding to the main volume deleting command to release the binding relation between the main volume and the auxiliary volume and recover the capacity space of the main volume;
an identifier changing unit: and a controller configured to change the identification information of the slave volume to the master volume identification information, so that the host accesses the slave volume based on the identification information of the master volume.
In a third aspect, a computer device is provided, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores computer instructions executable by the at least one processor to enable the at least one processor to perform the method referred to in the first aspect above.
In a fourth aspect, a computer-readable storage medium is provided, on which computer instructions are stored, wherein the computer instructions are configured to cause a computer to perform the method according to the first aspect.
According to the technical content provided by the embodiment of the present application, the binding relationship between the master volume and the slave volume is released and the capacity space of the master volume is recovered by receiving a master volume deletion command, and then the identification information of the slave volume is changed to the identification information of the master volume, so that the host continues to access the slave volume based on the identification information of the master volume. Through the method, the replacement of the slave volume uuid is completed when the master volume is deleted, and the accessed volume becomes the slave volume when the host side continues to access the volume through the uuid. Because the dual activities are synchronous in real time and complete data exists in the secondary volumes, the service is not influenced before and after switching, the application of the host end does not need to be reconfigured, and the host application is not sensed in the uuid switching process. The problem of how to delete the main volume without influencing the service of the host after the main volume of the double live volumes is mapped to the host is solved.
Drawings
FIG. 1 is a flowchart illustrating a method for dual live volume destacking of a storage system in an embodiment;
FIG. 2 is a diagram of a storage system dual live volume teardown method in one embodiment;
FIG. 3 is a diagram of a storage system dual live volume teardown method in one embodiment;
FIG. 4 is a block diagram of a storage system dual live volume destacking assembly in one embodiment;
FIG. 5 is a schematic block diagram of a computer apparatus in one embodiment.
Detailed Description
The present application will be described in further detail below with reference to the drawings and examples. It should be understood that the specific embodiments described herein are merely illustrative of and not restrictive on the broad application.
Fig. 1 is a flowchart of a method for removing a dual live volume of a storage system according to an embodiment of the present application, where as shown in fig. 1, the method may include the following steps:
step 101: a primary volume delete command is received.
Specifically, the dual live volume is to virtually integrate the master volume and the slave volume into one at the storage end, and map the master volume to the host stub service, as shown in fig. 2. In a storage system, a logical volume is created, and a UUID (universal Unique Identifier) is automatically allocated to the logical volume, in a double active technology, a master volume and a slave volume are virtually integrated into one at a storage end, the UUID of the master volume is mapped to a host stub service, and the host end identifies a double active volume through the UUID of the master volume. As shown in fig. 2, the dual live volume in fig. 2 is a volume created from two site resource pools, each of which has 1 volume, and assuming that the UUID of the primary volume is 1 and the UUID of the secondary volume is 2, after the primary volume and the secondary volume are virtually integrated, that is, the storage system binds two volumes into one dual live volume, the dual live volume is mapped to the host through the UUID of the primary volume, that is, 1, and the host identifies and accesses the dual live volume through the UUID of 1.
Because the host side recognizes that the primary volume is the UUID, when the primary volume has an unrecoverable problem, the primary volume needs to be deleted, and because when the storage side deletes the logical volume, resources such as capacity and the UUID are recycled, and the host cannot continuously access the volume through the UUID, the prior art does not allow the primary volume of the double live volumes to be deleted, and if the double live volumes are not used, only the whole double live volumes or the secondary volumes are deleted. The method for removing the double live volumes of the storage system can be used for removing the main volumes of the double live volumes, and meanwhile, has no influence on host services. When the primary volume has the unrecoverable problem and needs to be deleted, a user issues a primary volume deleting command to the storage system, and the storage system receives the primary volume deleting command and executes the following operation. For example, in fig. 2, when site1 has a problem and causes the primary volume to be unavailable, the user only wants to delete the primary volume, and in order to ensure that the host service is not affected, the UUID of the primary volume needs to be reserved when the primary volume is deleted. The adopted mode is that a main volume deleting command is issued to the storage system, and the storage system receives the main volume deleting command.
Step 102: and releasing the binding relation between the master volume and the slave volume in response to the master volume deleting command, and recycling the capacity space of the master volume.
Specifically, after the storage system receives the primary volume deletion command, the storage system releases the binding relationship between the primary volume and the secondary volume in response to the primary volume deletion command, so that the primary volume and the secondary volume become two mutually independent volumes, and recovers the capacity space of the primary volume while reserving the UUID of the primary volume. The primary and secondary volume data of the dual live volumes can be kept synchronized in real time because a synchronous remote copy relationship is pre-established between the primary and secondary volumes. Therefore, the binding relationship between the master volume and the slave volume, that is, the synchronous copy relationship between the master volume and the slave volume is released, and the state values of the two volumes are cleared. Since the storage system disguises the UUID of the slave volume as the UUID of the master volume by virtualization when the master volume and the slave volume are bound, the value of the slave volume is restored from the UUID of the slave volume when the binding is released, for example, as shown in fig. 2, the UUID of the slave volume is originally 2, and the UUID of the slave volume is restored to 2 when the binding is released. The storage pool of the storage system is responsible for double live volume capacity management, and when a volume is newly created, the storage pool allocates the physical space applied by the double live volume and is responsible for space management. When a volume is deleted, the space is reclaimed from the storage pool and can be reallocated to other volumes. In this step, after the binding relationship between the master volume and the slave volume is released, the master volume and the slave volume become two mutually independent volumes, and based on the master volume deletion command, the storage system recovers the capacity space of the master volume and reserves the UUID of the master volume.
Step 103: the identification information of the slave volume is changed to the identification information of the master volume so that the host accesses the slave volume based on the identification information of the master volume.
Specifically, as shown in fig. 3, after the binding relationship between the master volume and the slave volume is released and the capacity space of the master volume is reclaimed, the primary volume of the dual live volumes is removed, which is equivalent to directly mapping the slave volume of site2 to the host. The identification information of the slave volume needs to be changed into the identification information of the master volume, that is, the UUID of the slave volume is changed into the UUID of the master volume, that is, the UUID of the slave volume of site2 is changed from original 2 into 1, so that the host continues to access the slave volume based on the identification information UUID of the master volume being 1, and the host application is not perceived and has no influence on the service.
It can be seen that, in the embodiment of the present application, by receiving a master volume deletion command, a binding relationship between a master volume and a slave volume is released, a capacity space of the master volume is recovered, and then, identification information of the slave volume is changed to identification information of the master volume, so that a host continues to access the slave volume based on the identification information of the master volume. Through the method, the replacement of the slave volume uuid is completed when the master volume is deleted, and the accessed volume becomes the slave volume when the host side continues to access the volume through the uuid. Because the dual activities are synchronous in real time and complete data exists in the secondary volumes, the service is not influenced before and after switching, the application of the host end does not need to be reconfigured, and the host application is not sensed in the uuid switching process. The problem of how to delete the main volume without influencing the service of the host after the double active volume main volume is mapped to the host is solved.
In one embodiment of the present application, the unbinding of the binding relationship between the master volume and the slave volume includes: the synchronous remote copying relation between the master volume and the slave volume is released; the identification information of the slave volume is recovered.
In particular, the primary and secondary volume data of the dual live volumes can be kept synchronized in real time because a synchronous remote copy relationship is pre-established between the primary and secondary volumes. Therefore, the binding relationship between the master volume and the slave volume, that is, the synchronous copy relationship between the master volume and the slave volume is released, and the state values of the two volumes are cleared. Since the storage system disguises the UUID of the slave volume as the UUID of the master volume by virtualization when the master volume and the slave volume are bound, it is necessary to restore the identification information of the slave volume when the binding is released, restore the UUID of the slave volume to the original value, for example, as shown in fig. 2, the UUID of the slave volume is originally 2, and restore the UUID of the slave volume to 2 when the binding is released. The storage pool of the storage system is responsible for double live volume capacity management, and when a volume is newly created, the storage pool allocates the physical space applied by the double live volume and is responsible for space management. When a volume is deleted, the space is reclaimed from the storage pool and can be reallocated to other volumes. In this step, after the binding relationship between the master volume and the slave volume is released, the master volume and the slave volume become two mutually independent volumes, and based on the master volume deletion command, the storage system recovers the capacity space of the master volume and reserves the UUID of the master volume.
In one embodiment of the present application, the identification information includes: a universally unique identification code.
Specifically, a Universally Unique Identifier, UUID (Universally Unique Identifier), is used to identify the dual live volumes, the master volume, and the slave volume by this.
In one embodiment of the present application, before changing the identification information of the slave volume to the identification information of the master volume, the method further includes: identification information of the master volume and identification information of the slave volume are acquired.
In one embodiment of the present application, acquiring identification information of a master volume and identification information of a slave volume includes: acquiring identification information of a main volume, wherein the identification information of the main volume is first identification information; and acquiring the identification information of the slave volume, wherein the identification information of the slave volume is obtained as second identification information.
Specifically, as shown in fig. 2, the dual live volume in fig. 2 is a volume created from each of two site resource pools and having 1 designated capacity, the UUID of the master volume is 1, the UUID of the slave volume is 2, and after the master volume and the slave volume are virtually integrated, that is, the storage system binds the two volumes into one dual live volume, the dual live volume is mapped to the host through the UUID of the master volume, that is, 1, and the host identifies and accesses the dual live volume through the UUID of 1. Before changing the identification information of the slave volume to the identification information of the master volume in step 103, the method further includes: identification information of the master volume and identification information of the slave volume are acquired. Acquiring identification information of a main volume, wherein the acquired identification information UUID of the main volume is first identification information 1; and acquiring the identification information of the slave volume, wherein the acquired identification information UUID of the slave volume is the second identification information (2).
In one embodiment of the present application, changing the identification information of the slave volume to the identification information of the master volume so that the host accesses the slave volume based on the identification information of the master volume includes: the identification information of the slave volume is changed to the first identification information, and the second identification information is recovered so that the host accesses the slave volume based on the first identification information.
Specifically, as shown in fig. 3, the identification information UUID of the secondary volume, that is, 2, is changed into the identification information UUID of the primary volume, that is, 1, the identification information UUID of the secondary volume of site2 is changed from original 2 into 1, so that the host continues to access the secondary volume based on the identification information UUID of the primary volume, that is, 1, and no perception to the application of the host and no influence to the service are realized.
In one embodiment of the present application, reclaiming the volume space of the primary volume includes: the capacity space allocated to the primary volume is set to zero.
Specifically, the storage pools of the storage system are responsible for capacity management, the physical space applied for by the storage pools is allocated when a volume is newly created, and are responsible for space management. When a volume is deleted, the storage pools reclaim the space and may reallocate it to other volumes by setting the capacity space allocated by the storage pools to the primary volume to zero.
According to the embodiment of the application, the binding relation between the master volume and the slave volume is released by receiving the master volume deleting command, the capacity space of the master volume is recovered, and then the identification information of the slave volume is changed into the identification information of the master volume, so that the host continuously accesses the slave volume based on the identification information of the master volume. Through the method, the replacement of the slave volume uuid is completed when the master volume is deleted, and the accessed volume becomes the slave volume when the host side continues to access the volume through the uuid. Because the dual activities are synchronous in real time and complete data exists in the secondary volumes, the service is not influenced before and after switching, the application of the host end does not need to be reconfigured, and the host application is not sensed in the uuid switching process. The problem of how to delete the main volume without influencing the service of the host after the double active volume main volume is mapped to the host is solved.
It should be understood that, although the steps in the flowchart of fig. 1 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in a strict order unless explicitly stated in the application, and may be performed in other orders. Moreover, at least a portion of the steps in fig. 1 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
Fig. 4 is a schematic structural diagram of a dual live-roll dismounting device of a storage system according to an embodiment of the present application, and as shown in fig. 4, the device may include: receiving section 401, removing section 402, and identifier changing section 403. The main functions of each component module are as follows:
the receiving unit 401: for receiving a primary volume delete command.
Specifically, the dual active volume is to virtually integrate two volumes, i.e., a master volume and a slave volume, into one at a storage end, and map the master volume to the host stub service, as shown in fig. 2. In a storage system, a logical volume is created, and a UUID (universal Unique Identifier) is automatically allocated to the logical volume. As shown in fig. 2, the dual active volume in fig. 2 is a volume created from two site resource pools, each of which has 1 designated capacity, assuming that the UUID of the master volume is 1 and the UUID of the slave volume is 2, the master volume and the slave volume are virtually integrated, that is, after the storage system binds two volumes into one dual active volume, the dual active volume is mapped to the host through the UUID of the master volume, that is, 1, and the host identifies and accesses the dual active volume through the UUID of the host, that is, 1.
Because the host side recognizes that the primary volume is the UUID, when the primary volume has an unrecoverable problem, the primary volume needs to be deleted, and because when the storage side deletes the logical volume, resources such as capacity and the UUID are recycled, and the host cannot continuously access the volume through the UUID, the prior art does not allow the primary volume of the double live volumes to be deleted, and if the double live volumes are not used, only the whole double live volumes or the secondary volumes are deleted. The method for removing the double live volumes of the storage system can be used for removing the main volumes of the double live volumes, and meanwhile, has no influence on host services. When the primary volume has an unrecoverable problem and needs to be deleted, the user issues a primary volume deletion command to the storage system, and the receiving unit 401 receives the primary volume deletion command and executes the following operations. For example, in fig. 2, when site1 has a problem and causes the primary volume to be unavailable, the user only wants to delete the primary volume, and in order to ensure that the host service is not affected, the UUID of the primary volume needs to be reserved when the primary volume is deleted. The adopted mode is that a main volume deleting command is issued to the storage system, and the storage system receives the main volume deleting command.
Detaching unit 402: and the system is used for releasing the binding relationship between the main volume and the auxiliary volume in response to the main volume deleting command and recovering the capacity space of the main volume.
Specifically, after the storage system receives the primary volume deletion command, the dismounting unit 402 is configured to release the binding relationship between the primary volume and the secondary volume in response to the primary volume deletion command, so that the primary volume and the secondary volume become two mutually independent volumes, and reclaim the capacity space of the primary volume while preserving the UUID of the primary volume. The primary and secondary volume data of the dual live volumes can be kept synchronized in real time because a synchronous remote copy relationship is pre-established between the primary and secondary volumes. Therefore, the binding relationship between the master volume and the slave volume, that is, the synchronous copy relationship between the master volume and the slave volume is released, and the state values of the two volumes are cleared. Since the storage system disguises the UUID of the slave volume as the UUID of the master volume by virtualization when the master volume and the slave volume are bound, the value of the slave volume is restored from the UUID of the slave volume when the binding is released, for example, as shown in fig. 2, the UUID of the slave volume is originally 2, and the UUID of the slave volume is restored to 2 when the binding is released. The storage pool of the storage system is responsible for double live volume capacity management, and when a volume is newly created, the storage pool allocates the physical space applied by the double live volume and is responsible for space management. When a volume is deleted, the space is reclaimed from the storage pool and can be reallocated to other volumes. In this step, after the binding relationship between the master volume and the slave volume is released, the master volume and the slave volume are changed into two mutually independent volumes, and based on the master volume deletion command, the storage system recovers the capacity space of the master volume and retains the UUID of the master volume.
Identifier changing section 403: and a controller for changing the identification information of the slave volume to the master volume identification information so that the host accesses the slave volume based on the identification information of the master volume.
Specifically, as shown in fig. 3, after the binding relationship between the master volume and the slave volume is released and the capacity space of the master volume is reclaimed, the primary volume of the dual live volumes is removed, which is equivalent to directly mapping the slave volume of site2 to the host. The identifier changing unit 403 is configured to change the identifier information of the secondary volume to the identifier information of the primary volume, that is, change the UUID of the secondary volume to the UUID of the primary volume, that is, change the UUID of the site2 secondary volume from original 2 to 1, so that the host continues to access the secondary volume based on the identifier information UUID of the primary volume being 1, thereby implementing no awareness to the application of the host and no influence on the service.
According to the embodiment of the application, the binding relation between the master volume and the slave volume is released by receiving the master volume deleting command, the capacity space of the master volume is recovered, and then the identification information of the slave volume is changed into the identification information of the master volume, so that the host continuously accesses the slave volume based on the identification information of the master volume. Through the method, the substitution of the slave volume uuid is completed when the master volume is deleted, and when the host side continues to access the volume through the uuid, the accessed volume becomes the slave volume. Because the dual activities are synchronous in real time and complete data exists in the slave volumes, the service is not influenced before and after switching, the application of the host end does not need to be reconfigured, and the host application is not perceived in the uuid switching process. The problem of how to delete the main volume without influencing the service of the host after the main volume of the double live volumes is mapped to the host is solved.
In one embodiment of the present application, the unbinding of the binding relationship between the master volume and the slave volume includes: releasing the synchronous remote copy relationship between the primary volume and the secondary volume; the identification information of the slave volume is recovered.
In one embodiment of the present application, before changing the identification information of the slave volume to the identification information of the master volume, the method further includes: identification information of the master volume and identification information of the slave volume are acquired.
In one embodiment of the present application, the obtaining of the identification information of the master volume and the identification information of the slave volume includes: acquiring identification information of a main volume, wherein the acquired identification information of the main volume is first identification information; and acquiring the identification information of the slave volume, wherein the identification information of the slave volume is obtained as second identification information.
In one embodiment of the present application, changing the identification information of the slave volume to the identification information of the master volume so that the host accesses the slave volume based on the identification information of the master volume includes: the identification information of the slave volume is changed to the first identification information, and the second identification information is recovered so that the host accesses the slave volume based on the first identification information.
In one embodiment of the present application, the identification information includes: a universal unique identification code.
In one embodiment of the present application, reclaiming the volume space of the primary volume includes: the capacity space allocated to the primary volume is set to zero.
According to the specific embodiment provided by the application, the technical scheme provided by the application can have the following advantages:
the application provides a mode through volume id automatic switch-over, guarantees that the business is not influenced when two live rolls are demolished, when deleting the main roll of two live rolls, from the volume id automatic switch-over to main volume id, guarantees that host computer business can continue to use main volume id to carry out read-write operation. And the host service is not influenced in the dismantling process, and the configuration of the upper application does not need to be adjusted and adapted. By receiving a master volume deletion command, the binding relationship between the master volume and the slave volume is released, the capacity space of the master volume is collected, and then the identification information of the slave volume is changed to the identification information of the master volume, so that the host continues to access the slave volume based on the identification information of the master volume. Through the method, the replacement of the slave volume uuid is completed when the master volume is deleted, and the accessed volume becomes the slave volume when the host side continues to access the volume through the uuid. Because the dual activities are synchronous in real time and complete data exists in the secondary volumes, the service is not influenced before and after switching, the application of the host end does not need to be reconfigured, and the host application is not sensed in the uuid switching process. The problem of how to delete the main volume without influencing the service of the host after the double active volume main volume is mapped to the host is solved.
The same and similar parts among the various embodiments are referred to each other, and each embodiment focuses on differences from other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and reference may be made to the partial description of the method embodiment for relevant points.
It should be noted that, in the embodiments of the present application, the user data may be used, and in practical applications, the user-specific personal data may be used in the schemes described herein within the scope permitted by applicable laws and regulations under the condition of meeting the requirements of applicable laws and regulations in the country (for example, explicit consent of the user, explicit notification of the user, explicit authorization of the user, and the like).
According to an embodiment of the present application, a computer device and a computer-readable storage medium are also provided. The application also provides a computer device comprising at least one processor, and a memory communicatively coupled to the at least one processor; wherein the memory stores computer instructions executable by the at least one processor, the computer instructions being executable by the at least one processor to enable the at least one processor to perform the method for dual live volume teardown of a storage system as described in any of the above embodiments.
Fig. 5 is a block diagram of a computer device according to an embodiment of the present application. Computer apparatus is intended to represent various forms of digital computers or mobile devices. Which may include desktop computers, laptop computers, workstations, personal digital assistants, servers, mainframe computers, and other suitable computers. Mobile devices may include tablet computers, smart phones, wearable devices, and the like.
As shown in fig. 5, the computer apparatus 500 includes a computing unit 501, a ROM 502, a RAM 503, a bus 504, and an input/output (I/O) interface 505, and the computing unit 501, the ROM 502, and the RAM 505 are connected to each other through the bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The calculation unit 501 may perform various processes in the method embodiments of the present application according to computer instructions stored in a Read Only Memory (ROM) 502 or computer instructions loaded from a storage unit 508 into a Random Access Memory (RAM) 505. The computing unit 501 may be a variety of general and/or special purpose processing components with processing and computing capabilities. The computing unit 501 may include, but is not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. In some embodiments, the methods provided by the embodiments of the present application may be implemented as a computer software program tangibly embodied in a computer-readable storage medium, such as storage unit 508.
The RAM 505 may also store various programs and data required for the operation of the device 500. Part or all of the computer program may be loaded and/or installed on the device 500 via the ROM 502 and/or the communication unit 509.
An input unit 506, an output unit 507, a storage unit 508, and a communication unit 509 in the computer apparatus 500 may be connected to the I/O interface 505. The input unit 506 may be, for example, a keyboard, a mouse, a touch screen, a microphone, or the like; the output unit 507 may be, for example, a display, a speaker, an indicator lamp, or the like. The device 500 can exchange information, data, and the like with other devices through the communication unit 509.
It should be noted that the device may also include other components necessary to achieve proper operation. It may also contain only the components necessary to implement the solution of the present application and not necessarily all of the components shown in the figures.
Various implementations of the systems and techniques described here can be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof.
Computer instructions for implementing the methods of the present application may be written in any combination of one or more programming languages. These computer instructions may be provided to the computing unit 501 such that the computer instructions, when executed by the computing unit 501 such as a processor, cause the steps involved in the method embodiments of the present application to be performed.
The present application further provides a computer-readable storage medium, on which computer instructions are stored, where the computer instructions are used to cause a computer to execute the method for dual live volume teardown of a storage system according to any one of the above embodiments.
The computer-readable storage medium provided herein may be a tangible medium that may contain, or store, computer instructions for performing the steps involved in the method embodiments of the present application. The computer readable storage medium may include, but is not limited to, storage media in the form of electronic, magnetic, optical, electromagnetic, and the like.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims (10)

1. A storage system double live volume dismantling method is characterized by comprising the following steps:
receiving a main volume deleting command;
releasing the binding relationship between the main volume and the auxiliary volume in response to the main volume deleting command, and recovering the capacity space of the main volume;
changing the identification information of the slave volume to the identification information of the master volume so that the host accesses the slave volume based on the identification information of the master volume.
2. The storage system dual live volume teardown method of claim 1, wherein the unbinding of the primary volume and the secondary volume comprises:
releasing the synchronous remote copy relationship of the master volume and the slave volume;
recovering the identification information of the slave volume.
3. The storage system dual live volume teardown method according to claim 2, further comprising, before the changing the identification information of the slave volume to the identification information of the master volume:
and acquiring the identification information of the master volume and the identification information of the slave volume.
4. The storage system dual live volume teardown method of claim 3, wherein the obtaining the identification information of the primary volume and the identification information of the secondary volume comprises:
acquiring identification information of the main volume, wherein the identification information of the main volume is first identification information;
and acquiring the identification information of the secondary volume, and acquiring the identification information of the secondary volume as second identification information.
5. The storage system dual live volume teardown method according to claim 4, wherein the changing the identification information of the slave volume to the master volume identification information so that the host accesses the slave volume based on the identification information of the master volume includes:
changing the identification information of the slave volume to the first identification information, and recovering the second identification information, so that the host accesses the slave volume based on the first identification information.
6. The storage system dual live volume teardown method of any one of claims 1 to 5, wherein the identification information comprises: a universal unique identification code.
7. The storage system dual live volume destacking method according to claim 1, wherein the reclaiming the capacity space of the primary volume comprises:
setting the capacity space allocated to the primary volume to zero.
8. A storage system dual live roll destacking apparatus, comprising:
a receiving unit: for receiving a primary volume delete command;
dismantling the unit: the system is used for responding to the main volume deleting command to release the binding relation between the main volume and the auxiliary volume and recover the capacity space of the main volume;
an identifier changing unit: for changing the identification information of the slave volume to the master volume identification information, so that the host accesses the slave volume based on the identification information of the master volume.
9. A computer device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein, the first and the second end of the pipe are connected with each other,
the memory stores computer instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.
10. A computer-readable storage medium having stored thereon computer instructions for causing a computer to perform the method of any one of claims 1 to 7.
CN202210901665.4A 2022-07-28 2022-07-28 Method, device and equipment for removing double live volumes of storage system and storage medium Pending CN115373597A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210901665.4A CN115373597A (en) 2022-07-28 2022-07-28 Method, device and equipment for removing double live volumes of storage system and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210901665.4A CN115373597A (en) 2022-07-28 2022-07-28 Method, device and equipment for removing double live volumes of storage system and storage medium

Publications (1)

Publication Number Publication Date
CN115373597A true CN115373597A (en) 2022-11-22

Family

ID=84063951

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210901665.4A Pending CN115373597A (en) 2022-07-28 2022-07-28 Method, device and equipment for removing double live volumes of storage system and storage medium

Country Status (1)

Country Link
CN (1) CN115373597A (en)

Similar Documents

Publication Publication Date Title
US11550675B2 (en) Remote data replication method and system
CN102594849B (en) Data backup and recovery method and device, virtual machine snapshot deleting and rollback method and device
EP2002339B1 (en) Use of volume containers in replication and provisioning management
US11093162B2 (en) Method and apparatus for deleting cascaded snapshot
CN111078667B (en) Data migration method and related device
CN104391873A (en) Database operation separation method and database operation separation system
US20070233753A1 (en) Database system management method, database system, database device, and backup program
JP2007072975A (en) Apparatus for switching systems for writing transaction data to disk, switching method, and switching program
JP6475304B2 (en) Transaction processing method and apparatus
CN106469117B (en) Storage resource management method and device for virtual machine storage migration
CN106777394B (en) Cluster file system
US20200218573A1 (en) Memory management method, electronic apparatus, and storage device
CN104750573A (en) Whole-consistency back-up and restoration methods for data nodes of distributed data system
CN110968417B (en) Method, apparatus, system and computer storage medium for managing storage units
CN111666266A (en) Data migration method and related equipment
CN104035728A (en) Hard disk hot plug handling method, device and node
CN107402839B (en) Method and system for backing up data
WO2012066605A1 (en) Storage control apparatus and logical volume size setting method
WO2016107219A1 (en) Data recovery method and apparatus
WO2023241528A1 (en) Data processing method and apparatus
US10235089B2 (en) Storage control device, method and storage system to backup data using allocation information
CN111124256B (en) Method, apparatus and computer program product for managing storage
CN115373597A (en) Method, device and equipment for removing double live volumes of storage system and storage medium
CN103729301A (en) Data processing method and device
CN107783826A (en) A kind of virtual machine migration method, apparatus and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination