JP2021179732A - Security system, host system, and backup method - Google Patents

Abstract

To allow for securing backup data of the maximum number of generations to be held even when backup data is locked.SOLUTION: When inhibition of overwriting one or more storage regions 51 is locked, a backup server 14 prepares a new backup management table 504, and stores backup data of the maximum number of generations to be held in a storage system 11 using the backup management table 504 and an archive management table 503, which is the past backup management table 504.SELECTED DRAWING: Figure 1

Description

The present disclosure relates to security systems, higher-level systems and backup methods.

Some storage systems back up data to a given storage area independently of the host that controls the reading and writing of the data. In this type of storage system, a storage area for the maximum number of retention generations is secured in advance, and backup data is sequentially stored in the storage area to retain backup data for the maximum number of retention generations. At this time, backup data older than the backup data for the maximum number of retained generations is deleted.

In addition, the above storage system locks the backup data that may be contaminated when an incident that causes data contamination occurs, and restores (restores) the data based on the backup data of the generation before the contamination. I have something to do.

In the above storage system, the locked backup data may be contaminated and therefore cannot function as backup data and is not counted in the number of backup generations. Also, locked backup data may be retained for extended periods of time (eg, months or longer) for forensic investigations. Therefore, there is a problem that the storage area secured in advance is occupied by the data that cannot function as the backup data, and the backup data for the maximum number of retained generations cannot be secured.

An object of the present disclosure is to provide a security system, a higher-level system, and a backup method capable of securing backup data for the maximum number of retained generations even when the backup data is locked.

A security system according to one aspect of the present disclosure is a security system having a storage system capable of storing backup data of a plurality of generations and a higher-level system for controlling the storage system, and the higher-level system is the storage system. When the memory that stores the management information that manages the storage area that stores the backup data for the maximum number of generations and the lock that prohibits overwriting of one or more storage areas are performed, the new management information is newly added. A control unit that stores backup data for the maximum number of retained generations in the storage system using the new management information prepared as management information and the old management information that is the management information stored in the memory. , Have.

According to the present invention, even if the backup data is locked, it is possible to secure the backup data for the maximum number of retained generations.

It is a figure which shows one situation of the security system of 1st Embodiment of this invention. It is a figure which shows the security system of 1st Embodiment of this invention in other situations. It is a figure which shows the security system of 1st Embodiment of this invention in other situations. It is a figure which shows the structural example of the security system of 1st Embodiment of this invention. It is a figure which shows an example of the confirmation result table. It is a figure which shows an example of the integrated management setting file. It is a figure which shows an example of an archive management table. It is a figure which shows an example of the backup management table. It is a figure which shows an example of an archive setting table. It is a figure which shows an example of a backup setting table. It is a flowchart for demonstrating an example of preprocessing by a backup server. It is a flowchart for demonstrating an example of preprocessing by a backup server. It is a flowchart for demonstrating an example of the backup process by a backup server. It is a flowchart for demonstrating an example of the backup process by a backup server. It is a flowchart for demonstrating an example of the backup process by a backup server. It is a figure which shows the structural example of the security system of another embodiment of this invention.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

In the following description, the process may be described with the "program" as the main operating body, but the program is executed by a processor (for example, a CPU (Central Processing Unit)) to perform the specified process. The subject of the process may be a processor because it is performed while appropriately using a storage resource (for example, memory) and / or a communication interface device (for example, a port). The process described with the program as the subject may be a process performed by a processor or a computer having the processor.

(First Embodiment)
1 to 3 are views showing a security system according to the first embodiment of the present invention. The security system 1 shown in FIGS. 1 to 3 includes a storage system 11, a business server 12, a verification server 13, and a backup server 14.

The storage system 11 is a system for storing data. The business server 12, the verification server 13, and the backup server 14 are higher-level systems that control the storage system 11. The business server 12 is a device (host) that controls reading and writing of data to and from the storage system 11. The verification server 13 is a device that verifies the data stored in the storage system 11 at a predetermined trigger such as when an incident that causes data contamination occurs. The backup server 14 is a higher-level device that controls backup of data stored in the storage system 11.

The storage system 11 has a business volume 21, an access volume 22, and a backup environment 23.

The business volume 21 is a logical volume provided to the business server 12 and the backup server 14. The access volume 22 is a logical volume provided to the verification server 13.

