Overall status is an OR of resource, protection,conformance and space. Since the dataset is not protected, it couldn't be because of conformance or protection its should either be because of resource or space status.Below is the same I created Regards adai ... View more

Hi Niels,      I tried this. Created a Dataset with Backup policy. C:\>dfpm dataset list -x largeQtree Id:                              362 Name:                            largeQtree Protection Policy:               Back up Application Policy: Description: Owner: Contact: Volume Qtree Name Prefix: Snapshot Name Format: Primary Volume Name Format: Secondary Volume Name Format: Secondary Qtree Name Format: DR Capable:                      No Requires Non Disruptive Restore: No Node details:    Node Name:           Primary data    Resource Pools:      priRp    Provisioning Policy: thinProvNas    Time Zone:    DR Capable:          No    vFiler:    Node Name:           Backup    Resource Pools:      secRp    Provisioning Policy:    Time Zone:    DR Capable:          No    vFiler: C:\>dfpm dataset list -m largeQtree Id         Node Name            Dataset Id Dataset Name         Member Type                                        Name ---------- -------------------- ---------- -------------------- -------------------------------------------------- -------------------------------------------------------        363 Primary data                362 largeQtree           volume                                             fas-sim-1:/largeQtree        371 Backup                      362 largeQtree           volume                                             fas-sim-2:/largeQtree_backup_fasxsimx1_largeQtree C:\>dfpm dataset list -R largeQtree Id         Name                        Protection Policy           Provisioning Policy Relationship Id State        Status  Hours Source                       Destination ---------- --------------------------- --------------------------- ------------------- --------------- ------------ ------- ----- ---------------------------- ----------------------------        362 largeQtree                  Back up                     thinProvNas                     375 snapvaulted  idle    0.1   fas-sim-1:/largeQtree/two    fas-sim-2:/largeQtree_backup_fasxsimx1_largeQtree/two        362 largeQtree                  Back up                     thinProvNas                     377 snapvaulted  idle    0.1   fas-sim-1:/largeQtree/four   fas-sim-2:/largeQtree_backup_fasxsimx1_largeQtree/four        362 largeQtree                  Back up                     thinProvNas                     379 snapvaulted  idle    0.1   fas-sim-1:/largeQtree/one    fas-sim-2:/largeQtree_backup_fasxsimx1_largeQtree/one        362 largeQtree                  Back up                     thinProvNas                     381 snapvaulted  idle    0.1   fas-sim-1:/largeQtree/three  fas-sim-2:/largeQtree_backup_fasxsimx1_largeQtree/three        362 largeQtree                  Back up                     thinProvNas                     383 snapvaulted  idle    0.1   fas-sim-1:/largeQtree/-      fas-sim-2:/largeQtree_backup_fasxsimx1_largeQtree/largeQtree_fas-sim-1_largeQtree C:\> snaplist on source volume after baseline. fas-sim-1> snap list largeQtree Volume largeQtree working...   %/used       %/total  date          name ----------  ----------  ------------  -------- 20% (20%)    0% ( 0%)  Apr 19 05:45  fas-sim-2(0099931872)_largeQtree_backup_fasxsimx1_largeQtree_largeQtree_fas-sim-1_largeQtree-src.0 (snapvault) 35% (22%)    0% ( 0%)  Apr 19 05:45  fas-sim-2(0099931872)_largeQtree_backup_fasxsimx1_largeQtree_three-src.0 (snapvault) 45% (22%)    0% ( 0%)  Apr 19 05:44  fas-sim-2(0099931872)_largeQtree_backup_fasxsimx1_largeQtree_four-src.0 (snapvault) 52% (22%)    0% ( 0%)  Apr 19 05:44  fas-sim-2(0099931872)_largeQtree_backup_fasxsimx1_largeQtree_one-src.0 (snapvault) 58% (20%)    0% ( 0%)  Apr 19 05:44  fas-sim-2(0099931872)_largeQtree_backup_fasxsimx1_largeQtree_two-src.0 (snapvault) fas-sim-1> snaplist on the destination volume. fas-sim-2> snap list largeQtree_backup_fasxsimx1_largeQtree Volume largeQtree_backup_fasxsimx1_largeQtree working...   %/used       %/total  date          name ----------  ----------  ------------  -------- 19% (19%)    0% ( 0%)  Apr 19 05:46  fas-sim-2(0099931872)_largeQtree_backup_fasxsimx1_largeQtree-base.2 (busy,snapvault) fas-sim-2> Snapvault status. fas-sim-2> snapvault status Snapvault is ON. Source                                         Destination                                                                               State          Lag        Status fas-sim-1:/vol/largeQtree/four                 fas-sim-2:/vol/largeQtree_backup_fasxsimx1_largeQtree/four                                Snapvaulted    00:03:15   Idle fas-sim-1:/vol/largeQtree/-                fas-sim-2:/vol/largeQtree_backup_fasxsimx1_largeQtree/largeQtree_fas-sim-1_largeQtree     Snapvaulted    00:02:23   Idle fas-sim-1:/vol/largeQtree/one                  fas-sim-2:/vol/largeQtree_backup_fasxsimx1_largeQtree/one                                 Snapvaulted    00:03:15   Idle fas-sim-1:/vol/largeQtree/three                fas-sim-2:/vol/largeQtree_backup_fasxsimx1_largeQtree/three                               Snapvaulted    00:03:14   Idle fas-sim-1:/vol/largeQtree/two                  fas-sim-2:/vol/largeQtree_backup_fasxsimx1_largeQtree/two                                 Snapvaulted    00:03:16   Idle fas-sim-2> Now I did a protect now. fas-sim-1> snap list largeQtree Volume largeQtree working...   %/used       %/total  date          name ----------  ----------  ------------  -------- 26% (26%)    0% ( 0%)  Apr 19 05:58  dfpm_base(largeQtree.362)conn1.0 (snapvault,acs) 38% (20%)    0% ( 0%)  Apr 19 05:57  2012-04-20_0022+0530_daily_largeQtree_fas-sim-1_largeQtree_.-.four.one.three.two fas-sim-1> fas-sim-2> snap list largeQtree_backup_fasxsimx1_largeQtree Volume largeQtree_backup_fasxsimx1_largeQtree working...   %/used       %/total  date          name ----------  ----------  ------------  -------- 18% (18%)    0% ( 0%)  Apr 19 05:59  fas-sim-2(0099931872)_largeQtree_backup_fasxsimx1_largeQtree-base.0 (busy,snapvault) fas-sim-2> So I am trying to understand what you are doing ? are you using QSM instead of SV only in that case each qtree requires 1 base snapshot. Regards adai ... View more

