JPH06236308A - Network server - Google Patents

Abstract

PURPOSE:To store a file in a backup storage device which is smaller in storage capacity than a storage device used for filing. CONSTITUTION:Files which are necessary among files sent from respective terminal devices 2a-2n connected through a network 5 are compressed and stored in the backup storage device 4. The files can be stored no the backup storage device 4 which is smaller in storage capacity than any of the storage devices 3a-3m used for filing. File attributes are stored together with the compressed files to easily decide which of likes the storage devices 3a-3m are stored as backup files.

Description

Detailed Description of the Invention

[0001]

This invention relates to a LAN (Local Area N
It is related to the network server connected to the etwork), especially the backup of files.

[0002]

2. Description of the Related Art In recent years, word processors and personal computers have become widespread. Efficient use is achieved by sharing such information, and filing systems that connect these devices via a network server to store and manage information have become widespread. Also, because of the centralized management of information storage, backup and recovery using conventional floppy disks etc. takes time and is not practical, so a large amount of information can be easily backed up to ensure the safety of these information. In addition, as a system that can easily perform recovery when a failure occurs in the storage device used for filing,
A backup system by mirroring has been developed that equips a storage device with the same capacity as the storage device used for filing and stores the same information stored in the storage device used for filing for backup. There is.

[0003]

[Problems to be Solved by the Invention]
Since backup with a ring requires a storage device with the same configuration as the storage device used for filing,
A system using a large-capacity storage device of 1 GB or more requires an expensive storage device of the same capacity. Also,
A system having a plurality of storage devices of 100 Mbytes or 200 Mbytes requires the same number of storage devices of the same capacity, so not only the storage device cost but also the interface part for connecting the storage devices is expensive. It was.

Furthermore, in the conventional mirroring backup system, since all the data sent from each connected terminal device is backed up,
The data already backed up by the floppy disk, tape, etc. has also been backed up, and duplicate backups have occurred.

The present invention has been made in order to solve the above disadvantages, and has an advantage of backup by mirroring which can easily back up and recover a large amount of data, and can be connected via a network. It is an object of the present invention to provide a network server capable of backing up the data sent from each terminal device stored in a storage device having a storage capacity smaller than that of the storage device used for filing.

[0006]

A network server according to the present invention has a compression means and a writing means, and the compression means stores a file sent from another terminal device via the network. The compressing and writing means stores the file compressed by the compressing means in the storage device for backup together with the file attributes.

Further, it is preferable that the writing means does not back up the files set to be excluded from the backup, the files with the extension set to not to be the backup, and the files of the terminal device set to be not the backup.

[0008]

According to the present invention, the file sent from each terminal device connected via the network is compressed and then stored as a backup. Therefore, the backup device has a smaller storage capacity than the storage device used for filing. Files can also be stored in this storage device.

Further, since the file attribute is stored together with the compressed file, it is possible to easily determine which storage device the file was backed up based on the file attribute.

Furthermore, since files that are set as not to be backed up or files with an extension set as not to be backed up are not backed up, files that do not need to be backed up are set not to be backed up for each file or for each file type. it can.

Further, since the files of the terminal device set as the non-backup target are not backed up, it is possible to set not to back up the file for each terminal device.

[0012]

1 is a block diagram showing an embodiment of the present invention. As shown in the figure, the network server 1 is a LAN 5
Is connected to a plurality of terminal devices 2a to 2n through a plurality of filing hard disks 3a to 3m and a backup hard disk 4.

FIG. 2 is a storage area configuration diagram of the backup hard disk 4. As shown in the figure, the backup hard disk 4 is a directory table 4a-4.
m, a file allocation table 41 and a file storage unit 42. Directory table 4a-4
m corresponds to the filing hard disks 3a to 3m, and the corresponding filing hard disks 3a to 3m.
The file name stored in is registered. In the file allocation table 41, the storage locations of the compressed files stored in the filing hard disks 3a to 3m are registered. The file storage unit 42 stores a compressed file for backup.

As shown in FIG. 1, the network server 1
Has a main control unit 6, a compression unit 7, a writing unit 8, a storage unit 9, a network control unit 10 and a hard disk control unit 11.

The main controller 6 controls the entire system.
The compressing means 7 reads the file sent from the terminal devices 2a to 2n connected via the LAN 5 from the storage section 9 according to the command of the writing means 8 and compresses it, and sends it to the writing means 8. Writing means 8
Stores the files sent from the terminal devices 2a to 2n in the storage unit 9
And the read file is written to the hard disks 3a to 3m via the hard disk control unit 11.
The writing means 8 sends the file to be backed up to the compression means 7, and stores the file compressed by the compression means 7 in the file storage section 42 of the backup hard disk 4 via the hard disk control section 11. At the same time, the directory tables 4a to 4m and the file allocation of the backup hard disk 4 set corresponding to the hard disks 3a to 3m used for filing.
The table table 41 is updated to register the file attribute. The storage unit 9 is the terminal device 2 connected via the LAN 5.
The files sent from a to 2n are temporarily stored. The network control unit 10 connects and controls the LAN 5 and receives files and the like sent from the terminal devices 2a to 2n. The hard disk control unit 11 connects and controls the hard disks 3a to 3m and the backup hard disk 4 used for filing, and writes means 8 to the hard disks 3a to 3m, 4. The file is stored by the command.

Next, the operation for transferring and storing a file from the terminal device 2a will be described with reference to the flowchart of FIG.

A terminal device 2 for the network server 1
a issues a connection request and establishes a link (step S
1). At this time, the terminal device 2a is connected to the network server 1.
Is requested to exclude a file with the extension BAK from the backup target. When the file is modified and saved in the editor of the terminal device 2a, B
This is because there is one that saves the uncorrected file with an extension of AK. The backup target exclusion request from the terminal device 2a is stored in the storage unit 9.

It should be noted that the terminal device 2a connects to the network server.
Instead of making a backup exclusion request so that the file with the extension BAK is not backed up to the server 1, manually set the network server 1 not to back up the file with the extension BAK. Is also good.

There is a request from the terminal device 2a to store a file abc to be backed up, for example, the file abc.
Is sent (step S2), the storage unit 9 temporarily stores the file abc. The writing means 8 reads the file abc from the storage unit 9 and stores it in the hard disk 3a for filing, for example, via the hard disk control unit 11. Or file abc in hard disk 3a
If the file a already exists, the writing means 8 writes the file a.
bc is updated (step S3).

Since the file abc is the file to be backed up (step S4), the writing means 8 sends the file abc to the compression means 7. The compression means 7 compresses the sent file abc and then sends the compressed file to the writing means 8 (step S5).

The writing means 8 reads the directory table 4a of the backup hard disk 4 corresponding to the hard disk 3a storing the file abc, and the file name abc is registered in the directory table 4a. If not, the file attributes such as the file name abc are registered in the directory table 4a. After registering the file name abc in the directory table 4a, the writing means 8
Is the file ab in the file allocation table 41.
The storage location of the compressed file of c is registered, and the compressed file is stored in the file storage section 42 of the backup hard disk 4 via the hard disk control section 11 (step S6).

Next, for example, the file abc. There is a request to store BAK, and the file abc. When the BAK is sent (step S2), the writing means 8 writes the file abc. BAK is stored in the hard disk 3a for filing, or the file abc. BAK is updated (step S3).

File abc. Since BAK has the extension BAK set as a backup target,
The process is terminated without storing in the backup hard disk 4 (step S4).

Here, for example, when the terminal device 2n is a non-backup target terminal device, when the link is established, the terminal device 2n instructs that the terminal device 2n is a non-backup target terminal in the same way as setting a file not to be backed up. Alternatively, the network server 1 is manually set not to back up the file from the terminal device 2n.

It is also possible to send a command from the terminal device 2a together with a file to instruct the exclusion of the backup target so that the backup target file is not backed up.

Next, the operation when the hard disk 3a, which is filing the file abc, fails and the file is recovered will be described.

A failure occurs in the hard disk 3a and the hard disk 3a
If the hard disk 3a becomes unreadable, the hard disk 3a is replaced and then the directory table 4a is read. Hard disk 3 storing file abc
Since all the file names stored in the hard disk 3a are registered in the directory table 4a of the backup hard disk 4 corresponding to "a", the directory table of the backup hard disk 4 is stored. The file a stored in the hard disk 3a just by reading the bull 4a
All bc etc. are known. Since the storage location of the compressed file stored as a backup is registered in the file allocation table 41, the file allocation table 41 is opened based on the file name read from the directory table 4a. Check the storage location of the reading file. Based on the confirmed storage location of the file, the file is read from the file storage unit 42 and the file is restored before compression and the file stored in the hard disk 3a is restored.

In the above embodiment, the backup hard disk is used.
Although a plurality of directory tables 4a to 4m of the hard disk 4 are provided, the directory table 4a may be provided with the addresses of the filing hard disks 3a to 3m and the like.

[0029]

As described above, according to the present invention, a file sent from each terminal device connected via a network is compressed and then stored as a backup, so that the storage device used for filing. A large number of files can be stored in a backup storage device with a smaller storage capacity. For example, one backup storage device can back up a plurality of storage devices.
The device configuration can be simplified.

Further, the backup storage device stores the file attributes together with the files and stores them so that all the necessary files can be specified for each filing hard disk.
Recovery can be easily performed when the hard disk or its storage is damaged.

Further, since files not set as the backup target or files with the extension set as the non-target are not backed up, unnecessary files or files that have already been backed up and do not need to be backed up are file-by-file or file-based. It is possible to prevent unnecessary files from being stored in the storage area of the backup storage device by setting the backup not to be performed for each type.

Further, since the file of the terminal device set as the non-backup target is not backed up, it is possible to set not to back up the file for each terminal device when the backup is not necessary depending on the terminal device, which facilitates the setting. can do.

[Brief description of drawings]

FIG. 1 is a block diagram showing an embodiment of the present invention.

FIG. 2 is a storage area configuration diagram of a backup hard disk.

FIG. 3 is a flowchart showing the operation of the above embodiment.

[Explanation of symbols]

 1 Network Server 2a to 2n Terminal Device 3a to 3m Hard Disk 4 Backup Hard Disk 4a to 4m Directory Table 5 LAN 6 Main Control Unit 7 Compressing Means 8 Writing Means 9 Storage Unit 10 Network control unit 11 Hard disk control unit

Claims (3)

[Claims] 1. A network server connected to another terminal device via a network, comprising compression means and writing means, and the compression means is sent from the other terminal device via the network. A network server characterized by compressing a received file and storing the file compressed by the compressing means together with the file attributes in a backup storage device. 2. The network server according to claim 1, wherein the writing means does not store a file set as a non-backup target or a file with an extension set as a non-backup target in a backup storage device. 3. The network server according to claim 1, wherein the writing means does not store the file of the terminal device set as the non-backup target in the backup storage device.
Ba.