Hi Terry, Thanks for the info. The "save" process is the process that has the
CPU pegged.
>From a ps -ef variant:
root 972551 972549 97.0 Jul 18 ?? 21:03:55
/usr/opt/networker/bin/save -s nfs-a.jtc.jcvsf.org -g ArchiveGroup -LL -m
nfs-a.jtc.jcvsf.org -l full -q -W 78 -N /export/jtc/archive /export/jtc/archive
The nsrindexd doesn't appear to have done much since I started this backup
yesterday morning.
root 972552 709563 0.0 Jul 18 ?? 4:55.35
/usr/opt/networker/bin/nsrindexd -a ADD nfs-a.jtc.jcvsf.org index for backup on
nfs-a-1.jtc.jcvsf.org
Thanks,
Randy
-------------- Original message --------------
> Hi Randy
>
> On your backup server, check out the processes that are running. Look for
> the process running nsrindexd; this is the one that maintains the client
> file index files. It would be interesting to know how much CPU time that
> process is consuming.
>
> Also, check out the performance of the disk holding the client file index
> file. If that disk is very busy and/or the disk is fragmented, that would
> contribute to the slow backups.
>
> If neither of these things indicate a problem, we'll need to look elsewhere
> for the cause of these slow backups. Once cause could be the backup of many
> small files from a slow and/or fragmented disk.
>
> Hope this helps.
> Tl
>
> Terry Lemons
> CLARiiON Appliance Engineering
> CLARiiON Application Solutions Integration
> EMC²
> where information lives
> 4400 Computer Drive, MS D239
> Westboro MA 01580
> Phone: 508 898 7312
> Email: Lemons_Terry AT emc DOT com
>
>
> -----Original Message-----
> From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT
> EDU] On
> Behalf Of Randy Doering
> Sent: Tuesday, July 19, 2005 12:36 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] No Index Save Question
>
> Greetings, I'm in the midst of trying to get a full backup of a file system
> that is alittle of 4 TB and contains more than 132 Million files.
>
> When I started this yesterday, I noticed it was backing up at around 20-22
> MB/s, and I started to calculate how many hours this would take after it
> had filled the first tape.
>
> Well, today it is backing up at 150-190 KB/s and the System CPU is pegged.
> At this rate, we looking at at least a month to get this backup finished.
> We have concluded that the system is trying to keep the index information
> and that is the reason for the slow down.
>
> I have noticed a button in the Group that is called: "No Index Save". So,
> what does this button actually mean?
>
> We are in the middle of moving the file systems from an HP-EVA based file
> system to an EMC Centerra, and was planning on restoring to the EMC
> Centerra.
>
> So, will using the "No Index Save" speed things along and more importantly
> will I be able to restore?
>
> Thanks,
> Randy
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listserv.temple DOT edu or visit the list's Web site at
> http://listserv.temple.edu/archives/networker.html where you can
> also view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listserv.temple DOT edu or visit the list's Web site at
> http://listserv.temple.edu/archives/networker.html where you can
> also view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
