Dear managers,
many thanks for your replies:
Jan Mark Holzer
Tom Webster
Gerardo Blitzer
my question was:
> I would like to use raw disks and /or files as backupmedia
> for DECNSR 4.3/4.4 (SPD says raw disk and files are supported).
> But I don't know, how to configure it - can anyone give me a hint please?
I misunderstanded the word "supported backupmedium" in SPD.
It seems, SPD means backup-source.
I would like to use raw disk as target of backup,
because
- some slow-net-clients blocks our tapedevices for a long time,
- our TL820-Tapelibrary is "high-watermark-filled" (130 backup-clients)
- there is no money for the next time for solution of this problem.
Is in NSR really no disk-caching supported?
How to backup from raw-disk explains Jan Mark Holzer in his excellent answer:
NetWorker is using the rawasm executable to perform
raw device backups.
"rawasm" (it is part of the save command) is a NetWorker
application-specific module that can be used to back up data
from raw partitions on a Digital UNIX system.
On most other NetWorker platforms, rawasm is provided for a fee.
It is included with the NetWorker for Digital UNIX product.
As of NetWorker V4.3 rawasm is now fully supported for
backups (it has been shipped with kit prior to V4.3 but was
not supported at this time).
To use rawasm the following steps need to be performed:
In your /dev directory, create a .nsr file with the contents:
rawasm: rrzxyX rrzzbC
That is, the line should include rawasm: and then a list of the
partitions which you want to back up. Please use the raw device
name (rrz*).
If you are not explicit about which disks to back up, (i.e. if
you were tempted to get lazy and use rrz*) then ALL disks in your
system would be saved with rawasm as you backed up your dev
directory, as well as being backed up via the filesystems.
To test the rawasm setup type the following :
save -s <your-server> -lfull /dev/rz3c (or whatever your dev is)
and monitor on the NetWorker Server GUI.
For each disk (raw partition) you want to save, type in another
save... (using csh syntax):
save -s <your-server> -lfull /dev/rz3c >& /tmp/log1 &
save -s <your-server> -lfull /dev/rz4c >& /tmp/log2 &
save -s <your-server> -lfull /dev/rz5c >& /tmp/log3 &
Just insure the parallelism setting on your server is set high enough
to allow all the appropriate saves to operate simultaneously, and set
the sessions per device to feed the device enough not to starve it.
If you want to see if rawasm is really getting used, add in -vvvv
to the save command, and look for:
Name=`/dev/rrz3c', name=`/dev/rrz3c', fname=`rrz3c'
walk(/dev/rrz3c, rrz3c)
`/dev/rrz3c' change time Fri Jul 24 13:22:32 1998
rawasm queryfunc /dev/rrz3c
rawasm -s /dev/rrz3c
/dev/rrz3c: fid = <800000, 3328>
in the -vvvv output.
Hth,
Jan Mark Holzer
--
---------------------------------------------------------------------------
I Regine Polnick I
I TU Dresden URZ; Zellescher Weg 12/ Wil A104 Briefanschrift: I
I tel : (++49) 351 463-3460 TU Dresden ; URZ/ CS I
I mail: Regine.Polnick_at_urz.tu-dresden.de D-01062 Dresden I
---------------------------------------------------------------------------
Received on Mon Jul 27 1998 - 08:09:36 NZST