Backup Central

I am having issues with excessively long NDMP Backups on a Netapp 2050C. I am running Networker 7.5 sp1. This just started happening about 2 weeks ago, and since then I have tried some of the things I thought fixed this problem once before. I ran a full backup starting Friday night and I still have 3 volumes waiting for backup. 2 of the volumes are close to 1TB in size and at least 1 has limited snapshot space available. Not sure if that is the cause.

This is what I tried so far to fix the problem.
1. Created new clients
2. Made sure that I did not have mixed volumes in my save set

Any suggestions on what to try next or where to look for possible causes?

TIA

On 02 8, 2010, at 9:25 AM, tkutil wrote:

I am having issues with excessively long NDMP Backups on a Netapp 2050C. I am running Networker 7.5 sp1. This just started happening about 2 weeks ago, and since then I have tried some of the things I thought fixed this problem once before. I ran a full backup starting Friday night and I still have 3 volumes waiting for backup. 2 of the volumes are close to 1TB in size and at least 1 has limited snapshot space available. Not sure if that is the cause.

This is what I tried so far to fix the problem.
1. Created new clients
2. Made sure that I did not have mixed volumes in my save set

Any suggestions on what to try next or where to look for possible causes?

Check the network connectivity between your Netapp 2050C and your NetWorker server. Perhaps there's a faulty switch or bad cable somewhere in the mix.


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

I am having issues with excessively long NDMP Backups on a Netapp 2050C. I am running Networker 7.5 sp1. This just started happening about 2 weeks ago, and since then I have tried some of the things I thought fixed this problem once before. I ran a full backup starting Friday night and I still have 3 volumes waiting for backup. 2 of the volumes are close to 1TB in size and at least 1 has limited snapshot space available. Not sure if that is the cause.

This is what I tried so far to fix the problem.
1. Created new clients
2. Made sure that I did not have mixed volumes in my save set

Any suggestions on what to try next or where to look for possible causes?

TIA

I'm running a level 1 backup on just one Qtree and tape drive is writing at 11MB/s on LTO3 tape drive. Does that sound OK?

I'm running a level 1 backup on just one Qtree and tape drive is writing at 11MB/s on LTO3 tape drive. Does that sound OK?

What else is your filer doing at the time of the backup? What's in
its /etc/messages during the time of the backup? Do you have enough
spindles to service the workload? How fragmented is the volume (have
you analyzed or ran re-allocation?) do you have plenty of free space
at the aggr level? Do you have performance advisor to monitor the
filer while performing the backup?


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Watching mine this morning, 2 NDMP backups are running at 110-120MB/s.
They are on 4 gig fiber... what/how is your LTO3's connected? They are
also direct connects to the storage nodes so they bypass networker. If
you are backing up thru copper [GIG-E] even, you will experience slow
backups.


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On
Behalf Of Eugene Vilensky
Sent: Monday, February 08, 2010 6:12 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: Re: [Networker] Slow NDMP Backups

I'm running a level 1 backup on just one Qtree and tape drive is
writing at 11MB/s on LTO3 tape drive. Does that sound OK?

What else is your filer doing at the time of the backup? What's in
its /etc/messages during the time of the backup? Do you have enough
spindles to service the workload? How fragmented is the volume (have
you analyzed or ran re-allocation?) do you have plenty of free space
at the aggr level? Do you have performance advisor to monitor the
filer while performing the backup?


type "signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.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
TD Securities does not accept any liability or losses either direct or consequential
caused by the use of this information. This communication is for informational
purposes only and is not intended as an offer or solicitation
for the purchase or sale of any financial instrument or as an
official confirmation of any transaction. TD Securities is
neither making any investment recommendation nor providing any
professional or advisory services relating to the activities
described herein. All market prices, data and other information
are not warranted as to completeness or accuracy and are subject
to change without notice. The information contained herein is provided
for your exclusive benefit and use. The information shall not be further distributed
or duplicated in whole or in part by any means without the prior
written consent of TD Securities. Any statements made herein do not
necessarily reflect those of TD Securities or its affiliates.
TD Securities is a trademark of The Toronto-Dominion Bank and
represents TD Securities (USA) LLC and certain investment
banking activities of The Toronto-Dominion Bank and its subsidiaries.


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Check the network connectivity between your Netapp 2050C and your NetWorker server. Perhaps there's a faulty switch or bad cable somewhere in the mix.


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Thanks! Sometimes the simple, easy things get lost in the panic. I reseated everything and since I had created all new groups set the inactivity timeout to zero and all is working great.

Watching mine this morning, 2 NDMP backups are running at 110-120MB/s.
They are on 4 gig fiber... what/how is your LTO3's connected? They are
also direct connects to the storage nodes so they bypass networker. If
you are backing up thru copper [GIG-E] even, you will experience slow
backups.


We have the tape attached to the server via SCSI. Next step is to attach to the filer for the exact reason you stated in your own performance example.