System for managing access and storage of worm files without sending parameters for associated file access
First Claim
1. A storage system, comprising:
- a client that issues a file write request or a file read request;
an archive server that is connected to the client via a network, and processes the request issued from the client;
a storage device that is connected to the archive server, and records files; and
a disk drive connected to the client, wherein;
the client comprises at least one client process and an archive client library;
the client process sends a first file read request containing at least one of a first file identifier and a combination of a first file name and an archived date to the archive server;
the archive server;
when the archive server receives the first file read request sent from the client process, referring to a file information table stored beforehand in the archive server, identifies the first file, based on the at least one of the file identifier and the combination of the first file name and the archived date contained in the first file read request,obtains the identified first file from the storage device, andsends the obtained first file to the client process;
the archive client library;
extracts a file archived date from the first file sent from the archive server, obtains a process identifier of the client process that requested the first file;
stores in the disk drive a combination of the extracted archived date and the obtained process identifier, in an archived date management table for processes;
when the archive client library receives a second file read request containing a second file name of a second file relating to the first file obtained from the archive server, obtains an archived date stored in the archived date management table for processes,appends the obtained archived date to the second file read request, andsends the second file read request to the archive server; and
the archive server;
when the archive server receives the second file read request sent from the client process, obtains the second file name and the archived date from the second file read request,identifies a latest archived file having the obtained second file name that was recorded before the obtained archived date, from among the files recorded in the storage device,referring the file information table recorded in the archive server, obtains the identified second file from the storage device, andsends the obtained second file to the client process.
1 Assignment
0 Petitions
Accused Products
Abstract
To provide a storage system and a file management device which enable obtaining a file, without designating detailed information. A client is provided with a read request module that sends a file read request containing information corresponding to a file name and an archived date of the file. A WORM archive server is provided with a file identifying module that extracts information corresponding to the file archived date and the file name from the file read request that was received from the client, and identifies the latest archived file with the file name registered before the archived date corresponding to the extracted information from among files recorded in a storage device, and a file sending module that sends the identified data to the client that sent the request.
-
Citations
7 Claims
-
1. A storage system, comprising:
-
a client that issues a file write request or a file read request; an archive server that is connected to the client via a network, and processes the request issued from the client; a storage device that is connected to the archive server, and records files; and a disk drive connected to the client, wherein; the client comprises at least one client process and an archive client library; the client process sends a first file read request containing at least one of a first file identifier and a combination of a first file name and an archived date to the archive server; the archive server; when the archive server receives the first file read request sent from the client process, referring to a file information table stored beforehand in the archive server, identifies the first file, based on the at least one of the file identifier and the combination of the first file name and the archived date contained in the first file read request, obtains the identified first file from the storage device, and sends the obtained first file to the client process; the archive client library; extracts a file archived date from the first file sent from the archive server, obtains a process identifier of the client process that requested the first file; stores in the disk drive a combination of the extracted archived date and the obtained process identifier, in an archived date management table for processes; when the archive client library receives a second file read request containing a second file name of a second file relating to the first file obtained from the archive server, obtains an archived date stored in the archived date management table for processes, appends the obtained archived date to the second file read request, and sends the second file read request to the archive server; and the archive server; when the archive server receives the second file read request sent from the client process, obtains the second file name and the archived date from the second file read request, identifies a latest archived file having the obtained second file name that was recorded before the obtained archived date, from among the files recorded in the storage device, referring the file information table recorded in the archive server, obtains the identified second file from the storage device, and sends the obtained second file to the client process.
-
-
2. A storage system, comprising:
-
a client that issues a file write request or a file read request; an archive server that is connected to the client via a network, and processes the request issued from the client; a storage device that is connected to the archive server, and records files; and a disk drive connected to the client, wherein; the client comprises at least one client process and an archive client library; the client process sends a first file read request containing at least one of a first file identifier and a combination of a first file name and an archived date to the archive server; the archive server; when the archive server receives the first file read request sent from the client process, referring to a file information table stored beforehand in the archive server, identifies the first file requested in the file read request, based on the at least one of the first file identifier and the combination of the first file name and the archived date contained in the first file read request, stores a combination of an archived date of the identified first file, and a connection identifier contained in the first file read request from the client process, in an archived date management table for processes, obtains the identified first file from the storage device, and sends the obtained first file to the client process; the client process; sends to the archive server a second file read request containing a second file name of a second file associated with the first file obtained from the archive server; and the archive server; when the archive server receives the second file read request sent from the client process, obtains the second file name contained in the second file read request and the connection identifier of the first file read request; obtains the archived date that corresponds to the obtained connection identifier that is stored in the archived date management table for processes, appends the obtained archived date to the received second file read request, identifies a latest archived file having the obtained second file name that file was recorded before the appended archived date, from among the files stored in the storage device, refers to the file information table stored in the archive server, obtains the identified second file from the storage device, and sends the obtained second file to the client process.
-
-
3. A storage system, comprising:
-
a client that issues a file write request or a file read request; a file management device that is connected to the client and processes the request issued from the client; and a storage device that is connected to the file management device, and records files, wherein; the client comprises a read request module that sends, to the file management device, a first file read request containing at least one of a first file identifier and a combination of a first file name and an archived date and that sends, to the file management device after a first response of the first file read request from the file management device, a second file request containing a second file name and information corresponding to an archived date of the first file; a disk module that stored a combination of an archived date of a first file obtained before the process sent the second file read request and a process identifier, in an archived date management table for processes; and an archived date appending module that appends, to the second file read request, the archived date of the first file corresponding to the identifier of the process that sent the first file read request, and the file management device comprises; a file identifying module that identifies the first file based on the at least one of the file identifier and the combination of the first file name and the archived date contained in the first file read request, when the first file read request is received, that obtains the identified first file from the storage device, that, when the second file read request is received, extracts the information corresponding to the first file archived date and the second file name from the second file read request received from the client, and identifies a latest archived file recorded before the archived date indicated in the extracted information from among the files recorded in the storage device; and a file sending module that sends the obtained first or second file to the client that sent the first or second request. - View Dependent Claims (4, 5, 6, 7)
-
Specification