The backup environment 23 is an environment for backing up the data stored in the storage system 11. The backup environment 23 is moved to a new environment each time the backup data, which is the backed up data, is locked. In the example of FIGS. 1 to 3, as the backup environment 23, the old environment 31 before the backup data is locked and the new environment 32 after the backup data is locked are shown. Specifically, the lock on the backup data is a process for prohibiting overwriting of the storage area 51 (described later) for storing the backup data. In the present embodiment, data contamination is detected by the verification by the verification server 13. It is done when it is done.

The old environment 31 and the new environment 32 each have a backup image volume 41, a temporary use volume 42, a management volume 43, and a data protection area 44, respectively.

The backup image volume 41 is a logical volume for storing a backup image of data stored in the storage system 11. The backup image is created, for example, by the backup software on the business server 12 side.

The temporary use volume 42 is a logical volume that is temporarily used for backing up the backup image stored in the backup image volume 41 to the data protection area 44.

The management volume 43 is a logical volume that is temporarily used to store the backup management table 504 (described later) in the data protection area 44.

The data protection area 44 is a logical area for storing backup data of the data stored in the storage system 11. In the present embodiment, the data protection area 44 stores a copy (duplicate) of the backup image stored in the backup image volume 41 as backup data. Further, the data protection area 44 stores backup data for the maximum number of retained generations whose creation times differ. The maximum number of retained generations may be, for example, predetermined or may be specified by the user who uses the storage system 11. In the present embodiment, the maximum number of retained generations is 6, but it is not limited to 6.

Specifically, the data protection area 44 has a plurality of storage areas 51 and a storage area 52. The storage area 51 is an area for storing backup data, and one backup data is stored in one storage area 51. The number of storage areas 51 is the same as the maximum number of retained generations. Therefore, in this embodiment, there are six storage areas 51. A copy number, which is identification information for identifying the storage area, is assigned to each storage area 51. In the example of FIG. 1, copy numbers from # 3 to # 8 are assigned to each of the six storage areas 51. The storage area 52 is an area for storing the backup management table 504.

The backup server 14 has a backup management table 504, an archive management table 503, and backup data 507. The backup management table 504 is management information (new management information) for managing the current (latest) backup environment 23 (new environment 32 in the example of FIG. 1). The archive management table 503 is management information (old management information) for managing the past (old) backup environment 23 (old environment 31 in the example of FIG. 1). The backup data 507 is backup data stored in the storage system 11.

In the security system 1 described above, the possibility of data contamination is detected by the verification by the verification server 13, and in the state before the data is restored, the backup data for the maximum number of retained generations is stored in the storage system by the old environment 31. In the state after being stored in 11 and the data is restored, backup data for the maximum number of retained generations is stored in the storage system 11 using both the old environment 31 and the new environment 32.

Backup data of generations after the backup data in which the possibility of data contamination is detected is locked because it may be contaminated. Locked backup data is not counted in the number of generations. Therefore, in the case of a single backup environment as in the past, when a restore occurs, the overwritable storage area 51 becomes smaller than the maximum number of retained generations, so backup data for the maximum number of retained generations should be retained. I can't.

On the other hand, in the security system 1 of the present embodiment, when a restore occurs, the backup image volume 41 to be used is migrated from the old environment 31 to the new environment 32, and the backup data is stored in the storage area 51 of the new environment 32. By doing so, backup data for the maximum number of retention generations is retained. The new environment 32 may be built at the timing when the restoration occurs, or may be built in advance.

In the example of FIG. 1, the backup data of the third generation of the old environment 31 is the target of restoration, and the storage area 51 for storing the backup data of the fourth generation to the sixth generation thereafter is locked. In this case, the backup data from the 7th generation to the 9th generation generated after being locked is stored in the storage area 51 of the new environment 32 so that the backup data for the maximum number of retained generations is stored.

After that, as shown in FIG. 2, the backup images of the 10th to 12th generations are sequentially backed up in the storage area 51 of the new environment 32. In the present embodiment, since the maximum number of retained generations is 6, each time the backup data of the 10th to 12th generations is backed up, it is deleted from the first generation, which is the oldest generation.

