JP2002500787A - Distributed mirroring of data volumes in network systems - Google Patents

Abstract

(57) [Summary] Work products are backed up from the workstations (13, 15, 17) on the network to one or more file servers (19), and the work products are backed up from one or more file servers (19). A mirroring system (14) for the network (9) that performs the updating of the changes of the master copy of the working environment to 13, 15, 17). In one embodiment, the mirroring system (14) checks the traffic level of the network and initiates a data transfer if the traffic level is below a predetermined value. Backups and updates are made, a status list (29) is maintained, and the backup and update revision level of each workstation (13, 15, 17) on the network is tracked. In one embodiment, workstations (13, 15, 17) that failed to backup or update are listed and reported.

Description

DETAILED DESCRIPTION OF THE INVENTION Distributed mirroring of data volumes in a network system Technical field to which the invention belongs The present invention relates to computer networks, and more particularly, to an apparatus and method for leveling traffic on a computer network. Background of the Invention One of the most economical tools for managing and controlling the output from a large number of grouped computer users is a computer network. Computer networks typically include a system of workstations (which may be personal computers (PCs)) connected by serial data links. One or more file servers on the network provide a place to store the generated data, as well as a source of application software needed by the user to run. By configuring a network, many users can share data storage hardware, software resources, and peripherals such as printers and facsimile machines. Network deployments have tended to rely increasingly on server capabilities and minimize resident software and hardware at each workstation. This concept allows the administrator to have more control over the work results while reducing the cost factor for individual workstations. Companies such as Sun, Oracle, Microsoft and Intel have introduced workstations called Net PCs into the prior art. Indeed, by storing specific tools and applications for job functions on a server, users can generally be located on the same workstation. At the same time, a storage area is provided on a server on the network to provide a place for storing and temporarily storing data files to workstations on the network. There are many types of network systems available for different topology types and technologies used. Networks are typically created and customized to suit the circumstances in which they are used. Even if the systems are different, their functions are fairly common. That is, data storage, generation, backup, update, and the like are performed economically and efficiently. One of the inherent limitations that must be addressed when operating a computer network is the capacity of the network data link to exchange data between servers, peripherals, and workstations on the network. . This capacity or capability is known as bandwidth. Information about transit on active network tracks is known as network traffic. For example, when a large number of users are simultaneously transmitting and receiving data, a large amount of traffickers are generated. In a typical network environment, there are periods of maximum (peak) usage and periods of light traffic. For example, as many users close applications, store data from a temporary storage location on a workstation to a server, and perform work with peripherals (printing, faxing, etc.), the end of working hours, eg, in the afternoon Around 5 o'clock is the peak traffic period. Other periods, such as lunch time, break time, late night or early morning time, are light traffic periods. Due to the large amount of data that must be identified and processed, system and operator efficiency is affected during peak periods. If the amount of data transferred in a given time period exceeds the network capacity, the function will be delayed. There are improvements in system technology that can partially address the network load problem. For example, burst techniques are used to reduce the number of processes, such as identification, or to speed up the delivery of information packets by simplifying the protocol. Broadband systems, such as optical fiber systems, will be deployed and introduced. A number of servers strategically placed or as mirrors are used as a way to minimize network traffic. Another approach is to increase the memory capacity of individual workstations, typically with cache memory, to eliminate the need for frequent access to network servers. As noted above, while improvements in known systems can reduce network traffic, some of them introduce new problems. For example, providing a cache on a workstation can help reduce network traffic, but if the cache is full of data during a managed boot sector revision, a cache-capable workstation will create a new revision. Cannot receive. Obviously, what is needed is the ability to recognize and use light traffic periods for backup, whether or not a cache is used, while automatically synchronizing and updating application and boot information. Apparatus and method for enabling transparent backup of user files used by users. Summary of the Invention In a preferred embodiment of the present invention, a data mirroring system for a network including one or more workstations and a file server, wherein the workstations are adapted according to changes in work product data stored on the one or more workstations. A backup device for backing up the work product data from the server to the file server, and an update device for mirroring the work environment from the file server to one or more workstations as the master copy of the work environment is changed. System is provided. In some embodiments, one or both of the backup device and the update device check the level of network traffic and operate only if the traffic is below a pre-stored level. The system runs on a file server and / or one or more workstations. In some embodiments, the system maintains a status list of backup and update status of all workstations on the network. In another embodiment, the system tracks backup and update anomalies and provides notification of unserviced stations during the backup or update process. In some embodiments, only a backup device is provided, and in some embodiments, only updates are provided. Another aspect of the present invention is a method of mirroring workspace and work environment data between a file server and a workstation on a network, the method comprising: (a) providing a file server with respect to changes made in a master work environment; (B) initiating an update routine that mirrors the work environment from the file server to the workstation in response to detecting a change made in the master work environment; and (c) workspace storage. Monitoring the workstation for changes made on the device; and (d) initiating the transfer of backup data from the workstation to the file server in response to detecting a change made on the workspace storage device; Having. In various embodiments, the system according to the present invention provides a new and improved functionality of the data maintenance tool of the network, which often allows data transmission where network activity is restricted to low times. BRIEF DESCRIPTION OF THE FIGURES FIG. 1 is a simplified overview of a corporate network of a preferred embodiment of the present invention. FIG. 2 is an example of pseudo code of a method for implementing the present invention. FIG. 3 is another example of pseudo code of a method for implementing the present invention. Detailed description of the invention FIG. 1 is a schematic diagram of a network system 9 according to the present invention, comprising individual workstations 13, 15 and 17 coupled to a file server 19 via a network data link 11. It will be apparent to those skilled in the art that the network system 9 may be composed of different or multiple workstations, peripheral devices and different types of servers. However, in the present embodiment, three workstations and one server are shown, which are sufficient to properly describe the present invention. In FIG. 1, workstations 13, 15, and 17 are indicated by the same symbols. However, it should be understood that there may be several different types of workstations. The workstation used to create the mechanical drawings may include, for example, large, high precision monitors and other hardware used for graphical displays. Workstations used for secretarial work do not require high-end monitors such as those used for graphics workstations. Each of the workstations 13, 15, and 17 has a non-volatile memory (disk in this example) for storage. The station 13 has a disk 20, the station 15 has a disk 21, and the station 17 has a disk 22. The disk at each workstation stores the working environment and workspace for the associated workstation. In FIG. 1, the disc 20 has a section (a) for providing a work space and a section (b) used for a work environment. The workstation 15 also has a section (c) for providing a workspace and a section (d) used for a work environment. The disk 22 in the workstation 17 has a section (e) for providing a work space and a section (f) used for a work environment. A workspace is a memory area for at least temporarily storing files and other data generated during a work session by a user. The work environment is a memory area used to execute copies of applications, utilities, and the like executed on the workstation for workability. For example, part of the working environment on a graphics technology workstation is typically a powerful graphics generator, and the workstation has certain hardware to enhance performance for its application (graphics). It will be appreciated by those skilled in the art that the non-volatile storage capacity of each workstation will vary greatly depending on the application of the workstation and other elements, and the requirement that the capacity be sufficient for the workspace and work environment. It is obvious. The file server 19 may include a non-volatile memory 23 for logical capacity across a single physical hard disk or a group of devices such as a RAID array. There are many types of memory storage methods and devices, including but not limited to a hard disk used for the memory 23, for example. In a typical network installation, the storage capacity of the disks 20-22 is several tens of megabytes to several gigabits, while the storage capacity of the memory 23 in the file server 19 is up to terabytes. In this embodiment, the disk 23 is divided into two areas 25 and 27. In this example, area 25 is the master workspace for data temporarily stored in workspace sections a, c and e of disk drives 20, 21 and 22 at workstations 13, 15 and 17. It has three sections a, c, and e. Area 27 has sections b, d and f corresponding to sections b, d and f of disks 20, 21 and 22 at workstations 13, 15 and 17, respectively. This correspondence assumes that workstations 13, 15, and 17 are not identical in hardware and assigned functions. That is, this example assumes that the workstations are quite different, with one workstation for computer graphics, the other for secretarial work, and the other for accounting work. In this example, the working environment of each of the three workstations is quite different, and each master environment is different on disk 23. Assuming that the functions of the workstations 13, 15 and 17 are the same, the service is provided by a master copy of one working environment on the disk 23. Disk 23 may have other information and multi-purpose data accessible to all workstations. However, the invention relates to a corresponding workspace and work environment section. In a networked system of the type shown in the overview of FIG. 1 above, the ability to share space and function is particularly important. The workstations are not independent, but periodically derive their work environment from the file server 19, data and applications stored in memory 23. Similarly, the master storage and storage of the work product at each workstation is stored in the memory 23 via the file server 19. The ability to share makes it possible to minimize the overall computer equipment for the whole function. However, as mentioned above, access to the work environment from all workstations and backup of all data from the workstations to the file server can be made without causing undue delay or failure in the network. Needs to be provided on the data link of the network. The file server 19 accesses a list 29 containing information about all workstations on the network 9. List 29 is a database in this example. The list 29 according to the present embodiment stores, for example, a configuration map of each workstation that identifies work functions (ie, graphics or document processing) used by the application, startup information, and the like from other information. Similarly, the list 29 stores in the memory 23 the association of the workstation's logical workspace and work environment section with the corresponding master section. For example, in this example, section d of work environment memory 23 is a master copy of workstation 15 (and of another workstation on the network, identical in function to workstation 15, if any). In the event of a change in the working environment in section d of the memory 23, for example, an upgrade of a drawing program used by the workstation 15, it is important that a new version be sent to the workstation 15 on the network as soon as possible. It is. Similarly, as operators at various workstations create copies and files (work products), it is important that the work products be backed up in the master section of memory 23 corresponding to each workstation. Thus, while there is considerable bidirectional traffic on a typical network, unfortunately traffic is not distributed very well over time. It is this distribution of traffic over time that the present invention addresses in some aspects. It will be apparent to those skilled in the art that list 29 may be maintained in many different ways and stored in many different locations. This list may be maintained, for example, in memory 23 or in any other memory accessible by file server 19. In an embodiment of the present invention, the backup of the generated work product and the update of the work environment are achieved by a work using a convenient period and idle time when the network traffic is below a predetermined threshold. This unique mirroring operation is accomplished by mirroring routine 14 according to an embodiment of the present invention (FIG. 1). In FIG. 1, these mirroring routines are indicated by the abbreviation MR. For example, in one embodiment, when network traffic is at 40 percent of the maximum, a process is initiated in which the workstation initiates or continues to back up previously suspended work products and other data. A mirroring routine 14 accessible and executable by each workstation 13, 15 and 17 and also by the file server 19 is shown in FIG. In various embodiments, the mirroring routine 14 may be on the file server only, on one or more workstations only, or on all workstations and file servers with functionality distributed among the various mirroring routines. It may be performed. The mirroring routine according to embodiments of the present invention accomplishes one of two general purposes. One is a backup of the workspace, and the other is a mirroring update of the master working environment. For each function, actions are usually triggered by data changes. For example, if there is no change in workspace content at any workstation, there is no need to back up the workspace. However, when the contents of the workspace of any workstation, such as section a at workstation 20, are changed, the new workspace contents are stored for section a in memory 23 associated with file server 19 ( Mirror) need to be. One embodiment is an example of a mirroring routine 14 running on a workstation 13. When workspace activity is detected, a mirroring routine running on that workstation checks the level of network traffic and if the traffic level is below a preset threshold, mirroring is initiated. If the traffic exceeds the threshold, the backup is stopped until the operation drops below the threshold again. In this way, backups may be fragmented and distributed over a relatively long period of time, such as some now and some later. This distributed operation is the principle purpose of the traffic mirroring aspect according to the invention. Since the backup needs to be used only during low traffic periods, it is necessary to keep track of the backup status of each workstation and this function is performed by the list 29. Backup revisions are tracked and the backup status of each workstation is maintained in database 29. [DK1] In other architectures, the mirroring routine is executed on the file server 19 and is triggered whenever network activity is below a threshold. During all low activity periods in this embodiment, the mirroring routine begins checking each workstation in turn, backing up any changes to the workspace data content since the last active period of the workspace mirroring routine. To start. It will be apparent to those skilled in the art that there are various ways in which a backup may be performed due to the two requirements that a backup is required and network traffic is below a preset threshold. In the case of a work environment update, the mirroring operation is triggered by a change in the master work environment. Typically, the system administrator performs the updates using special hardware and / or software tools. In the preferred embodiment of the present invention, processing is initiated by the fact of a change in the master copy of the work environment, and the workstation requesting an update for the change is updated. In this case, the direction of data transfer is from the file server to the workstation. In various embodiments of the present invention, work environment updates may be scheduled in various ways. For example, the administrator performing the update may assign a priority according to the reason for the update. A very high priority means that the workstation will be updated immediately, irrespective of network traffic, even if other traffic is (probably) delayed. A lower priority may be assigned to allow updates when network traffic is low. The administrator may also have access to a scheduling routine that updates at specific times during the day (including at night). Also, because the level of network traffic changes, and in some embodiments of the present invention the mirroring routine operates only during low traffic periods, mirroring of updates may be somewhat sporadic, allowing accurate tracking of updated versions. And this is also done in list 29. Thus, in most embodiments of the present invention, list 29 is updated after each update of the work environment for a workstation, recording which workstation has the revision of which update. In one embodiment of the invention, the compression and decompression tools are installed and automated by software at the server and at each workstation on the network 9, and only the compressed data is transmitted over the network line 11. It will be apparent to those skilled in the art that known technologies that facilitate lower network traffic, such as burst technology, fiber optic lines, server mirroring technology, etc., can be used for the network 9 [DK2]. Due to the dynamic nature of the network, it may sometimes be impossible to access the file server for environment updates or workspace backups, or both. If the workstation is offline or unable to update or back up the workstation during data transfer, the information is recorded in list 29 and at a later time, the installation may be attempted again or the failure may be corrected. Notify the administrator. FIG. 2 is a pseudo-code listing illustrating one example of a procedure for updating a work environment according to an embodiment of the present invention. In this embodiment, the update for each work environment is executed when the work environment in the file server 19 is updated to a master copy or a copy. Typically, the system administrator has access tools or workstations to access the file server and initiate changes. Referring to FIG. 2, in step 200, the system checks for a master change (by performing MR 14). If a new revision is required, a revision counter is set and incremented in step 201. Next, at step 202, the system reads the information in list 29 to determine the particular workstation to be revised at the master. In step 203, an entry point is set for the repetition of the mirroring operation to be performed until all workstations that need updating have been successfully updated or added to the list of inaccessible workstations. In step 204, contact is made with the targeted workstation. The first workstation is contacted first in an iterative process, and the next workstation is contacted by order, such as an ID number. In step 205, a new revision is sent. When the revision is completed at a particular workstation, at step 206 that workstation responds that the revision was successful. At step 207, list 29 is updated to reflect the new revision. In steps 204-208, the process is repeated until all targeted workstations have been updated. In step 209, the list 29 containing all of the new updates is saved and stored. After the process is completed, one or more workstations may not have been updated. These workstations may be malfunctioning or offline for repair, etc. In step 210, the location of the workstation is accessed to identify the information, and in step 211, the system administrator is alerted of the situation. In the example shown in FIG. 2, the step of checking network traffic is not explicitly shown. However, in some embodiments, such a step is included and has a pre-programmed traffic level below a threshold as a condition for continuing the update. Also, the step of setting a priority or a specific time for updating by an administrator is not shown. However, as noted above, some embodiments include such a step. The code shown in FIG. 2 is pseudo-code that illustrates the functionality in a particular embodiment and is intended for illustrative purposes only. It will be apparent to those skilled in the art that many specific programming languages may be used to implement the mirroring routine. It will also be apparent to one skilled in the art that there are many modifications to the configuration and steps to adapt the software to a particular network environment. For example, in one embodiment, if a system administrator interface is desired, manual steps may be integrated with automated steps. In other embodiments, the functionality of the software may be fully automated for scheduled events over a period of time, such as several days. FIG. 3 is a pseudo code listing step for backing up data generated at the workstation. At step 300, the software network traffic detection feature checks the network traffic and alerts the system if the network traffic falls below a predetermined level, as described above. In step 301, a new backup procedure is started. In step 302, the list 29 is accessed and the workstation is located and contacted. The backup iteration is started in step 303. In step 304, the first and next workstations are contacted and a workspace backup is started. As described above with respect to FIG. 1, this process is transparent to the user, meaning that the user can continue working without being aware of the process. In one embodiment, a pop-up icon may indicate to the user that a backup is taking place, but that is not required. In step 305, all marked files on the contacted workstation are accessed. In step 306, the file is stored in the appropriate associated section of memory 23 (FIG. 1). In step 307, list 29 is updated with respect to the workstations that are communicating to index the backup version. If, in step 2008, all stations have been accessed or did not respond, control returns to step 303. Typically, in this process all files are backed up and stored on the server, but files may be backed up partially for the current situation while the user is working. This is a process in which network traffic automatically proceeds until a backup procedure is stopped or rises above a predetermined level that is terminated during operation. In step 309, the list 29 is saved. Although the update procedure is described with reference to FIG. 2, there may be one or more workstations for which file backup was not successful due to being offline or under repair. The system locates and identifies the information of these particular workstations at step 310 and alerts the system manager at step 311. It should be emphasized that the list of FIG. 3 is one example of how a backup system operates in an embodiment of the present invention. It will be apparent to those skilled in the art that there are various ways in which the software of the present invention may be written and configured to adapt to a network environment without departing from the scope of the present invention. For example, the software may be executed over a large scale between multiple corporate networks, such as a joint corporate intranet, located at different locations and connected together. The embodiments described above and above are possible. The features of the invention are limited only by the following claims.

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06F 15/177 678 G06F 9/06 610D

Claims (1)

[Claims] 1. Network data that includes one or more workstations and file servers. Data mirroring system,   Change the work product data stored on the one or more workstations Work product from the workstation to the file server A backup device for backing up data,   As the master copy of the working environment changes, the file server An update device for mirroring the work environment to one or more workstations; A system comprising: 2. One or both of the backup device and the update device are connected to a network Inspect traffic levels to ensure that traffic is below a pre-stored level. 2. The system according to claim 1, wherein the system operates only when the system is operating. 3. The backup device and the update device operate on the file server The system of claim 1, wherein: 4. The backup device runs on each workstation and the update device The system according to claim 1, wherein the system operates on the file server. 5. Characterized in that both devices operate on the one or more workstations The system according to claim 1. 6. Backup and update of all workstations on the network The system of claim 1, wherein the system maintains a state list of states. 7. Track backup and update anomalies and provide support during the backup or update process. 7. The method according to claim 6, wherein a notification of a station that is not serviced is presented. system. 8. Network network including one or more workstations and file servers Backup system,   Pre-stored as a condition for network traffic to start backup A traffic level device that checks that the traffic level is below a specified traffic threshold value. ,   The traffic level device, wherein the traffic is below the threshold. The file server from the one or more workstations for a period during which A data transfer device for transmitting data to the server. System. 9. The system of claim 11, wherein the system operates on the file server. 8. The backup system according to item 8. 10. The system operates on each workstation. Item 9. The backup system according to Item 8. 11. Backup and update of all workstations on the network 9. The backup system according to claim 8, wherein a state list of states is maintained. Stem. 12. Track backup abnormalities, 2. The method of claim 1, further comprising presenting a notification of the station not being serviced. The backup system according to 1. 13. A network including one or more workstations and a file server. A work environment update system,   Network traffic must be pre-configured as a condition to start backup. A traffic level device that checks that the traffic is below a stored traffic threshold When,   The traffic level device, wherein the traffic is below the threshold. The file server from the one or more workstations for a period during which And a data transfer device for transmitting data to the server. M 14． The system operates on the file server. Item 14. The update system according to Item 13. 15. Update status list of all workstations on the network 14. The update system according to claim 13, wherein? 16. Tracks backup anomalies and is not serviced during the backup process The update system according to claim 15, wherein a notification of a station is presented. . 17． Work between file servers and workstations on the network A method of mirroring space and work environment data, (a) File changes in the master work environment. Monitoring the server (b) upon detecting a change made in the master working environment, Update routine for mirroring the work environment from server to workstation Starting the application, (c) Monitor workstations for changes made on workspace storage. Steps to (d) upon detecting a change made in the workspace storage device, To start the transfer of backup data from the application to the file server And a step. 18. The conditions under which network traffic initiates a backup or update Further comprising the step of determining that the level is less than or equal to the previously stored level. 18. The method according to claim 17, wherein: 19. Update and backup status of workstations on the network The method of claim 17, further comprising the step of maintaining a state list. Law. 20. Including recorded code for performing the steps of claim 16. Nonvolatile memory device.