The information contained in this E-Mail and any subsequent
correspondence is private and is intended solely for the intended
recipient(s).  The information in this communication may be
confidential and/or legally privileged.  Nothing in this e-mail is
intended to conclude a contract on behalf of QinetiQ or make QinetiQ
subject to any other legally binding commitments, unless the e-mail
contains an express statement to the contrary or incorporates a formal Purchase Order.

For those other than the recipient any disclosure, copying,
distribution, or any action taken or omitted to be taken in reliance
on such information is prohibited and may be unlawful.

Emails and other electronic communication with QinetiQ may be
monitored and recorded for business purposes including security, audit
and archival purposes.  Any response to this email indicates consent
to this.

Telephone calls to QinetiQ may be monitored or recorded for quality
control, security and other business purposes.

QinetiQ Limited
Registered in England & Wales: Company Number:3796233
Registered office: 85 Buckingham Gate, London SW1E 6PD, United Kingdom
Trading address: Cody Technology Park, Cody Building, Ively Road, Farnborough, Hampshire, GU14 0LX, United Kingdom
http://www.qinetiq.com/home/notices/legal.html

Date: Wed, 13 May 2009 09:50:42 -0400
From: "K. M. Peterson" <kmp.lists+bacula-users AT gmail DOT com>
Subject: Re: [Bacula-users] Delay between end of despool and spooling
        again
To: Mattinson David <DPMATTINSON AT qinetiq DOT com>
Cc: bacula-users AT lists.sourceforge DOT net
Message-ID:
        <44b17ca60905130650g113b04d9vfd372ecdd416540b AT mail.gmail DOT com>
Content-Type: text/plain; charset="iso-8859-1"

Dave,

A really interesting question this is.  I can't answer it.

But, I would ask you this: if the spooling time elapsed is near to the
despool time, then why spool at all?

Our setup was set up originally with all jobs spooled (and we have the
same
Quantum Superloader/Drive that you do); I realized after 8 months that
some
of the jobs were able to acquire data quickly enough that they did not
need
to use spooling at all - and for those jobs, we dropped the backup time
by
over 50%.

_KMP

**************

The reason I use spooling is that I use only one backup device (the
autoloader) and one pool for all my backups.  The other clients I have
are
1. Windows 2003 connected by 100M Ethernet
2. Solaris 2.6 connected by 10M Ethernet
3. Windows XP SP2

Spooling has been proved to be the more efficient in (1) and absolutely
essential in (2).  Solaris 2.6 and Windows XP don't have enough data to
cause a spool again, Windows 2003 has a similar effect to the
director/storage server local drives, but the generation of the full
spool file takes longer.  I thought the local data had less complication
when run on it's own to isolate the problem.

On reviewing the spool.c code, the only obvious points where a delay may
occur are in the set_jr_job_status or dir_send_job_status if a director
(or its TCP port) has gone to sleep for some reason.

Dave

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users