WO2018011914A1 - Système d'archives de données et procédé d'archives de données - Google Patents

Système d'archives de données et procédé d'archives de données Download PDF

Info

Publication number
WO2018011914A1
WO2018011914A1 PCT/JP2016/070702 JP2016070702W WO2018011914A1 WO 2018011914 A1 WO2018011914 A1 WO 2018011914A1 JP 2016070702 W JP2016070702 W JP 2016070702W WO 2018011914 A1 WO2018011914 A1 WO 2018011914A1
Authority
WO
WIPO (PCT)
Prior art keywords
archive
data
storage
path
server
Prior art date
Application number
PCT/JP2016/070702
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/JP2016/070702 priority Critical patent/WO2018011914A1/fr
Publication of WO2018011914A1 publication Critical patent/WO2018011914A1/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/14—Error detection or correction of the data by redundancy in operation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures

Definitions

  • the present invention relates to a data archiving system and a data archiving method, and more particularly to optimizing the storage destination of archive data when both data archiving to a local environment and data archiving to a cloud environment are available.
  • the present invention relates to a suitable data archive system and a data archive method.
  • an archive system moves only data intended for long-term storage from the storage that stores business data to archive storage as archive data. This is a storage system.
  • the archive application stores the path information to the archive source data and the path information to the archive destination data for each archive data.
  • the archive data stored in the archive destination data path is replaced with the archive source data path or the storage designated in advance.
  • Patent Document 1 is an archive system for efficiently storing and managing data files and improving convenience.
  • data is stored in an archive storage according to a predetermined policy, and the stored archive data is copied to another storage based on the policy.
  • Whether to archive the data is determined by whether the management information of the archive data matches the rules described in the policy.
  • Patent Document 2 discloses a system that selects a storage destination of a target file for system migration.
  • the file server specifies a migration target file, and a storage conforming to a storage attribute condition represented by an information set including information representing a file attribute condition conforming to the file attribute of the target file.
  • the device is specified based on the storage management information. Then, the target file is migrated from the storage device storing the target file to the identified storage device.
  • the archive application itself is migrated from an on-premises to a server on a different network such as a cloud
  • the path information to the archive source data or archive destination data in the network referenced by the archive application before migration Since the network is different from the archive application after migration, the archive source data and the archive destination data cannot be reached. For this reason, when an archive application is migrated from an on-premise server to a cloud server, there is a problem that access continuity to the archive data before the migration cannot be secured, or the path for that purpose needs to be rewritten. It was.
  • Patent Document 2 it is disclosed that an appropriate storage device is selected according to a file attribute, but consideration is given to ensuring continuity of access to archive data when migrating an archive environment. Absent.
  • the present invention has been made to solve the above-mentioned problems, and its purpose is to automatically determine the storage destination storage of archive data according to the data content of the archive data itself, and to make effort for archiving It is to provide a data archive system that can reduce the risk.
  • the configuration of the data archive system of the present invention includes an archive server, a first storage connected to the archive server via a first network, and an archive server connected via the first network. And a third storage connected to the archive server via a second network.
  • the archive server archives data from the first storage to the second storage or the third storage, and when archiving the data by the archive means, the second storage and the third storage
  • a data migration destination determination unit that determines which data is to be archived, and the data migration destination determination unit determines the archive destination of the data according to the control information embedded in the data when determining the archive To do.
  • FIG. 1 is a block diagram showing a data archive system according to a first embodiment. It is a figure which shows the hardware constitutions and software constitution of an archive server. It is a figure which shows an example of an archive path table. It is a figure which shows an example of an archive rule table. It is a figure which shows an example of a storage information table. It is a figure which shows an example of the header part of archive data. It is a flowchart which shows the process at the time of data archive. It is a flowchart when restoring archive data of the second embodiment (part 1). It is a block diagram which shows the data archive system which concerns on 2nd embodiment. It is a figure which shows the hardware constitutions of the cloud installation server installed in the cloud environment, and a software configuration.
  • FIG. 1 It is a figure which shows an example of a storage path conversion table. It is a flowchart which shows the process of a virtual environment transfer tool. It is a flowchart which shows an archive path
  • Embodiment 1 Hereinafter, a first embodiment of the present invention will be described with reference to FIGS.
  • FIG. 1 is a block diagram showing a data archive system according to the first embodiment.
  • FIG. 2 is a diagram illustrating a hardware configuration and a software configuration of the archive server.
  • a device group of an on-premises environment 130 and a device group of a cloud environment 140 are connected via a LAN (Local Area Network) 20 and a WAN (Wide Area Network) 30.
  • the client terminal 110, the business application server 133, the local storage 131, the archive server 150, the archive storage 132, and the management server 120 are connected via a LAN (Local Area Network) 20 and a WAN (Wide Area Network) 30.
  • the client terminal 110 is a terminal device operated by a company or an individual who receives functions from various servers.
  • the business application server 133 is a server device composed of one or a plurality of devices that respond to the client terminal 110 and execute business applications related to various services for companies and individuals.
  • the local storage 131 is a single or plural storage device that stores data handled by the business application server 133.
  • the archive server 150 is a server device that executes an archive application program (described later) that archives data stored in the local storage 131 in accordance with a policy previously determined by a user or a system administrator.
  • the archive storage 132 is a storage device configured by one or a plurality of storing archive data to which the archive application program archives data.
  • the management server 120 is a server device that is loaded with operation management software necessary for operation management of each device described above and provides functions such as configuration, status management, and capacity management of each device.
  • the archive server 150 includes functional blocks of an archive unit 160 and a data migration destination determination unit 161.
  • the archive unit 160 is a functional unit that archives specified data in accordance with a policy determined by a user or a system administrator.
  • the data migration destination determination unit 161 is a functional unit that determines a storage destination for archiving data based on designated information. The functions of these functional units will be described in detail later.
  • the archive server 150 has a system DB (Data Base) 170, and an archive path table 171, an archive rule table 172, and a storage information table 173 are stored in the system DB 170.
  • the archive path table 171 is a table that stores an archive source path and an archive destination path.
  • the archive rule table 172 stores an archive destination rule according to the nature of the data.
  • the storage information table 173 is a table that stores paths stored as archives for each type of storage. Details of the tables will be described later.
  • the client terminal 110, the business application server 133, the local storage 131, the archive server 150, the archive storage 132, and the management server 120 are connected as an internal network by a wired / wireless LAN 20.
  • the client terminal 110 may be disposed in an office in the company and connected via a LAN of an internal network, or may be disposed in a remote place and connected from the outside via a WAN.
  • the management server 120 may also be connected to the WAN to remotely manage these devices.
  • the business application server 133, the local storage 131, the archive server 150, and the archive storage 132 in this system are independent of the external environment in terms of network.
  • a company owns an information system and data on its own facilities. It is arranged in an on-premises environment 130 (local environment closed by a business entity) held in the center. The location of data such as files and folders within the on-premises environment 130 is indicated by a path that is unique within the on-premises environment 130.
  • the LAN 20 in the on-premises environment 130 is connected to the WAN 30 that is an external network via a firewall (not shown) and a proxy server (not shown).
  • the WAN 30 is connected to the cloud environment 140.
  • the cloud environment 140 may be, for example, a private cloud that builds a cloud computing system in-house and provides computing resources to departments or group companies in the company, or provided by a cloud provider via the Internet. It can be a public cloud.
  • computing resources such as the cloud storage 141 are provided to the cloud user.
  • the cloud storage 141 of the cloud environment 140 is a storage resource that stores data.
  • a user of the cloud environment 140 can make a contract with a cloud operator and secure resources of the cloud storage 141.
  • the path to the cloud resource is indicated by a path that is unique in the entire external network such as the Internet.
  • management server 120 may be able to monitor the increase or decrease in resources, state, and capacity of the cloud storage 141 in the cloud environment 140 via the network.
  • the system of FIG. 1 is an example of this embodiment, and may have other configurations.
  • the local storage 131 and the archive storage 132 may be physically configured by a plurality of devices, or may be storage areas that are virtually divided in the same storage device.
  • the cloud storage 141 of the cloud environment 140 may be distributed in the cloud environment 140 provided by a plurality of cloud operators.
  • This embodiment relates to a method in which an archive application program distributes data to be archived from the local storage 131 to the archive storage 132 in the on-premises environment 130 and the cloud storage 141 in the cloud environment 140 in such a system configuration.
  • FIG. 2 is a diagram showing the hardware configuration and software configuration of the archive server using FIG.
  • the hardware configuration of the archive server 150 includes a CPU 151, a display I / F (InterFace) 152, an input / output I / F 153, a main storage device 154, a network I / F 155, and an auxiliary storage I / F 156 as a bus. It is connected by.
  • the display device 40 displays an operational status monitor and output result in the data archive.
  • Input / output devices such as a keyboard 50 and a mouse 52 are connected to the input / output I / F 153, and the administrator inputs commands and the like from these input / output devices.
  • a LAN 20 is connected to the network I / F 155 and communicates with an external device via the I / F.
  • the client terminal 110, the business application server 133, the local storage 131, the archive storage 132, and the management server 120 are connected via the LAN 20.
  • the auxiliary storage I / F 156 is connected to an external storage device such as a hard disk device (HDD: Hard Disk Drive) 60 for storing data and programs.
  • the hard disk device 60 may be connected on the array to form a disk array.
  • the hard disk device 60 stores an OS (Operating System) 70, an archive application program 61, and a data migration destination determination program 62 as programs. These programs are stored in the hard disk device 60, loaded into the main storage device 154 when executed, and executed by the CPU 151 after interpreting the instructions.
  • OS Operating System
  • the OS 70 is a management program that arbitrates hardware resources and software resources on the archive server 150 and executes various application programs.
  • the archive application program 61 is a program for realizing the archive unit 160 of the functional unit shown in FIG.
  • the data migration destination determination program 62 is a program for realizing the data migration destination determination unit 161 of the functional unit shown in FIG.
  • the archive application program 61 determines whether or not the data on the local storage 131 can be archived according to a predetermined archiving policy. If the data is determined to be archived, the archive application program 61 executes the data migration destination determination program 62. A program for moving data on the local storage 131 as archive data to an archive destination storage determined by an archive destination determination method to be described later. At this time, the archive application program 61 may replace the data in the archive source storage with a stub file and store an archive path table 171 (to be described later) in the stub file.
  • data archiving is determined based on data creation and update date / time, data access frequency, file attributes, etc. on the local storage 131, and data archiving is started. .
  • the hard disk device 60 stores the system DB 170.
  • the system DB 170 stores the archive path table 171, the archive rule table 172, and the storage information table 173.
  • FIG. 3 is a diagram illustrating an example of the archive path table.
  • FIG. 4 is a diagram illustrating an example of the archive rule table.
  • FIG. 5 is a diagram illustrating an example of the storage information table.
  • FIG. 6 is a diagram illustrating an example of a header portion of archive data.
  • the archive path table 171 is a table that stores information on the path to the archive source data and the path to the archive destination data after the archive application program 61 archives the data.
  • the archive path table 171 includes fields of a data ID 201, an archive source path 202, and an archive destination path 203.
  • the data ID 201 is a field for storing a unique identifier assigned to each archive unit of data archived by the archive application.
  • the archive source path 202 and the archive destination path 203 are fields for storing the path to the archive source data and the path to the archive destination data of the data ID 201, respectively.
  • the unit of data to be archived is a file unit, but is not limited to this, and may be a folder unit, a logical drive unit, or a volume unit.
  • the archive rule table 172 is a table for storing a tag information to be written to data and a rule for associating the data storage destination. As shown in FIG. 4, the archive rule table 172 includes a tag ID 301, a tag value 302, a rule 303, and a priority 304.
  • the tag ID 301 is a field for storing the tag ID for describing the tag value 302.
  • a tag value 302 is a field for storing a value described in the tag column by the tag ID 301.
  • the user in order to specify the storage destination of the archive, the user describes the character string of the tag value 302 in the tag field according to the value of the tag ID 301 as additional information in the header portion of the file to be archived.
  • the rule 303 is a field that describes a rule that is applied as a destination of archive data when the value of the tag ID 301 of the record matches the tag value 302.
  • the condition of the rule 303 designates a storage to be an archive destination based on information stored in the storage path 401 of the storage information table 173 shown in FIG.
  • the rule 303 specifies a storage destination of archive data when information indicated by a tag ID 301 and a tag value 302 is described in a file.
  • the specification method of the tag ID 301 and the tag value 302 is described according to the grammar of XML (Extensible Markup Language) as shown in FIG.
  • XML Extensible Markup Language
  • the value in the tag field indicated by ⁇ SECURITY> ⁇ / SECURITY> is Confidential.
  • the rule 303 has “on-premise”. This means storing the classification in storage. In this way, by embedding tag information in a file, the user designates on-premises archive storage in the company as the archive data storage destination instead of the cloud storage area that is external storage as data including confidential information can do.
  • the tag value 302 “BITTool” is assigned to the tag field of the tag ID “Tool”
  • the BI tool is used by specifying storage in the storage of the “cloud” classification in the rule 303.
  • a storage area on the cloud that can use computing resources in a scalable manner can be designated as a storage destination of archive data.
  • the priority 304 stores information that can be ordered to determine which rule 303 to select and determine the destination storage of archive data when a plurality of tag IDs 301 and tag values 302 match.
  • the information stored in the archive rule table 172 may be determined in advance by the system administrator, or the system may prepare and set a template, or both.
  • the rules are selected in descending order of priority numbers. “*” Indicates a wild card, which means that it is applied when there is no matching condition.
  • the storage information table 173 is a table that indicates a specific storage path at the time of on-premises or cloud storage classification, and includes fields of a storage path 401 and a storage classification 402 as shown in FIG.
  • the storage path 401 is a field for storing path information from the archive application program 61 to storage of data that is a candidate for data archive or archive data restore destination.
  • the storage classification 402 is a field for storing the classification information of the migration destination storage that is a condition in the rule 303 for each storage path 401.
  • the storage classification for example, in the system configuration of FIG. 1, the archive storage 132 is arranged on the on-premises environment 130. Therefore, when archiving to the archive storage 132 is desired, the character string “on-premises” is described in the storage classification 402. To do.
  • the information in the storage information table 173 may be determined in advance by a system administrator or a system builder. Alternatively, the system may prepare a template and let the user select it.
  • Tag information is embedded in the header of the file to be archived.
  • the tag information may be embedded in the use of data by the data creator or business application when creating or updating data, or may be embedded by other applications. Further, it is assumed that a specific form or character string already in the data may be used without embedding tag information.
  • FIG. 7 is a flowchart showing processing at the time of data archiving.
  • FIG. 8 is a flowchart when restoring archive data according to the second embodiment (part 1).
  • the archive server 150 determines whether or not the data on the local storage 131 can be archived by executing the archive application program 61. When it is determined that the data is to be archived, archiving of data on the local storage 131 is started.
  • the archive server 150 executes the data migration destination determination program 62, refers to the information about the archive of the header portion of the file determined to start archiving, and the archive rule table 172, and describes it in the header portion of the file.
  • the rule 303 of the record of the tag ID 301 and the tag value 302 that matches the contents of the tag field thus selected is selected (S601 in FIG. 7).
  • a rule having a higher priority 304 is selected.
  • the tag ID 301, the tag value 302, and the rule 303 that match the management server are displayed and output on a display device (not shown) connected to the management server. Assume that the administrator may select one of the plurality of rules 303.
  • the archive server 150 determines the storage path 401 of the storage information table 173 that matches the condition of the rule 303 selected in S601 by executing the data migration destination determination program 62 (S602). For example, when ⁇ SECURITY> Confidential ⁇ / SECURITY> is described in the header of the file, the first record in FIG. 4 is selected and “stored in on-premises storage” as a rule. As the path, referring to FIG. 5, “ ⁇ A1” is designated as the archive destination.
  • priority information for selecting the storage paths 401 is set in advance by the system administrator or system designer, and the priority is selected. Determine one with the degree information. Alternatively, a plurality of storage paths 401 selected by the system administrator may be displayed and one may be determined.
  • the archive server 150 moves the file designated as archived in S601 to the storage in the storage path 401 determined in S602 (S603).
  • the archive server 150 executes the archive application program 61 to add the data ID column of the moved data to the archive path table 171 shown in FIG. Register the data path.
  • the client terminal 110 When restoring archive data, the client terminal 110 requests the archive server 150 to access the archive data.
  • the archive server 150 executes the archive application program 61 to copy the archive data to a predetermined archive data restore destination accessible by the client.
  • the restore destination of the archive data is a path described in the archive source path 202 of the archive path table 171 shown in FIG.
  • the restore destination of the archive data may be a restoration area designated in advance.
  • the storage path to the area for restoration and the storage classification are registered in the storage information table 173 in advance.
  • the client terminal 110 requests the archive server 150 to access a specific archive data.
  • This restore request may be sent via the management server 120.
  • the archive application program 61 holds the list information of data that has already been archived, displays it to the user, and then designates specific archive data for the client terminal 110. Good. Further, specific archive data may be specified by the client terminal 110 specifying the stub file stored in the archive source storage described above.
  • the archive server 150 refers to the archive path table 171 by executing the archive application program 61, and from the data ID 201 of the specified archive data, the archive destination path 203 and the archive source path 202 are specified (S701 in FIG. 8).
  • the archive server 150 refers to the data contents stored in the archive destination path 203 and the archive rule table 172 by executing the data migration destination determination program 62, and the rules applied when the data is archived. 303 is confirmed (S702). In this step, the rule 303 applied for each data ID 201 may be recorded and confirmed when data is archived.
  • the data migration destination determination unit 161 determines whether or not the restore destination of the archive data matches the rule 303 confirmed in step S703 with reference to the storage information table 173 (S703).
  • the archive server 150 executes the archive application program 61 to copy the archive data in the archive destination path 203 to the archive data restore destination (S704). Then, the archive application program 61 notifies the client terminal 110 that has requested access to the archive data of the completion of the restore of the archive data and the path of the data copied to the restore destination of the archive data (S706).
  • the archive application program 61 When it is determined NO in S703, the archive application program 61 notifies the system administrator, the management server 120, or the client terminal 110 that the restore destination of the archive data does not match the rule 303. For example, if the rule 303 is an instruction to store in the “cloud” storage, but the restore destination of the archive data is “on-premises”, they do not match. In this case, the system administrator who receives the notification from the archive application program 61 or the management server 120 designates another archive data restore destination in the archive application program 61. At that time, the processing of the flowchart of FIG. 8 may be performed again. Alternatively, the system administrator may instruct the user to ignore the notification and execute the processing of S705, and the system administrator may change the rule 303.
  • the same rule 303 is applied when archiving data and restoring archive data.
  • Different rules 303 may be applied when data is archived and when archive data is restored.
  • FIG. 9 is a block diagram showing a data archive system according to the second embodiment.
  • FIG. 10 is a diagram illustrating a hardware configuration and a software configuration of a cloud installation server installed in a cloud environment.
  • This embodiment is a cloud computing resource provided by a cloud operator on the cloud environment 140 that provides the archive function of the archive server 150A of the on-premises environment 130 in addition to the function of the data archive system of the first embodiment.
  • This is a case of migrating to the archive server (virtual server) 150B.
  • the archive application program 61A executed on the archive server 150A is automatically migrated including the execution environment so as to operate on the archive server (virtual server) 150B without requiring the user. It is.
  • a migration using a so-called P2V Physical to Virtual
  • a physical server is migrated to a virtual environment using a dedicated tool
  • the archive server in the cloud environment may be realized by a physical server.
  • the archive server 150A of this embodiment includes an archive unit 160A and a data migration destination determination unit 161A as functional blocks, and the system DB 170A includes an archive path.
  • a table 171A, an archive rule table 172A, and a storage information table 173A are stored. In this embodiment, all of these are migrated to a virtual server provided by a cloud operator on the cloud environment 140.
  • the present embodiment provides a mechanism that allows the archive function to access data stored in the archive storage 132 and the cloud storage 141 in the same manner as before the migration when the on-premises environment 130 is migrated to the cloud environment.
  • the function of the archive unit 160A is not used in the archive server 150A.
  • the information stored in the archive path table 171A, the archive rule table 172A, and the storage information table 173A of the archive server 150A is all copied or moved to the archive server (virtual server) 150B at the timing of migrating the archive environment.
  • the archive path tables 171A and 171B, the archive rule tables 172A and 172B, and the storage information tables 173A and 173B of the present embodiment are the archive path table 171 (FIG. 3) and the archive rule table 172 (FIG. 4) described in the first embodiment. ) And the storage information table 173A (FIG. 5).
  • the archive server (virtual server) 150B of this embodiment has a path conversion unit 162 as a functional unit.
  • the path conversion unit 162 converts the path from the cloud environment 140 to the archive source data and the archive destination data in the on-premises environment 130 stored in the archive path table 171A. It is a functional part that converts the path to the archive source data and the archive destination data. It is assumed that the path conversion unit 162 may be on the management server 120.
  • the system DB 170B of the archive server (virtual server) 150B has a storage path conversion table 174.
  • the storage path conversion table 174 has a conversion unit 801.
  • the path conversion unit 162 is a table that stores path conversion information when the archive function is transferred from the on-premises environment 130 to the cloud environment 140. Details of the storage path conversion table 174 will be described later.
  • the configuration of the cloud installation server (physical server) 200 installed in the cloud environment may be the hardware configuration of a general server device, similar to the archive server 150 of the first embodiment shown in FIG.
  • the hard disk device 60 of the cloud installation server 200 includes the tables of the system DB 170B of the archive server (virtual server) 150B described above, the archive application program 61B, the data migration destination determination program 62B, and the path conversion program 63. .
  • the archive application program 61B and the data migration destination determination program 62B are programs that execute the functions of the path conversion program 63, the archive unit 160B, the data migration destination determination unit 161B, and the path conversion unit 162, respectively.
  • a virtual machine monitor 80 and guest OSs 82a, 82b,... are stored as basic software.
  • the virtual machine monitor 80 is a program for allocating hardware resources to the guest OSs 82a, 82b,.
  • the archive server (virtual server) 150B of the present embodiment is realized as one guest OS 82a, 82b,... Executed on the virtual machine monitor 80, and includes an archive application program 61B, a data migration destination determination program 62B, and a path conversion program 63. Are application programs executed on the guest OSs 82a, 82b,.
  • the virtual server is described as an example of so-called hypervisor type virtualization in which a virtual machine monitor mediates hardware resources and a guest OS.
  • virtualization software is executed on the host OS.
  • a so-called host OS type virtualization for starting the guest OS may be used.
  • it may be a container type that abstracts the execution environment of a part of the OS and the middleware application part.
  • FIG. 11 is a diagram illustrating an example of a storage path conversion table.
  • the storage path conversion table 174 is a table that stores path conversion information when the archive function is migrated from the on-premises environment 130 to the cloud environment 140. As shown in FIG. 11, the storage path conversion path 901 before conversion and the storage after conversion It consists of the field of path 902.
  • the pre-conversion storage path 901 is a field for storing path information for accessing the storage arranged in the system from the archive application program 61A in the on-premises environment 130.
  • the post-conversion storage path 902 is a field for storing path information for accessing the storage of the path destination of the corresponding pre-conversion storage path 901 from the archive application program 61B in the cloud environment 140.
  • FIG. 12 is a flowchart showing processing of the virtual environment migration tool.
  • FIG. 13 is a flowchart showing archive path conversion processing.
  • the virtual environment migration tool may be executed by the archive server 150A or the archive server (virtual server 150B). Alternatively, it may be executed by the management server 120.
  • the virtual environment migration tool first copies or moves the archive application program 61A to the HDD 260 of the cloud environment 140 (S1001). This is the archive application program 61B.
  • the virtual environment migration tool copies or moves the tables (archive path table 171A, archive rule table 172A, storage information table 173A) to the HDD 260 of the cloud environment 140 (S1002).
  • These are the archive path table 171B, the archive rule table 172B, and the storage information table 173B, respectively.
  • the virtual environment migration tool executes archive path conversion processing (S1003).
  • the archive path conversion process may be executed from the virtual environment migration tool as described below, or may be executed by the system administrator notifying the migration explicitly.
  • the management server 120 may monitor the server on which the archive application programs 61A and 61B are operating, and confirm and notify the migration.
  • the path conversion unit 162 requests the system administrator to change the storage path 401 of the storage information table 173B (see the storage information table 173 in FIG. 5).
  • the system administrator inputs a storage path when accessing the same storage as the storage path destination stored in the storage path 401 from the archive application program 61B of the cloud environment 140.
  • the storage path “ ⁇ A1” in the storage information table 173 shown in FIG. 5 is a path in the file system in the on-premises environment 130, and the archive in the file system in the cloud environment 140 when accessing the storage location of this storage Assume that the path accessed from the application program 61B is “ ⁇ Hinc ⁇ A1”.
  • the program that migrates the archive application programs 61A and 61B may be requested to be changed and input.
  • the path conversion unit 162 or the archive application program 61B sends a command for confirming whether the network is connected to the input storage path 401, or actually reads / writes test data to confirm whether it is accessible. Also good. If the access is impossible, the user is requested to input an accessible storage path.
  • the storage path 401 of the storage information table 173B is changed with the storage path accessible from the input archive application program 61B (S1001).
  • the path conversion unit 162 stores the storage path 401 of the storage information table 173B before the change in FIG. 11 in the storage path 901 before the conversion of the storage path conversion table 174, and the storage path 401 of the storage information table 173B after the change.
  • “ ⁇ A1” is stored in the pre-conversion storage path 901
  • “ ⁇ Hinc ⁇ A1” is stored in the post-conversion storage path 902.
  • the path conversion unit 162 based on the storage path 401 of the storage information table 173B changed in S1001, archive source path 202 and archive destination path 203 of the archive path table 171B (see archive path table 171 of FIG. 3). Is converted (S1002). That is, the path corresponding to the pre-conversion storage path 901 in the storage path conversion table 174 is converted into the post-conversion storage path 902 value by the values of the archive source path 202 and the archive destination path 203 stored in the storage information table 173B. To do.
  • the archive source path 202 of the record with the data ID “0001” in FIG. 3 is changed from “ ⁇ S1 ⁇ 001” to “ ⁇ Hinc ⁇ S1 ⁇ 001”, and the archive destination path 203 is “ ⁇ A1 ⁇ 001”. To “ ⁇ Hinc ⁇ A1 ⁇ 001”.
  • the archive destination path 203 stored in the storage information table 173B is stored in the stub file of the archive source storage, the corresponding information in the stub file is changed.
  • the archive application program and the data migration destination determination program in the on-premises environment 130 do not operate.
  • the archive server (virtual server) 150B, the archive application program 61B, and the data migration destination determination program 62B are shown in FIG. Execute processing at the time of data archiving.
  • the archive application program 61B and the data migration destination determination program 62B use the archive path table 171B, the archive rule table 172B, and the storage information table 173B.
  • FIG. 8 will be used and only differences from the first embodiment will be described.
  • the archive application program and the data migration destination determination program in the on-premises environment 130 do not operate.
  • the archive server (virtual server) 150B, the archive application program 61B, and the data migration destination determination program 62B are shown in FIG. Execute processing when restoring archived data.
  • the archive application program 61B and the data migration destination determination program 62B use the archive path table 171B, the archive rule table 172B, and the storage information table 173B.
  • the archive function of this embodiment has been transferred from the on-premises environment 130 to the server on the cloud environment 140.
  • the cloud environment 140 may be transferred to the on-premises environment 130, or the cloud environment 140 may be transferred to a different cloud not shown.
  • FIG. 14 is a flowchart when restoring archive data according to the second embodiment (part 2).
  • the archive path information in the archive path table 171B is changed in step S1002 of the process of the path conversion unit 162 in FIG.
  • the processing of the path conversion unit 162 does not perform the processing of step S1002, and changes the access path to the data at the time of restoration.
  • the archive server 150 refers to the storage path conversion table 174 by executing the path conversion program 63, and among the storage path information in the storage information table 173 included in the access destination path for confirming the data contents,
  • the path corresponding to the pre-conversion storage path 901 in the storage path conversion table 174 is converted into the post-conversion storage path 902 (S701a).
  • the converted archive path table 171 is referred to, and the archive destination path 203 and archive source path 202 of the specified archive data are specified (S701b).
  • the storage path conversion table 63 is executed by referring to the storage path conversion table 174, and the storage path among the storage path information included in the restore path of the archive data is stored.
  • the path corresponding to the pre-conversion storage path 901 in the conversion table 174 is converted to the post-conversion storage path 902 (S704a).
  • the archive data in the archive destination path 203 of the archive path table 171B is copied to the restore destination of the archive data (S704b).
  • FIG. 15 is a flowchart illustrating a process for transferring archive data from the on-premises environment to the cloud environment.
  • the cloud storage 141 of the cloud environment 140 is newly constructed. A case where archive data already stored in the archive storage 132 of the on-premises environment 130 is moved to the cloud storage 141 of the cloud environment 140 will be described. This embodiment will also be described with a focus on differences from the first embodiment.
  • the archive application program 61 When moving the archive data from the on-premises environment to the cloud environment, the archive application program 61 first temporarily stops a new archive of data from the local storage 131 (S1101 in FIG. 15).
  • the cloud storage 141 of the cloud environment 140 is constructed in an existing system and connected to the system.
  • the system administrator updates or adds the archive rule table 172 and the storage information table 173 so as to conform to the new system configuration (S1102).
  • a change in the system configuration may be monitored by the management server 120, and when a configuration change is detected, the system administrator may be prompted to make a change.
  • the archive server 150 checks the data content of the archive data stored in the archive storage by executing the data migration destination determination program 62, refers to the archive rule table 172, and matches the data content
  • a rule 303 with ID 301 and tag value 302 is selected (S1103).
  • the rule for the data with the tag ID “SECURITY” and the tag value “Confidential” of the first record is “stored on-premises”. Since the rule for the data with the tag ID “TOOL” and the tag value “BI tool” of the second record is “stored in the cloud”, it is a target of the archive data transfer.
  • one rule having a higher priority 304 is selected.
  • the tag ID 301, the tag value 302, and the rule 303 that match the management server may be displayed, and the system administrator may select one of the plurality of rules 303. Shall.
  • the archive server 150 determines the storage path 401 of the storage information table 173 that matches the condition of the rule 303 selected in S1103 by executing the data migration destination determination program 62 (S1104).
  • priority information is set in advance by a system administrator or a designer, and one is determined based on the priority information. Alternatively, the system administrator may be allowed to determine one of the plurality of storage paths 401.
  • Step 1103 it is compared whether or not the storage of the storage path 401 determined in S1104 is the same storage as the archive storage 132 storing the archive data whose data content has been confirmed in Step 1103 (S1105).
  • the archive server 150 moves the archive data to the storage of the storage path 401 determined in S1104 by executing the archive application program 61 (S1106).
  • the archive application program 61 refers to the archive path table 171 and updates the archive destination path 203 in the data ID column of the moved archive data to a path storing the destination data (S1107).
  • the processing of S1103 to S1108 in this processing is performed for all archive data stored in the archive storage 132. Alternatively, it may be performed only on one or more archive data designated in advance by the system administrator. At this time, the archive data may be specified in units of volumes or folders, or may be performed only on data that meets certain conditions. For example, it can be specified by a file created during a specific period, data in a specific format, data with an access frequency of a certain value or less, and the like.
  • the data archiving system of each embodiment when migrating from the on-premises environment of the archiving system to the cloud environment, the data of the archiving data of the plurality of different archival storages in accordance with the data contents is stored. Data can be archived to an appropriate archive storage according to the property. Therefore, archiving of data to the cloud in a form that the user does not expect can be suppressed, and only data that needs to be migrated to the cloud environment can be specified and archived. In addition, after the archive application is migrated, the service can be provided by continuing to access the archive data as before the migration.

