It's a special release to fix this bug. The bug number is 85559. You have to do a priv set diag and run rtag -t malloc. Look for JAVA having to do with NDMP. If you see this line, watch it for a day or 2. If the numbers increment, you have the leak. You really should never see the JAVA NDMP tape device line at all.
Hope this helps!
-----Original Message----- From: Francett, Robert D (SAIC) [mailto:FranceRD@BP.com] Sent: Tuesday, February 11, 2003 1:44 PM To: 'Jay Newton (Email)'; 'toasters@mathworks.com' Subject: RE: NDMP issues with 6.2.x of DataONTAP
Jay,
Checking to see if this is affecting us, however I could not find info on DOT 6.2.2d8 on NOW. Do you know the bug number of the NDMP memory problem?
Thanks, Bob Francett BP Exploration
-----Original Message----- From: Jay Newton (Email) [mailto:jnewton@chkenergy.com] Sent: Tuesday, February 11, 2003 7:33 AM To: 'toasters@mathworks.com' Subject: NDMP issues with 6.2.x of DataONTAP
We are experiencing issues with NDMP backups. I'm hoping other people in this group have seen it as well and may have suggestions for us to try. Here's an explanation of what has happened.
On 12-13-2002 we upgraded from 6.1.3r2 to 6.2.1r2 to fix issues with Autosupports not being sent in the event of hardware failure. A couple of things went sour after the upgrade. Our SnapManager for Exchange performance went down more than 30%, NDMP backups would run slow intermittently, and general Filer performance got worse. NetApp discovered a memory leak in 6.2.1r2 in the NDMP daemon about the same time we upgraded to 6.2.1r2. We had to upgrade to 6.2.2d8 to fix that issue. However, a backup or two will invariably run slower than the rest. If the backup is restarted, it usually picks up speed and runs normally. By slow I mean 10 gigs in 10 hours on a DLT8000 drive. I used to get 20-30 gig per hour before we upgraded to 6.2.1r2. This can happen with each of the 4 DLT8000 drives attached to the Filer meaning that I can't pin the problem to a bad piece of hardware.
Today we have discovered that snapshots for backup are not deleting correctly. The NDMPD process was holding the snapshot hostage. A volume ran out of space due to this issue. We were able to kill the NDMPD sessions that were holding the snapshot open and the snapshot deleted normally.
Has anyone else experienced similar issues?
For those of you running SnapManager for Exchange, how big are your databases and how long does it take to verify them? Also, those who run multiple backups, what is your CPU utilization like when running 4 simultaneous backups and what is your tape throughput?
DataONTAP 6.2.2d8 Commvault Galaxy 3.7.1 SP4 ATL P2000 library with 4 DLT8000 drives attached to Filer on 2 SCSI HVD controllers (2 drives per controller)
Thanks!
Jay Newton Systems Engineer Chesapeake Energy Corporation Natural Gas - Natural Advantages Building 6112, Room 114 (405)848-8000 ext. 683 jnewton@chkenergy.com