As no one has responded, I guess no one else has a clue either. :((

Of course, not having a clue seldom stops me from posting ;)


On Sun, Aug 27, 2006 at 04:56:03PM +0100, Stephen Carter wrote:
> I have 2 physical boxes I'm backing up, one called srv1 and the other called 
> srv2.
>
> srv1 is always backed up correctly, which also has the tape device and runs 
> the amanda backups.
>
> srv2 is a SLES 10 server running 3 virtual SLES 10 XEN guests within it, but 
> I'm treating them as separate physical boxes for the purposes of amanda.
>
> On different nights, different XEN guests fail (including the host, srv2) 
> with a "could not connect" error in the amanda report.
>
> amstatus says 'wait for dumping driver: (aborted:could not connect to data 
> port: Connection timed out)


If I understand the configuration, svr2 has 4 separate installations
or the amanda client.  To amanda it appears as 4 distinct remote hosts.
As you indicate different logical hosts fail nightly, it sounds like
all have also had successful backups, thus the basic config is ok.

Do the 4 logical hosts also have their own separate disks and network
controllers?  Or is a single network interface serving multiple IP
addresses and the hosts have separate partitions on a shared disk(s)?

I ask from the view that amanda considers them distinct and may be
asking for dumps simultaneously from all 4, possibly overloading
the shared resources on the single physical client, svr2.  This
could trigger some timeout mechanism that daily hits different
logical hosts.

Even if you are only running a single dumper so multiple, simultaneous
dumps do not occur on svr2, perhaps the interval between estimates and
dumps is so long that a network timeout is triggered.

These are total guesses, just seeing it they might fly.


-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)