Landscapes

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

Abstract

Selon la présente invention, un serveur d'archives installé dans un environnement sur site peut archiver des données depuis une banque locale de données aussi bien dans une archive dans l'environnement sur site et dans une banque de données dématérialisée. Dans chaque ensemble de données à archiver sont incorporées des informations de contrôle comportant un marqueur, et le serveur d'archives contient une table de règles d'archives pour la détermination, sur la base des informations de contrôle de chaque ensemble de données à archiver, de l'archivage de cet ensemble de données dans une banque d'archives dans l'environnement sur site ou dans la banque de données dématérialisée. Le serveur d'archives se réfère aux informations de contrôle d'un ensemble de données à archiver et à la table de règles d'archives, et détermine s'il faut archiver cet ensemble de données dans la banque d'archives dans l'environnement sur site ou dans la banque de données dématérialisée. De cette manière, le système d'archives détermine automatiquement dans quelle banque de données envoyer les données à archiver, réduisant ainsi le travail requis pour l'archivage.
PCT/JP2016/070702 2016-07-13 2016-07-13 Système d'archives de données et procédé d'archives de données WO2018011914A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2016/070702 WO2018011914A1 (fr) 2016-07-13 2016-07-13 Système d'archives de données et procédé d'archives de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2016/070702 WO2018011914A1 (fr) 2016-07-13 2016-07-13 Système d'archives de données et procédé d'archives de données

