i have to agree here. after upgrading my F520's to 5.3.X and budtool to 4.6.X i have had nothing but nightmares with respect to my backups, leaving me with a large amount of heartburn. my backups are failing due to bug #13252. this is another ndmp/java problem. here is the problem summary:
Problem Summary: The problem is inherent with any process who's stack is VM mapped and touches VM mapped pages. Problem has only been seen on F5xx hardware platform.
In the case of 5.3, NDMP uses Java extensively and the Java Garbage collector has the VM Mapped stack. Thus this problem is most prevalent when: - running 5.3 - during NDMP - on F5xx hardware
netapp does not have a solution (or an idea when there will be one) but there workaround is:
Recommended Solution/Workaround: 13252 is OPEN
The chance of this problem occurring during NDMP can be minimized by:
1. Turning off file history during NDMP backups 2. Reducing the size of the dump (no suggested size except the bigger it is, the more chance you may see the problem).
i'm really wishing i had not decided to go down the ndmp path.
On Mon, Aug 02, Shaun T. Erickson wrote:
I have little faith in NetApp's ability to properly impliment this protocol. Backups are the single most important function I manage as an administrator, and NetApp seems hell bent on making that process a nightmare for me, rather than providing me with a rock solid solution.