Procedure for configuring a spooling unit of a print server for high-performance digital printing systems and print servers

DE102019122708B4Active Publication Date: 2025-02-20CANON PRODN PRINTING HLDG BV
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
DE102019122708
Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Filing Date
2019-08-23
Publication Date
2025-02-20
Estimated Expiration
2039-08-23

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

Method for configuring a storage system of a print server (2) for high-performance digital printing systems (1), wherein the storage system is designed to store an operating system and print jobs and other files and has one or more storage media (9), and one or more printing devices (3) are connected to the print server (2), wherein the storage media (9) are automatically set up depending on predetermined parameters of the high-performance printing system (1), wherein the predetermined parameters include at least benchmark parameters and the benchmark parameters are measured parameters that each represent a specific property of the print server (2) and / or printing device (3), wherein the following steps are performed for automatic setup: - Recording the predetermined parameters, - Specifying a certain number of logical hard drives depending on predetermined parameters, - Assignment of the logical hard drives to at least one print data cache depending on the predetermined parameters, and - Distribution of the storage system's storage capacity across the logical hard drives depending on the predetermined parameters, wherein the configuration of the print data cache memory (18) is started when a change to the printing system (1), i.e. a printing system change, is detected which causes a change in the load on the print data cache memory (18), and where the detection of a printing system change is performed using one or more of the following methods: - Monitoring predetermined parameters that reflect the system state of the printing system (1), whereby when such a parameter changes, it is checked whether this is a relevant printing system change in order to start setting up or updating the storage capacity of the print data cache memory(s) (18), - Monitoring the print data streams in order to start configuring the storage capacity of the print data cache memory(s) (18) when a relevant change occurs, - Monitoring the print data cache memory(s) (18) to detect an overload or underload of one of the print data cache memory(s) (18) in order to start configuring the storage capacity of the print data cache memory(s) (18) in the event of a predetermined overload or underload.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] The present invention relates to a method for configuring a spooling unit of a print server for high-performance digital printing systems and to such a print server.

[0002] Chapter 15 of the book "Digital Printing, Technology and Printing Techniques of Océ Digital Printing Presses", 9th edition, February 2005, ISBN 3-00-001081-5, describes print servers for high-performance printers. It schematically illustrates the process used in an Océ PRISMAproduction Document Output Management System for communication between two processes of a computer system to transfer print data.

[0003] German patent DE 10 2016 125 023 A1 describes a method for operating a print server for high-performance digital printing systems, which includes the following steps: - Reading state parameters that describe system states, such as the load on a CPU, RAM, file system, network and / or system interface, using a collective trigger, - Triggering filters to read further state parameters, which include process states of application processes running on the print server, whereby the triggering is performed with a trigger logic, depending on whether the system states captured with the collective trigger represent an exceptional operating state.

[0004] German patent DE 10 2016 125 020 A1 discloses a storage system for a print server comprising a first logical hard drive and a second logical hard drive. A third mass storage medium is provided for storing the operating system, application programs, control data, and trace data. The first logical hard drive is used to store print data (PD: Print Data), and the second logical hard drive is used to store print data already prepared for printing (R2P: Ready to Print). Incoming print jobs (PD) at the print server are written to the first logical hard drive. When a print job is executed, the print data is read from the first logical hard drive into main memory, processed, and written back to the first logical hard drive. This process is repeated for each print job. This process converts the print jobs (PD) into print data ready for printing (R2P: Ready to Print).The second logical hard drive stores only print data that has already been prepared for printing, referred to below as ready-to-print data. This second logical hard drive can also be called a print data spooler, where the ready-to-print data is temporarily stored.

[0005] For print servers in high-performance digital printing systems, it is crucial that a continuous stream of print data can be supplied to the printers. If a print data stream requested by a printer could not be transmitted in time, the printer would have to be stopped. However, a printer in a high-performance printing system cannot simply be stopped. For example, the transport of the recording medium cannot be easily halted. Therefore, a sudden stop to the printing process leads to a significant waste of recording medium, also known as waste paper. Furthermore, printer downtime incurs substantial production costs.

[0006] Therefore, in print servers, a print spooler typically consists solely of a cache memory, which allows for the rapid writing and reading of large amounts of data. Since the data volume of print jobs is known to be large, and multiple print jobs must be stored simultaneously in such a print spooler, the cache memory capacity must be correspondingly large. However, cache memory is technically far more complex than conventional mass storage and therefore considerably more expensive. In addition to the cache memory, a print server's storage system often includes one or more memory areas for the operating system. The operating system is stored on one of these memory areas. Further memory areas can be allocated to and used by the operating system. These memory areas are described below as logical hard drives.

[0007] Previously, the storage system was configured manually. Any system change, such as replacing or expanding the cache memory, requires a complete system reinstallation. This may necessitate formatting all hard drives and reinstalling the operating system and print manager.

[0008] When installing an operating system, multiple partitions can be created on the hard drive. Typically, at least one system partition and one application partition are provided. If special logical hard drives are to be set up, as in the procedure described in DE 10 2016 125 020 A1, they are configured manually after the operating system is installed, according to the specific requirements. In principle, the logical hard drives could be created along with the other partitions during the operating system installation.

[0009] Manual configuration is not only very time-consuming, but also expensive due to the use of specialist personnel.

[0010] Document US 2013 / 0238785A1 discloses a cloud computing system with a plurality of computer devices configured to host instances of virtual machines, wherein each computer device in the plurality includes a monitor capable of collecting metadata about the associated computer device. The system also includes a register capable of receiving and storing the metadata from the plurality of computer devices and a scheduler that selects a host computer device from the plurality of computer devices on which to instantiate an instance of a virtual machine based on the metadata stored in the register.

[0011] Document US 9,851,933 B2 discloses the allocation of computational tasks based on metadata of computer devices. In particular, this document discloses a method and system for capability-based resource allocation in a software-defined environment that performs the following steps: (i) determining a set of capability attributes for a plurality of workload resources within a software-defined environment; (ii) determining a set of workload components for a specified workload; and (iii) identifying a set of workload resources from the plurality of workload resources to be allocated to the specified workload.

[0012] The invention is based on the objective of creating a method for configuring a storage system of a print server for high-performance digital printing systems, with which print jobs can be transmitted reliably and very efficiently to one or more printing devices in a simple and cost-effective manner.

[0013] The problem is solved by one of the subject matters of the independent claims. Advantageous further developments and preferred embodiments form the subject matter of the dependent claims.

[0014] In a method for configuring a storage system of a print server for high-performance digital printing systems with the features of claim 1, the predetermined benchmark parameters can be analyzed using a benchmark method. The parameters describing the print server, such as storage capacity, read and write speeds, or latency of the storage media, depend not only on the storage medium actually used, but also on the peripherals surrounding the storage medium, such as data buses, drivers, or the integration of the respective hard drive into a storage management system, such as a RAID system. Therefore, the actual properties of the respective storage medium are not always precisely predictable based on general manufacturer specifications. Thus, such a benchmark method allows the actual properties to be determined and taken into account very precisely during configuration.The benchmarking process can also identify different usage patterns. These patterns can differ in segment size during read and / or write operations, in the ratio of simultaneous read and write operations, and / or in the physical location where the data is written. For example, storage media can differ in performance depending on whether small or large files are being written and / or read.

[0015] Storage media can be any type of data storage, such as semiconductor memory (RAM, SRAM, ROM, SSD) or hard disks (HDD).

[0016] The print data cache is designed to transmit print data of a print job to one or more printing devices.

[0017] The data stream must always be supplied by the print server when the printer requests it or is ready to receive it. If the printing process were to be interrupted, this would result in significant costs for a high-performance printing system. Such an interruption leads to a so-called printer clutching. This produces waste, also known as scrap paper, with a paper roll ranging from several tens to several hundred meters. It can even lead to a print job having to be completely reprinted. Furthermore, the downtime of the printer incurs considerable costs. The term "continuous print data stream" therefore refers to a print data stream that is continuously available, i.e., without interruption, to be transmitted to the printer(s), but does not necessarily mean that it is actually transmitted continuously at all times.If the printer does not request print data, the transmission of print data can be interrupted. Current technology minimizes the risk of printer clutching by using a very large cache hard drive. However, such high-capacity cache hard drives are very expensive.

[0018] Automatic configuration ensures efficient use of available storage media capacity. This means no capacity remains unused unintentionally. This would be the case, for example, if the logical hard drive on which the operating system is to be installed had a capacity many times greater than actually required. Since the operating system's capacity will not change significantly during operation, the capacity of the associated logical hard drive can be smaller than in standard computers. The remaining capacity can then be allocated, for example, to the print data cache. The capacity of the print data cache can also be optimized so that each device has sufficient capacity available for the data stream. Therefore, storage media with a smaller overall capacity can be selected for the print server.

[0019] Furthermore, no fixed order for the storage media is necessary. When storage media are connected to a computer system, the operating system typically assigns names based on the insertion order. However, arbitrary or difficult-to-understand assignments can also occur. For example, under Linux, hard drives are named sda, sdb, sdc, etc., according to the insertion order. HDDs are named hda, hdb, etc. Some operating systems, such as Ubuntu, name all hard drives sda, sdb, etc. An assignment based on this name is not initially possible.

[0020] The automatic setup allows the assignment to be made based on the properties of the storage media. For example, it may be irrelevant whether the fastest storage medium is called sda or sdb, as long as the property is known.

[0021] Preferably, the predetermined parameters include default parameters, wherein the default parameters are parameters entered by the user or parameters entered by the user and calculated therefrom.

[0022] Preferably, when dividing the storage capacity of the storage system among the logical hard disks, one or more print data cache memories are assigned to the logical hard disks.

[0023] Each printer or group of printers is assigned one of the logical print data caches. This ensures that each printer or group of printers has a logical print data cache tailored to its specific needs. The storage capacity of the cache disks can be optimally utilized by individually customizing the logical print data caches. Experience has shown that this individual customization allows multiple printers to be reliably supplied with their respective print data streams using a comparatively small cache disk capacity. This results in significantly more efficient use of the cache disk storage capacity than conventional print servers.

[0024] Such a logical print data cache can be represented by a partition with respect to the operating system used on the print server. For the purposes of the invention, a partition is a logical hard drive of an operating system.

[0025] Preferably, the predetermined parameters for determining the number of logical hard disks include one or more of the following parameters: - Number of storage media, - Type of storage media, - Number of printing devices, - Print data streams that the respective printing devices require in order to print without interruption, - average number of processing steps for print job files, - average number of pages to be printed, - average file size, - average size of print jobs to be loaded onto the respective print data caches, and / or - average load on the print data cache memory.

[0026] Preferably, the number and distribution of the storage capacity of the logical hard disks is determined according to one or more of the following criteria: - The number of logical hard drives is proportional, and in particular linearly proportional, to the number of connected printing devices. - The number of logical hard disks is proportional, and in particular linearly proportional, to the number of storage media. - The storage capacity of the print data cache is proportional, and in particular linearly proportional, to the respective print data stream and / or to the average load on the print data cache, and / or - The storage capacity is inversely proportional and, in particular, linearly inversely proportional to the number of storage media.

[0027] Furthermore, the number and distribution of caches can depend on whether the storage medium needs to be fault-tolerant or not. This means whether a failure of the storage medium would be critical. For example, a storage medium on which the operating system is stored would need to be more fault-tolerant than a single cache among several.

[0028] Generally, a large data stream requires a large storage capacity. However, with a very fast cache drive, such as an SSD or RAM, a high data stream can be provided even with a smaller storage capacity. In this way, the storage capacity required for a logical print data cache can be compensated for by a fast cache drive.

[0029] Since it is advantageous to always temporarily store print jobs completely in the print data cache, the storage capacity of the corresponding print data cache for a printing device that typically processes large print jobs must be appropriately sized. It is important to note that preferably sufficient storage capacity for at least two print jobs should be provided in a print data cache, so that one print job currently being printed and a second print job, ready to print once the first is finished, are held in reserve.

[0030] The storage capacity of the print data cache memory can be proportional, and in particular linearly proportional, to the print data stream of the respective printing device.

[0031] If the load on the individual print data caches is known, then the storage capacity is preferably distributed according to the loads on the individual print data caches.

[0032] Since the print data cache storage can comprise the storage capacities of different cache hard drives, which have different speeds, the write and / or read speed of the different cache hard drives can be taken into account when allocating the storage capacity. The faster the write or read speed of the respective cache hard drive, the lower the storage capacity that needs to be allocated to the corresponding print data cache, because a higher throughput can be achieved with a smaller storage capacity due to the higher read and / or write speed.

[0033] In the method according to claim 1, the configuration of the print data cache is initiated when a change in the printing system is detected that causes a change in the load on the print data cache. Such a change in load can be detected, for example, by exceeding or falling below predetermined load limits of the print data cache.

[0034] Such a change to the printing system can be detected if a change in the printing system results in a change in utilization or if the hardware necessary for transmitting print jobs from the print server to the printing devices is changed, in particular if - a mean print data stream changes by at least 10%, preferably by at least 25% and in particular by at least 50%, within a predetermined period, e.g. at least one hour, preferably at least ten hours and in particular at least 24 hours, - the state of the printing device receiving the print data stream changes, for example by connecting, removing or placing a printing device in maintenance mode, - the available storage capacity of the cache hard drives changes, for example by adding, removing or replacing a storage medium, and / or - the assignment of a printing device to one of the print data caches changes, which can happen, for example, through manual intervention.

[0035] Printing devices can be characterized by their print data stream requirements, which are the speed at which the printing device must read and receive data to print without interruption. Print data stream requirements are primarily influenced by the printing speed and the type of print image. A color print image, especially one with different color levels, requires more data per page than a purely black and white print image, particularly if it consists solely of text and can be represented using appropriate encoding (e.g., ASCII).

[0036] The available storage capacity of the cache disks can change if, for example, a storage medium is added, removed, or replaced. Since the storage capacity of the cache disks must be shared with other applications on the print server, the storage capacity available to the spooling unit can change if the other applications on the print server change.