Hi Chris,      I smell a bug here. Will circle back once some check is done. Regards adai ... View more

Hi Yaron,      Based on my experience. 1) What is more commonly used when defining the SM relationship: host IPs or Host names? Host Name as IP keeps changing. 2) When using Hostnames - Do you use fully qualified names or short hostnames? Short names. 3) How do you resolve the host address - DNS or host files? DNS And another question, less related to our survey here 🙂 4) When SM is working with a dedicated interface - Is it mandatory to add "multi" notation to the snapmirror.conf? It can even be failover too. ... View more

Hi Todd,      Happy to help you.Still I strongly feel this as a bug, as Pete said the conformance should have warned you about the downstream relationship creation when you finished importing the leg A>B. I am filing the bug for the same. Can you add your case to bug594423 ? Also the same will happen in case of a fan out topology as well. i.e A >B and A> C and  its little tricky as we cant do the same here like the A>B>C by importing B>C first and A>B later. The only way I can think off is by suspending the dataset and importing  either of A>B or A>C and once completed resume the dataset. Regards adai ... View more

Just around the corner.Definitely before end of this month. But I cant spell out a definitive date. Regards adai ... View more

Hi      In fact you can even add an entire filer, its called indirect referencing.Though at the end of the day the relationship are created at the qtree or volume level depending upon the replication technology. When an entire filer is added to the primary of  a dataset, PM knows what are all the volume and its containing qtrees in the filer. Once you commit your dataset PM kick off creating relationship for each of them as per the technology( VSM/QSM/SV). PM takes its data from the dfm db, which discovers for new volumes or qtrees once every 15minutes by default. When conformance run on the dataset once every 1 hour by default checks for primary members like its qtree and volumes( irrespective of what is the  direct member of the dataset, like volume/aggr/filer) and check its secondary to see if there is a corresponding relationship if not it kicks off create relationship jobs. This is the one of the sole job of conformance engine. Regards adai ... View more

Hi Neils,      I have done it many time with other customer who had more than 255 like  300+ and not 1000. Regards adai ... View more

Hi Michel,      Bug 592938 if filed for the same. Pls add your case to this bug. Regards adai ... View more

Hi Real,      Confimed with the concerned ppl. No version of DFM/OC supports BMC. OC 5.0.1 which is around the corner supports SP. Regards ... View more

Hi Erik,      Since you said you have 6CPU, can you check if you are hitting the vmware problem ? Determining if multiple virtual CPUs are causing performance issues Regards adai ... View more

