WO2012063311A1 - Procédé de commande de calculateur, système de calculateur et support de stockage - Google Patents

Procédé de commande de calculateur, système de calculateur et support de stockage Download PDF

Info

Publication number
WO2012063311A1
WO2012063311A1 PCT/JP2010/069857 JP2010069857W WO2012063311A1 WO 2012063311 A1 WO2012063311 A1 WO 2012063311A1 JP 2010069857 W JP2010069857 W JP 2010069857W WO 2012063311 A1 WO2012063311 A1 WO 2012063311A1
Authority
WO
WIPO (PCT)
Prior art keywords
computer
disk volume
data
disk
bad block
Prior art date
Application number
PCT/JP2010/069857
Other languages
English (en)
Japanese (ja)
Inventor
俊幸 馬場
勇介 筒井
智斉 内田
高本　良史
Original Assignee
株式会社日立製作所
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 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to PCT/JP2010/069857 priority Critical patent/WO2012063311A1/fr
Publication of WO2012063311A1 publication Critical patent/WO2012063311A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0712—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a virtual computing platform, e.g. logically partitioned systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0727—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a storage system, e.g. in a DASD or network based storage system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G06F11/0778—Dumping, i.e. gathering error/state information after a fault for later diagnosis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring

Definitions

  • the present invention relates to a technique for operating a disk volume replica on a computer, and more particularly to a technique for operating a disk volume replica on a virtual machine.
  • P2V uses image conversion software such as VMware (registered trademark), vCenter, Converter, etc., and is used to operate the disk image format of the system that includes the OS and applications running on the physical server on the virtual server. This is realized by converting to a format for the conversion unit.
  • VMware registered trademark
  • vCenter vCenter
  • Converter etc.
  • the conventional P2V technology has the following problems.
  • a format error is converted from a disk image of a physical server to a disk image of a virtual server, if a read error occurs in a specific physical block, the conversion of the format process cannot be completed and P2V may fail.
  • an object of the present invention is to complete the replication of the disk image even if an error occurs when reading the disk volume.
  • the present invention includes a computer including a processor and a memory, a management computer connected to the computer and including a processor and a memory, a first disk volume connected to the management computer, the management computer, and the computer.
  • a computer control method for providing a second disk volume, writing a copy of the first disk volume to the second disk volume, and allowing the computer to access the second disk volume comprising: A first step in which the computer reads the data of the first disk volume; and a second step of determining whether an error has occurred when the management computer reads the data of the first disk volume.
  • a fifth step in which the management computer allocates the second disk volume to the computer a sixth step in which the management computer transmits the bad block management information to the computer,
  • the seventh step in which the computer receives the bad block management information, and when the computer accesses the second disk volume, the access position is determined by referring to the received bad block management information.
  • the second disk volume is The process of writing a copy of one disk volume can be continued. Then, the second disk volume can notify the computer using the second disk volume of the error by managing the block in which the error has occurred with the bad block management information.
  • FIG. 5 is a block diagram illustrating an example of a management server when the virtual disk 501 is restored with dump data according to the embodiment of this invention.
  • FIG. 1 is a block diagram showing an example of the configuration of a computer system according to an embodiment of the present invention.
  • a physical server 110-1 a physical server 110-2 that provides virtual servers 109-1 to 109-n, and a management server 101 that manages the physical servers 110-1 and 110-2 are connected via a network 108.
  • the physical servers 110-1 and 110-2 and the management server 101 are connected to a storage apparatus 115 having a plurality of disk volumes 116p, 116d, and 116v via a network (not shown) (for example, SAN: Storage Area Network).
  • a network not shown
  • SAN Storage Area Network
  • the physical server 110-1 and 110-2 are generically indicated by reference numeral 110
  • the virtual servers 109-1 to 109-n are generically indicated by reference numeral 109
  • the physical server 110-1 is connected to a disk volume 116p storing a business system including an OS 210 and an application (not shown), and loads the OS 210 and an application (not shown) into a memory for execution.
  • the OS 210 includes a dump information acquisition unit 114 that dumps the contents of the memory of the physical server 110-1.
  • the physical server 110-1 is also connected to the disk volume 116d, and writes the dump data (memory dump) 401 acquired by the dump information acquisition unit 114 to the disk volume 116d.
  • the physical server 110-1 uses the disk volume 116p as a boot disk.
  • the physical server 110-2 executes the virtualization unit 111 and provides a plurality of virtual servers 109-1 to 109-n.
  • the physical server 110-2 is connected to the disk volume 116v that stores the virtual disk 501-0, and the virtualization unit 111 reads the virtual disk 501-0 and provides the virtual server 109-1.
  • the virtualization unit 111 can be configured by a virtual machine monitor (VMM) or a hypervisor that generates a virtual server 109 by virtualizing physical computer resources (hereinafter, physical resources) of the physical server 110-2. .
  • the physical server 110 that provides the virtual server 109 includes a plurality of physical servers 110-2 to 110-i as shown in FIG. In each physical server 110, the virtualization unit 111 is operating, and the virtual server 109 is executed on each virtualization unit 111. Note that reference numeral 501 is used as a generic name of the virtual disk 501-0.
  • the management server 101 includes a virtualization unit 111 of a plurality of physical servers 110, a virtualization management unit 102 that manages the virtual server 109 executed on the virtualization unit 111, and a disk volume 116p used by the physical server 110-1.
  • the P2V execution management unit 103 converts the virtual unit 111 to a virtual disk that can be used in block units, and various tables.
  • the virtualization management unit 102 includes a physical server management table 104 that manages physical resources of a plurality of physical servers 110, a virtual server 109 generated by the virtualization unit 111 on each physical server 110, a virtual server management table 105, The virtual disk management table 107 that manages the virtual disk 501 assigned to the server 109 is used. These tables are set by a manager or the like from a management terminal (not shown).
  • the P2V execution management unit 103 When converting the disk volume 116 of the physical server 110 to the virtual disk 501, the P2V execution management unit 103 records a defective block management table 106 that records an error occurrence location (bad block) of the disk volume 116p, and a virtual disk management table 107. Is used.
  • the bad block management table 106 is generated by the P2V execution management unit 103.
  • the virtualization management unit 102 holds the correspondence between the virtual disk 501 and the virtual server 109, and the P2V execution management unit 103 determines whether there is an error for each virtual disk 501 and the conversion source of the virtual disk 501.
  • the relationship of the physical server 110 is maintained.
  • FIG. 2 is a block diagram showing a detailed configuration of the management server 101.
  • the management server 101 includes a processor 202 that performs arithmetic processing, a memory 201 that stores data and programs, a network interface 203 that communicates with the network 108, and a disk interface 204 that accesses the storage device 115.
  • the management server 101 includes an input device and an output device (not shown).
  • the input device is composed of, for example, a mouse and a keyboard.
  • the output device is composed of a display device, for example.
  • the memory 201 stores the above-described virtualization management unit 102, P2V execution management unit 103, and various tables.
  • the virtualization management unit 102 and the P2V execution management unit 103 are programs executed by the processor 202.
  • the virtualization management unit 102 and the P2V execution management unit 103 are stored in a storage device 115 as a storage medium, and are read into the memory 201 by the processor 202 and executed.
  • the virtualization management unit 102 stores a physical server management table 104, a virtual server management table 105, and a virtual disk management table 107 on the memory 201.
  • the P2V execution management unit 103 stores the bad block management table 106 in the memory 201.
  • the virtualization management unit 102 manages the virtual server 109 by controlling the virtualization unit 111 of the plurality of physical servers 110.
  • the virtualization management unit 102 receives an administrator command from an input device (not shown), and commands the virtualization unit 111 of the physical server 110 to generate, move, and delete the virtual server 109.
  • the processing for the virtualization management unit 102 to operate the virtual server 109 can be the same as a known or known VMM or hypervisor, and will not be described in detail here.
  • the management server 101 also has a storage control unit (not shown) that allocates the plurality of disk volumes 116 of the storage device 115 to the physical server 110.
  • the function of the storage control unit may be included in the virtualization management unit 102.
  • the virtualization management unit 102 of the present invention uses a block of the disk volume 116p in which an error has occurred when converting the disk volume 116p of the physical server 110-1 to the virtual disk 501-0. Further, a bad block notification control unit 205 that notifies the conversion unit 111 is further provided.
  • the block of the disk volume 116 indicates a unit by which the OS 210 of the physical server 110-1 accesses the disk volume 116p, and is represented by, for example, LBA (Logical Block Addressing).
  • the P2V execution management unit 103 assigns the disk volume 116p or physical disk of the physical server 110-1 designated by the administrator or the like from the input device of the management server 101 to the virtual disk 501-0 that can be handled by the virtualization unit 111.
  • the data is converted and stored in the disk volume 116v of the storage device 115.
  • the P2V execution management unit 103 copies the data of the disk volume (or physical disk) from the storage device 115 and generates a conversion source disk image, and the virtualization unit 111 handles the copied disk image.
  • the disk volume 116p is read by acquiring dump data of the memory of the image conversion control unit 206 and the physical server 110-1 that converts to a virtual disk image that can be stored in the storage device 115 as the virtual disk 501 And a data repair control unit 207 that repairs a block in which an error (for example, a read error) has occurred from memory dump data.
  • the disk copy control unit 208 If an error occurs when the disk copy control unit 208 reads the disk volume 116p of the physical server 110-1, the disk copy control unit 208 stores the block number where the error occurred in the bad block management table 106, and the error occurs. Skip the block that has been read.
  • the image conversion control unit 206 acquires the block number of the disk volume 116p of the physical server 110-1 in which an error has occurred from the bad block management table 106, and the disk image of the physical server 110-1 is a virtual disk that is a virtual disk image.
  • the block number on the virtual disk 501-0 corresponding to the block number in which an error has occurred is stored in the bad block management table 106.
  • the converted virtual disk 501-0 can notify the error even in the virtualized environment by managing the block in which the error has occurred during the conversion by the bad block management table 106.
  • the OS 210 can provide the business without any problem. Therefore, the block can be obtained even on the virtual server 109 by making P2V successful. There is also a high possibility that no data will be accessed.
  • the P2V is made successful so that the OS 210 and applications of the physical server 110-1 are transferred to the virtual server 109. Can be migrated.
  • the data repair control unit 207 acquires the block number where the error of the disk volume 116p of the physical server 110-1 stored in the bad block management table 106 occurs, and stores it in the dump data of the memory of the physical server 110-1. When the data of this block number exists, the corresponding block number of the virtual disk 501-0 is updated with the dump data and repaired. The data repair control unit 207 deletes the entry in the bad block management table 106 that has been successfully repaired.
  • the block number of the virtual disk 501-0 that could not be repaired by the data repair control unit 207 is notified to the virtualization unit 111 by the bad block notification control unit 205 of the virtualization management unit 102.
  • the virtualization unit 111 notifies the virtual server 109 that the block is an error. That is, when the virtualization management unit 102 instructs the virtualization unit 111 of the physical server 110-2 to generate the virtual server 109-1, the bad block notification control unit 205 configures the virtual server 109-1 that configures the virtual server 109-1. If the disk 501-0 contains a block in which an error has occurred, information on the bad block management table 106 is notified.
  • the disk copy control unit 208 and the image conversion control unit 206 of the P2V execution management unit 103 read the conversion source disk volume 116p or the physical disk in units of blocks, and block the virtual disk image (virtual disk 501-0). Convert to The virtual disk image can be configured, for example, as a file in which the contents of blocks on the disk volume 116p are associated with block position information (block numbers).
  • the image conversion control unit 206 of the P2V execution management unit 103 converts the conversion source block read by the disk copy control unit 208 into a virtual disk image block that can be used by the virtualization unit 111 of the physical server 110-2.
  • the virtual disk 501 is stored in the storage device 115 as a single block.
  • a known or well-known technique such as Patent Document 1 described in the above-described conventional example may be used.
  • FIG. 10 is a diagram illustrating an example of the physical server management table 104 in which the virtualization management unit 102 manages the physical resources of the physical server 110.
  • the physical server management table 104 includes a physical server 1001 that stores the identifier of the physical server 110, a volume size 1002 that stores the capacity of the disk volume connected to the physical server 110, and a memory that stores the memory capacity of the physical server 110.
  • One record is composed of the size 1003 and the volume identifier 1004 for storing the identifier of the disk volume assigned to the physical server 110.
  • the number of cores of the processor, the operating frequency, and the like may be included.
  • Each item of the physical server management table 104 can be set by an administrator or the like from an input device (not shown) of the management server 101.
  • FIG. 9 is a diagram illustrating an example of the virtual server management table 105 in which the virtualization management unit 102 manages the virtual server 109.
  • the virtual server management table 105 executes a virtual server identifier 901 that stores the identifier of the virtual server 109, a virtualization unit identifier 902 that stores an identifier of the virtualization unit 111 that provides the virtual server, and the virtualization unit.
  • One record is composed of a physical server identifier 903 that stores the identifier of the physical server 110.
  • the physical server identifier 903 corresponds to the physical server 1001 in the physical server management table 104.
  • the virtualization unit identifier 902 and the virtual server identifier 901 can be set by an administrator or the like from an input device (not shown) of the management server 101.
  • FIG. 8 is a diagram showing an example of the virtual disk management table 107 for managing the conversion-source physical server 110 and the converted virtual disk 501.
  • the virtual disk management table 107 includes a virtual disk identifier 801 that stores the identifier of the virtual disk 501, a virtual server identifier 803 that stores the identifier of the virtual server 109 to which the virtual disk is allocated, and the conversion source of the virtual disk 501.
  • One record is composed of a physical server identifier 803 that stores the identifier of the physical server 110-1 and a bad block detection 804 that indicates whether or not an error has occurred during the conversion of the virtual disk 501.
  • the P2V execution management unit 103 After the conversion source disk volume 116p is converted to the virtual disk 501-0, the P2V execution management unit 103 generates a new record.
  • the P2V execution management unit 103 stores the identifier of the physical server 110 that used the conversion source disk volume 116p in the physical server identifier 803, and uses the identifier of the virtual disk given from the virtualization management unit 102 as described later. If a bad block occurs when storing in the virtual disk identifier 801 and converting to the virtual disk 501-0, “YES” of the bad block detection 804 is stored, and “NO” is stored if there is no bad block. .
  • the virtualization management unit 102 uses the virtual disk 501-0 of the virtual disk identifier 801, the virtual server identifier is assigned and stored in the virtual server identifier 802 of the virtual disk management table 107.
  • the virtual disk management table 107 holds the relationship between the physical server 110 that used the conversion source disk volume 116 of the virtual disk 501 and the identifier of the virtual disk 501, and whether or not an error has occurred during the conversion. Further, the virtual disk management table 107 manages the relationship between the virtual disk identifier 801 and the virtual server by the virtual server identifier 802 when the virtualization management unit 102 assigns the virtual disk 501 to the virtualization unit 111.
  • FIG. 7 is a diagram illustrating an example of the bad block management table 106 in which the P2V execution management unit 103 manages the relationship between the virtual disk 501 and the bad block of the conversion source disk volume 116.
  • One record is composed of the bad block number 704.
  • Information is stored in the physical server 701 and the physical disk bad block number 702 by the disk copy control unit 208 that reads the conversion source disk volume 116p. Information is written into the virtual disk identifier 703 and the virtual disk bad block number 704 by the image conversion control unit 206 that converts the conversion source disk image into a virtual disk image.
  • FIG. 3 is a block diagram illustrating an example of the physical server 110 (110-2 to 110-i) that executes the virtualization unit 111 and the virtual server 109. Since the plurality of physical servers 110-2 to 110-i have the same configuration, the physical server 110-2 will be described.
  • the physical server 110-2 includes a processor 202 that performs arithmetic processing, a memory 201 that stores data and programs, a network interface 203 that communicates with the network 108, and a disk interface 204 that accesses the storage device 115.
  • the memory 201 stores the above-described virtualization unit 111 and the virtual servers 109-1 and 109-2 generated by the virtualization unit 111.
  • the virtualization unit 111 is a program executed by the processor 202.
  • the virtualization unit 111 is stored in a storage device 115 as a storage medium, and is read into the memory 201 by the processor 202 and then executed.
  • the virtual servers 109-1 and 109-2 are virtual resources provided by the virtualization unit 111, and an OS and applications included in the virtual disk 501 are executed by the processor 202 on the virtual server 109. As shown in FIG. 8, the virtual server 109-1 (virt1) is activated by the virtual disk vdik0, and the virtual server 109-2 (virt2) is activated by the virtual disk vdik1.
  • the virtualization unit 111 accesses the error emulation control unit 112 that notifies the virtual server 109 of a bad block and the virtual server 109
  • a virtual disk I / O control unit 113 that monitors the virtual disk 501 and a bad block management table 301 that manages bad blocks of the virtual disk 501 are provided.
  • FIG. 18 is a diagram illustrating an example of the bad block management table 301 managed by the virtualization unit 111.
  • the bad block management table 301 includes a virtual server identifier 601 that stores the identifier of the virtual server generated by the virtualization unit 111, a virtual disk identifier 602 that stores the identifier of the virtual disk 501 that started the virtual server 109, and a virtual disk 501.
  • One record is configured from the virtual disk bad block management 603 for storing the position of the bad block included in the virtual disk.
  • the bad block management table 301 is a table notified to the virtualization unit 111 by the bad block notification control unit 205 of the virtualization management unit 102.
  • the virtual disk I / O control unit 113 refers to the bad block management table 301 and blocks the currently accessed virtual disk.
  • the error emulation control unit 112 is notified of the bad block number and the virtual server identifier 601.
  • the error emulation control unit 112 notifies the virtual server 109 corresponding to the received virtual server identifier 601 that an error (I / O error) has occurred in the block of the virtual disk 501 that is currently accessed.
  • the error emulation control unit 112 notifies the virtual server 109 of the bad block number 603.
  • FIG. 4 is a block diagram showing an example of the physical server 110-1 that uses the conversion source disk volume 116p.
  • the physical server 110-1 is configured in the same manner as the physical servers 110-2 to 110-i in FIG.
  • the physical server 110-1 includes a processor 202 that performs arithmetic processing, a memory 201 that stores data and programs, a network interface 203 that communicates with the network 108, and a disk interface 204 that accesses the storage device 115.
  • the disk interface 204 accesses the disk volume 116p and the disk volume 116d of the storage device 115.
  • the above-described OS 210 is stored in the memory 201.
  • the OS 210 is a program executed by the processor 202.
  • the OS 210 is stored in the disk volume 116p of the storage apparatus 115 as a storage medium, and is executed after being read into the memory 201 by the processor 202.
  • the OS 210 has a dump information acquisition unit 114 that writes the contents of the memory 201 to the disk volume 116d of the storage apparatus 115.
  • the dump information acquisition unit 114 acquires the contents of the memory 201 when receiving a command from the OS 210 or when a predetermined error (for example, a system error) occurs in the OS 211, and the disk volume 116 d as the dump data 401. Write to.
  • the disk to which the dump data 401 is written may be a disk volume 116p used by the OS 210.
  • an application (not shown) is executed on the OS 210 to provide a predetermined service.
  • the application is stored in the same disk volume 116p as that of the OS 210.
  • the physical server 110-1 uses the disk volume 116p as a system volume (boot disk).
  • FIG. 5 is a block diagram showing an example in which the virtual server 109 migrated from the physical server 110-1 with P2V accesses with a disk volume.
  • the virtualization unit 111 (hyper1) of the physical server 110-2 (phy2) accepts an instruction from the virtualization management unit 102 of the management server 101, and the virtual disk 501-0 (vdisk0) of the disk volume 116v.
  • the virtual server 109-1 (virt1) is generated and the virtual server 109-2 (virt2) is generated with the virtual disk 501-1 (vdisk1).
  • the virtual server 109 is generated by the virtualization unit 111 by allocating a virtual resource obtained by virtualizing the physical resource of the physical server 110-2 to the virtual server and starting the OS 210v of the virtual disk 501-0 on the virtual resource. Service provision is started by the application included in the virtual disk 501-0.
  • the block number of the currently accessed virtual disk 501-0 is a bad block. It is determined whether or not the management table 301 exists. When the block number of the virtual disk 501-0 to be accessed matches the virtual disk bad block number 603 in the bad block management table 301, the error emulation control unit 112 is notified of the bad block number and the virtual server identifier 601.
  • the error emulation control unit 112 generates an error in the bad block number 603 of the virtual disk 501-0 currently accessed to the OS 210v of the virtual server 109-1 corresponding to the virtual server identifier 601 notified from the error emulation control unit 112. Notify you.
  • the virtual disk I / O control unit 113 accesses the virtual disk 501-0 of the disk volume 116v and displays the access result. Responds to the virtual server 109-1.
  • the position of the converted bad block is registered in the bad block management table 301.
  • the virtual disk I / O control unit 113 and the error emulation control unit 112 of the virtualization unit 111 notify the OS 210v of the virtual server 109-1 of the bad block number 603.
  • the OS 210 of the physical server 110-1 shifts to the virtual environment and is executed as the OS 210v by the virtual server 109-1, but when the bad block of the disk volume 116p is read by the virtual server 109, it is the same as before the virtualization.
  • the error emulation control unit 112 can notify the OS 210v of an error and prevent the OS 210v from reading illegal data.
  • FIG. 6 is a block diagram showing an example of repairing a bad block from the dump data 401 in the memory of the physical server 110-1 after conversion to the virtual disk 501-0 with P2V.
  • the P2V execution management unit 103 acquires the dump data 401 of the memory 201 of the physical server 110-1 before copying the disk volume 116p of the physical server 110-1.
  • the acquired dump data 401 is stored in a predetermined disk volume 116d.
  • the P2V execution management unit 103 manages, in the bad block management table 106, a block in which an error has occurred when copying the disk volume 116p of the physical server 110-1. Then, the image conversion control unit 206 converts the block (bad block) in which an error has occurred to the virtual disk 501-0.
  • the image conversion control unit 206 stores predetermined data such as null or dummy data in the corresponding block of the virtual disk 501 corresponding to the defective block.
  • the data repair control unit 207 of the P2V execution management unit 103 acquires the virtual disk bad block number 704 from the bad block management table 106 for the virtual disk 501 that has been converted.
  • the data repair control unit 207 searches for the acquired bad block number 704 in the dump data 401 of the memory 201.
  • the data repair control unit 207 writes the data corresponding to the bad block number 702 in the dump data 401 to the virtual disk 501-0 and repairs it. .
  • the data repair control unit 207 can acquire the dump data 401 in the memory 201 before reading the disk volume 116p, and can repair a bad block from the dump data 401 after conversion to the virtual disk 501. .
  • FIG. 11 is a flowchart showing an outline of the processing performed by the P2V execution management unit 103 to read the conversion source disk volume 116 in units of blocks and convert the blocks into virtual disk image blocks. This process is executed by the management server 101 when a conversion source disk volume 116p and a storage destination disk volume 116v designated by an administrator or the like are received from an input device (not shown) of the management server 101.
  • the management server 101 generates a virtual disk 501-0 by converting the disk volume 116p of the physical server 110-1 into a virtual disk image, and the physical server 110-2 (phy2) is created using the virtual disk 501-0.
  • the administrator assigns a disk volume 116v for storing the converted virtual disk 501-0 to the virtual server 109-1 on the physical server 110-2 from an input device (not shown) of the management server 101. .
  • step 1101 the virtualization management unit 102 of the management server 101 activates the P2V execution management unit 103. Then, the P2V execution management unit 103 refers to the physical server management table 104 from the identifier of the conversion source disk volume 116p received from an input device (not shown), and adds the physical server 110-1 using the disk volume 116p to the network 108. Select from.
  • the virtualization management unit 102 determines the identifier (vdisk0) of the converted virtual disk 501 and notifies the P2V execution management unit 103 of it.
  • the identifier of the virtual disk 501 is a unique virtual disk identifier within the computer system. Note that the virtualization management unit 102 may accept a value specified by an administrator or the like for the virtual disk identifier.
  • step 1102 the data restoration control unit 207 of the P2V execution management unit 103 notifies the selected physical server 110-1 of an instruction to acquire the dump data 401 of the memory 201 and store it in the disk volume 116d.
  • the disk volume 116d that stores the dump data 401 is set in advance.
  • the OS 210 of the physical server 110-1 receives the command from the data restoration control unit 207 and activates the dump information acquisition unit 114.
  • the dump information acquisition unit 114 acquires a dump of the memory 201 and stores the dump data 401 in the designated disk volume 116d.
  • the OS 210 notifies the management server 101 of the completion of the dump.
  • step 1103 when the P2V execution management unit 103 receives the completion of the dump from the physical server 110-1, the P2V execution management unit 103 activates the disk copy control unit 208, and copies the disk volume 116p used by the physical server 110-1. Directs conversion to a virtual disk image.
  • the disk copy control unit 208 reads the designated disk volume 116p in block units, converts it into virtual disk image blocks in the image conversion control unit 206, and sets the virtual disk 501-0 to the predetermined disk volume 116v as a block unit. Store with. Details of the disk copy control unit 208 and the image conversion control unit 206 will be described in detail with reference to FIGS.
  • the disk copy control unit 208 uses the identifier (phy1) of the physical server 110-1 and the block number in which the error has occurred in the physical of the bad block management table 106.
  • the server identifier 701 and the physical disk bad block number 702 are stored.
  • the image conversion control unit 206 converts the block read by the disk copy control unit 208 into a block of the virtual disk 501-0. At this time, if the block number read from the disk volume 116p matches the physical disk bad block number 702 with reference to the bad block management table 106, the image conversion control unit 206 stores the virtual disk image in which the block is stored. Are stored in the virtual disk bad block number 704 of the bad block management table 106, and the identifier of the virtual disk 501-0 to be converted is stored in the virtual disk identifier 703 (step 1104). Then, since the block read by the disk copy control unit 208 is a bad block, the image conversion control unit 206 writes the above-described dummy data in the corresponding block of the virtual disk 501-0. Note that the processing of steps 1103 and 1104 is repeatedly performed during the period of processing for converting the disk volume 116p into a virtual disk image.
  • the disk copy control unit 208 When the disk copy control unit 208 has read all the blocks of the conversion source disk volume 116p, the disk copy control unit 208 notifies the P2V execution management unit 103 that the conversion from the disk volume 116p to the virtual disk 501-0 has been completed.
  • the P2V execution management unit 103 searches the bad block management table 106 using the identifier of the virtual disk 501-0 given from the virtualization management unit 102, and a bad block is found during the conversion. It is determined whether it has occurred (step 1105).
  • step 1106 If a defective block has occurred, the process proceeds to step 1106, and if there is no defective block, the process proceeds to step 1107.
  • step 1106 the P2V execution management unit 103 activates the data repair control unit 207 and repairs the defective block of the virtual disk 501-0 from the dump data 401 of the memory 201 of the physical server 110-1 as described above.
  • the data repair control unit 207 deletes the corresponding record in the bad block management table 106 when the bad block of the virtual disk 501-0 is successfully repaired.
  • the processing of the data restoration control unit 207 will be described in detail with reference to FIG.
  • the data restoration control unit 207 notifies the P2V execution management unit 103 when the processing is completed.
  • step 1107 the P2V execution management unit 103 sets the virtual disk management table 107.
  • the P2V execution management unit 103 adds a new record to the virtual disk management table 107, stores the virtual disk identifier assigned from the virtualization management unit 102 in the virtual disk identifier 801, and converts the virtual disk 501-0 conversion source
  • the identifier of the physical server 110-1 that has used the disk volume 116p is stored in the physical server identifier 803.
  • the P2V execution management unit 103 searches the bad block management table 106 using the virtual disk identifier given from the virtualization management unit 102, and if the virtual disk 501-0 includes a bad block, the virtual disk management table 103 “YES” is stored in the bad block detection 804 of 107, and “NO” is stored if no bad block is included.
  • the virtual server identifier 802 in the virtual disk management table 107 is assigned by the virtualization management unit 102 when the virtual disk 801-0 is used by the virtual server 109, so immediately after the virtual disk 501-0 is generated. Then, the value of the virtual server identifier 802 is blank.
  • step 1108 the P2V execution management unit 103 notifies the virtualization management unit 102 that the conversion of the virtual disk 501-0 from the disk volume 116p has been completed, and the process ends.
  • the P2V execution management unit 103 converts the disk volume 116p to the virtual disk 501-0 in units of blocks, and blocks in which an error has occurred when reading the disk volume 116p are managed by the bad block management table 106, and the virtual Dummy data is written to the disk 501-0.
  • the data repair control unit 207 repairs the bad block management table 106 from the dump data 401.
  • the virtual disk management table 107 is updated, and the virtual disk 501-0 is added to the table 107 as a new virtual disk image.
  • FIG. 12 is a flowchart showing an example of processing performed by the disk copy control unit 208. This processing is the processing of steps 1103 and 1104 in FIG.
  • step 1201 the disk copy control unit 208 reads the first block from the disk volume 116p received by the P2V execution management unit 103.
  • step 1202 it is determined whether an error has occurred, in other words, whether reading has failed. If reading of the block fails, the process proceeds to step 1203. If successful, the process proceeds to step 1204.
  • step 1203 the disk copy control unit 208 adds a new record to the bad block management table 106, writes the number of the block that failed to be read into the physical disk bad block number 702, and is currently reading the disk volume 116p. Is written in the physical server identifier 701.
  • Step 1204 the disk copy control unit 208 notifies the image conversion control unit 206 of the read block data, the block number, and the identifier of the physical server 110, and requests conversion to a virtual disk image.
  • the image conversion control unit 206 converts the requested block into a virtual disk image.
  • step 1205 the disk copy control unit 208 determines whether or not the currently read block is the last block. If it is not the last block, the process proceeds to step 1206 and the disk copy control unit 208 reads the next last block. Then, the processing in steps 1202 to 1205 is repeated. On the other hand, if the currently read block is the last block, the P2V execution management unit 103 is notified that the conversion to the virtual disk image has been completed, and the process ends.
  • FIG. 13 is a flowchart showing an example of the conversion process from the disk volume 116p to the virtual disk image performed in step 1204 of FIG.
  • step 1301 the image conversion control unit 206 determines whether the block number received from the disk copy control unit 208 and the identifier of the physical server 110 exist in the bad block management table 106. If the received block number and the identifier of the physical server 110 exist in the bad block management table 106, the image conversion control unit 206 makes a determination after determining that it is a bad block in which an error has occurred during reading, and proceeds to step 1304. On the other hand, if the received block number and the identifier of the physical server 110 do not exist in the bad block management table 106, the image conversion control unit 206 determines that the block has been read normally, and proceeds to step 1302.
  • step 1302 the image conversion control unit 206 converts the block data received from the disk copy control unit 208 into a virtual disk image. That is, the block of the disk volume 116p is converted into the format of the virtual disk 501-0.
  • step 1303 the converted virtual disk image block is written to the virtual disk 501-0 of the disk volume 116v, and the processing of the image conversion control unit 206 is terminated.
  • step 1304 which proceeds when it is determined in step 1301 that a bad block exists, the image conversion control unit 206 writes the virtual disk bad block number 704 and the virtual disk identifier 703 in the bad block management table 106.
  • the image conversion control unit 206 assigns the virtual disk identifier assigned by the virtualization management unit 102 to the record of the bad block management table 106 in which the bad block number of the disk volume 116p matches the identifier of the physical server 110, and the virtual disk identifier 703. To store. Then, the image conversion control unit 206 assumes that the virtual disk bad block number 704 of the record has converted the data of the bad block number received from the disk copy control unit 208 into a virtual disk image. Stores the block number on ⁇ 0. Then, the image conversion control unit 206 writes the dummy data as described above into the block of the virtual disk 501-0 corresponding to the defective block, and ends the process.
  • the disk copy control unit 208 reads from the first block to the last block of the conversion source disk volume 116p in units of blocks, and the image conversion control unit 206 converts them into virtual disk images. If an error occurs when reading a block of the disk volume 116p, the disk copy control unit 208 adds the block number and the identifier of the physical server 110 to the bad block management table 106, and the image conversion control unit 206 determines the virtual disk identifier and virtual Write the block number of disk 501-0. The image conversion control unit 206 writes predetermined dummy data in the virtual disk 501-0 instead of the defective block data, and continues the conversion to the virtual disk 501-0.
  • the P2V execution management unit 103 tries to repair the bad block from the dump data 401 by the data repair control unit 207.
  • FIG. 14 is a flowchart illustrating an example of processing performed by the data repair control unit 207. This process is a process performed in step 11066 of FIG.
  • step 1401 the data repair control unit 207 acquires all physical disk bad block numbers 702 corresponding to the disk volume 116p converted to the current virtual disk 501-0. If a plurality of errors have occurred when the disk volume 116p is read, there are a plurality of records in the bad block management table 106 that include the identifier of the physical server 110 using the disk volume 116p in the physical server identifier 701. The data repair control unit 207 acquires all physical disk bad block numbers 702.
  • step 1402 the data restoration control unit 207 acquires the dump data 401 of the memory 201 of the physical server 110-1 that is the conversion source of the virtual disk 501-0 from the disk volume 116d. Then, the data repair control unit 207 searches the dump data 401 using the conversion source defective block number 702 acquired in step 1401. This search is performed for all physical disk bad block numbers 702 acquired in step 1401.
  • step 1403 the data repair control unit 207 determines whether there is data that matches the bad block number 702 in the dump data 401. If data matching the bad block number 702 is included in the dump data 401, the process proceeds to step 1404. On the other hand, if the data matching the bad block number 702 is not included in the dump data 401, the data restoration control unit 207 cannot be executed, and the process ends.
  • step 1404 the data repair control unit 207 copies data matching the bad block number 702 from the dump data 401.
  • step 1405 the data restoration control unit 207 instructs the image conversion control unit 206 to convert the copied data into a virtual disk image format. Then, the data restoration control unit 207 acquires the block converted into the virtual disk image from the image conversion control unit 206.
  • the data repair control unit 207 refers to the bad block management table 106, acquires the virtual disk bad block number 704 corresponding to the bad block number 702, and writes it to the block of the virtual disk 501-0 indicated by the virtual disk bad block number 704. .
  • step 1406 the data repair control unit 207 deletes and updates the record of the bad block management table 106 that has successfully repaired the virtual disk 501-0 with the bad block number 704 from the dump data 401.
  • the data repair control unit 207 searches the bad block management table 106 for the identifier of the physical server 110-1 currently focused on.
  • the data repair control unit 207 searches for the identifier of the physical server 110-1 currently focused on from the physical server identifier 803 of the virtual disk management table 107, and sets the bad block detection 804 of the corresponding record to “NO”. Update.
  • FIG. 15 is a flowchart illustrating an example of processing performed by the virtualization management unit 102. This flowchart is executed when the virtualization management unit 102 receives a notification from the P2V execution management unit 103 that the conversion of the virtual disk 501-0 is completed. As described in the explanation of FIG. 11, the virtualization management unit 102 receives the virtual resource assigned to the virtual server 109-1 by the virtualization unit 111 of the physical server 110-2 and the identifier of the virtual server. An example is shown in which the virtual server 109-1 is activated with the virtual disk 501-0.
  • step 1501 the virtualization management unit 102 receives a notification of conversion completion of the virtual server 109-1 from the P2V execution management unit 103.
  • step 1502 the virtualization management unit 102 searches the bad block management table 106 using the converted identifier of the virtual disk 501-0 and acquires the corresponding record. Then, the virtualization management unit 102 notifies the record acquired in Step 1502 to the virtualization unit 111 of the physical server 110-2 that executes the virtual server 109-1 with the virtual disk 501-0. At this time, the virtualization management unit 102 also notifies the virtual server identifier and the virtual resource assigned to the virtual server 109-1.
  • the virtualization management unit 102 sets the value notified to the virtualization unit 111 in the virtual server identifier 802 of the virtual disk management table 107 corresponding to the identifier of the virtual disk 501-0.
  • the virtualization unit 111 of the physical server 110-2 allocates a virtual resource to the virtual server 109-1, and converts the disk volume 116p of the physical server 110-1 to the virtual server 109- using the virtual disk 501-0. 1 is activated.
  • FIG. 16 is a flowchart illustrating an example of processing performed by the virtual disk I / O control unit 113 of the virtualization unit 111 that provides the virtual server 109-1.
  • the virtualization unit 111 of the physical server 110-2 receives a part of the bad block management table 106 from the virtualization management unit 102 of the management server 101, the virtualization unit 111 of FIG.
  • the bad block management table 301 shown is generated or updated.
  • the virtualization unit 111 allocates the disk volume 116v to the virtual server 109-1, starts the OS 210v with the virtual disk 501-0, and operates the virtual server 109-1.
  • Step 1601 the virtual disk I / O control unit 113 receives an access (I / O request) from the virtual server 109-1 to the virtual disk 501-0.
  • step 1602 the virtual disk I / O control unit 113 acquires the virtual disk bad block number 603 of the virtual disk 501-0 assigned to the virtual server 109-1 from the bad block management table 301.
  • step 1603 the virtual disk I / O control unit 113 searches the virtual disk bad block number 603 acquired in step 1602 with the block number of the I / O request received in step 1601.
  • step 1604 the virtual disk I / O control unit 113 determines whether or not the virtual disk bad block number 603 is included in the I / O request block. If a defective block is included, the process proceeds to step 1605. If a defective block is not included, the process proceeds to step 1606.
  • step 1605 the virtual disk I / O control unit 113 notifies the error emulation control unit 112 that a bad block in the virtual disk 501-0 has been accessed.
  • step 1606 the virtual disk I / O control unit 113 executes access to the virtual disk 501-0 and returns an access result to the virtual server 109-1.
  • FIG. 17 is a flowchart showing an example of processing performed by the error emulation control unit 112. This process is executed when the error emulation control unit 112 receives a notification indicating that the virtual disk I / O control unit 113 is accessing a bad block.
  • step 1701 the error emulation control unit 112 notifies the virtual server 109-1 that issued the I / O request that an I / O error has occurred in the requested block.
  • the OS 210v of the virtual server 109-1 receives the notification from the error emulation control unit 112 and executes predetermined error processing.
  • the error emulation control unit 112 If there is a defective block in which an error has occurred when converting the disk volume 116p of the physical server 110-1 by the above processing, the error emulation control unit 112 notifies the access result to the virtual server 109-1. As a result, the virtual server 109-1 can be restricted from directly accessing the bad block of the virtual disk 501-0.
  • the disk copy control unit 208 reads from the first block to the last block of the conversion source disk volume 116p in block units, and the image conversion control unit 206 converts the block into a virtual disk image, and the virtual disk 501-0. Is generated. If an error occurs when the disk copy control unit 208 reads a block of the disk volume 116p, the image conversion control unit 206 transfers dummy data, blanks, etc. to the virtual disk 501-0 instead of converting the block to a virtual disk image. To continue generating the virtual disk 501-0.
  • the conversion process of the conversion source disk volume to a virtual disk image is performed. Can continue.
  • the environment of the physical server 110-1 operating on the conversion source disk volume 116p can be migrated to the environment of the virtual server 109-1.
  • the data repair control unit 207 can repair the bad block from the dump data 401, it is possible to ensure the stability of the virtual server 109-1.
  • the virtualization unit 111 a copy of the bad block management table 106 is acquired from the management server 101, and the virtual disk I / O control unit 113 monitors the I / O access of the virtual server 109-1, and the virtual disk 501- When the 0 bad block is accessed, the error emulation control unit 112 notifies the virtual server 109-1 of the error without actually accessing the virtual disk 501-0. As a result, the virtual server 109-1 can be prevented from reading illegal data from a bad block, and the stability of the virtual environment can be ensured.
  • the management server 101 reads the conversion source disk volume 116p and writes dummy data to the conversion destination virtual disk 501 when an error occurs.
  • the defective block is not repaired, it is not necessary to write the dump data 401 of the virtual disk 501, and the virtual disk defective block number may be recorded in the defective block management table 106. That is, the management server 101 skips the bad block of the conversion source disk volume, determines the block number on the virtual disk 501 corresponding to the bad block number, and stores it in the bad block management table 106.
  • the management server 101 does not write a bad block on the virtual disk 501.
  • the virtual server 109 using the virtual disk 501 is monitored for an I / O request by the virtual disk I / O control unit 113 of the virtualization unit 111.
  • the virtual server 109 issues an I / O request for accessing a bad block, an error occurs from the virtual disk I / O control unit 113 via the error emulation 112.
  • the error emulation control unit 112 reads a bad block, so it is not necessary that a bad block is actually generated on the virtual disk 501. .
  • the management server 101 sets the virtual disk 501 to the virtual disk 501.
  • Block 3 ' is written after block 1' converted to an image.
  • the P2V execution management unit 103 of the management server 101 sets block 3 ′ as the next write position of block 1 ′ of the virtual disk 501, and sets the bad block. Ignore and continue to generate the virtual disk 501.
  • the disk volume 116p in the storage device 115 is used as the conversion source.
  • the conversion source disk volume 116 may be a physical disk, a logical disk, or a partition.
  • the virtual disk 501-0 is generated using the disk volume 116p as the conversion source.
  • the conversion destination may be a disk image, and is not limited to the virtual disk image.
  • the present invention can be applied when copying the contents of the first disk volume to the second disk volume. It can. That is, when an error occurs when the first disk volume is read, the bad block information is stored in the bad block management table 106 of the management server 101, and dummy data is stored in the corresponding block of the second disk volume. The predetermined data such as are stored. Alternatively, the corresponding block of the second disk volume is blank.
  • the management server 101 allocates the second disk volume to the server, and the bad block information of the second disk volume is obtained from the bad block management table 106 and the OS of the server. Or notify the virtualization department.
  • the OS or virtualization unit of the server accesses the bad block when accessing the second disk volume, it can generate an error without actually accessing the bad block of the second disk volume.
  • the server may be a physical server and is not limited to a virtual server.
  • a PCI express switch is installed between the second disk volume and the server, the management server 101 notifies the PCI express switch of a copy of the bad block management table 106, and the switch monitors the I / O access of the server. Also good.
  • the PCI express switch can notify the server of the occurrence of an error.
  • the first computer uses the first disk volume
  • the management server 101 creates a second disk volume by duplicating the first disk volume
  • the second computer accesses the second disk volume.
  • the present invention can be applied.
  • the management server 101 records the block in which an error has occurred when replicating the first disk volume in the bad block management table 106 to generate a second disk volume. After connecting the second disk volume to the second computer, the management server 101 notifies the second computer of the bad block management table 106.
  • the OS or the virtualization unit refers to the bad block management table 106 and monitors access to a bad block on the second disk volume. When the second computer accesses the bad block of the second disk volume, the OS or the virtualization unit can generate an I / O error without actually accessing the bad block of the second disk volume. .
  • the conversion source (copy source) disk volume and the conversion destination (copy destination) disk volume are stored in the same storage device 115. However, they are stored in different storage devices. May be.
  • the conversion source disk volume is read in block units and written to the conversion destination disk volume in block units.
  • a copy of the conversion source disk volume is generated, You may make it write in the disk volume of a conversion destination.
  • a storage device composed of a nonvolatile semiconductor can be used in addition to a hard disk drive, or a storage device including both a hard disk drive and a nonvolatile semiconductor can be used. .
  • the present invention can be applied to a computer system that replicates a disk volume and uses the replicated disk volume.
  • the present invention includes a virtualization unit for replicating a disk image or converting a physical disk to a virtual disk. It is suitable for a virtual computer system to be performed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Un calculateur de gestion lit des données dans un premier volume de disque, détermine si une erreur se produit ou pas lors d'une lecture des données dans le premier volume de disque, écrit les données lues dans un second volume de disque de façon à générer une reproduction lors d'une détermination selon laquelle aucune erreur ne s'est produite, écrit la position des données lues dans des informations de gestion de blocs défectueux lors d'une détermination selon laquelle une erreur s'est produite, attribue le second volume de disque à un calculateur et transmet les informations de gestion de blocs défectueux au calculateur et le calculateur se rapporte aux informations de gestion de blocs défectueux reçues lors d'un accès au second volume de disque et provoque une erreur lorsque la position à laquelle il a accédé correspond aux informations de gestion de blocs défectueux.
