Hi Steve --

Glad to hear this is mostly working for you.

When I've seen this sort of situation, it often means there's a second QSM relationship from your source qtree to somewhere else in the dataset. When that happens, ProtMgr will only update one of the two relationships, so the other one lags. That doesn't explain why a manual backup clears the lag condition.

My second thought is there's a lag warning on the primary node. That might mean we're not trying to create snapshot copies on the primary volumes, or we're trying and failing. When you click the "Protect Now" button, we'll create backups on every node we can, which might clear the lag error. If that's the case, you can use the "dfpm primary node set" command to disable lag warnings and errors on the primary node.

You said you're running ProtMgr version 3.7. I strongly encourage you to upgrade to 3.7.1 -- we discovered a serious performance issue in 3.7 where one of our processes goes into a busy loop and uses up all your CPUs.

-- Pete Smoot, NetApp

http://communities.netapp.com/community/products_and_solutions/storage_m anagement_software

-----Original Message----- From: steve klise [mailto:klises@caminomedical.org] Sent: Monday, April 27, 2009 12:06 PM To: toasters@mathworks.com Subject: Protection Manager

I have an issue with protection manager 3.7. I have a primary filer (6030 ontap 7.24) that I have backups running to another filer (3070 7.3P5D1).

I have manually created the resource volumes on the 3070, and DPM creates the qtree snapmirrror relationship with no issues between filers. The backup happens at 8pm (default policy), and everything is hunky dory. Over time, the GUI has an overall status of normal, then goes to lag warning, then lag error. The snapmirror status is current, and I have removed all the alerts per kb (https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb42 558), but still stays with a status of error.

What is strange is if I do a manual backup, it goes from error to normal. All the jobs that run at 8pm are completed, and succeded.

This is not in prod yet, but would save the backup guys about 26 hours on the weekend, so they are interested it getting this resolved. I dont want to upgrade the filers to 7.3.1. I am waiting for 7.3.2 to come out, and most likely will not go live on DPM until 3.8 comes out.

-- View this message in context: http://www.nabble.com/Protection-Manager-tp23262914p23262914.html Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.