1833771 Members
2361 Online
110063 Solutions
New Discussion

cloning lp config

 
SOLVED
Go to solution
doug mielke
Respected Contributor

cloning lp config

What am I missing here. I've done this before with no problem.

I'm trying to copy my 500+ printer config. from one 11.0 system to another using sam.

sam restore print config runs with no error, and creates most of the files / directories that I need.
I've looked at a few postings on this topic, such as below, and I think I've followed instructions.
I've run Sam restore config and transferqueue

http://forums1.itrc.hp.com/service/forums/parseCurl.do?CURL=%2Fcm%2FQuestionAnswer%2F1%2C%2C0xd2dcf9beca68d511abcd0090277a778c%2C00.html&admit=716493758+1089122942645+28353475


What I dont get are the files under /var/spoo/lp/request/printername

for instance, there is no c00000printername_system name.


Do I have to create these?

5 REPLIES 5
Geoff Wild
Honored Contributor

Re: cloning lp config

Not too sure why that didn't work.

Here's what I do:

/usr/sam/lbin/lpmgr -S -v -xsavedir=/var/sam/lp/ ; cp -r -p /var/sam/lp/lp.new/* /var/sam/lp/

tar cvf /var/sam/lp.tar /var/sam/lp/

ftp/rcp that tarball to remote server.

cd /var/sam/
tar xvf /var/sam/lp.tar

lpshut

/usr/sam/lbin/lpmgr -R -xsavedir=/var/sam/lp/

lpsched -v

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Bill Hassell
Honored Contributor
Solution

Re: cloning lp config

The request directory is never backed up using lpmgr. The contents of the /var/spoo/lp/request/ directory are files (data and control) for job that have not printed. Normally, you would not want these files copied to another server as these files are either in process of being printed or are stuck in the print queue. The transferqueue command is a little misleading in that it does copy printer queues (ie, printer names) but does not save any print jobs. On a normal system, the request directory will have a directory for each printer but nothing in the directory since nothing has been printed on the new system yet.


Bill Hassell, sysadmin
doug mielke
Respected Contributor

Re: cloning lp config

great info Bill,

so is there something prior to my error that I've missed...

the message in the lp log is



can not find or
open /var/spool/lp/request/printername/cxxx
Bill Hassell
Honored Contributor

Re: cloning lp config

The message indicates that the spooler's outputq and/or qstatus are out of sync. Since these files are binary, the easiest fix is to remove the printer with lpadmin -x and then re-add the one printer.


Bill Hassell, sysadmin
Jose Mosquera
Honored Contributor

Re: cloning lp config

Hi,

I've been using continually in a satisfactory way the following procedure:
(On source server)
#/usr/sam/lbin/lpmgr -S -xsavedir=/var/sam/lp
#cd /var/sam/
#tar cvf spool.tar lp/
Put via ftp (binary) the spool.tar file to target server in /var/sam/ directory.

(On target server)
#cd /var/sam/
#mv lp lp.old
#tar xvf spool.tar
#/usr/sam/lbin/lpmgr -R -xsavedir=/var/sam/lp

Although HP doesn't certify this procedure fully, I comment you that it has always worked me.

Don't forget to delete the file spool.tar!

Rgds.