Hi,
I've got a similar setup running here and I must agree the documentation on
SnapImage is 'challenging', to say the least.
Here are a few quick 'gotcha's' to remember.
1. root password on the NetApp ( you fill this in in the client resource on
the Networker server ) can't be longer than 8 characters. Networker uses
this to remotely start a dump on the filer
2. NDMP version on Filer defaults to 4. Networker 6 is version 3. Make them
match.
3. When you setup a tape drive to be used for NDMP backups, you have to
specify a hostname that owns the drive. If your Library is directly
attached to the Networker server, the hostname you specify here can't be
different from the nodename of the server ( hostname command ) of the
Legato Server name. No problem so far, but if you try to backup the NetApp
through a NIC that is not associated with the primary hostname of the
server ( i.e. the name you specified in jbconfig when defining the NDMP
drive ), the data will come through the NIC that IS associated with the
primary nodename ( at least it will try to ). Apparently, ndmp ( or
SnapImage ) passes the hostname and / or IP number ( I forget which, but
it's in the backup.log on the netApp ) to the dump command on the filer,
and Networker has no control over this. SnapImage as used in this setup (
as a NDMP tape server ) is completely seperate from NetWorker. So, if you
want to backup through a specific NIC to a device attached to the networker
server, make sure the hostname controlling the NDMP tape device matches
the name/ip associated with that NIC.
4 Try to keep the NetApp volumes small enough. We run a backup of a volume
770Gb in size, and the the initial phases of the dump (gathering file and
directory info ) take up to two hours. Set you timeout accordingly. After
that, the complete backup takes over 24 hours, using a 9840 over Gigabit,
writing up to 11Mb/sec. Apparently, this is normal speed for such a setup
and seems to indicate the data is not being compressed by the 9840 drive.
5. communication between the NetApp and Networker server is sketchy at best
and doesn't always make sense. You will see backup abort messages on the
filer ( it seems to time out ) and then backup completed successfull on the
Networker side.
6 You may want to stop networker from automatically retrying failed backup
on this one, as they take so long.
Setup of SnapImage is straightforward. I don't seem to remember any
problems there.
Regards,
and good luck
It can take quite some time to get this one working and really know what's
going on.
Dirk Verhoeff
---------------------------------------------------------------------------
This message (including any attachments) is confidential and may be
privileged. If you have received it by mistake please notify the sender by
return e-mail and delete this message from your system. Any unauthorised
use or dissemination of this message in whole or in part is strictly
prohibited. Please note that e-mails are susceptible to change.
ABN AMRO Bank N.V. (including its group companies) shall not be liable for
the improper or incomplete transmission of the information contained in
this communication nor for any delay in its receipt or damage to your
system. ABN AMRO Bank N.V. (or its group companies) does not guarantee that
the integrity of this communication has been maintained nor that this
communication is free of viruses, interceptions or interference.
---------------------------------------------------------------------------
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