Then, as shown in FIG. 3, the 13th generation backup data is overwritten in the storage area 51 storing the oldest 7th generation backup data in the new environment 32. Therefore, after that, the old environment 31 is not used, and the backup data is stored for the maximum number of retained generations only in the new environment 32.

FIG. 4 is a diagram showing a specific configuration of the security system 1 according to the first embodiment of the present invention. As shown in FIG. 4, in the security system 1, the storage system 11, the business server 12, the verification server 13, and the backup server 14 are connected to each other via the network 15.

The storage system 11 has a storage device 111 and a controller 112.

The storage device 111 stores data, a backup image based on the data, backup data which is a copy of the backup image, and the like. There are a plurality of storage devices 111, and the plurality of storage devices 111 may form a logical group 114 corresponding to one logical volume 113. Further, there may be a plurality of logical groups 114. The controller 112 controls reading and writing data to and from the storage device 111.

The business server 12 has a virtualization control unit 121 and a plurality of virtual machines (VMs) 122. The virtualization control unit 121 controls the virtual machine 122. The virtual machine 122 reads and writes data to and from the storage device 111 via the controller 112 of the storage system 11. The business server 12 may read / write data to / from the storage system 11 without constructing the virtual machine 122.

The backup server 14 has a CPU 141, a UI (User Interface) 142, an IF (Interface) 143, and a memory 144.

The CPU 141 is a control unit that reads a program 401 recorded in the memory 144 and executes the read program 401 to realize various functions. The UI 142 inputs and outputs information to and from the user who uses the backup server 14. The IF 403 inputs / outputs information to / from the storage system 11 via the network 15.

The memory 144 is a recording medium for storing the program 401 that defines the operation of the CPU 141 and the data 402 used in the processing performed by the CPU 141.

The program 401 includes a backup acquisition program 411 and a data protection area management program 412. The backup acquisition program 411 is a program for acquiring backup data which is a copy of the backup image stored in the storage system 11. The data protection area management program 412 is a program for managing the backup environment 23 of the storage system 11, particularly the data protection area 44.

The usage data 402 includes a confirmation result table 501, an integrated management setting file 502, an archive management table 503, a backup management table 504, an archive setting table 505, a backup setting table 506, and backup data 507.

FIG. 5 is a diagram showing an example of the confirmation result table 501. The confirmation result table 501 is information showing the verification result of the verification of data contamination on the backup data by the verification server 13, and includes the fields 511 to 513.

The field 511 stores a backup image ID which is identification information for identifying the backup data. The field 512 stores the backup date and time, which is the date and time when the backup data was backed up (date and time stored in the protected area 44). Field 513 stores the verification result. The verification result indicates, for example, an "infection" indicating that the possibility of data contamination has been detected, and a "restoration candidate" indicating that the data is a target for restoration. In addition, the verification result may indicate "non-infection" indicating that the possibility of data contamination has not been detected.

FIG. 6 is a diagram showing an example of the integrated management setting file 502. The integrated management setting file 502 is information for managing backup data, and includes items 521 to 525.

Item 521 indicates a policy name that identifies a user policy set by a user who uses the storage system 11. The user policy defines, for example, the maximum retention generation and the backup interval. Although the user policy is not shown, it is recorded in the memory 144, for example.

Item 522 shows a backup management table 504 that manages the current (latest) backup environment. Item 523 indicates the data protection area 44 managed in the current backup environment. Item 524 shows the archive management table 503 that manages the past backup environment. Item 525 indicates a data protection area 44 managed in the past backup environment.

FIG. 6A shows an example of the integrated management setting file 502 before the restoration is performed. In the example of FIG. 6A, items 524 and 525 are empty because there is no backup environment in the past. Further, the item 522 indicates the “management table (1)” as the backup management table 504, and the item 523 indicates the “data protection area (1)” as the data protection area 44.

FIG. 6B shows an example of the integrated management setting file 502 after the restoration is performed once. In the example of FIG. 6B, item 524 indicates the "management table (1)" shown in item 522 (item 522 of FIG. 6A) before the restore was performed, and item 525 is The "data protection area (1)" shown in the item 523 (item 523 of FIG. 6A) before the restoration is performed is shown. Further, in item 522, a new "management table (2)" is shown as the backup management table 504, and in item 523, a new "data protection area (2)" is shown as the data protection area 44.