PCT/JP2010/069857 2010-11-08 2010-11-08 Procédé de commande de calculateur, système de calculateur et support de stockage WO2012063311A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2010/069857 WO2012063311A1 (fr) 2010-11-08 2010-11-08 Procédé de commande de calculateur, système de calculateur et support de stockage

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2010/069857 WO2012063311A1 (fr) 2010-11-08 2010-11-08 Procédé de commande de calculateur, système de calculateur et support de stockage

Publications (1)

Publication Number Publication Date
WO2012063311A1 true WO2012063311A1 (fr) 2012-05-18

Family

ID=46050494

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2010/069857 WO2012063311A1 (fr) 2010-11-08 2010-11-08 Procédé de commande de calculateur, système de calculateur et support de stockage

Country Status (1)

Country Link
WO (1) WO2012063311A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH1040022A (ja) * 1996-07-26 1998-02-13 Nec Corp 磁気ディスク制御装置
JPH1185594A (ja) * 1997-09-01 1999-03-30 Hitachi Ltd リモートコピー用情報処理システム
JP2002182951A (ja) * 2000-12-18 2002-06-28 Hitachi Ltd 情報処理装置のメンテナンス方法および情報処理装置
JP2009536762A (ja) * 2006-05-08 2009-10-15 マイクロソフト コーポレーション マシンから仮想マシンへの変換

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH1040022A (ja) * 1996-07-26 1998-02-13 Nec Corp 磁気ディスク制御装置
JPH1185594A (ja) * 1997-09-01 1999-03-30 Hitachi Ltd リモートコピー用情報処理システム
JP2002182951A (ja) * 2000-12-18 2002-06-28 Hitachi Ltd 情報処理装置のメンテナンス方法および情報処理装置
JP2009536762A (ja) * 2006-05-08 2009-10-15 マイクロソフト コーポレーション マシンから仮想マシンへの変換