[0037] For example, the available storage capacity can change when the operating mode of the corresponding printing system switches from a 12 / 5 mode (printing only for 12 hours on five weekdays) to a 24 / 7 mode (printing continuously 24 hours a day, 7 days a week). In a 24 / 7 mode, conversion programs that convert incoming print jobs at the print server, for example, into different formats, must process the print jobs as quickly as the data needs to be forwarded to the printing devices. Therefore, conversion programs in 24 / 7 mode require more processing power on the print server than in a 12 / 5 mode, where most of the print job conversions can be completed during printing breaks at night or on weekends.If the conversion programs, which are special applications on the print server, require more processing power, then less RAM is available for RAM disks than cache disks. Changing the operating mode of the printing system can therefore change the available storage capacity for the cache disks used by the spooling unit. Activating a conversion program can also demand additional processing power from the print server and thus change the available storage capacity of the cache disks. Conversion programs are very computationally intensive applications on a print server, so changes to their settings or usage can result in a change in the storage capacity available to the spooling unit.

[0038] According to claim 1, the detection of a change in the pressure system is carried out using one or more of the following methods: - Monitoring predetermined files that reflect the system state of the printing system, checking whether a change to such a file constitutes a relevant printing system change in order to initiate the configuration of the storage capacity of the print data cache(s), - Monitoring print data streams to initiate configuration of the print data cache capacity(s) when a relevant change occurs, - Monitoring the print data cache to detect an overload or underload of one of the print data caches in order to start configuring the storage capacity of the print data cache(s) in the event of a predetermined overload or underload.

[0039] Predefined parameters that reflect the system state of the printing system include, for example, the size or designation of a storage medium. If such a parameter changes, or if a change in the printing system is detected in any other way, a new distribution of the storage capacity of the cache disks across the print data cache is preferably calculated. If this distribution differs by a predetermined amount, this change in the printing system is considered relevant, and a configuration of the print data cache is initiated at the next available opportunity. The predetermined amount is, for example, at least 5% and, in particular, at least 10% of the storage capacity of a current print data cache.

[0040] Another opportunity arises when the print server is not in use for a certain period. This could be, for example, a specific time of day. The time can also be specified manually by the user.

[0041] The spooling unit can optionally include an additional spooling buffer to temporarily store print jobs before forwarding them to the print data cache. This allows large quantities of print jobs to be stored cost-effectively in the spooling buffer. As a result, a relatively small print data cache is sufficient to ensure a fast and continuous supply of print data to the printer.

[0042] Preferably, the total capacity of the spooling memory is larger than the capacity of the print data cache; in particular, the capacity is many times larger, at least twice as large, preferably at least five times as large, and if possible at least ten times as large. All print jobs to be printed are preferably stored in the spooling memory. From the spooling memory, the print jobs are then forwarded to the individual print data caches, which then forward the print jobs to the individual printing devices. Since the print jobs can be stored in the print data cache, they can easily be deleted from the print data cache without being lost.

[0043] Preferably, the capacity of the operating system memory is not greater than 150%, preferably not greater than 125%, and in particular not greater than 110% of the size of the operating system.

[0044] In addition to the operating system memory, the storage system can also have other logical system memories, such as a logical: - System logging storage (also called "var") - Outsourcing storage (also called "swap"), - Service memory (also called "service"), and / or - Benchmark memory (also called "benchmark").

[0045] Preferably, the print data cache is formatted automatically. During formatting, a suitable format, also known as a file system, is selected. Typical formats include XFS, ext4, BTRFS, NTFS, FAT, and exFAT. FAT is a particularly widespread format. exFAT was developed for flash memory, while NTFS offers advantages over FAT due to its superior disk compression and lower rate of data loss. Formats can differ in aspects such as block size, security, fault tolerance, data loss probability, disk compression capabilities, and block size limitations. Depending on the storage medium, operating system, and / or application, a different format may be required.Furthermore, this ensures that no data remains on any of the print data caches that are not print jobs and could occupy storage space on the print data cache.

[0046] Preferably, the print data cache is cleared automatically. This can be done by deleting a corresponding entry in a directory or, in the case of certain types of print data caches, by overwriting each memory area of ​​the print data cache one or more times with random data. This deletes any old print jobs that might be occupying the print data cache. Furthermore, the multiple overwrites ensure that the data cannot be read later, thus increasing security.

[0047] Preferably, logical hard drives are assigned in such a way that they interfere with each other as little as possible. If two or more logical hard drives are assigned to a storage medium, it may happen with certain types of storage media that the two logical hard drives cannot be read from or written to simultaneously. Therefore, a storage medium should be assigned to as few logical hard drives as possible. The operating system's logical hard drive, on which many small files (often smaller than 50 MB) are read from and written to, should preferably be assigned to a different storage medium, such as a logical hard drive for spooling print files, which are predominantly large (larger than 100 MB).

[0048] Preferably, the load generated by reading and writing data is distributed. This can be achieved by distributing the logical hard drives across as many storage media as possible.

[0049] Another advantage of distributing logical hard drives across as many storage media as possible is that the speed for creating and deleting files on a given logical hard drive can decrease if there are too many files and / or directories. A typical limit here is 1,000 directories and 10,000 files.

[0050] A print server for high-performance digital printing, which receives print jobs, comprises a CPU, a spooling unit which includes a print data cache, wherein the print server is equipped with a computer program that is designed to execute the procedure described above.

[0051] Preferably, the print server has one or more backend modules that read print jobs from their respective assigned print data caches and forward them to one or more print devices. The number of print data caches is preferably equal to the number of backend modules. It may be advantageous for a print device to have multiple print data caches assigned to it if the print device is frequently used to print different types of images. This is the case, for example, if successive print jobs alternate between primarily color image pages and primarily text-only pages.

[0052] Preferably, several storage media are integrated into a storage management system, in particular a software RAID system (redundant array of independent disks), and together form a logical hard disk.

[0053] A logical hard disk, or rather a property and / or functionality of a logical hard disk, where the functionality describes the executable property of the logical hard disk, such as ensuring a certain capacity or a certain I / O performance, can be provided, created, modified, and / or deleted by the operating system and / or by appropriate software. Logical hard disks can also be connected externally to the system, for example, via a storage area network (SAN). Using certain methods, such as iSCSI (Internet Small Computer System Interface), real or virtual storage media, which may contain logical hard disks, can be accessed.

[0054] Logical hard disks are therefore storage areas that can be accessed with operating system commands just like a conventional physical hard disk. These storage areas can be configured independently of physical storage areas and, for example, comprise only a part of a physical storage medium or several parts of different physical storage media.

[0055] The present invention is particularly suitable for use on a print server.

[0056] The invention is explained in more detail below by way of example with reference to the drawing. The drawings show: Fig. 1. Schematic representation of a printing system with a print server in a block diagram. Fig. 2. A memory structure of the print server with a spooling unit in a block diagram, Fig. 3 a storage structure of a print server according to a further embodiment with a spooling unit in a block diagram, Fig. 4 essential software modules, logical data connections and logical storage units for executing the procedure in a block diagram, Fig. 5. A procedure for configuring a storage system in a flowchart, Fig. 6a(1) a method for automatically determining the purpose / sequence / size of the storage medium in a flowchart, Fig. 6a(2) Continuation of Fig. 6a(1), Fig. 6b a method for using predefined and / or benchmark parameters to determine the allocation / order of storage media, in a flowchart, Fig. 6c a method for using predefined allocation parameters in a flowchart, Fig. 7a a method for determining a standard capacity of a logical hard disk in a flowchart, Fig. 7b a method for determining the standard capacity of the logical disks on the storage medium I in a flowchart, Fig. 7c a method for determining the standard capacity of the logical disks on storage medium II, III, etc. in a flowchart, Fig. 7d a method for determining the standard capacity of the logical disks on the storage medium I in the normal and safety range in a flowchart, Fig. 8a(1) a method for displaying a user suggestion and entering changes in a flowchart, Fig. 8a(2) Continuation of Fig. 8a(1), Fig. 8a(3) Continuation of Fig. 8a(2), Fig. 8b a method for dealing with a reassignment of storage media in a flowchart, Fig. 9. A procedure for adding logical disks during operation in a flowchart, Fig. 10. A procedure for switching between a logical hard disk and a logical backup disk in a flowchart, Fig. 11. A procedure for checking the storage media / logical hard disks during startup in a flowchart, and Fig. 12. A method for monitoring the storage media / logical hard disks during operation in a flowchart.

[0057] The invention is explained in more detail below with reference to a printing system 1. The printing system 1 comprises a print server 2 ( Fig. 1) on, to which several printing devices 3 are connected, each via a data line 4. The data line 4 usually conforms to a network standard, such as Ethernet.

[0058] The print server 2 is connected to a network (LAN or WAN) and in particular to the Internet 5, to which one or more clients 6 are connected, on which print jobs are created and transmitted to the print server 2 via the Internet 5.

[0059] Print server 2 receives print jobs and forwards them to the respective printers 3. The print jobs are temporarily stored on print server 2 and processed as needed so that they can be received by print server 2, rasterized by printer 3, and printed. An operator on the print server can also view the print jobs, for example, using a preview program, allowing them to check individual pages and influence the routing and processing of print jobs on the print server.

[0060] Print servers that forward print data to one or more printing devices are typically used in high-speed printing. High-speed printing, as defined in the present invention, refers to the use of a printing device capable of printing at least five DIN A4 pages per second. However, high-speed printing devices can also be designed for higher printing speeds, such as at least 30 DIN A4 pages per second, and in particular at least 50 DIN A4 pages per second, and preferably at least 90 DIN A4 pages per second. These printing devices are digital, meaning that they receive print data in digital form, which is converted into a print image by a printhead in the printing device 3. This image is then applied to a substrate, often paper, using ink.Typically, such a printing device is designed as an inkjet printer or an electrophotographic printer. It can also be a printer that uses liquid toner as its printing ink.

[0061] Experience shows that the data size of a color page in DIN A4 format (Portable Document Format, or PDF) averages between 0.5 and 2 MB. At 2 MB per page and a print speed of 50 pages per second, this means the printer receives a data stream of 100 MB / sec. This data is not yet rasterized. For high-resolution color printing, and especially for documents containing multiple images, the data size per DIN A4 page can reach 10 to 25 MB, and in extreme cases, up to 600 MB.

[0062] Print server 2 must therefore receive a substantial data stream, assign the data contained therein to the individual printing devices 3, and adapt it as necessary. Such adaptation may include changing the format of the print data stream (IPDS, PCL, PDF, etc.), scaling the print data, changing the resolution of the print data, or otherwise adapting the print data to the requirements of the respective printing device or to specific requirements of the operator of the printing device or a client placing a print job.

[0063] The storage structure of print server 2 ( Fig. 2) comprises a spooling unit 8 with at least two hard disks 9, 10, one of which is a conventional mass storage device, which is referred to below as the M disk 9, which is used to store print data (PD: Print Data), and the other disk is designed as a cache memory, which is referred to as the cache memory medium 10.

[0064] Print server 2 has an additional hard drive 11, which is used to store the operating system, application programs, control data, and trace data. This hard drive will be referred to below as system hard drive 11.

[0065] The print data generated on client 6 is transmitted via the Internet 5 to the print server 2 and initially stored there on the M hard drive 9.

[0066] The print data is converted into ready-to-print data, while remaining stored on the M hard drive 9. The converted ready-to-print data is then transferred to the cache storage medium 10. As explained above, the cache storage medium 10 is a cache memory in which data can be written and read quickly. This allows the ready-to-print data to be quickly supplied to the printer 3.

[0067] Both the print data and the ready-to-print data are divided into individual print jobs. A print job can contain one or more files.

[0068] The spooling unit 8 is characterized by the fact that print jobs already stored on the cache hard drive 10 can be deleted to free up storage space for print jobs with a higher priority. This is explained in more detail below. This makes it possible to keep the capacity of the cache storage medium 10 relatively small while still providing a continuous stream of print data to the connected printers 3.

[0069] In Fig. Figure 2 shows the M drive (9), the cache drive (10), and the system drive (11) as separate hard drives. It is also possible that these drives simply form separate partitions on a single hard drive. The term "partition" is used here to mean a logical hard drive.

[0070] The M-hard drive 9 and the cache memory medium 10 of the spooling unit 8, however, are at least two separate hardware elements ( Fig. 3) The cache storage medium 10 is designed as a cache memory, whereas the M hard drive 9 is a conventional mass storage medium that does not constitute a cache memory. A cache memory within the meaning of the present invention is a mass storage device with a faster read and write speed than the M hard drive 9. Therefore, the cache memory or the cache storage medium 10 can also be a conventional, fast hard disk drive (HDD). However, faster mass storage media, in particular semiconductor memory such as an SSD, flash memory, and / or a RAM disk, are preferred. As will be explained in more detail below, the cache memory can also comprise several different mass storage media in combination.

[0071] The following section describes the logical elements of printing system 1, namely the software modules, logical data connections, and logical storage units, based on: Fig. 4 explained in more detail. The print jobs are generated by print data generation programs 12, which are executed on the client 6, and transmitted via the Internet 5 to an input module 13 of the print server 2. The input module 13 writes the print jobs to a logical M-disk 17, which is the logical counterpart to the M-disk 9 and is part of the spooling unit 8. The logical M-disk 17 is referred to below as spooling memory 17.

[0072] The print server 2, or spooling unit 8, features a configuration module 23 that can automatically configure the cache disk 10(s) into multiple print data cache memories 18. Furthermore, it configures the spooling memory 17 and a logical system disk 24, which is the logical counterpart to the system disk 11.

[0073] In comparison to conventional print servers, the total capacity of the print data cache memory 18 can be comparatively small, yet a secure and reliable supply of print data to the individual printing devices 3 is still enabled.

[0074] Print data services 15 read the print job from the spooling memory 17 and process it. After processing, the print data services 15 write the print job back to the spooling memory 17. By processing using one or more such print data services, the print jobs received by the print server 2 are converted into print jobs that represent ready-to-print data and can therefore be printed directly by the printing devices 3. These converted print jobs are referred to below as R2P print jobs.

[0075] These ready-to-print jobs are transmitted by a spooler module 16 to one of several logical print data caches 18.1 / 18.2 according to predefined rules. In the present embodiment, all print jobs received by the spooling unit 8 are initially stored in the spooling memory 17. The print jobs can be assigned to a specific printer 3, or if this is not the case, the spooler module 16 assigns the print jobs to one of the printers 3 based on their properties. Print jobs with many color images are preferably assigned to a high-performance color printer, while black-and-white forms are preferably assigned to a dedicated form printer. This assignment can be made to one of the printers 3 based on a variety of different parameters, such as the size of the print job, the proportion of color, the resolution of the printed image, and the like.

[0076] If a print job is assigned to a specific print device 3, then the spooler module 16 attempts to write the print job to the print data cache memory 18, which is assigned to the respective print device 3 via one of the backend modules 19.

[0077] The following is an example of how to configure the storage system of printing system 1. The configuration is performed by configuration module 23.

[0078] Such a configuration is initiated, for example, when a print server is initially set up. Alternatively, the configuration can be performed when the system is modified, such as when the storage media is expanded.

[0079] The process begins with step S1.

[0080] In the next step (S2), predetermined parameters are recorded.

[0081] These predetermined parameters include benchmark parameters that are captured via a benchmarking procedure.

[0082] In the benchmark procedure for checking the capacity of a storage medium, as well as its read and write speeds, random data sets are written to the storage medium until it is completely full. The speed at which the data is written is monitored. This determines not only the maximum capacity but also a write speed profile. A read speed profile can be created by reading this written data. Alternatively, or in combination, a small (benchmark) partition can be created last on the storage medium. This allows you to quickly measure the speed of a full hard drive without the time-consuming process of writing it completely. The first partition can be used to measure the maximum speed. If further partitions exist, their respective speeds can also be determined.

[0083] In this embodiment, the predetermined parameters also include default parameters. These are, for example, the expected average size of the print jobs to be loaded onto the respective print data caches and / or the average load on the print data caches. The average load on the print data caches is determined by both the speed of the print job and the type of print job. For example, the load is significantly higher for a photo print job at 50 A4 pages per second than for a black and white text print job at 10 A4 pages per second.

[0084] Other predetermined parameters include, for example: - Number of storage media, - Type of storage media, - Number of printing devices, and - Print data streams that the respective printing devices require in order to print without interruption.

[0085] In the next step (S3), a specific number of logical hard drives is determined depending on the predetermined parameters.

[0086] The number of logical hard drives can be linearly proportional to the connected printing devices and / or the number of storage media.

[0087] In this embodiment, three storage media are provided: - a cache hard drive 10, which has a small capacity and fast read and write speeds, - an M-series hard drive 9, which has a large capacity but slow read and write speeds, and - a system hard drive 11, which has a small capacity (approximately 125% of the size of the operating system) and slow read and write speeds. Small and large, or fast and slow, should be understood here in relation to the other two storage media.

[0088] Furthermore, five printing devices are connected.

[0089] Seven logical hard drives are required for operation: - a logical system hard drive 24, - a spooling memory of 17, and - five print data cache memories 18.1-18.5.

[0090] Next, in step S4, the logical hard drives are assigned depending on the predetermined parameters.

[0091] Preferably, storage media are divided into as few logical areas as possible. Therefore, the first step is to ensure that each storage medium contains as few logical disks as possible. These logical areas are used for reasons of space requirements, various limitations, mutual file cache interference (flushing), and / or speed.

[0092] Logical system disk 24 is intended for storing the operating system. Therefore, this logical disk should have a capacity that is no greater than 150%, preferably no greater than 125%, and particularly no greater than 110% of the size of the operating system.

[0093] The logical system hard drive 24 is thus assigned to the system hard drive 11.

[0094] Since the spooling memory 17 requires a large capacity, it is assigned to the M hard drive 9.

[0095] Cache hard drive 10 is the fastest of the connected storage media. Therefore, it is assigned to the five print data cache memories 18.1-18.5.

[0096] Step S5 follows, in which the storage capacity of the storage system is divided among the logical hard drives depending on the predetermined parameters.

[0097] In this embodiment, the entire capacity of the system hard disk 11 is allocated to the logical system hard disk 24. Likewise, the entire capacity of the M hard disk 9 is allocated to the spooling memory 17.

[0098] The capacity of the cache hard drive 10 is divided for the five print data cache memories 18.1-18.5.

[0099] If the individual print jobs are quite large, a long loading time is required to load the print jobs from the spooling memory 17 into the print data cache memory 18. In this case, it is necessary that the print data cache memory 18 be sufficiently large so that there is enough capacity for one or more further print jobs to be transmitted to the printer 3 while another print job is being loaded into the same print data cache memory 18.

[0100] The minimum size of the print data cache 18 must be such that it has enough capacity to accept at least two print jobs, allowing one of the two print jobs to be transferred from the print data cache 18 to the printer 3 and the other print job to be loaded from the spooling memory 17 into the print data cache 18. However, experience has shown that this minimum size is insufficient in practice, especially when there is a high print data stream and when the size of the print jobs varies considerably. Therefore, the size of the print data cache 18 should be chosen to be larger the larger the print data stream and the greater the variance of the average print job size.

[0101] The available storage capacity of print data cache memory 18 is therefore distributed as evenly as possible among the individual print data cache memory locations 18 by the configuration module 23, with this distribution being weighted primarily according to the average size of the print jobs. If the average size of the print jobs varies considerably, it is advisable to slightly increase the capacity of the corresponding print data cache memory locations 18. If the data streams are quite high, it is also advisable to increase the capacity of the print data cache memory locations 18 and / or, if different cache storage media are present, to assign the corresponding print data cache memory locations 18 to a faster cache storage medium.

[0102] This weighted, even distribution of the cache memory capacities to the individual print data cache memories 18 ensures efficient and continuous transmission of print jobs from the individual print data cache memories 18 to the printing devices 3.

[0103] The procedure ends with step S6.

[0104] Once the storage system of print server 2 has been configured, the corresponding logical hard drives can be formatted into the appropriate formats.

[0105] As described above, logical hard drives are not necessarily limited to a single storage medium ( Fig. 3) The configuration module can allocate 23 capacities from a storage medium to any logical hard drive. This allows the capacity of the logical hard drives to be adapted to the requirements.

[0106] Reconfiguration may be necessary if the system is changed. For example, connecting three new printers may increase capacity requirements. Connecting additional storage media also requires reconfiguration.

[0107] Another possibility is that reconfiguring the system does not require reformatting all logical hard drives. The increased or decreased capacities are allocated to the respective logical hard drives by reassigning the areas on the storage media.

[0108] An additional possibility is to assign multiple printing devices to a single print data cache 18. The print data cache 18 then has several sub-areas. This is particularly effective if two print data caches 18 have different read and write speeds. Depending on the requirements of a printing device 3, it can be assigned to either one or the other print data cache.

[0109] However, it can also be assigned to both simultaneously, in order to receive data from one or the other print data cache 18 depending on the print job.

[0110] The following is a further embodiment of a method for configuring the storage system of printing system 1 described above ( Fig. 1 to 12) are explained. The configuration is performed by configuration module 23.

[0111] First, the automatic determination of the purpose, order, and size of the storage media is described ( Fig. 6a). The procedure begins with step F1.

[0112] The next step (F2) checks whether print system 1 already includes logical hard drives. If yes, it proceeds to step F22. If no, the next step is F3, which checks whether only default parameters for one or more storage media are present. If they are, step F4 sets the calculated size, data rate, and / or type for the one or more storage media.

[0113] If no default parameters are present, step F5 checks whether only benchmark parameters are available. If yes, the measured size, data rate, and / or type are set for the one or more storage media (step F6).

[0114] In the next step, F7, it is checked whether both default and benchmark parameters are present. If yes, in step F8 both parameter types are combined and the parameters for one or more storage media are set.

[0115] In the following step F9, it is checked whether the printing system 1 includes more than three storage media. If yes, step F10 checks whether the predetermined parameters include instructions for assigning these storage media. If yes, the process continues to step F18. If the predetermined parameters do not include instructions for assignment, a storage medium (I) is assigned to the storage medium with the smallest capacity that still exceeds a predetermined minimum capacity of, for example, 600 GB (step F11). The largest storage medium is assigned to a storage medium (II), and the remaining storage media are assigned to storage media III, IV, and so on.

[0116] If print system 1 has no more than three storage media, step F12 checks whether print system 1 has three storage media. If so, step F13 checks whether the predetermined parameters include instructions for allocation. If so, the process continues to step F18; otherwise, the storage media are allocated as follows: Storage medium I is allocated to the storage medium with the smallest capacity and a capacity greater than 600 GB (step F14). Storage medium II is allocated to the largest storage medium, and the remaining storage medium is allocated to storage medium III.

[0117] If print system 1 does not include three storage media, it is checked whether print system 1 includes two storage media (step F15). If so, in step F16 the storage medium with the smallest capacity and a capacity of at least 600 GB is assigned to storage medium I. The largest storage medium is assigned to storage medium II.

[0118] If the printing system does not include two storage media, step F17 checks whether printing system 1 includes a single storage medium. If yes, the single storage medium is henceforth referred to as storage medium I. The next step is F26.

[0119] The following steps describe the process when the predetermined parameters include instructions for assignment ( Fig. 6b). The use of predefined and / or benchmark parameters to begin the allocation / sequencing of storage media starts with step F18. Next, the capacity and throughput are allocated to storage medium I (F19). The throughput should be, for example, between 200 and 600 MB per second, and the capacity, for example, between 600 and 1200 GB. In the next step, F20, the remaining largest storage medium is allocated to storage medium II, where the throughput should be, for example, greater than 200 megabytes per second and the capacity, for example, greater than 600 gigabytes. In the next step, F21, the remaining storage media are allocated as storage medium III, IV, etc. The next step is S26.

[0120] The following describes the use of predefined assignment parameters ( Fig. 6c). This procedure can be used in particular when a server with identical hardware and / or configuration needs to be replaced. The procedure begins with F22.

[0121] In step F23, the mapping parameters are read from a configuration file.

[0122] In the following step F24, it is checked whether the storage media / logical hard disks assigned by the allocation parameters are present in print system 1 and do not generate an error message. If they are present in print system 1 and do not generate an error message, the process continues to step 51. If they are not present in the print system and / or generate an error message, the corresponding storage media and / or logical hard disks are marked, and the next step is also step F51.

[0123] The following explains the procedure for determining a standard capacity of a logical hard disk ( Fig. 7a). A standard capacity is a default capacity value assigned to the logical disk by configuration module 23. The procedure begins with step F26.

[0124] In the following step F27, the default capacities of the logical system hard disk are set as follows: - Logical UEFI hard drive of 0.2 GB - Logical “ / ” (root) hard drive of 75 GB - Logical "var" hard drive of 25 GB - Logical "swap" hard drive up to 2 GB - Logical "service" hard drive of 50 GB, with a minimum size of 30 GB. - Logical “benchmark” hard drive of 15 GB.

[0125] The next step, F28, checks whether a normal and a security setting are required and whether the storage medium capacity is 1 ≥ 1,200 GB. If YES, proceed to step F48.

[0126] If NOT, step F29 checks whether the capacity of storage medium 1 is > 1,800 GB. If YES, step F30 sets the default capacity of the logical database storage to 100 GB, the default capacity of the logical diagnostic storage to 100 GB, and the default capacity of the logical virtual machine storage to 600 GB. The process then continues with step F37.

[0127] If the storage medium capacity is between 1,200 GB and 1,800 GB (step F31), then in step F32 the default capacity of the logical database storage is set to 100 GB, the default capacity of the logical diagnostic storage to 75 GB, and the default capacity of the logical virtual machine storage to 400 GB. The process then continues with step F37.

[0128] If the storage medium capacity is between 600 GB and 1,200 GB (step F33), step F34 sets the default capacity of the logical database storage to 50 GB, the default capacity of the logical diagnostic storage to 50 GB, and the default capacity of the logical virtual machine storage to 75 GB. Then it continues with step F37.

[0129] If the capacity of storage medium 1 is ≤ 600 GB, an error message is displayed indicating that the capacity of storage medium 1 is too small (step F35). The procedure then ends with step F36.

[0130] The following describes further steps for determining the standard capacity of the logical hard drives ( Fig. 7b). The procedure begins with step F37.

[0131] In the following step, F38, it is checked whether both a normal and a security setting are required. If yes, in step F39, the remaining capacity is allocated to the logical disks using predefined ratio parameters. This is followed by step F41.

[0132] If no normal or security settings are required, in step F40 the default capacity of the logical memory for print server control software, hereinafter referred to as Prisma memory, is set to the remaining capacity of storage medium 1. The next step is F41.

[0133] The following describes how the standard capacity of the logical hard disks is allocated to storage media 2, 3, etc. ( Fig. 7c). The procedure begins with step F41.

[0134] In the next step, F42, the default capacity of the logical benchmark memory is set to 15 GB.

[0135] In the following step F43, it is checked whether a normal and a security setting are required. If yes, the remaining capacity is allocated to the logical disks using predefined ratio parameters (step F44). From here, the process continues with step F51.

[0136] If no normal and a security setting is required, in step F45 the remaining capacity on the storage medium is allocated to the logical hard drives.

[0137] In the following step, F46, it is checked whether there is another storage medium. If YES, the next step is F41 again.

[0138] If this is not the case, then in step F47, storage medium II is assigned to the logical spooling memory, also called print data memory, and / or to the logical security pooling memory, also called print data secure memory, and storage medium III, IV, etc. are assigned to the print data cache memory and / or security print data cache memory. The next step is F51.

[0139] The following describes a procedure for determining the standard capacities of the logical disks of a storage medium 1, provided that a normal and a security area are present ( Fig. 7d). The procedure begins with step F48.

[0140] Step F49 checks what the capacity ratio between the normal and the safety area should be.

[0141] In step F50, the default capacity of the logical database storage, the logical diagnostic storage, and the logical virtual machine storage is set using the capacity ratios. From here, the process continues with step F37.

[0142] The following describes a procedure for displaying a user suggestion and receiving input of changes ( Fig. 8a). The procedure begins with step F51.

[0143] In the following step F52, the capacity of the logical hard disks is adjusted after the capacity of a logical hard disk has been increased and / or decreased.

[0144] In the subsequent step F53, each storage medium is displayed with its logical hard drives and capacity allocation.

[0145] Next, the system asks whether storage medium I should be replaced with another storage medium. Step F54 includes both a prompt for user input and a check to see if that input has been entered.

[0146] The query is a prompt to the user, requiring them to make a decision. This prompt is displayed in a graphical user interface (GUI). The user must respond to this prompt by choosing between two states, labeled YES and NO.

[0147] It is also possible to check a box, which corresponds to, for example, YES. Leaving the box unchecked would correspond to NO.

[0148] The user can also be supported in their decision by a preset value (default value). In this case, the user must actively change this preset decision, for example, by changing a value from NO to YES.

[0149] Another possibility is to give the user a fixed time limit to make a decision. After this time has elapsed, a predefined decision is made. For example, a software window with the corresponding prompt can open in the GUI, and if the user does not enter anything after a predetermined time period of, say, 10 seconds, the state "NO" is selected and the window closes.

[0150] The validation process analyzes the user's input. It determines whether the user has selected YES. Depending on the choice, YES or NO, a different step is executed next.

[0151] Such combined user actions, which involve both a prompt for input and a check (decision) as to whether it has been recorded, are represented by an octagon in the flowcharts. In the following, selecting YES means triggering a user action, and selecting NO means not triggering it.

[0152] If the user confirms during input verification that storage medium I should be replaced with another storage medium, step F55 checks the capacity and throughput of both storage media to be replaced. Step F56 then evaluates whether the replacement can be accepted. If yes, both storage media are replaced in step F57, after which the process continues with step F26. If the replacement cannot be accepted, the process continues with step F51.

[0153] If user action F54 was not triggered (NO), step F58 checks whether other storage media should be replaced. In step F59, the capacity and throughput of both storage media are checked. In step F60, it is evaluated whether this can be accepted. If YES, the two storage media are replaced in step F61. This then proceeds to step F41. If it cannot be accepted, step F51 follows.

[0154] If user action F58 was not triggered, step F62 checks whether the capacity of a logical hard disk on storage medium I should be increased or decreased. If this was triggered, the maximum capacity of storage medium 1 is checked in step F63. Step F64 evaluates whether a change in capacity can be accepted. If yes, the next step is F65; if no, the next step is F51.

[0155] If the user has not made any capacity changes or if the change has been accepted, step F65 asks whether the user wants to assign a new logical hard drive to a separate storage medium. If so, step F66 checks the maximum capacity. Step F67 evaluates whether this can be accepted. If yes, the next step is F68; if no, the next step is F51.

[0156] If no new logical hard drive was assigned, or if the assignment was accepted, step F68 checks whether a user wants to designate a logical hard drive as a security drive. If yes, step F69 checks whether this is possible. If no, the next step is F51. If yes, a security marker is set for this logical hard drive in step F70, and the next step is F51.

[0157] If no logical hard drive has been designated as a backup drive, step F71 prompts the system to ask whether a RAM storage medium should be added to the configuration. Step F72 checks whether this can be accepted. If NOT, the process continues to step F51; if YES, this is saved as a parameter (step F73), and the process continues to step F51.

[0158] If no RAM storage medium is to be added to the configuration, the system checks whether only one virtual machine, such as the integrated viewing software IVS VM, is to be installed (step F74). If yes, the capacity of the logical virtual machine memory is reduced (step F75). The next step is step F76.

[0159] Regardless of whether the user action was triggered after step F74 or not, step F76 prompts the system to decide whether to install another virtual machine, such as the TrueProof VM screen inspection system from OCÉ. If yes, step F77 increases the capacity of the logical virtual machine memory. The next step is F78.

[0160] In step F78, the user has several actions available: - Abort, which leads to the end of the procedure (F79), - Acceptance (F80), which is used to check whether this logical hard drive exists (F82), and - Deleting and creating existing logical disks (F81), which is continued with step F89.

[0161] If the check to see if the logical hard drive exists (step F82) reveals that it does, the next step is F78.

[0162] If this is not the case, in step F83 the logical hard disk is created on the storage medium according to the selected type and security marking.

[0163] If a RAM storage medium has been specified, a logical RAM disk will be created (step F84).

[0164] In the following step, F85, the logical hard drives are mounted.

[0165] In the next step (F86), information about the storage media and logical hard drives is saved in a secured file (encrypted / md5 secured).

[0166] A user is notified about the product purpose via the logical hard drives (step F87).

[0167] The procedure ends with step F88.

[0168] The following describes how to handle a reassignment of storage media ( Fig. 8b). The procedure begins with step F89.

[0169] First, the printing process is interrupted (step F90).

[0170] Next, data is backed up to the relevant logical hard drives (step F91).

[0171] In step F92, the relevant logical hard drives are deleted.

[0172] Next, new logical hard disks are created on the storage media (step F93).

[0173] The next step is to restore the data to the new logical hard drives (step F94).

[0174] In the following step, F95, the new logical hard drives are mounted.

[0175] In step F96, information about the storage media and logical hard disks is written to the secured file (encrypted / md5 secured).

[0176] In step F97, the user is notified about product information for the available logical hard drives.

[0177] In step F98, printing is resumed.

[0178] The procedure ends with step F99.

[0179] The following describes a procedure for adding logical hard disks during operation ( Fig. 9). The procedure begins with step F100.

[0180] First, configuration parameters are read from a configuration file via current storage media and / or logical hard disks (step F101).

[0181] The following step checks whether the corresponding storage media and / or logical hard disks exist and do not display any error messages (step F102). If they do not exist or display error messages, the storage media and / or logical hard disks are marked in step F103.

[0182] If they exist and do not display an error message, step F104 checks whether a security function is desired. If so, step F105 allocates the capacity and assigns it to the logical security disks, and the proposal is then displayed to a user.

[0183] Step F106 checks whether all standard logical hard disks exist. If so, step F107 suggests using the additional logical hard disk as an additional print data cache. This is followed by step F51.

[0184] The following describes the procedure for switching between a logical hard drive and a logical backup hard drive ( Fig. 10). It begins with step F108.

[0185] First, the printing process is interrupted (step 109).

[0186] The following steps unmount the logical database, diagnostics and print data storage as well as the print data cache storage (step F110).

[0187] Step F111 checks whether a normal logical hard drive was active. If so, a logical security hard drive is mounted in step F112. In the following step (F114), the system switches to security mode. The next step is F115.

[0188] If no normal logical hard drive was active, a normal logical hard drive is mounted in step F112. Then, the system switches to normal mode (step F113).

[0189] The printing process is then restarted (step F115). The procedure ends with step F116.

[0190] The following describes a procedure for checking storage media and / or logical hard disks during startup ( Fig. 11). The procedure begins with step F117.

[0191] First, in step F118, information about the current storage media and / or logical hard drives is read from a configuration file.

[0192] Step F118 checks whether the storage media and / or logical hard drives exist and whether there are any error messages. If they do not exist and / or an error message is present, the corresponding storage medium and / or logical hard drive is selected (step F120). The next step is F121.

[0193] If the logical hard disks and / or storage media exist and there is no error message, then in step F121 the user is notified about the storage media and / or logical hard disks with error messages.

[0194] In the following step, F122, the system checks whether the print data cache has issued an error message. If so, step F123 checks whether the logical hard drive can be repaired. If yes, the logical hard drive is repaired (step F124). The user is then informed about the product change and the need to re-enter data (step F125), at which point the process ends.

[0195] If the logical hard drive cannot be repaired, the system checks whether multiple print data caches are available (step F126). If so, the user is informed about the new logical hard drive (step F127). The procedure then ends with step F128.

[0196] If the print data cache did not issue an error message, the logical hard drive containing the error message is deactivated in step F129. The system startup is stopped in step F130. This is followed by step F89.