FIG. 6C shows an example of the integrated management setting file 502 after the restoration is performed twice.
In the example of FIG. 6 (c), item 524 is the "management table (1)" shown in items 522 and 524 (items 522 and 524 of FIG. 6 (b)) before the second restore was performed. And "management table (2)", item 525 is the "data protection area (1)" shown in item 523 (items 523 and 524 in FIG. 6B) before the second restore was performed. "And" data protection area (2) ". Further, in item 522, a new "management table (3)" is shown as the backup management table 504, and in item 523, a new "data protection area (3)" is shown as the data protection area 44.

As shown in FIG. 6, there is always one backup management table 504 regardless of whether or not there is a restore, and the archive management table 503 is newly added each time a restore is performed.

FIG. 7 is a diagram showing an example of the archive management table 503. FIG. 7 shows the archive management table 503 in the situation shown in FIG. Archive management table 503 includes fields 531 to 536.

Field 531 stores a backup image generation, which is a backup generation of backup data. Field 532 stores the backup image ID. Field 533 stores the backup date and time. Field 534 stores the copy number of the storage area 51 that stores the backup data. The field 535 stores the locked state of the storage area 51. The locked state indicates "True" when the storage area 51 is locked, and indicates "False" when the storage area 51 is not locked. Field 536 stores the restore date and time when the restore was performed. In the present embodiment, the restore date and time are stored in the backup management table 504 that manages the backup environment after the restore when the restore is performed, so that the field 536 is empty in FIG. 7.

FIG. 8 is a diagram showing an example of the backup management table 504. FIG. 8 shows the backup management table 504 in the situation shown in FIG. The backup management table 504 includes fields 541-546.

Field 541 stores the backup image generation. Field 542 stores the backup image ID. Field 543 stores the backup date and time. Field 544 stores the copy number. Field 545 stores the locked state of the storage area 51. Field 546 stores the restore date and time when the restore was performed.

The copy number, lock state, and restore date / time are stored in advance for all records when the backup management table 504 is prepared.

FIG. 9 is a diagram showing an example of the archive setting table 505. The archive setting table 505 is information indicating settings related to backup in the past backup environment, and includes fields 551 to 553.

Field 551 stores a setting number that identifies the setting for backup. Field 552 stores the maximum number of retained generations as a backup setting. Field 553 stores a backup policy for backing up as a backup setting. In the present embodiment, the backup policy includes "policy A" corresponding to "setting 1" and "policy B" corresponding to "setting 2".

"Policy A" indicates that the data is backed up (stores the backup data) in the data protection area 44 of the current backup environment when both the following conditions 1 and 2 are satisfied.
Condition 1. A new backup image is created (the backup image is newly stored in the backup image volume 41).
Condition 2. The number of generations of the backup image stored in the backup image volume 41 has reached the specified number. The specified number is specified by the backup software on the business server 12 side.

The "policy B" deletes the unlocked data, which is the backup data stored in the data protection area 44 of the past backup environment and is not locked, when the following condition 3 is satisfied.
Condition 3. The total number of generations of unlocked data stored in the data protection area 44 of the past backup environment and the number of generations of backup data stored in the data protection area 44 of the current backup environment is the maximum number of retained generations. Over.

FIG. 10 is a diagram showing an example of the backup setting table 506. The backup setting table 506 has the same information as the archive setting table 505.

11 to 15 are flowcharts for explaining an example of processing by the backup server 14. Specifically, FIGS. 11 and 12 are flowcharts for explaining preprocessing for performing (restarting) backup processing, and FIGS. 13 to 15 are flowcharts for explaining an example of backup processing. Is. The backup process is performed, for example, during the operation of the storage system 11.

In the preprocessing, first, the data protection area management program 412 acquires information indicating each of the archive management tables 503 from the integrated management setting file 502 as configuration information, and obtains the configuration information in a predetermined memory area (Archive_Tables_Config) of the memory 144. ) (Step S101).

The data protection area management program 412 acquires the backup image ID and the backup date and time of the backup data of the restore candidate from the confirmation result table 501 (step S102).

The data protection area management program 412 determines whether or not the memory area (Archive_Tables_Config) is empty (step S103).