Similar Documents

Publication Publication Date Title
CN114341792B (zh) 存储集群之间的数据分区切换
US20220179701A1 (en) System and method for dynamic data protection architecture
US8413133B2 (en) Software update management apparatus and software update management method
US8122212B2 (en) Method and apparatus for logical volume management for virtual machine environment
US10353872B2 (en) Method and apparatus for conversion of virtual machine formats utilizing deduplication metadata
US9003149B2 (en) Transparent file system migration to a new physical location
US8635395B2 (en) Method of suspending and resuming virtual machines
US9336132B1 (en) Method and system for implementing a distributed operations log
US8024536B2 (en) Method of constructing replication environment and storage system
US8943498B2 (en) Method and apparatus for swapping virtual machine memory
EP3502877B1 (fr) Procédé et dispositif de chargement de données pour machines virtuelles
US9183060B2 (en) Computer product, migration executing apparatus, and migration method
JP2019016135A (ja) 情報処理システム、情報処理システムの制御プログラム及び情報処理システムの制御方法
US10789007B2 (en) Information processing system, management device, and control method
JP2014044553A (ja) プログラム、情報処理装置および情報処理システム
US10095616B2 (en) Garbage collection for virtual environments
US9524251B2 (en) Storage system, virtualization control apparatus, information processing apparatus, and method for controlling storage system
US11086649B2 (en) Minimizing downtime of highly available virtual machines
US10241818B2 (en) In-memory virtual desktop system
US20220237306A1 (en) Method and system for limiting data accessibility in composed systems
EP3647953B1 (fr) Système et procédé de sauvegarde de données dans un environnement de disque mixte
WO2012063311A1 (fr) Procédé de commande de calculateur, système de calculateur et support de stockage
JP2021047806A (ja) 情報処理システム、情報処理装置および情報処理プログラム
US11768612B2 (en) System and method for distributed deduplication in a composed system
US11675665B2 (en) System and method for backup generation using composed systems

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10859553

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10859553

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP