Networker

Re: [Networker] NetApp Backup

2002-09-19 15:50:34
Subject: Re: [Networker] NetApp Backup
From: "Glassman, Adam" <adam.glassman AT ATTWS DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Thu, 19 Sep 2002 12:50:18 -0700
I would add only that cloning and staging NDMP save sets is not supported.
Also, I would stress that if you want to use NDMP to back up 2 filers, you
will need at least 1 drive attached to each filer.  These drives would not
be available to back up other servers.  Full backups of a filer when you are
limited to one drive and one target session can take quite a while depending
on the capacity of your filer.  It takes us ten and a half hours to do a
full back up of 250GB using one drive on a SCSI connection.

Adam Glassman
System Administrator
AT&T Wireless Services

-----Original Message-----
From: Shelley L. Shostak [mailto:sls AT QSTECH DOT COM]
Sent: Thursday, September 19, 2002 12:09 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] NetApp Backup


On Thu, 19 Sep 2002, SUBSCRIBE NETWORKER Anonymous wrote:

> Subject: [Networker] NetApp Backup
>
> Dear Networkers,
>
> I was wondering if any of you guys were using Legato for backing up your
> Network Appliance boxes. I currently have 2 filers that i am backing up
> to
> a Legato server running Solaris 2.8 over NFS. I mount the NetApp volumes
> onto the legato server and then backup those mount points.
>
> I am not sure this is the best thing to do in terms of performance.
>

We have two NetApps and are using NDMP to dump our NetApps to locally
attached
drives.  There are pros and cons to using NDMP and I will summarize them
briefly.  Note that the problems are due primarily to the limitations of the
NDMP protocol and not to lack of features with Legato or NetApp.

Advantages:

  Performance
    With locally attached drives, performance generally increases unless
    you have a fast, dedicated network between your filer and backup server.
    Reading over NFS is likely to create a performance hit as well.
  Point-in-time dumps
    The filer makes a snapshot and writes the snapshot to tape, thus
ensuring
    a clean point-in-time representation of your files.

Disadvantages:

  Loss of Legato-like feature with NDMP
    NDMP dumps essentially use the old unix "dump" semantics.  You therefore
    lose the following Legato functionality:
      - no incr dumps, just level 0-9
      - nwrecover indexes for a given browse time only contain files which
        were written to tape on the previous backup
      - can only recover 10,240 files with GUI/recover command
  Performance
    Target sessions per tape drive is limited to 1, thus it requires faster
    NetApps to be able to keep a single tape drive writing a maximum speed.

My complaint to NetApp about broken restores (bugid 76695) has been fixed.

My recommendation is to use a combination of filer snapshots for by-file
recovers and rely on tape backups for disaster recovery.

That is my little soapbox for NDMP vs nonNDMP dumps.  Feel free to jump in
and
add to the foray!

Shelley

--
Note: To sign off this list, send a "signoff" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

<Prev in Thread] Current Thread [Next in Thread>