Publications (1)

Publication Number Publication Date
WO2018011914A1 true WO2018011914A1 (fr) 2018-01-18

Family

ID=60952378

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2016/070702 WO2018011914A1 (fr) 2016-07-13 2016-07-13 Système d'archives de données et procédé d'archives de données

Country Status (1)

Country Link
WO (1) WO2018011914A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2575155A (en) * 2018-04-30 2020-01-01 Emc Ip Holding Co Llc Data storage system with LUN archiving to cloud using volume-to-object translation
CN110837592A (zh) * 2019-11-08 2020-02-25 京东数字科技控股有限公司 数据归档的方法、装置和计算机可读存储介质

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100333116A1 (en) * 2009-06-30 2010-12-30 Anand Prahlad Cloud gateway system for managing data storage to cloud storage sites

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100333116A1 (en) * 2009-06-30 2010-12-30 Anand Prahlad Cloud gateway system for managing data storage to cloud storage sites

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2575155A (en) * 2018-04-30 2020-01-01 Emc Ip Holding Co Llc Data storage system with LUN archiving to cloud using volume-to-object translation
US10536522B2 (en) 2018-04-30 2020-01-14 EMC IP Holding Company LLC Data storage system with LUN archiving to cloud using volume-to-object translation
GB2575155B (en) * 2018-04-30 2020-08-26 Emc Ip Holding Co Llc Data storage system with LUN archiving to cloud using volume-to-object translation
CN110837592A (zh) * 2019-11-08 2020-02-25 京东数字科技控股有限公司 数据归档的方法、装置和计算机可读存储介质

Similar Documents

Publication Publication Date Title
US11829256B2 (en) Data storage management system for holistic protection of cloud-based serverless applications in single cloud and across multi-cloud computing environments
US11436038B2 (en) Hypervisor-independent block-level live browse for access to backed up virtual machine (VM) data and hypervisor-free file-level recovery (block- level pseudo-mount)
US11182255B2 (en) Sharing of secondary storage data
US11442896B2 (en) Systems and methods for optimizing restoration of deduplicated data stored in cloud-based storage resources
US20210011812A1 (en) Preparing containerized applications for backup using a backup services container and a backup services container-orchestration pod
US10303557B2 (en) Data transfer to a distributed storage environment
US11677632B2 (en) Smart network topology systems and methods
US11921594B2 (en) Enhanced file indexing, live browsing, and restoring of backup copies of virtual machines and/or file systems by populating and tracking a cache storage area and a backup index
JP5082310B2 (ja) データ移行装置及びプログラム
US20220043727A1 (en) Assigning backup resources in a data storage management system based on failover of partnered data storage resources
US11347707B2 (en) File indexing for virtual machine backups based on using live browse features
US11449486B2 (en) File indexing for virtual machine backups in a data storage management system
WO2016199232A1 (fr) Ordinateur de gestion de stockage et procédé de gestion pour un dispositif de stockage
US20220012134A1 (en) Cloud-based air-gapped data storage management system
US20210064486A1 (en) Access arbitration to a shared cache storage area in a data storage management system for live browse, file indexing, backup and/or restore operations
US20210191629A1 (en) Expandable data storage management system
JP2008276488A (ja) ストレージシステムおよびストレージシステムの情報移行方法
WO2015145632A1 (fr) Système informatique
AU2019263048B2 (en) Client managed data backup process within an enterprise information management system
WO2018011914A1 (fr) Système d'archives de données et procédé d'archives de données
US20230124827A1 (en) Data storage management system for live-mounting a virtual machine in a cloud computing environment based on using nested virtual machines for immediate access to data in a proprietary backup copy
US20230147671A1 (en) Systems and methods for optimizing storage and retention of deduplicated secondary copies at storage platforms that are write-once read-many (worm) enabled
US20230297403A1 (en) Live mounting a virtual machine in a public cloud based on accessing a simulated virtual disk as an internet small computer systems interface (iscsi) target
US20230409405A1 (en) Holistically protecting serverless applications based on detecting in-cloud deployments
JP2006113814A (ja) ディレクトリサービス提供システム、及びプログラム

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: 16908818

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: 16908818

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP