US20140172802A1 - Information processor and backup method - Google Patents

Information processor and backup method Download PDF

Info

Publication number
US20140172802A1
US20140172802A1 US14/073,259 US201314073259A US2014172802A1 US 20140172802 A1 US20140172802 A1 US 20140172802A1 US 201314073259 A US201314073259 A US 201314073259A US 2014172802 A1 US2014172802 A1 US 2014172802A1
Authority
US
United States
Prior art keywords
snapshot
data
file system
information
storage apparatus
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US14/073,259
Other versions
US9430485B2 (en
Inventor
Norihito KATO
Nobuhiro Takano
Norichika IMAMURA
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Assigned to FUJITSU LIMITED reassignment FUJITSU LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: IMAMURA, NORICHIKA, TAKANO, NOBUHIRO, KATO, NORIHITO
Publication of US20140172802A1 publication Critical patent/US20140172802A1/en
Application granted granted Critical
Publication of US9430485B2 publication Critical patent/US9430485B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • G06F17/30088
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/11File system administration, e.g. details of archiving or snapshots
    • G06F16/128Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1448Management of the data involved in backup or backup restore
    • G06F11/1451Management of the data involved in backup or backup restore by selection of backup contents
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16Error detection or correction of the data by redundancy in hardware
    • G06F11/20Error 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/2053Error 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/2056Error 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
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/84Using snapshots, i.e. a logical point-in-time copy of the data

Definitions

  • Embodiments discussed herein are related to backup and restoration of information performed by an information processor.
  • the backup restoration is performed using a function that copies a disk area in the disk array apparatus into another disk in the same apparatus while stopping input and output (I/O).
  • an information processor coupled to a storage apparatus that stores information includes: a creation unit configured to create a snapshot of a file system that manages first information stored in the storage apparatus and to output the snapshot to the storage apparatus; a writing unit configured to write second information stored in cache memory onto the storage apparatus after the snapshot has been created; and a replication instruction unit configured to instruct the storage apparatus to create a replication of the first information stored in the storage apparatus after the second information has been written and the snapshot.
  • FIG. 1 illustrates an example of an information processor
  • FIG. 2 illustrates an example of a server storage system
  • FIG. 3 illustrates an example of schedule information
  • FIG. 4 illustrates an example of a system process at a time of backup
  • FIG. 5 illustrates an example of a system process at a time of restoration
  • FIG. 6 illustrates an example of a backup restoration process
  • FIG. 7 illustrates an example of a process of a control unit
  • FIG. 8 illustrates an example of a process of a file system
  • FIG. 9 illustrates an example of a process of an operating system (OS).
  • OS operating system
  • FIG. 10 illustrates an example of a process of a controller
  • FIG. 11 illustrates an example of a process of a copy unit
  • FIG. 12 illustrates an example of a process of a control unit
  • FIG. 13 illustrates an example of a process of a controller
  • FIG. 14 illustrates an example of a process of a copy unit
  • FIG. 15 illustrates an example of a process of an OS
  • FIG. 16 illustrates an example of a process of a file system.
  • a data update after acquisition of a snapshot is performed in an update data storage disk apparatus, which is a storage area physically different from a disk apparatus that stores original data. Accordingly, the disk array apparatus causes a backup apparatus to acquire a backup through sequential reading from an area of a disk of the update data storage disk apparatus without distributing a storage area of the snapshot.
  • the disk array apparatus on a regular site manages backup data of a main volume over a plurality of generations based on a differential snapshot. Differential data of the main volume and a main pool is transferred from the regular site to a secondary site at a certain timing.
  • the secondary site holds a secondary volume, which is a copy of the main volume, and a secondary pool, which is a copy of the main pool.
  • Generation management information is also transferred from the regular site to the secondary site.
  • the generation management information includes a differential bitmap table and a save destination address management table.
  • the secondary site holds a copy of the generation management information. Thus, the whole including the generation management information is backed up and fault tolerance is enhanced.
  • a main volume group includes a primary volume and a differential volume.
  • a secondary volume group includes a primary volume and a differential volume. For example, when the differential snapshots of the plurality of generations are accumulated in the differential volume and the utilization rate reaches a certain value, a request for acquisition of a new snapshot is transmitted.
  • Each of the volume groups is synchronized based on a volume snapshot and then split. After the split, the differential volume is initialized and the secondary volume group is backed up. Thus, a new differential snapshot is created and held in the differential volume.
  • data being written may be incompletely written onto the disk.
  • the snapshot taken by the disk array apparatus such as the data on the physical disk, differs from an image on the file system.
  • the consistency of the data may fail to be maintained on the disk and the state at the time of the backup may fail to be completely restored.
  • the backup restoration Since in the backup restoration, copying is performed using a resource of the disk array apparatus, use of a resource of a server, such as a central processing unit (CPU), may be undesired at the time of the copying. Since the input and output to the disk array apparatus are stopped in order to ensure the consistency of the backup data, the backup restoration may be performed offline.
  • a server such as a central processing unit (CPU)
  • a snapshot is utilized such that data of the moment at which the snapshot is taken in the same storage is copied as a link to actual data and is backed up instantly. In this manner, the backup restoration may be performed.
  • the consistency of the data may fail to be maintained on the disk and the state at the time of the backup may fail to be completely restored.
  • a file system like a Zettabyte File System (ZFS) does not have a function that stops the input and output. Since an application or business is stopped in order to stop the input and output in the file system, no online backup may be performed.
  • ZFS Zettabyte File System
  • the online backup may be performed by taking a snapshot, which is an image of the file system. Since the data of the snapshot is linked to the actual data, when, for example, data loss caused by disk failure or the like occurs, the data of the snapshot may be lost as well.
  • the online backup may be performed by copying the actual data of the snapshot into another disk.
  • a resource of an business server is used and thus, other businesses may be affected.
  • FIG. 1 illustrates an example of an information processor.
  • An information processor 1 is coupled to a storage apparatus 7 that stores information.
  • the information processor 1 includes a creation unit 2 , a writing unit 3 , and a replication instruction unit 4 .
  • the creation unit 2 creates a snapshot of a file system that manages first information stored in the storage apparatus 7 and outputs the snapshot to the storage apparatus 7 .
  • the creation unit 2 may correspond to, for example, a file system 19 , or a control unit 15 that instructs the file system 19 to create a snapshot.
  • the writing unit 3 writes second information stored in cache memory onto the storage apparatus 7 after the creation of the snapshot.
  • the writing unit 3 may correspond to, for example, an operating system (OS) 18 , or the control unit 15 that instructs the OS 18 to perform writing.
  • OS operating system
  • the replication instruction unit 4 instructs the storage apparatus 7 to create a replication of the first information, which is held by the storage apparatus 7 after the second information has been written, and the snapshot.
  • the replication instruction unit 4 may correspond to, for example, a controller 29 , or the control unit 15 that gives instructions to the controller 29 .
  • the backup may be performed with the integrity of the data at the time of the backup.
  • the information processor 1 further includes a recognition unit 5 and a rollback execution unit 6 .
  • the recognition unit 5 recognizes information resulting from replicating the snapshot and the first information, onto which the second information is written after the creation of the snapshot, as a file system.
  • the recognition unit 5 may be the OS 18 that performs the recognition based on, for example, the instructions of the control unit 15 .
  • the rollback execution unit 6 executes rollback based on the snapshot.
  • the rollback execution unit 6 may be the file system 19 that performs the rollback based on, for example, the instructions of the rollback execution unit 6 .
  • the restoration may be performed using the backup data having the integrity of the data at the time of the backup and the data may be returned to the state at the time of the backup.
  • FIG. 2 illustrates an example of a server storage system.
  • a server storage system 11 the backup restoration of the data is performed online without stopping the input and output from a server 12 to a storage apparatus.
  • the server storage system 11 includes the server 12 and a disk array apparatus 28 , which is the storage apparatus.
  • the server 12 and the disk array apparatus 28 are coupled via a communication network 26 .
  • the server storage system 11 may be provided with a backup apparatus or a backup server.
  • the server 12 may be a server that executes an application software program, which is hereinafter referred to as an application or an app, 13 to perform an business processing.
  • the server 12 is coupled to an information processing terminal 27 for inputting a command or data to the server 12 .
  • the server 12 includes a hardware 20 , such as a CPU 21 , cache memory 22 , which is hereinafter referred to as a cache 22 , memory 23 , a communication interface (I/F) 24 , and a hard disk drive (HDD) 25 .
  • the CPU 21 , the cache 22 , the memory 23 , the communication I/F 24 , and the HDD 25 are coupled via a bus.
  • the HDD 25 is a mass storage device and stores the OS 18 , an application 13 , and the like.
  • the CPU 21 reads the OS 18 or the application 13 from the HDD 25 and executes a certain process.
  • the creation unit 2 , the writing unit 3 , the replication instruction unit 4 , the recognition unit 5 , and the rollback execution unit 6 are operated.
  • the memory 23 is a storage device that stores data temporarily.
  • the cache 22 may be a storage device with a speed higher than the speed of the memory 23 and with a capacity smaller than the capacity of the memory 23 .
  • the communication I/F 24 is coupled to the communication network 26 and may be an interface for communicating with a device coupled to the communication network 26 .
  • the OS 18 includes the file system 19 .
  • the file system 19 is used for managing data recorded in the storage device.
  • the file system 19 may have no I/O stop function.
  • the file system 19 operates on the server 12 .
  • the target data to be backed up is managed in the file system 19 .
  • the file system 19 includes a snapshot function and a rollback function.
  • the snapshot function serves to take a data image on the file system 19 at a certain moment.
  • the rollback function serves, using the snapshot that has previously been taken on the file system 19 , to return the file system to the state at the time at which the snapshot has been taken.
  • the data managed by the file system 19 is saved in a physical disk on the disk array apparatus 28 and is partially present on the cache 22 .
  • the cache 22 temporarily saves the data written onto the file system 19 having no I/O stop function. Since in the cache 22 , a process is performed with a speed higher than the speed for the saving into the physical disk on the disk array apparatus 28 , the writing may be performed at a high speed. The data present only on the cache is not present on the disk array apparatus 28 . Thus, when the information stored in an business data storage unit 31 is copied in this state into a replication data storage unit 32 by the copy function of the disk array apparatus 28 , the data on the cache 22 is not copied into the replication data storage unit 32 .
  • the application 13 includes an app 14 for businesses, a control program, and the like.
  • the CPU 21 may function as the control unit 15 by reading and executing a control program.
  • the control unit 15 instructs the file system 19 used in the OS 18 or the controller 29 present in the disk array apparatus 28 to start to execute various functions including taking a snapshot and giving instructions for the copying among disks.
  • the control unit 15 may include a determination unit 16 or schedule information 17 .
  • the determination unit 16 determines a timing for taking the snapshot using the schedule information 17 and then determines a timing for writing the data on the cache 22 onto the physical disk of the disk array apparatus 28 .
  • a schedule which includes a start time of taking the snapshot and a start time of the copying from the business data storage unit 31 into the replication data storage unit 32 , is registered in the schedule information 17 and managed based on a snapshot flag and a copy flag.
  • the schedule information 17 includes a management item for managing the entire schedule.
  • the schedule information 17 may be, for example, a table of n days or a table of a few weeks.
  • the disk array apparatus 28 is provided with a plurality of physical disks, includes a controller that manages the plurality of physical disks, and has characteristics of a high speed, a large capacity, and high reliability.
  • the disk array apparatus 28 includes the controller 29 , a copy unit 30 , and the physical disks, which are the business data storage unit 31 and the replication data storage unit 32 .
  • the controller 29 manages the plurality of the physical disks. Based on the instructions of the control unit 15 present on the server 12 , the controller 29 requests the copy unit 30 to copy the data included in the physical disk from the business data storage unit 31 into the replication data storage unit 32 or from the replication data storage unit 32 into the business data storage unit 31 .
  • the copy unit 30 When the copy unit 30 receives the request from the controller 29 , the copy unit 30 reads the data from the designated physical disk and writes the data onto another designated physical disk.
  • the physical disks are physical disks of the disk array apparatus 28 and include the business data storage unit 31 that stores the business data and the replication data storage unit 32 .
  • the communication network 26 couples the server 12 and the disk array apparatus 28 .
  • the communication network 26 may be a Fiber Channel (FC), a Serial Attached SCSI (SAS), an Internet Small Computer System Interface (iSCSI), a Fiber Channel over Ethernet (FCoE), or the like.
  • FIG. 3 illustrates an example of schedule information.
  • the schedule information 17 includes a schedule management item 41 and schedule entries 42 - 1 , 42 - 2 , . . . , and 42 - n .
  • the schedule entries 42 - 1 , 42 - 2 , . . . , and 42 - n may be referred to as the schedule entries 42 .
  • the schedule management item 41 may be an item for managing which one of the schedule entries 42 is active.
  • the schedule entries 42 may be information for managing the start time of taking the snapshot and the start time of the copying from the business data storage unit 31 into the replication data storage unit 32 .
  • the schedule entries 42 include data items of “entry identification information” 43 , a “flag” 44 , and a “start time” 45 .
  • the “entry identification information” 43 may be information for identifying the schedule entries.
  • the entry identification information on the schedule entry that is currently active is set for the schedule management item 41 .
  • the snapshot flag (S), the copy flag (C), or none (N) may be set for the “flag” 44 .
  • the start time for the snapshot or the copying may be set for the “start time” 45 .
  • FIG. 4 illustrates an example of a system process at a time of the backup.
  • solid line arrows indicate backup procedures and broken line arrows indicate a flow data processing performed online.
  • Data 33 directly written from the app 14 via the file system 19 is stored in the business data storage unit 31 of the disk array apparatus 28 .
  • Data 34 which is saved temporarily from the app 14 into the cache 22 via the file system 19 and written from the cache 22 , is stored in the business data storage unit 31 .
  • a snapshot 35 of the file system 19 has been taken before the data is copied by the disk array apparatus 28 .
  • the data on the cache 22 has been written onto the physical disk before the data is copied by the disk array apparatus 28 .
  • the copy function of the disk array apparatus 28 the data and the snapshot stored in the business data storage unit 31 are copied from the business data storage unit 31 into the replication data storage unit 32 .
  • the determination unit 16 notifies the control unit 15 of the creation of the snapshot or the timing for writing the data on the cache onto the physical disk.
  • the control unit 15 instructs the file system 19 to create the snapshot (S 1 ).
  • the file system 19 creates the snapshot of the file system 19 and outputs the snapshot to the business data storage unit 31 (S 2 ).
  • the control unit 15 instructs the cache 22 to write the data on the cache 22 onto the physical disk of the disk array apparatus 28 (S 3 ).
  • the cache 22 writes the data on the cache 22 onto the physical disk, which is the business data storage unit 31 (S 4 ).
  • the control unit 15 instructs the controller 29 to copy the data from the business data storage unit 31 into the replication data storage unit 32 (S 5 ).
  • the controller 29 instructs the copy unit 30 to copy the data and the snapshot, which are stored in the business data storage unit 31 , from the business data storage unit 31 into the replication data storage unit 32 (S 6 ).
  • the copy unit 30 copies the data 33 , the data 34 , and the snapshot 35 , which are stored in the business data storage unit 31 , from the business data storage unit 31 into the replication data storage unit 32 (S 7 ).
  • the control unit 15 takes the snapshot for the target data to be backed up on the disk array apparatus 28 , which is managed in the file system 19 .
  • an image of the file system at a desired timing may be taken online without stopping the I/O.
  • the file system 19 writes the data on the cache 22 onto the physical disk and writes all the data that the file system 19 is instructed to write onto the physical disk. Even when the copying is performed by the disk array apparatus 28 , the backup may be performed online without stopping the I/O by combining the writing process and the copy function of the disk array apparatus.
  • FIG. 5 illustrates an example of a system process at a time of restoration.
  • solid line arrows indicate the restoration procedures.
  • one of the sets of the data and the snapshot is copied from the replication data storage unit 32 into the business data storage unit 31 by using the copy function of the disk array apparatus 28 is used.
  • the server 12 mounts the data and the snapshot copied into the business data storage unit 31 . Because of the mounting, the consistency of the data may fail to be maintained and the state may fail to return to the state at the time of taking the snapshot. Thus, the state returns to the state at the time of taking the snapshot by performing the rollback on the snapshot.
  • guaranteed data may be restored using the characteristics that ensure the consistency of the data at the time of taking the snapshot under a ZFS snapshot command and the rollback function of the ZFS.
  • the process illustrated in FIG. 5 may be performed.
  • the replication data storage unit 32 may store one or more sets of the data 33 and 34 and the snapshot 35 .
  • the control unit 15 instructs the controller 29 to copy one of the sets of the data 33 and 34 and the snapshot 35 from the replication data storage unit 32 into the business data storage unit 31 (S 11 ).
  • the controller 29 instructs the copy unit 30 to copy a designated set of the data 33 and 34 and the snapshot 35 from the replication data storage unit 32 into the business data storage unit 31 (S 12 ).
  • the copy unit 30 copies the designated set of the data 33 and 34 and the snapshot 35 from the replication data storage unit 32 into the business data storage unit 31 (S 13 ).
  • the control unit 15 instructs the OS 18 to recognize the data 33 and 34 and the snapshot 35 copied into the business data storage unit 31 as a file system (S 14 ).
  • the OS 18 recognizes the data 33 and 34 and the snapshot 35 stored in the business data storage unit 31 as the file system 19 (S 15 ).
  • the control unit 15 instructs the file system 19 to perform the rollback (S 16 ).
  • the file system 19 performs the rollback based on the data 33 and 34 and the snapshot 35 (S 17 ).
  • FIG. 6 illustrates an example of a backup restoration process.
  • the business data is backed up (S 21 ).
  • detection of an abnormality of the business data is performed.
  • the business data is restored (S 22 ).
  • the detection of the business abnormality and the abnormality of the business data may be taken into the control unit 15 .
  • FIG. 7 illustrates an example of a process of a control unit.
  • the process illustrated in FIG. 7 may correspond to the process performed by the control unit in operation S 21 illustrated in FIG. 6 .
  • FIG. 8 illustrates an example of a process of a file system.
  • the process illustrated in FIG. 8 may correspond to the process performed by the file system in operation S 21 illustrated in FIG. 6 .
  • FIG. 9 illustrates an example of a process of an OS.
  • the process illustrated in FIG. 9 may correspond to the process performed by the OS in operation S 21 illustrated in FIG. 6 .
  • FIG. 10 illustrates an example of a process of a controller.
  • the process illustrated in FIG. 10 may correspond to the process performed by the controller in operation S 21 illustrated in FIG. 6 .
  • FIG. 11 illustrates an example of a process of a copy unit.
  • the process illustrated in FIG. 11 may correspond to the process performed by the copy unit in operation S 21 illustrated in FIG. 6 .
  • the determination unit 16 of the control unit 15 reads the entry identification information set for the schedule management item 41 of the schedule information 17 stored in the storage device, and reads the schedule entry 42 corresponding to the entry identification information.
  • the determination unit 16 determines whether the snapshot flag is on in the “flag” 44 included in the read schedule entry 42 (S 31 ).
  • the determination unit 16 determines a timing for creating a snapshot in accordance with the “start time” 45 included in the read schedule entry 42 .
  • the determination unit 16 notifies the control unit 15 of the timing for creating the snapshot.
  • the control unit 15 instructs the file system 19 having no I/O stop function to create the snapshot (S 32 ).
  • the file system 19 having no I/O stop function creates the snapshot and the OS 18 outputs the snapshot to the business data storage unit 31 (S 41 ).
  • the file system 19 notifies the control unit 15 of the completion of the creation of the snapshot.
  • the process described next is performed in the control unit 15 after the completion of the creation of the snapshot (“Yes” in S 33 ).
  • the determination unit 16 determines whether the copy flag in the “flag” 44 included in the read schedule entry 42 is on or not (S 34 ).
  • the determination unit 16 determines a timing for writing the data on the cache 22 onto the physical disk in accordance with the “start time” 45 included in the read schedule entry 42 .
  • the determination unit 16 notifies the control unit 15 of the timing for writing the data on the cache 22 onto the physical disk.
  • the control unit 15 instructs the OS 18 to write the data on the cache 22 onto the physical disk (S 35 ).
  • the OS 18 performs the process of writing the data on the cache 22 onto the physical disk (S 51 ). All the data on the cache 22 may be written out.
  • the control unit 15 instructs the controller 29 of the disk array apparatus 28 to copy the information stored in the business data storage unit 31 into the replication data storage unit 32 (S 37 ).
  • the controller 29 instructs the copy unit 30 to copy the data including the data written from the cache 22 and the snapshot, which are stored in the business data storage unit 31 , into the replication data storage unit 32 (S 61 ).
  • the copy unit 30 of the disk array apparatus 28 copies the data including the data written from the cache 22 and the snapshot, which are stored in the business data storage unit 31 , into the replication data storage unit 32 (S 71 ).
  • the copy unit 30 When the copying is completed, the copy unit 30 notifies the controller 29 of the completion of the copying.
  • the controller 29 notifies the control unit 15 of the completion of the copying (S 62 ).
  • the control unit 15 receives the notification of the completion of the copying from the controller 29 (“Yes” in S 38 ), the process ends.
  • the copying may be performed without stopping the I/O.
  • FIG. 12 illustrates an example of a process of a control unit.
  • the process illustrated in FIG. 12 may correspond to the process performed by the control unit in operation S 22 illustrated in FIG. 6 .
  • FIG. 13 illustrates an example of a process of a controller.
  • the process illustrated in FIG. 13 may correspond to the process performed by the controller in operation S 22 illustrated in FIG. 6 .
  • FIG. 14 illustrates an example of a process of a copy unit.
  • the process illustrated in FIG. 14 may correspond to the process performed by the copy unit in operation S 22 illustrated in FIG. 6 .
  • FIG. 15 illustrates an example of a process of an OS.
  • the process illustrated in FIG. 15 may correspond to the process performed by the OS in operation S 22 illustrated in FIG. 6 .
  • FIG. 16 illustrates an example of a process of a file system.
  • the process illustrated in FIG. 16 may correspond to the process performed by the file system having no I/O stop function in operation S 22 illustrated in FIG. 6 .
  • the control unit 15 instructs the controller 29 of the disk array apparatus 28 to copy the replicated data from the replication data storage unit 32 into the business data storage unit 31 (S 81 ).
  • the controller 29 of the disk array apparatus 28 instructs the copy unit 30 to copy the replicated data from the replication data storage unit 32 into the business data storage unit 31 (S 91 ).
  • the copy unit 30 of the disk array apparatus 28 copies the data and the snapshot of the replication data storage unit 32 into the business data storage unit 31 (S 101 ). For example, when the data and the snapshot of a previous day are present on the replication data storage unit 32 , the copy unit 30 copies the data and the snapshot into the business data storage unit 31 .
  • the copy unit 30 When the copying is completed, the copy unit 30 notifies the controller 29 of the completion of the copying.
  • the controller 29 receives the notification of the completion of the copying (“Yes” in S 92 ), the controller 29 notifies the control unit 15 that the controller 29 has received the notification of the completion of the copying.
  • the control unit 15 instructs the OS 18 to recognize the copied data and snapshot in the disk as the file system 19 (S 83 ). As illustrated in FIG. 15 , the OS 18 recognizes the data and the snapshot of the business data storage unit 31 as the file system 19 (S 111 ).
  • the control unit 15 instructs the file system 19 having no I/O stop function to perform the rollback (restoration) based on the data and the snapshot (S 85 ).
  • the file system 19 having no I/O stop function performs the rollback (restoration) based on the data and the snapshot (S 121 ).
  • the process ends.
  • the backup (online backup), may be performed without stopping any business or application.
  • the backup may be performed without using a resource of the server 12 , such as the CPU.
  • the consistency of the data restored in the server 12 may be secured.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Retry When Errors Occur (AREA)

Abstract

An information processor coupled to a storage apparatus that stores information, includes: a creation unit configured to create a snapshot of a file system that manages first information stored in the storage apparatus and to output the snapshot to the storage apparatus; a writing unit configured to write second information stored in cache memory onto the storage apparatus after the snapshot has been created; and a replication instruction unit configured to instruct the storage apparatus to create a replication of the first information stored in the storage apparatus after the second information has been written and the snapshot.

Description

    CROSS-REFERENCE TO RELATED APPLICATION
  • This application is based upon and claims the benefit of priority from the prior Japanese Patent Application No. 2012-273115 filed on Dec. 14, 2012, the entire contents of which are incorporated herein by reference.
  • FIELD
  • Embodiments discussed herein are related to backup and restoration of information performed by an information processor.
  • BACKGROUND
  • As regards backup restoration in a disk array apparatus coupled to a server, the backup restoration is performed using a function that copies a disk area in the disk array apparatus into another disk in the same apparatus while stopping input and output (I/O).
  • Related art is disclosed in Japanese Laid-open Patent Publication No. 2005-332067, Japanese Laid-open Patent Publication No. 2005-292865, and Japanese Laid-open Patent Publication No. 2005-250676.
  • SUMMARY
  • According to one aspect of the embodiments, an information processor coupled to a storage apparatus that stores information, includes: a creation unit configured to create a snapshot of a file system that manages first information stored in the storage apparatus and to output the snapshot to the storage apparatus; a writing unit configured to write second information stored in cache memory onto the storage apparatus after the snapshot has been created; and a replication instruction unit configured to instruct the storage apparatus to create a replication of the first information stored in the storage apparatus after the second information has been written and the snapshot.
  • The object and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the claims.
  • It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention, as claimed.
  • BRIEF DESCRIPTION OF DRAWINGS
  • FIG. 1 illustrates an example of an information processor;
  • FIG. 2 illustrates an example of a server storage system;
  • FIG. 3 illustrates an example of schedule information;
  • FIG. 4 illustrates an example of a system process at a time of backup;
  • FIG. 5 illustrates an example of a system process at a time of restoration;
  • FIG. 6 illustrates an example of a backup restoration process;
  • FIG. 7 illustrates an example of a process of a control unit;
  • FIG. 8 illustrates an example of a process of a file system;
  • FIG. 9 illustrates an example of a process of an operating system (OS);
  • FIG. 10 illustrates an example of a process of a controller;
  • FIG. 11 illustrates an example of a process of a copy unit;
  • FIG. 12 illustrates an example of a process of a control unit;
  • FIG. 13 illustrates an example of a process of a controller;
  • FIG. 14 illustrates an example of a process of a copy unit;
  • FIG. 15 illustrates an example of a process of an OS; and
  • FIG. 16 illustrates an example of a process of a file system.
  • DESCRIPTION OF EMBODIMENTS
  • In a disk array apparatus, a data update after acquisition of a snapshot is performed in an update data storage disk apparatus, which is a storage area physically different from a disk apparatus that stores original data. Accordingly, the disk array apparatus causes a backup apparatus to acquire a backup through sequential reading from an area of a disk of the update data storage disk apparatus without distributing a storage area of the snapshot.
  • The disk array apparatus on a regular site manages backup data of a main volume over a plurality of generations based on a differential snapshot. Differential data of the main volume and a main pool is transferred from the regular site to a secondary site at a certain timing. The secondary site holds a secondary volume, which is a copy of the main volume, and a secondary pool, which is a copy of the main pool. Generation management information is also transferred from the regular site to the secondary site. The generation management information includes a differential bitmap table and a save destination address management table. The secondary site holds a copy of the generation management information. Thus, the whole including the generation management information is backed up and fault tolerance is enhanced.
  • A main volume group includes a primary volume and a differential volume. A secondary volume group includes a primary volume and a differential volume. For example, when the differential snapshots of the plurality of generations are accumulated in the differential volume and the utilization rate reaches a certain value, a request for acquisition of a new snapshot is transmitted. Each of the volume groups is synchronized based on a volume snapshot and then split. After the split, the differential volume is initialized and the secondary volume group is backed up. Thus, a new differential snapshot is created and held in the differential volume.
  • For example, when the backup of the disk array apparatus is performed while continuing an business processing without stopping the input and output, data being written may be incompletely written onto the disk. When data on a file system remains on a cache and is not written onto a physical disk, the snapshot taken by the disk array apparatus, such as the data on the physical disk, differs from an image on the file system. Thus, the consistency of the data may fail to be maintained on the disk and the state at the time of the backup may fail to be completely restored.
  • Since in the backup restoration, copying is performed using a resource of the disk array apparatus, use of a resource of a server, such as a central processing unit (CPU), may be undesired at the time of the copying. Since the input and output to the disk array apparatus are stopped in order to ensure the consistency of the backup data, the backup restoration may be performed offline.
  • In the backup of a storage coupled to a server, a snapshot is utilized such that data of the moment at which the snapshot is taken in the same storage is copied as a link to actual data and is backed up instantly. In this manner, the backup restoration may be performed.
  • In the backup of the storage coupled to the server, a complete copy of the actual data is created in the same storage with respect to what the snapshot is taken for. In this manner, the backup restoration may be performed.
  • The consistency of the data may fail to be maintained on the disk and the state at the time of the backup may fail to be completely restored. In order to maintain the consistency of the data, it is desired to stop the input and output to the disk at the time of the backup. A file system like a Zettabyte File System (ZFS) does not have a function that stops the input and output. Since an application or business is stopped in order to stop the input and output in the file system, no online backup may be performed.
  • The online backup may be performed by taking a snapshot, which is an image of the file system. Since the data of the snapshot is linked to the actual data, when, for example, data loss caused by disk failure or the like occurs, the data of the snapshot may be lost as well.
  • The online backup may be performed by copying the actual data of the snapshot into another disk. In the backup restoration for which no disk array apparatus is used, a resource of an business server is used and thus, other businesses may be affected.
  • FIG. 1 illustrates an example of an information processor. An information processor 1 is coupled to a storage apparatus 7 that stores information. The information processor 1 includes a creation unit 2, a writing unit 3, and a replication instruction unit 4.
  • The creation unit 2 creates a snapshot of a file system that manages first information stored in the storage apparatus 7 and outputs the snapshot to the storage apparatus 7. The creation unit 2 may correspond to, for example, a file system 19, or a control unit 15 that instructs the file system 19 to create a snapshot.
  • The writing unit 3 writes second information stored in cache memory onto the storage apparatus 7 after the creation of the snapshot. The writing unit 3 may correspond to, for example, an operating system (OS) 18, or the control unit 15 that instructs the OS 18 to perform writing.
  • The replication instruction unit 4 instructs the storage apparatus 7 to create a replication of the first information, which is held by the storage apparatus 7 after the second information has been written, and the snapshot. The replication instruction unit 4 may correspond to, for example, a controller 29, or the control unit 15 that gives instructions to the controller 29.
  • When the input and output (I/O) to the storage apparatus are performed in an environment of a file system having no I/O stop function or without stopping the I/O, the backup may be performed with the integrity of the data at the time of the backup.
  • The information processor 1 further includes a recognition unit 5 and a rollback execution unit 6. The recognition unit 5 recognizes information resulting from replicating the snapshot and the first information, onto which the second information is written after the creation of the snapshot, as a file system. The recognition unit 5 may be the OS 18 that performs the recognition based on, for example, the instructions of the control unit 15.
  • The rollback execution unit 6 executes rollback based on the snapshot. The rollback execution unit 6 may be the file system 19 that performs the rollback based on, for example, the instructions of the rollback execution unit 6.
  • The restoration may be performed using the backup data having the integrity of the data at the time of the backup and the data may be returned to the state at the time of the backup.
  • FIG. 2 illustrates an example of a server storage system. In a server storage system 11, the backup restoration of the data is performed online without stopping the input and output from a server 12 to a storage apparatus. The server storage system 11 includes the server 12 and a disk array apparatus 28, which is the storage apparatus. The server 12 and the disk array apparatus 28 are coupled via a communication network 26. The server storage system 11 may be provided with a backup apparatus or a backup server.
  • The server 12 may be a server that executes an application software program, which is hereinafter referred to as an application or an app, 13 to perform an business processing. The server 12 is coupled to an information processing terminal 27 for inputting a command or data to the server 12. The server 12 includes a hardware 20, such as a CPU 21, cache memory 22, which is hereinafter referred to as a cache 22, memory 23, a communication interface (I/F) 24, and a hard disk drive (HDD) 25. The CPU 21, the cache 22, the memory 23, the communication I/F 24, and the HDD 25 are coupled via a bus. The HDD 25 is a mass storage device and stores the OS 18, an application 13, and the like.
  • The CPU 21 reads the OS 18 or the application 13 from the HDD 25 and executes a certain process. When the CPU 21 reads and executes a program, the creation unit 2, the writing unit 3, the replication instruction unit 4, the recognition unit 5, and the rollback execution unit 6 are operated.
  • The memory 23 is a storage device that stores data temporarily. The cache 22 may be a storage device with a speed higher than the speed of the memory 23 and with a capacity smaller than the capacity of the memory 23. The communication I/F 24 is coupled to the communication network 26 and may be an interface for communicating with a device coupled to the communication network 26.
  • The OS 18 includes the file system 19. The file system 19 is used for managing data recorded in the storage device. The file system 19 may have no I/O stop function. The file system 19 operates on the server 12. The target data to be backed up is managed in the file system 19. The file system 19 includes a snapshot function and a rollback function. The snapshot function serves to take a data image on the file system 19 at a certain moment. The rollback function serves, using the snapshot that has previously been taken on the file system 19, to return the file system to the state at the time at which the snapshot has been taken. The data managed by the file system 19 is saved in a physical disk on the disk array apparatus 28 and is partially present on the cache 22.
  • The cache 22 temporarily saves the data written onto the file system 19 having no I/O stop function. Since in the cache 22, a process is performed with a speed higher than the speed for the saving into the physical disk on the disk array apparatus 28, the writing may be performed at a high speed. The data present only on the cache is not present on the disk array apparatus 28. Thus, when the information stored in an business data storage unit 31 is copied in this state into a replication data storage unit 32 by the copy function of the disk array apparatus 28, the data on the cache 22 is not copied into the replication data storage unit 32.
  • The application 13 includes an app 14 for businesses, a control program, and the like. The CPU 21 may function as the control unit 15 by reading and executing a control program.
  • The control unit 15 instructs the file system 19 used in the OS 18 or the controller 29 present in the disk array apparatus 28 to start to execute various functions including taking a snapshot and giving instructions for the copying among disks. The control unit 15 may include a determination unit 16 or schedule information 17.
  • The determination unit 16 determines a timing for taking the snapshot using the schedule information 17 and then determines a timing for writing the data on the cache 22 onto the physical disk of the disk array apparatus 28.
  • A schedule, which includes a start time of taking the snapshot and a start time of the copying from the business data storage unit 31 into the replication data storage unit 32, is registered in the schedule information 17 and managed based on a snapshot flag and a copy flag. The schedule information 17 includes a management item for managing the entire schedule. The schedule information 17 may be, for example, a table of n days or a table of a few weeks.
  • The disk array apparatus 28 is provided with a plurality of physical disks, includes a controller that manages the plurality of physical disks, and has characteristics of a high speed, a large capacity, and high reliability. The disk array apparatus 28 includes the controller 29, a copy unit 30, and the physical disks, which are the business data storage unit 31 and the replication data storage unit 32.
  • The controller 29 manages the plurality of the physical disks. Based on the instructions of the control unit 15 present on the server 12, the controller 29 requests the copy unit 30 to copy the data included in the physical disk from the business data storage unit 31 into the replication data storage unit 32 or from the replication data storage unit 32 into the business data storage unit 31.
  • When the copy unit 30 receives the request from the controller 29, the copy unit 30 reads the data from the designated physical disk and writes the data onto another designated physical disk. The physical disks are physical disks of the disk array apparatus 28 and include the business data storage unit 31 that stores the business data and the replication data storage unit 32.
  • The communication network 26 couples the server 12 and the disk array apparatus 28. The communication network 26 may be a Fiber Channel (FC), a Serial Attached SCSI (SAS), an Internet Small Computer System Interface (iSCSI), a Fiber Channel over Ethernet (FCoE), or the like.
  • FIG. 3 illustrates an example of schedule information. The schedule information 17 includes a schedule management item 41 and schedule entries 42-1, 42-2, . . . , and 42-n. The schedule entries 42-1, 42-2, . . . , and 42-n may be referred to as the schedule entries 42. The schedule management item 41 may be an item for managing which one of the schedule entries 42 is active.
  • The schedule entries 42 may be information for managing the start time of taking the snapshot and the start time of the copying from the business data storage unit 31 into the replication data storage unit 32. The schedule entries 42 include data items of “entry identification information” 43, a “flag” 44, and a “start time” 45. The “entry identification information” 43 may be information for identifying the schedule entries. The entry identification information on the schedule entry that is currently active is set for the schedule management item 41. The snapshot flag (S), the copy flag (C), or none (N) may be set for the “flag” 44. The start time for the snapshot or the copying may be set for the “start time” 45.
  • FIG. 4 illustrates an example of a system process at a time of the backup. In FIG. 4, solid line arrows indicate backup procedures and broken line arrows indicate a flow data processing performed online. Data 33 directly written from the app 14 via the file system 19 is stored in the business data storage unit 31 of the disk array apparatus 28. Data 34, which is saved temporarily from the app 14 into the cache 22 via the file system 19 and written from the cache 22, is stored in the business data storage unit 31.
  • A snapshot 35 of the file system 19 has been taken before the data is copied by the disk array apparatus 28. The data on the cache 22 has been written onto the physical disk before the data is copied by the disk array apparatus 28. Using the copy function of the disk array apparatus 28, the data and the snapshot stored in the business data storage unit 31 are copied from the business data storage unit 31 into the replication data storage unit 32.
  • In accordance with the schedule 17, the determination unit 16 notifies the control unit 15 of the creation of the snapshot or the timing for writing the data on the cache onto the physical disk. In accordance with the notification from the determination unit 16, the control unit 15 instructs the file system 19 to create the snapshot (S1). Based on the instructions from the control unit 15, the file system 19 creates the snapshot of the file system 19 and outputs the snapshot to the business data storage unit 31 (S2).
  • In accordance with the notification from the determination unit 16, the control unit 15 instructs the cache 22 to write the data on the cache 22 onto the physical disk of the disk array apparatus 28 (S3). The cache 22 writes the data on the cache 22 onto the physical disk, which is the business data storage unit 31 (S4).
  • The control unit 15 instructs the controller 29 to copy the data from the business data storage unit 31 into the replication data storage unit 32 (S5). The controller 29 instructs the copy unit 30 to copy the data and the snapshot, which are stored in the business data storage unit 31, from the business data storage unit 31 into the replication data storage unit 32 (S6). The copy unit 30 copies the data 33, the data 34, and the snapshot 35, which are stored in the business data storage unit 31, from the business data storage unit 31 into the replication data storage unit 32 (S7).
  • The control unit 15 takes the snapshot for the target data to be backed up on the disk array apparatus 28, which is managed in the file system 19. Thus, an image of the file system at a desired timing may be taken online without stopping the I/O.
  • The file system 19 writes the data on the cache 22 onto the physical disk and writes all the data that the file system 19 is instructed to write onto the physical disk. Even when the copying is performed by the disk array apparatus 28, the backup may be performed online without stopping the I/O by combining the writing process and the copy function of the disk array apparatus.
  • FIG. 5 illustrates an example of a system process at a time of restoration. In FIG. 5, solid line arrows indicate the restoration procedures. In FIG. 5, among one or more sets of the data and the snapshot, one of the sets of the data and the snapshot is copied from the replication data storage unit 32 into the business data storage unit 31 by using the copy function of the disk array apparatus 28 is used. The server 12 mounts the data and the snapshot copied into the business data storage unit 31. Because of the mounting, the consistency of the data may fail to be maintained and the state may fail to return to the state at the time of taking the snapshot. Thus, the state returns to the state at the time of taking the snapshot by performing the rollback on the snapshot. In connection with the snapshot, for example, guaranteed data may be restored using the characteristics that ensure the consistency of the data at the time of taking the snapshot under a ZFS snapshot command and the rollback function of the ZFS. When the snapshot is included in the restored data, the process illustrated in FIG. 5 may be performed.
  • The replication data storage unit 32 may store one or more sets of the data 33 and 34 and the snapshot 35. The control unit 15 instructs the controller 29 to copy one of the sets of the data 33 and 34 and the snapshot 35 from the replication data storage unit 32 into the business data storage unit 31 (S11). The controller 29 instructs the copy unit 30 to copy a designated set of the data 33 and 34 and the snapshot 35 from the replication data storage unit 32 into the business data storage unit 31 (S12). The copy unit 30 copies the designated set of the data 33 and 34 and the snapshot 35 from the replication data storage unit 32 into the business data storage unit 31 (S13).
  • The control unit 15 instructs the OS 18 to recognize the data 33 and 34 and the snapshot 35 copied into the business data storage unit 31 as a file system (S14). The OS 18 recognizes the data 33 and 34 and the snapshot 35 stored in the business data storage unit 31 as the file system 19 (S15).
  • The control unit 15 instructs the file system 19 to perform the rollback (S16). In accordance with the instructions from the control unit 15, the file system 19 performs the rollback based on the data 33 and 34 and the snapshot 35 (S17).
  • At the time of the restoration, guaranteed data may be restored by performing the rollback based on the data and the snapshot after the backup data has been copied by the copy function of the disk array apparatus 28. The backup restoration may be performed by the copy function of the disk array apparatus 28 without using a server resource, such as the CPU. FIG. 6 illustrates an example of a backup restoration process. The business data is backed up (S21). When an business abnormality is detected, detection of an abnormality of the business data is performed. When the abnormality of the business data is detected, the business data is restored (S22). The detection of the business abnormality and the abnormality of the business data may be taken into the control unit 15.
  • FIG. 7 illustrates an example of a process of a control unit. The process illustrated in FIG. 7 may correspond to the process performed by the control unit in operation S21 illustrated in FIG. 6. FIG. 8 illustrates an example of a process of a file system. The process illustrated in FIG. 8 may correspond to the process performed by the file system in operation S21 illustrated in FIG. 6. FIG. 9 illustrates an example of a process of an OS. The process illustrated in FIG. 9 may correspond to the process performed by the OS in operation S21 illustrated in FIG. 6. FIG. 10 illustrates an example of a process of a controller. The process illustrated in FIG. 10 may correspond to the process performed by the controller in operation S21 illustrated in FIG. 6. FIG. 11 illustrates an example of a process of a copy unit. The process illustrated in FIG. 11 may correspond to the process performed by the copy unit in operation S21 illustrated in FIG. 6.
  • In FIG. 7, the determination unit 16 of the control unit 15 reads the entry identification information set for the schedule management item 41 of the schedule information 17 stored in the storage device, and reads the schedule entry 42 corresponding to the entry identification information. The determination unit 16 determines whether the snapshot flag is on in the “flag” 44 included in the read schedule entry 42 (S31). When the snapshot flag is on (“Yes” in S31), the determination unit 16 determines a timing for creating a snapshot in accordance with the “start time” 45 included in the read schedule entry 42. When it is determined that the start time has arrived by comparing the “start time” 45 with a current time, the determination unit 16 notifies the control unit 15 of the timing for creating the snapshot.
  • In accordance with the notification from the determination unit 16, the control unit 15 instructs the file system 19 having no I/O stop function to create the snapshot (S32). For example, as illustrated in FIG. 8, the file system 19 having no I/O stop function creates the snapshot and the OS 18 outputs the snapshot to the business data storage unit 31 (S41). When the creation of the snapshot is completed, the file system 19 notifies the control unit 15 of the completion of the creation of the snapshot.
  • Since the data on the file system 19 may remain on the cache 22, the process described next is performed in the control unit 15 after the completion of the creation of the snapshot (“Yes” in S33). For example, the determination unit 16 determines whether the copy flag in the “flag” 44 included in the read schedule entry 42 is on or not (S34). When the copy flag is on (“Yes” in S34), the determination unit 16 determines a timing for writing the data on the cache 22 onto the physical disk in accordance with the “start time” 45 included in the read schedule entry 42. When it is determined that the start time has arrived by comparing the “start time” 45 with the current time, the determination unit 16 notifies the control unit 15 of the timing for writing the data on the cache 22 onto the physical disk.
  • In accordance with the notification from the determination unit 16, the control unit 15 instructs the OS 18 to write the data on the cache 22 onto the physical disk (S35). For example, as illustrated in FIG. 9, the OS 18 performs the process of writing the data on the cache 22 onto the physical disk (S51). All the data on the cache 22 may be written out.
  • When the writing from the cache is completed (“Yes” in S36), the control unit 15 instructs the controller 29 of the disk array apparatus 28 to copy the information stored in the business data storage unit 31 into the replication data storage unit 32 (S37). As illustrated in FIG. 10, the controller 29 instructs the copy unit 30 to copy the data including the data written from the cache 22 and the snapshot, which are stored in the business data storage unit 31, into the replication data storage unit 32 (S61). As illustrated in FIG. 11, the copy unit 30 of the disk array apparatus 28 copies the data including the data written from the cache 22 and the snapshot, which are stored in the business data storage unit 31, into the replication data storage unit 32 (S71). When the copying is completed, the copy unit 30 notifies the controller 29 of the completion of the copying. The controller 29 notifies the control unit 15 of the completion of the copying (S62). When the control unit 15 receives the notification of the completion of the copying from the controller 29 (“Yes” in S38), the process ends.
  • In the file system having no I/O stop function and the file system having an I/O stop function, the copying may be performed without stopping the I/O.
  • FIG. 12 illustrates an example of a process of a control unit. The process illustrated in FIG. 12 may correspond to the process performed by the control unit in operation S22 illustrated in FIG. 6. FIG. 13 illustrates an example of a process of a controller. The process illustrated in FIG. 13 may correspond to the process performed by the controller in operation S22 illustrated in FIG. 6. FIG. 14 illustrates an example of a process of a copy unit. The process illustrated in FIG. 14 may correspond to the process performed by the copy unit in operation S22 illustrated in FIG. 6. FIG. 15 illustrates an example of a process of an OS. The process illustrated in FIG. 15 may correspond to the process performed by the OS in operation S22 illustrated in FIG. 6. FIG. 16 illustrates an example of a process of a file system. The process illustrated in FIG. 16 may correspond to the process performed by the file system having no I/O stop function in operation S22 illustrated in FIG. 6.
  • In FIG. 12, the control unit 15 instructs the controller 29 of the disk array apparatus 28 to copy the replicated data from the replication data storage unit 32 into the business data storage unit 31 (S81). As illustrated in FIG. 13, the controller 29 of the disk array apparatus 28 instructs the copy unit 30 to copy the replicated data from the replication data storage unit 32 into the business data storage unit 31 (S91). As illustrated in FIG. 14, the copy unit 30 of the disk array apparatus 28 copies the data and the snapshot of the replication data storage unit 32 into the business data storage unit 31 (S101). For example, when the data and the snapshot of a previous day are present on the replication data storage unit 32, the copy unit 30 copies the data and the snapshot into the business data storage unit 31. When the copying is completed, the copy unit 30 notifies the controller 29 of the completion of the copying. When the controller 29 receives the notification of the completion of the copying (“Yes” in S92), the controller 29 notifies the control unit 15 that the controller 29 has received the notification of the completion of the copying.
  • After the disk array apparatus 28 has completed copying the data and the snapshot from the replication data storage unit 32 into the business data storage unit 31 (“Yes” in S82), for example, the control unit 15 instructs the OS 18 to recognize the copied data and snapshot in the disk as the file system 19 (S83). As illustrated in FIG. 15, the OS 18 recognizes the data and the snapshot of the business data storage unit 31 as the file system 19 (S111).
  • After the data and the snapshot of the business data storage unit 31 have been recognized as the file system 19 (“Yes” in S84), for example, the control unit 15 instructs the file system 19 having no I/O stop function to perform the rollback (restoration) based on the data and the snapshot (S85). As illustrated in FIG. 16, the file system 19 having no I/O stop function performs the rollback (restoration) based on the data and the snapshot (S121). When the file system 19 having no I/O stop function completes the rollback based on the data and the snapshot (“Yes” in S86), the process ends.
  • When the data is backed up in the server 12, the backup (online backup), may be performed without stopping any business or application. When the data is backed up in the server 12, the backup may be performed without using a resource of the server 12, such as the CPU. The consistency of the data restored in the server 12 may be secured.
  • All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions, nor does the organization of such examples in the specification relate to a showing of the superiority and inferiority of the invention. Although the embodiments of the present invention have been described in detail, it should be understood that the various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the invention.

Claims (6)

What is claimed is:
1. An information processor coupled to a storage apparatus that stores information, comprising:
a creation unit configured to create a snapshot of a file system that manages first information stored in the storage apparatus and to output the snapshot to the storage apparatus;
a writing unit configured to write second information stored in cache memory onto the storage apparatus after the snapshot has been created; and
a replication instruction unit configured to instruct the storage apparatus to create a replication of the first information stored in the storage apparatus after the second information has been written and the snapshot.
2. The information processor according to claim 1, wherein
the file system does not include a function that stops input and output to the storage apparatus.
3. The information processor according to claim 1, further comprising:
a recognition unit configured to recognize the replication as the file system; and
a rollback execution unit configured to execute rollback based on the snapshot.
4. An information processor coupled to a storage apparatus that stores information, comprising:
a recognition unit configured to recognize a snapshot of a file system and first information managed by the file system as a file system, the first information including second information which is written in a cache memory after the snapshot has been created; and
a rollback execution unit configured to execute rollback based on the snapshot.
5. A backup method, comprising:
creating, by a computer, a snapshot of a file system that manages first information stored in a storage apparatus and output the snapshot to the storage apparatus;
writing second information stored in a cache memory in the storage apparatus after the snapshot has been created; and
instructing the storage apparatus to create a replication of the first information stored in the storage apparatus after the second information has been written and the snapshot.
6. The backup method according to claim 5, further comprising:
recognizing the replication the file system; and
executing a rollback based on the snapshot.
US14/073,259 2012-12-14 2013-11-06 Information processor and backup method Active 2034-06-20 US9430485B2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2012-273115 2012-12-14
JP2012273115A JP6070146B2 (en) 2012-12-14 2012-12-14 Information processing apparatus and backup method

Publications (2)

Publication Number Publication Date
US20140172802A1 true US20140172802A1 (en) 2014-06-19
US9430485B2 US9430485B2 (en) 2016-08-30

Family

ID=50932152

Family Applications (1)

Application Number Title Priority Date Filing Date
US14/073,259 Active 2034-06-20 US9430485B2 (en) 2012-12-14 2013-11-06 Information processor and backup method

Country Status (2)

Country Link
US (1) US9430485B2 (en)
JP (1) JP6070146B2 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150089118A1 (en) * 2013-09-20 2015-03-26 Sandisk Technologies Inc. Methods, systems, and computer readable media for partition and cache restore
US20150347548A1 (en) * 2014-05-30 2015-12-03 Datto, Inc. Management of data replication and storage apparatuses, methods and systems
US20170277456A1 (en) * 2016-03-24 2017-09-28 Fujitsu Limited Apparatus and method to reduce a response time for writing data to redundant storage devices
US9836347B2 (en) 2013-08-09 2017-12-05 Datto, Inc. Apparatuses, methods and systems for determining a virtual machine state
US11163799B2 (en) * 2019-10-29 2021-11-02 Dell Products L.P. Automatic rollback to target for synchronous replication

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090265706A1 (en) * 2008-04-21 2009-10-22 Vmware, Inc. Computing machine migration
US8214367B2 (en) * 2007-02-27 2012-07-03 The Trustees Of Columbia University In The City Of New York Systems, methods, means, and media for recording, searching, and outputting display information
US20140089264A1 (en) * 2012-09-24 2014-03-27 Fusion-Io, Inc. Snapshots for a non-volatile device
US9075755B1 (en) * 2012-03-31 2015-07-07 Emc Corporation Optimizing data less writes for restore operations

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3726559B2 (en) * 1999-06-01 2005-12-14 株式会社日立製作所 Direct backup method and storage system
US7165145B2 (en) * 2003-07-02 2007-01-16 Falconstor Software, Inc. System and method to protect data stored in a storage system
JP4321705B2 (en) * 2003-07-29 2009-08-26 株式会社日立製作所 Apparatus and storage system for controlling acquisition of snapshot
JP4454342B2 (en) 2004-03-02 2010-04-21 株式会社日立製作所 Storage system and storage system control method
JP2005292865A (en) 2004-03-31 2005-10-20 Hitachi Ltd Storage system and backup method for storage system
JP2005332067A (en) 2004-05-18 2005-12-02 Hitachi Ltd Backup acquisition method and disk array device
JP2011165069A (en) * 2010-02-12 2011-08-25 Fujitsu Ltd Information storage device
US20110282843A1 (en) * 2010-05-17 2011-11-17 Computer Associates Think, Inc. Method and system for data backup and replication
WO2012164617A1 (en) * 2011-05-31 2012-12-06 Hitachi, Ltd. Data management method for nas

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8214367B2 (en) * 2007-02-27 2012-07-03 The Trustees Of Columbia University In The City Of New York Systems, methods, means, and media for recording, searching, and outputting display information
US20090265706A1 (en) * 2008-04-21 2009-10-22 Vmware, Inc. Computing machine migration
US9075755B1 (en) * 2012-03-31 2015-07-07 Emc Corporation Optimizing data less writes for restore operations
US20140089264A1 (en) * 2012-09-24 2014-03-27 Fusion-Io, Inc. Snapshots for a non-volatile device

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9836347B2 (en) 2013-08-09 2017-12-05 Datto, Inc. Apparatuses, methods and systems for determining a virtual machine state
US10705939B2 (en) 2013-08-09 2020-07-07 Datto, Inc. Apparatuses, methods and systems for determining a virtual machine state
US20150089118A1 (en) * 2013-09-20 2015-03-26 Sandisk Technologies Inc. Methods, systems, and computer readable media for partition and cache restore
US20150347548A1 (en) * 2014-05-30 2015-12-03 Datto, Inc. Management of data replication and storage apparatuses, methods and systems
US9594636B2 (en) * 2014-05-30 2017-03-14 Datto, Inc. Management of data replication and storage apparatuses, methods and systems
US10055424B2 (en) 2014-05-30 2018-08-21 Datto, Inc. Management of data replication and storage apparatuses, methods and systems
US10515057B2 (en) 2014-05-30 2019-12-24 Datto, Inc. Management of data replication and storage apparatuses, methods and systems
US20170277456A1 (en) * 2016-03-24 2017-09-28 Fujitsu Limited Apparatus and method to reduce a response time for writing data to redundant storage devices
US10108360B2 (en) * 2016-03-24 2018-10-23 Fujitsu Limited Apparatus and method to reduce a response time for writing data to redundant storage devices by detecting completion of data-writing to at least one driver before elapse of a retry-over time
US11163799B2 (en) * 2019-10-29 2021-11-02 Dell Products L.P. Automatic rollback to target for synchronous replication

Also Published As

Publication number Publication date
JP2014119851A (en) 2014-06-30
JP6070146B2 (en) 2017-02-01
US9430485B2 (en) 2016-08-30

Similar Documents

Publication Publication Date Title
US8689047B2 (en) Virtual disk replication using log files
JP6050342B2 (en) Managing replicated virtual storage at the recovery site
US10360110B2 (en) Point-in-time backups of a production application made accessible over fibre channel and/or iSCSI as data sources to a remote application by representing the backups as pseudo-disks operating apart from the production application and its host
US8407435B2 (en) Efficiently creating a snapshot of a large consistency group using multiple commands including a snapshot preparation command
US9135119B1 (en) System and method for data management
US8874508B1 (en) Systems and methods for enabling database disaster recovery using replicated volumes
US11249858B2 (en) Point-in-time backups of a production application made accessible over fibre channel and/or ISCSI as data sources to a remote application by representing the backups as pseudo-disks operating apart from the production application and its host
US9165012B2 (en) Periodic file system checkpoint manager
AU2012273366A1 (en) Managing replicated virtual storage at recovery sites
US9430485B2 (en) Information processor and backup method
US20120084260A1 (en) Log-shipping data replication with early log record fetching
JP6133396B2 (en) Computer system, server, and data management method
US8677088B1 (en) Systems and methods for recovering primary sites after failovers to remote secondary sites
US8429125B2 (en) Conversion of physical computers to virtualized environments method and system
US11226875B2 (en) System halt event recovery
US10013188B2 (en) Storage control device and method of copying data in failover in storage cluster
US8275743B1 (en) Method and apparatus for securing data volumes to a remote computer using journal volumes
US9952805B2 (en) Storage system and data write method using a logical volume to either store data successfully onto a first memory or send a failure response to a server computer if the storage attempt fails
NZ714756B2 (en) Managing replicated virtual storage at recovery sites
NZ619304B2 (en) Managing replicated virtual storage at recovery sites

Legal Events

Date Code Title Description
AS Assignment

Owner name: FUJITSU LIMITED, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KATO, NORIHITO;TAKANO, NOBUHIRO;IMAMURA, NORICHIKA;SIGNING DATES FROM 20131015 TO 20131024;REEL/FRAME:031701/0858

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY