Technical data

-v
Prints messages as it validates attributes provided on the command
line.
5.1.4 Backing Up Object Databases
You should make routine backups of your print system object databases to
protect against inadvertent data loss or data corruption. If a failure occurs
and your object databases become inaccessible or corrupt, you can restore
the system from a recent backup and avoid the need to recreate your print
system environment from scratch.
You should consider backing up the following areas:
• The /var/pd/odb directory contains the server databases. Backing up
this area saves the server, printer, and queue configurations as well as
job and document objects that are stored in the spooler.
• The /var/spool/pd directory contains the document data files. In most
instances, job data is time sensitive and not as valuable in a system
restoration as the printer and queue information.
• The /etc/printers.conf file contains the local file name on a server
host. Local name entries are created automatically when servers start
as long as the databases in /var/pd/odb are intact. However, you can
have entries for servers, printers, and queues that reside on other hosts
stored in this file. These entries are not added on startup, so it is wise
to back up this file.
Server databases should be backed up when the servers are not running.
This ensures that the backup copies are internally consistent. Routine
backups can be performed at a time of day or week when the print system
can be temporarily shut down for the duration of the backup.
5.2 Configuring Server Object Attributes
A number of server object attributes can be set or modified. Table 5–1 lists
the attributes and describes what effect they have on the server.
Table 5–1: Server Object Attributes
Attributes Description
access-control-list Specifies the authorized users of the
spooler or supervisor.
descriptor A text string describing the server.
Creating and Managing Servers 5–5