[0197] The following describes a method for monitoring storage media and / or logical hard drives during operation ( Fig. 12). The procedure begins with step F131.

[0198] In the first step, F132, storage media and / or logical hard drives are monitored.

[0199] Step F133 checks whether at least one of the storage media has a capacity utilization of over 80%. If this is not the case, the procedure is restarted with step F131.

[0200] If capacity utilization exceeds 80%, the user is informed in step F134.

[0201] Step F135 checks whether at least one of the logical hard drives has a capacity utilization of over 90%. If this is not the case, the procedure is restarted with step F131.

[0202] If a logical hard drive has a capacity utilization of over 90%, step F136 checks whether capacity is available on one or more other logical hard drives or whether an empty storage medium is available.

[0203] If this is the case, the setup for a new logical hard drive will begin in step F137.

[0204] In step F138, the user can choose whether to accept the re-allocation of the logical disk. If this is declined, the process restarts with step F131. If, however, the re-allocation is accepted, the process continues with step F51.

[0205] In the exemplary implementations described above, certain configurations are set and monitored automatically. The numerical values ​​given above, as well as the number of storage media, logical disks, and virtual machines, are examples that may vary accordingly in other configurations of printing systems. In other exemplary implementations, the assignments of the logical disks to the storage media, the capacities of the logical disks, and the designations of the logical disks may also vary. Individual process steps from F1 to F138 may be in a different order and / or omitted. Additional process steps may also be added. List of reference symbols 1 printing system 2 print servers 3 Printing device 4 data lines 5 Internet 6 Client 8 Spooling unit 9 MB hard drive 10 Cache storage medium 11 System hard drive 12 Print Data Generation Module 13 Input module 15 Print data service 16 Spooler module 17 Logical M disk / spooling memory 18 Logical cache storage medium / print data cache storage 19 Backend Module 20 Print module 22 Capacity reserve 23 Configuration module 24 logical system hard drive

Claims

[1] Method for configuring a storage system of a print server (2) for digital high-performance printing systems (1), wherein the storage system is designed to store an operating system and print jobs and other files and has one or more storage media (9), and one or more printing devices (3) are connected to the print server (2), wherein the storage media (9) are automatically set up depending on predetermined parameters of the high-performance printing system (1), wherein the predetermined parameters comprise at least benchmark parameters and the benchmark parameters are measured parameters which each represent a specific property of the print server (2) and / or printing device (3), wherein the following steps are carried out for the automatic setup: - Recording the predetermined parameters, - Determination of a specific number of logical hard disks depending on the predetermined parameters, - Assigning the logical hard disks to at least one print data cache memory depending on the predetermined parameters, and - Distribution of the storage capacity of the storage system to the logical hard disks depending on the predetermined parameters, wherein the configuration of the print data cache memories (18) is started when a change in the printing system (1), ie a printing system change, is detected, which causes a changed load on the print data cache memories (18), and wherein detecting a pressure system change is performed using one or more of the following methods: - monitoring predetermined parameters which reflect the system status of the printing system (1), wherein, in the event of a change in such a parameter, it is checked whether this is a relevant printing system change in order to start setting up or updating the storage capacity of the print data cache(s) (18), - monitoring the print data streams in order to start configuring the storage capacity of the print data cache(s) (18) in the event of a relevant change, - monitoring the print data cache memories (18) to detect an overload or underload of one of the print data cache memories (18) in order to start configuring the storage capacity of the print data cache memory(s) (18) at a predetermined overload or underload. [2] Method according to claim 1, characterized bythat the predetermined parameters comprise default parameters, wherein the default parameters are parameters entered by the user or parameters entered by the user and calculated therefrom. [3] Method according to claim 1 or 2, characterized by that when the storage capacity of the storage system (9) is distributed among the logical hard disks, one or more print data cache memories (18) are assigned to the logical hard disks. [4] Method according to one of claims 1 to 3, characterized by that the predetermined parameters for determining the number of logical disks include one or more of the following parameters: - Number of storage media, - Type of storage media, - Number of printing devices, - Print data streams required by the respective printing devices (3) to enable uninterrupted printing, - average size of the print jobs to be loaded into the respective print data caches (18), and / or - average load on the print data caches (18). [5] Method according to one of claims 1 to 4, characterized by that the number and distribution of the storage capacity of the logical disks is based on one or more of the following criteria: - the number of logical hard disks is proportional and in particular linearly proportional to the connected printing devices, - the number of logical disks is proportional and in particular linearly proportional to the number of storage media, - the storage capacity of the print data cache memory is proportional and in particular linearly proportional to the respective print data stream and / or to the average load of the print data cache memory (18), and / or - the storage capacity is inversely proportional and, in particular, linearly inversely proportional to the number of storage media(9). [6] Method according to one of claims 1 to 5, characterized by that a pressure system change has occurred if - the utilization of the print data cache memory (18) changes, - the hardware required to transmit print jobs from the print server (2) to the printing devices (3) changes, - the average print data stream changes by at least 10%, preferably by at least 25% and in particular by at least 50%, over a period of at least one hour, preferably of at least ten hours and in particular of at least 24 hours, - one or more pressure devices (3) are connected, removed or put into maintenance mode, - the available storage capacity of the cache hard disks (10) changes, e.g. by adding, removing or replacing a cache hard disk (10), and / or - the assignment of a printing device (3) to the print data cache memory (18) changes, e.g. due to a manual change. [7] Method according to one of claims 1 to 6, characterized by that the spooling unit (8) has a spooling memory (17), wherein the spooling memory (17) is provided in addition to the print data cache memory (18) and is designed to temporarily store print jobs in order to forward them to the print data cache memory (18). [8] Method according to one of claims 1 to 7, characterized bythat the total capacity of the spooling memory (17) is greater than the capacity of the print data cache memory (18), in particular the capacity is many times greater, at least 2 times, preferably at least 5 times and if possible at least 10 times. [9] Method according to one of claims 1 to 8, characterized by that the capacity of the operating system memory is not greater than 150%, preferably not greater than 125% and in particular not greater than 110% of the size of the operating system. [10] Method according to one of claims 1 to 9, characterized by that the print data cache memory (18) is automatically formatted. [11] Method according to one of claims 1 to 10, characterized by that the print data cache memory (18) is automatically emptied by overwriting each memory area of ​​the print data cache memory (18) one or more times with random data. [12] Print server for digital high-performance printing systems, comprising a CPU, a spooling unit (8) which comprises a print data cache memory (18), wherein the print server (2) is provided with a computer program which is designed to carry out the method according to one of claims 1 to 11. [13] Print server according to claim 12, characterized by that the print server has a plurality of backend modules (19) which read print jobs from the print data cache memory (18) respectively assigned to it and forward them to one or more printing devices (3), wherein preferably the number of print data cache memories (18) is equal to the number of backend modules (19). [14] Print server according to claim 12 or 13, characterized by that several storage media are integrated into a storage management system, in particular a software RAID system, and together form a logical cache hard disk (18).

Citation Information

Patent Citations

  • Process for operating a print server for digital high-performance printing systems

    DE102016125020A1

  • Process for operating a print server for digital high-performance printing systems

    DE102016125023A1

  • System and Method for Metadata Discovery and Metadata-Aware Scheduling

    US20130238785A1

  • Capability-based abstraction of software-defined infrastructure

    US9851933B2