If the memory area (Archive_Tables_Config) is not empty, the data protection area management program 412 acquires any of the configuration information stored in the memory area (Archive_Tables_Config) as the target configuration information, and the archive management table 503 indicated by the target configuration information. Is specified as the target archive management table 503 (step S104). For example, the data protection area management program 412 acquires the configuration information having the smallest index (not shown) that identifies the configuration information.

The data protection area management program 412 confirms the backup date and time of each backup image generation in the target archive management table 503, and identifies the backup image generation with a backup date and time newer than the backup date and time of the restore candidate as the post-contamination generation. (Step S105).

The data protection area management program 412 determines whether or not there is one or more post-contamination generations (step S106).

When the post-contamination generation exists, the data protection area management program 412 determines that the archive management table 503 needs to be updated, and sets the lock state of the backup data of the post-contamination generation in the target archive management table 503 to "True". Is set to, and the lock state of another backup data generation is set to "False" (step S107).

The data protection area management program 412 emptys all the restore dates and times in the target archive management table 503 (step S108).

The data protection area management program 412 deletes the target configuration information from the memory area (Archive_Tables_Config) (step S109), and returns to the process of step S103.

If there is no post-contamination generation in step S106 in the above process, the data protection area management program 412 skips the process of steps S107 and S108.

Further, in step S103, when the memory area (Archive_Tables_Config) is empty, the data protection area management program 412 determines whether or not restoration based on the backup data of the restore candidate is necessary (step S110 in FIG. 12).

For example, when verification is performed by the verification server 13 and a possibility of data contamination occurs, the data protection area management program 412 determines that restoration based on the backup data of the restoration candidate is necessary. Even if it is initially detected that there is no possibility of data contamination, the possibility of data contamination may be detected as a result of detailed verification thereafter. Even in this case, the restore is performed. In addition, as a result of detailed verification, the restore target may be replaced with a newer generation backup image. Again, the list is based on the new restore target.

If restoration is not required, the data protection area management program 412 ends the process. On the other hand, when a restore is required, the data protection area management program 412 performs a restore based on the backup data of the restore candidate, and acquires the restore date and time when the restore was performed as the performed restore date and time (step S111).

The data protection area management program 412 acquires the information indicating the backup management table 504 from the integrated management setting file 502 as the current configuration information, and stores the current configuration information in a predetermined memory area (Backup_Tables_Config) of the memory 144 (step S112). ).

The data protection area management program 412 acquires the current configuration information stored in the memory area (Backup_Tables_Config) and specifies the backup management table 504 indicated by the current configuration information (step S113).

The data protection area management program 412 sets the executed restore date and time for each restore date and time of the specified backup management table 504 (step S114), and ends the preprocessing.

Next, an example of the backup process will be described with reference to FIGS. 13 to 15.

First, the backup acquisition program 411 acquires information (records) of a generation whose backup date and time is older than the restore date and time as old generation information from the backup management table 504, and temporarily stores the information (record) in a predetermined memory area (New_Fort_Invalid) of the memory 144. (Step S201 in FIG. 13).

The backup acquisition program 411 acquires information on generations whose backup date and time is after the restore date and time as new generation information from the backup management table 504, and temporarily stores the information in a predetermined memory area (New_Fort_Valid) of the memory 144 (step S202).

The backup acquisition program 411 calculates the sum of the number of generations of backup data included in the old generation information and the number of generations of backup data included in the new generation information as the number of current generations (step S203).

The backup acquisition program 411 compares the number of current generations with the maximum number of retained generations and determines whether or not the number of current generations is less than the maximum number of retained generations (step S204).

If the number of current generations is less than the maximum number of retained generations, the backup acquisition program 411 selects the smallest copy number among the unused storage area copy numbers in the backup management table 504, and the storage area corresponding to the selected copy number. Is specified as the next storage area for storing the next backup data (step S205).

When the number of current generations is equal to or greater than the maximum number of retained generations, the backup acquisition program 411 selects the copy number with the oldest backup date and time in the backup management table 504, and designates the storage area corresponding to the selected copy number as the next storage area (. Step S206).

After that, the backup acquisition program 411 confirms the backup image volume 41 in the current backup environment (step S207), and determines whether or not there are more than the specified number of backup images (step S208).

If the number of backup images does not exist in excess of the specified number, the backup acquisition program 411 waits for a certain period of time (step S209), and returns to the process of step S207.

On the other hand, when there are more than a specified number of backup images, the backup acquisition program 411 determines whether or not a new backup image has been created and stored in the backup image volume 41 (step S210).

If a new backup image has not been created, the backup acquisition program 411 waits for a certain period of time (step S209), and then returns to the process of step S207.

On the other hand, when a new backup image is created, the backup acquisition program 411 temporarily uses the oldest backup image stored in the backup image volume 41 in the current backup environment in the current backup environment. Copy to volume 42 as backup data. Then, the backup acquisition program 411 acquires the backup image ID and the backup date and time of the copied backup data (step S211).

The backup acquisition program 411 stores the backup image ID and the backup date and time acquired in step S211 in the fields 542 and 543 corresponding to the copy numbers selected in steps S205 or S206 in the backup management table 504 (step S212). .. If the backup data is already stored in the storage area of the selected copy number, that is, if the backup image ID and the backup date and time are already stored in the fields 542 and 543, the backup acquisition program 411 will use the backup image. The backup image ID and backup date / time acquired in step S211 are overwritten with respect to the ID and the backup date / time.

The backup acquisition program 411 copies the backup management table 504 to the management volume 43 in the current backup environment (step S213). The backup acquisition program 411 may copy the portion of the backup management table 504 updated in step S212.

The backup acquisition program 411 stores the image data copied to the temporary use volume 42 in the storage area 51 designated as the next storage area, and stores the backup management table 504 copied to the management volume 43 in the storage area 52 (. Step S214).

After that, the data protection area management program 412 acquires all the backup data copy numbers, backup image IDs, and backup date / time sets of the generation whose lock state is "False" from all archive management tables 503 as old set information, and they are used. The old set information of is temporarily saved in a predetermined memory area (Old_Fort_Valid) of the memory 144 (step S215 in FIG. 15).

The data protection area management program 412 determines whether or not the set information exists in the memory area (Old_Fort_Valid) (step S216).

If the old set information does not exist, the data protection area management program 412 ends the backup process. On the other hand, when the old set information exists, the data protection area management program 412 uses the backup management table 504 as new set information for the backup data copy number, backup image ID, and backup date / time set whose backup date / time is after the restore date / time. It is acquired and the new set information is temporarily stored in a predetermined area (New_Fort_Valid) of the memory 144 (step S217).

The data protection area management program 412 calculates the sum of the number of generations of the old set information stored in the memory area (Old_Fort_Valid) and the number of generations of the new set information stored in the memory area (New_Fort_Valid) (step S218). ..

The data protection area management program 412 compares the total number of generations with the maximum number of retained generations, and determines whether or not the subtraction result obtained by subtracting the maximum number of retained generations from the total number of generations is greater than 0 (step). S219).

If the subtraction result is 0 or less, the data protection area management program 412 ends the backup process. On the other hand, when the subtraction result is larger than 0, the data protection area management program 412 identifies the archive management table 503 having the oldest backup image generation from all the archive management tables 503 (step S220).

The data protection area management program 412 acquires a set of the backup data copy number, backup image ID, and backup date and time of the oldest backup image generation from the specified archive management table 503 as the oldest set information (step S221).

The data protection area management program 412 deletes the backup data corresponding to the oldest set information from the past backup environment, and further deletes the oldest set information from the old set information of the memory area (Old_Fort_Valid) (step S222).

The data protection area management program 412 deletes the backup image generation, the backup image ID, and the backup date and time corresponding to the oldest set information in the specified archive management table 503 (step S223), and returns to the process of step S216.

As described above, according to the present embodiment, the backup server 14 prepares a new backup management table 504 and prepares a new backup management table 504 when a lock that prohibits overwriting is performed on one or more storage areas 51. And the archive management table 503, which is the backup management table 504 in the past, the backup data for the maximum number of retained generations is stored in the storage system 11. Therefore, even if the backup data is locked, it is possible to secure the backup data for the maximum number of retained generations.

Further, according to the present embodiment, each time the backup server 14 creates new backup data, the backup server 14 stores the new backup data in the storage area 51 managed by the backup management table 504. Therefore, the newly generated backup data can be backed up in the new backup environment, which facilitates management.

