|
Here's my breakdown, with Gb/hr units in "(..)" so you can use good
comparisons:
DMOV1+nsrV4.2b (33Gb/hr)
DMOv2+nsrV4.2b (70Gb/hr??)
The TZ87 (855) drive gets appx 1.2Mb/sec (4.32Gb/hr)
Ethernet gets appc 800Kb/sec (0.00288Gb/hr)
8400 backplane is appx 1.2Tb/sec (no worries)
8400 TLIOP is appx 1.2Tb/sec (no worries)
SCSI bus (fast/wide) is 20Mb/sec (72Gb/hr)
RZ29b disks are about 4.2Mb/sec (15.12Gb/hr)
Find your slowest point in the "data path", and that's how fast your Database
will backup. I suggest not backing up across Ethernet, and I suggest running
NetWorker and Oracle on the same system - when DMOV2 *and* the next NetWorker
Server come out, they'll scream, but only with NO NETWORK and *fast* tapes
(for example, multiple TZ89's).
Right now, it appears you'll get appx 8-9 hrs total backup time, best case.
"n"*DB-disk <--> 8400 <--> EBU <--> DMO <--> NSR <--> 2*TZ87
The more tapes you can connect, the faster you'll go. Use NetWorker's
session/device and parallism to control activation of devices in parallel.
------------------------------
Using DMOV1 there is no ASE awareness. You could try setting the NSR_CLIENT
environment variable to the service and see if that results in saving
the data to the proper client index file (you could see that when the save
is happening, by looking at the nwadmin GUI "sessions" display). Naturally,
you need to pre-define the client resource to the NetWorker Server.
|
| I will second the recommendation that large database backups
be done locally if possible. Also note that I have a TZ877
(TZ87 jukebox) that runs at 2.4 MB/sec reliably. So, that works out
to 8.4 GB/hr per TZ877.
Put the drives where they are needed most (i.e. two on the big-db-system
and one on the small-db-system) and get going. If/when the database
grows, and backup performance is not sufficient, you've got a simple
path to improve it by adding more/faster tape drives.
Kevin Farlee
|