Questions from another newbie

[Jeremy Shoup]

I'm relatively new to cups, but have not been able to find any info on this topic.  I like the centralized management of a print server (actually 2) but also want to be able to have local print queues setup on a few servers.  They're all on the same subnet.  We're currently using lprng and we have some "dummy" printers that just drop jobs to /dev/null that I don't want to have to transmit on the network if it can be helped.
If necessary I suppose that those jobs can use the network print server, but I am also curious to know how things are handled by cups as a client if it can't connect to the server.  Thus far when I bring down the print server and try to print a job I get an error back after about 30 seconds.  With lprng, which I am more used to, the jobs would queue until the print server comes back.  I should imagine that is also possible in cups, but I haven't figured out how yet.  Any suggestions?
One final question... I've got two servers and I'm running a high-availability tool to manage a virtual IP address between them (switches to the backup if the primary goes down).  Any suggestions on how I can keep the cups configurations in sync between them?  Unfortunately I really have a tendency to only manage the primary properly... Also, can I have a "Listen" line in cupsd.conf on the backup for the virtual IP even if it is not in possession of the virtual IP?

Jeremy