Networker

Re: [Networker] Long NDMP Backups

2008-02-25 13:34:18
Subject: Re: [Networker] Long NDMP Backups
From: Matthew Huff <mhuff AT OX DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 25 Feb 2008 13:30:48 -0500
Are you sure they are really using the 2nd network? Networker doesn't make it 
as easy as it should. Here are the steps:

 

1)      Setup DNS names for the 2nd interfaces. For example:

NetApp Servers

Host: netapp_a, IP: 10.1.1.1, backup interface: netapp_a_nsr, IP 10.2.1.1

Host: netapp_b, IP: 10.1.1.2, backup interface: netapp_b_nsr, IP 10.2.1.2

 

Server: legato_a, IP: 10.1.1.3, backup interface: legato_a_nsr, IP 10.2.1.3

 

Make sure that the names and IP resolve via DNS both forward and backwards

 

2)      Save the client ids of the netapp servers in Legato and delete them. 
Re-add them with the "netapp_a_nsr" name but with their old client_id. This 
will preserve their indexes and savesets but will be configured correctly

3)      Under the client properties in Legato, change the tab "Server 
network-interface:" under Globals (1 of 2) to the "legato_a_nsr" interface

4)      Change the "backup command" part of "Apps & Modules" to nsrndmp_save -P 
legato_a_nsr -M -T dump

5)      Configure your netapp MTU to 9000 on the "nsr" interface.  Change your 
legato server MTU to 9000. Configure on your switch interface to a MTU of 9216. 
This is a BIG improvement with gig interface and streaming backups.

6)      Modify some of the TCP settings on your legato server. For example on 
our Sun box, we do:

 

ndd -set /dev/tcp tcp_max_buf    4194304

ndd -set /dev/tcp tcp_cwnd_max   2097152

ndd -set /dev/tcp tcp_xmit_hiwat 1048576

ndd -set /dev/tcp tcp_recv_hiwat 1048576

ndd -set /dev/tcp tcp_tstamp_always 1

ndd -set /dev/tcp tcp_wscale_always 1

 

----
Matthew Huff       | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10577
www.otaotr.com <http://www.otaotr.com>      | Phone: 914-460-4039
aim: matthewbhuff  | Fax:   914-460-4139

From: Troy Kutil [mailto:Troy.Kutil AT milwaukeetool DOT com] 
Sent: Monday, February 25, 2008 12:44 PM
To: EMC NetWorker discussion; Matthew Huff
Subject: Re: [Networker] Long NDMP Backups

 


The backups do run on a separate VLAN, but I am not certain that Jumbo frames 
are enabled. Still new to Netapp and will investigate qtrees. 

Troy Kutil
Phone 262-783-8289
Fax 262-373-5689
Milwaukee Electric Tool 



Matthew Huff <mhuff AT OX DOT COM> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> 

02/25/2008 11:23 AM 

Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
Matthew Huff <mhuff AT OX DOT COM>

To

NETWORKER AT LISTSERV.TEMPLE DOT EDU 

cc

        
Subject

Re: [Networker] Long NDMP Backups

 

                




You could backup the volumes on separate days, but since you are already doing 
a DSA backup (backing up via the net rather than direct backup), you are 
already getting the advantages of parallelization and variable block lengths. 
To increase the parallelization, you can change to backing up by qtree's rather 
than volumes. Each qtree will be parallelized with the backup. Also, the delay 
in the nsrdump is reduced since it has to walk a smaller part of the volume.

Also, do you have the backups on a separate network? We have found by 
separating out the NetApp backups to a different nic on the NetApps and 
different NICs on the backup server and running Jumbo frames, the backup was 
greatly increased (and lowed the CPU overhead on the backup server).

----
Matthew Huff       | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10577
www.otaotr.com     | Phone: 914-460-4039
aim: matthewbhuff  | Fax:   914-460-4139

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of tkutil
Sent: Monday, February 25, 2008 12:13 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Long NDMP Backups

My last backup of ~3TB of data on a NETAPP filer took about 12 hours. I'm on a 
private vlan with an LTO3 tape SCSI conncected to my Networker server. Is that 
an acceptable time to accomplish a backup? I thought I saw on one of the 
postings that I could split up my volumes and backup each up on a separate 
schedule??? Am I halucinating?
ex. 
/vol/vol1 Full on Day1
/vol/vol2 Full on Day2
/vol/vol3 Full on Day3

You get the picture...

+----------------------------------------------------------------------
|This was sent by troy.kutil AT milwaukeetool DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER