Re: [Linux-decnet-user] Restore performance
Brought to you by:
chrissie_c,
ph3-der-loewe
|
From: Patrick C. <pa...@ty...> - 2004-04-21 16:01:20
|
On Wed, Apr 21, 2004 at 11:04:36AM -0300, Gustavo M. Boado wrote: > Well, this was a QUICK response... > Regarding the commands, to perform the backup I use: > > BACKUP /IMAGE/IGNORE=LABEL DKA0: 21.42"OFFLINE password"::PP.BCK/SAVE > > It takes about 20 minutes to backup a system disk with about 600 MB of data. The source is an AlphaStation 200/166 with OpenVMS 7.1 and 10 Mbps network card running through a switch. > 21.42 is the DECNet address of the Linux node. The Linux computer runs a standard 2.4.25 kernel with dnprogs 2.26. It is an Athlon 2200XP with 256 MB RAM and very light load (none at the time of the backup). > > To perform the restore I do: > > BACKUP 21.42OFFLINE password"::PP.BCK/SAVE DKA0:[*...] /BY_OWNER > > Then I do the usual writeboot stuff. > The process works properly but it takes about 4 hours. > The only FAL options I am using (in the dnetd.conf file) are -ae -r /offline > /offline is the exported path. > Standard file copy is fast (I didn't benchmark the system but it looks fine). I changed NSP_MAX_WINDOW to 1 in dn.h to improve the performance of the file copy (as it was suggested somewhere in the net) but the restore performance wasn't improved. That FAL option looks fine. The thing to do is to run fal with -vvvv -ae and have a look at the messages that are being sent. It's possible that BACKUP is setting some optins that FAL doesn't recognise as allowing it to do streaming IO, but I'm guessing here. I'll set up my test box and see if I can find out what's happening. patrick |