Further, in the present embodiment, when the number of generations of the stored backup data exceeds the maximum number of retained generations, the backup data of the oldest generation is deleted or overwritten. Therefore, the storage area 51 can be appropriately opened.

Further, in the present embodiment, the backup server 14 generates a copy of the backup image created by the business server 12 in the storage system 11 as backup data. Therefore, the backup data can be generated independently of the business server 12, and the security can be improved.

(Other embodiments)
The security system 1 may perform processing (preprocessing and backup processing) on the storage system 11 via another storage system or storage device.

FIG. 16 is a diagram showing a mode in which the security system 1 performs processing on the storage system 11 via another storage system. The security system 1 shown in FIG. 16 is different from the security system 1 of the first embodiment shown in FIG. 4 in that it newly has a storage system 11B. Further, the security system 1 performs processing on the storage system 11 via the storage system 11B. The storage system 11B may have the same function as the storage system 11.

The embodiments of the present disclosure described above are examples for the purpose of explaining the present disclosure, and the scope of the present disclosure is not intended to be limited only to those embodiments. One of ordinary skill in the art can implement the present disclosure in various other embodiments without departing from the scope of the present disclosure.

1: Security system, 11-11B: Storage system, 12: Business server, 13: Verification server, 14: Backup server, 15: Network, 21 Business volume, 22: Access volume, 31: Old environment, 32 : New environment, 41: Backup image volume, 42: Temporary use volume, 43: Backup management table volume, 44: Data protection area, 51 to 52: Storage area, 111: Storage device, 112: Controller, 113: Logical Volume, 114: Logical group, 141: CPU, 144: Memory

Claims (9)

A security system having a storage system capable of storing backup data of a plurality of generations and an upper system for controlling the storage system.
The host system is
A memory for storing management information for managing the storage area for storing the backup data in the storage system for the maximum number of retained generations, and a memory for storing the management information.
When a lock that prohibits overwriting is performed on one or more of the storage areas, the new management information is prepared as new management information, and the new management information and the old management information stored in the memory are used. A security system having a control unit that stores backup data for the maximum number of retained generations in the storage system using management information. According to claim 1, when the new management information is prepared, the control unit stores the new backup data in the storage area managed by the new management information every time the new backup data is created. The security system described. The control unit is managed by the old management information, and is managed by the number of backup data stored in the unlocked storage area, which is the unlocked storage area, and the new management information. When the number of stored generations, which is the sum of the number of backup data stored in the storage area, exceeds the maximum number of retained generations, the backup data of the oldest generation of the backup data stored in the unlocked storage area is used. The security system according to claim 2, which is to be deleted. When all the backup data stored in the unlocked storage area is deleted, the control unit transfers the new backup data to the backup data stored in the storage area managed by the new management information. The security system according to claim 3, which overwrites the backup data of the oldest generation. The host system includes a host device that verifies the backup data.
The control unit locks the storage area for storing the backup data of the generations after the backup data for which the possibility of data contamination is detected by the verification of the higher-level device, and the backup data of the generation older than the backup data. The security system according to claim 1, wherein the data is restored based on the above. The host system comprises a host device that controls reading and writing of data with respect to the storage system.
The host device creates a backup image of the data and stores it in the storage system.
The security system according to claim 1, wherein the control unit generates a copy of the backup image as the backup data. The security system according to claim 1, wherein the host system controls the storage system via another storage system. A higher-level system that controls a storage system that can store backup data of multiple generations.
A memory for storing management information for managing the storage area for storing the backup data in the storage system for the maximum number of retained generations, and a memory for storing the management information.
When a lock that prohibits overwriting is performed on one or more of the storage areas, the new management information is prepared as new management information, and the new management information and the old management information stored in the memory are used. A host system having a control unit that stores backup data for the maximum number of retained generations in the storage system using management information. It is a backup method by a security system having a storage system capable of storing backup data of a plurality of generations and an upper system that controls the storage system.
The host system stores management information in the memory for managing the storage area for storing the backup data in the storage system for the maximum number of holding generations.
When the host system locks one or more of the storage areas to prohibit overwriting, the new management information is prepared as new management information.
A backup method in which the host system stores backup data for the maximum number of retained generations in the storage system by using the new management information and the old management information which is the management information stored in the memory.

Images