Unfortunately the configuration and installation of 2.4.1p1 was before my time here.
Would using ufsdump the way we are slow the backups down. I've recently with the addition of a new DLT drive split up my backups as they were taking 22 hours to backup less than a DLT's worth of data. Now I've split them up, our fileserver is also a tapeserver but is only backing up itself. It starts at 10pm and is still running now(10.41am) having dumped 6.2GB and the 2 largest partitions comprising of 13GB still to be dumped. As you can imagine this is not satisfactory as amanda is trying to backup these partitions as users are accessing them. This server is a sun E450 and is only backing up it's internal disks. So I'm running out of ideas as to why it's so slow. Any ideas? On 8 Apr 2002, at 15:15, John R. Jackson wrote: > >... how would you explain > >(messed up index file or no) how it worked with bin as the user > >under 2.4.1p1? ... > > I don't think it was. I don't see any way it could have been working > unless you were running it as root. > > Well, actually, you might have been able to configure Amanda using > --with-rundump. Do you recall doing that? > > >Was there something changed between 2.4.1p1 > >and 2.4.2p2 that would affect this? > > No. > > >I don't want to appear to be nagging ... > > No problem. I'd be curious how you had it working, too. > > >David Flood > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] ----------------------------------------- David Flood Systems Administrator [EMAIL PROTECTED] Tel: +44 (0)1224 262721 The Robert Gordon University School of Computing St. Andrews Street Aberdeen -----------------------------------------