Hi Eric,      As per the public report this happens due to ldap and upgrade to OC 5.0. BTW is the windows dfm server configured for ldap ? http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=533814 Regards adai ... View more

Hi Michael,      I smell a bug here. Will confirm and get back to you. Mean time can you open a case with NetApp  global support ? Regards adai ... View more

Hi Real,      DFM currently has support only for the RLM cards. The support for SP is being added as part of OnCommand 5.0.1, which is around the corner for release. As far as I know and remember DFM does not support BMC, will confirm and update this post if its otherwise. Regards adai ... View more

Hi Real,      This bug526035  is fixed in 4.0.2D7 or in the upcoming 5.0.1 which is around the corner. Regards adai ... View more

Hi Phil,            Bug 592321 is filed for the same, pls add your customer case to the same. Regards adai ... View more

This available as out of the box thing in OnCommand/DFM, which is available along with the netapp controller you buy. C:\>dfm eventtype list | findstr /i snapshot aggregate-snapshot-reserve-almost-full        Warning      aggregate.snapshot aggregate-snapshot-reserve-full               Warning      aggregate.snapshot aggregate-snapshot-reserve-ok                 Normal       aggregate.snapshot lun-snapshot-not-possible                     Warning      lun.snapshot lun-snapshot-possible                         Normal       lun.snapshot snapshot-full                                 Warning      df.snapshot.kbytes snapshot-space-ok                             Normal       df.snapshot.kbytes snapshot:created                              Normal       snapshot snapshot:failed                               Error        snapshot snapshots:disabled                            Information  snap-status snapshots:enabled                             Normal       snap-status snapshots:not-too-old                         Normal       old-snaps snapshots:too-old                             Warning      old-snaps volume-first-snapshot-ok                      Normal       volume.first-snap volume-nearly-no-first-snapshot               Warning      volume.first-snap volume-new-snapshot                           Normal       snapshot.discovered volume-next-snapshot-not-possible             Warning      volume.next-snapshot volume-next-snapshot-possible                 Normal       volume.next-snapshot volume-no-first-snapshot                      Warning      volume.first-snap volume-snapshot-deleted                       Normal       snapshot.deleted volume-snapshots-auto-deleted                 Information  snapshot.autodelete C:\> Regards adai ... View more

Hi Peter,      Generally response time of OnCommand is better with FireFox and Linux. Change and let us know your experience. Regards adai ... View more

Hi Scott,      Do all your ossv host have a NHA (NetApp Host Agent ) as well ? If so you are hitting the issue you seem to be a victim of bug  556462. The public report of the same is available below and has a workaround. Has this work around been done in your case ? If not can you tell us you observations after doing the specified workaround ? http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=556462 Regards adai ... View more

One way to achieve this is by having the throttle set to zero during other times than the scheduled backup time.  Below is the conformance error message that I got. Conformance Results    === SEVERITY === Error:    Attention: No available bandwidth to start a backup relationship for Qtree : fas-sim-1:/TestDs/- === ACTION === Creating new backup relationship === REASON === Current throttle value is 0. === SUGGESTION === Change the throttle setting or retry the task at different time.   === SEVERITY === Error:    Attention: No available bandwidth to start a backup relationship for Qtree : fas-sim-1:/TestDs/later === ACTION === Creating new backup relationship === REASON === Current throttle value is 0. === SUGGESTION === Change the throttle setting or retry the task at different time. The conformance monitor runs once every 1 hour will try to conform but will fail, but once the bandwidth becomes availabe the baseline/creating relationship will happens.  Below is a pic of how my throttle looks like Regards adai ... View more

Hi Craig and Rahul,      If you have time read this doc on how history data is maintained in DFM. For each database table, the Operations Manager server saves sample values for periods of the following duration: • Each daily history sample covers 15 minutes. • Each weekly history sample covers 2 hours. • Each monthly history sample covers 8 hours. • Each quarterly history sample covers 1 day. • Each yearly history sample covers 4 days. Purging of Older Samples from History Tables.To keep the database size under control, samples from each of the history tables are purged when they get old. A maximum of 150 samples are kept in each sample history table for one storage object, which translates into: • 37.5 hours in daily sample table • 12.5 days in weekly sample table • 50 days in monthly sample table • 5 months in quarterly sample table. • Samples in yearly sample table are never purged. Operations Manager UI does not provide graphs that span longer than a year; “dfm graph” cli can be used to get older data from the yearly sample table. Below is the link to the doc. Storage Capacity Management using OnCommand Operations Manager Regards adai ... View more