![]() |
![]() |
This section discusses how the backup and recovery procedures relate to print queues, i.e., the physical directories and files relating to the NetWare printing environment. The objects relating to the printing environment (i.e., printer, print queue, and print server objects) which are stored in the NDS are backed up and restored as part of the NDS backup and restore procedures in this chapter.
The print queue proper is a directory entry where network print jobs reside until the actual printing. This directory is named by the object id and has a .QDR extension. The directory entries are located in the \QUEUES directory on a volume chosen by the administrator:
DATA:\QUEUES\05000005.QDR
The directory entries for the print queues are not recreated when you restore the NDS. Therefore, the directory entries must be restored from backup.
There are two file types which are created in the print queue directories which are hidden, system files: a print server ID file and system print information file.
The print server ID file has a .SRV extension and contains the IDs of print servers that are currently attached:
DATA:\QUEUES\05000004.QDR\Q_0005.SYS
The system print information file has a .SYS extension and contains print job information and links to the current print job files:
DATA:\QUEUES\05000004.QDR\Q_0005.SYS
These files are always opened with an access of Deny Read/Deny Write while the print server is active, and therefore cannot be processed by Tivoli Storage Manager. These files will be recreated after a restore when the print server driver (e.g., PSERVER.NLM) is loaded. We recommend that you exclude these files from Tivoli Storage Manager processing.
Network print jobs which are queued to printers exists as files in the print queue directories with a .Q extension:
DATA:\QUEUES\05000004.QDR\00050001.Q
Print jobs which are actively being printed (i.e., status=Active) are opened with an access of Deny Read/Deny Write and therefore cannot be processed by Tivoli Storage Manager. Print jobs which are queued to be printed (i.e., status=Ready) have no special attributes and can be processed by Tivoli Storage Manager as normal files.
Individual administrators must decide whether to backup queued print jobs. Since these files are temporary and can be quite large, we recommend that these files be excluded from Tivoli Storage Manager processing. After a restore, however, you must resubmit the print jobs if they are not processed by Tivoli Storage Manager.
There are two other files related to the print queues which should be mentioned which are used by the print server to reference the printer and print queues: PRINT.id and QUEUE.id. These files reside in a directory entry under \QUEUES which correlates to the print server object id:
DATA:\QUEUES\05000004\PRINT.000 DATA:\QUEUES\05000004\QUEUE.000
These files can be processed normally by Tivoli Storage Manager and thus need no special consideration. These files do not appear to be used in the NetWare 4 and 5 environments, although they are present.
We recommend that you back up the print queue directories but exclude the files contained in these directories since Tivoli Storage Manager cannot open them. To do this, you can specify the following exclude statement in your dsm.opt file:
EXCLUDE <vol>:\QUEUES\*.QDR\*
where <vol> is the volume on which the print queues reside.
If you want to process the actual queued print jobs, you can include these by specifying the following include statement in your dsm.opt file:
INLCUDE <vol>:\QUEUES\*.QDR\*.Q
Note: Do not use the exclude.dir statement to exclude the print queue directories because this will exclude the directory entries from processing.
If the print server drivers reside locally on the NetWare server (i.e., PSERVER.NLM), there are no explicit steps to restore the print environment if you use the include-exclude recommendations in Include-Exclude Recommendations for Print Queues. You can restore the print environment using the restore procedures in this chapter:
Network cards (e.g., HP's JetDirect) can provide print server services which attach directly to the network. In such environments, PSERVER.NLM is not used and special explicit considerations must be made to recreate the necessary .SRV and .SYS files in the print queue directories. To explicitely create these files after all other restore procedures have been accomplished, use the following steps:
After this step, the print queue is fully functional. This procedure has been verified in a JetDirect environment to correctly create the files necessary to make the print queues functional after a restore.