I just upgraded a FAS250 from 7.0 to 7.2.4. After the upgrade in Filerview under Snapmirror, the option "Manage" is gone. All other options are there, Configure, Report, Add etc. From the command line, everything is there. The snapmirrors are working. I just do not have the option to Manage them in Filerview. Has anyone seen this at 7.2.4?
Manage was integrated into Configure. What you really did lose though is Delete. You have to manually edit snapmirror.conf to delete a relationship now.
On Thu, 2008-02-14 at 15:21 -0500, David McWilliams wrote:
I just upgraded a FAS250 from 7.0 to 7.2.4. After the upgrade in Filerview under Snapmirror, the option "Manage" is gone. All other options are there, Configure, Report, Add etc. From the command line, everything is there. The snapmirrors are working. I just do not have the option to Manage them in Filerview. Has anyone seen this at 7.2.4?
-- Sláinte,
David
Get a safer, faster, better web browser @ http://www.mozilla.org/products/firefox/
This is a known bug. I believe it's fixed in 7.2.4P4 and later. Unfortunately 7.2.4P4 isn't publically available yet but should be soon. In the mean time, the CLI still works, it's strictly a FilerView bug.
-- Adam Fox adamfox@netapp.com
________________________________
From: David McWilliams [mailto:davidkmcw@gmail.com] Sent: Thursday, February 14, 2008 3:21 PM To: NetApp list; Jerry Rioux Subject: Snapmirror problem after upgrade
I just upgraded a FAS250 from 7.0 to 7.2.4. After the upgrade in Filerview under Snapmirror, the option "Manage" is gone. All other options are there, Configure, Report, Add etc. From the command line, everything is there. The snapmirrors are working. I just do not have the option to Manage them in Filerview. Has anyone seen this at 7.2.4?
How is the FAS250 working with 7.2.x? Any change in performance?
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Fox, Adam Sent: Thursday, February 14, 2008 1:28 PM To: David McWilliams; NetApp list; Jerry Rioux Subject: RE: Snapmirror problem after upgrade
This is a known bug. I believe it's fixed in 7.2.4P4 and later. Unfortunately 7.2.4P4 isn't publically available yet but should be soon. In the mean time, the CLI still works, it's strictly a FilerView bug.
-- Adam Fox adamfox@netapp.com
________________________________ From: David McWilliams [mailto:davidkmcw@gmail.com] Sent: Thursday, February 14, 2008 3:21 PM To: NetApp list; Jerry Rioux Subject: Snapmirror problem after upgrade I just upgraded a FAS250 from 7.0 to 7.2.4. After the upgrade in Filerview under Snapmirror, the option "Manage" is gone. All other options are there, Configure, Report, Add etc. From the command line, everything is there. The snapmirrors are working. I just do not have the option to Manage them in Filerview. Has anyone seen this at 7.2.4?
-- Sláinte,
David
Get a safer, faster, better web browser @ http://www.mozilla.org/products/firefox/
We've got 7.2.3 running on a single-node FAS270 for Exchange (small implementation) - soon to upgrade to cluster so we can support file services on the partner node. No issues that we've seen - smooth running, really.
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Hadrian Baron Sent: Thursday, February 14, 2008 7:11 PM To: 'Fox, Adam'; David McWilliams; NetApp list; Jerry Rioux Subject: RE: Snapmirror problem after upgrade
How is the FAS250 working with 7.2.x? Any change in performance?
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Fox, Adam Sent: Thursday, February 14, 2008 1:28 PM To: David McWilliams; NetApp list; Jerry Rioux Subject: RE: Snapmirror problem after upgrade
This is a known bug. I believe it's fixed in 7.2.4P4 and later. Unfortunately 7.2.4P4 isn't publically available yet
but should be soon. In the mean time, the CLI still works, it's strictly a FilerView bug.
-- Adam Fox adamfox@netapp.com
________________________________
From: David McWilliams [mailto:davidkmcw@gmail.com] Sent: Thursday, February 14, 2008 3:21 PM To: NetApp list; Jerry Rioux Subject: Snapmirror problem after upgrade
I just upgraded a FAS250 from 7.0 to 7.2.4. After the upgrade in Filerview under Snapmirror, the option "Manage" is gone. All other options are there, Configure, Report, Add etc. From the command line, everything is there. The snapmirrors are working. I just do not have the option to Manage them in Filerview. Has anyone seen this at 7.2.4?
I have not seen any performance changes yet. Snapmirrors are working the same. The only thing I have noticed so far is the "Manage" options for Snapmirror in Filerview is missing. And it sounds like that is a bug.
Jerry Rioux
Enterprise Systems Engineer
Help Desk 1-888-746-6478
www.incat.com
________________________________
From: Hadrian Baron [mailto:Hadrian.Baron@vegas.com] Sent: Thursday, February 14, 2008 7:11 PM To: 'Fox, Adam'; David McWilliams; NetApp list; Jerry Rioux Subject: RE: Snapmirror problem after upgrade
How is the FAS250 working with 7.2.x? Any change in performance?
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Fox, Adam Sent: Thursday, February 14, 2008 1:28 PM To: David McWilliams; NetApp list; Jerry Rioux Subject: RE: Snapmirror problem after upgrade
This is a known bug. I believe it's fixed in 7.2.4P4 and later. Unfortunately 7.2.4P4 isn't publically available yet
but should be soon. In the mean time, the CLI still works, it's strictly a FilerView bug.
-- Adam Fox adamfox@netapp.com
________________________________
From: David McWilliams [mailto:davidkmcw@gmail.com] Sent: Thursday, February 14, 2008 3:21 PM To: NetApp list; Jerry Rioux Subject: Snapmirror problem after upgrade
I just upgraded a FAS250 from 7.0 to 7.2.4. After the upgrade in Filerview under Snapmirror, the option "Manage" is gone. All other options are there, Configure, Report, Add etc. From the command line, everything is there. The snapmirrors are working. I just do not have the option to Manage them in Filerview. Has anyone seen this at 7.2.4?
I checked the NOW site, and didn't really find anything that seemed pertinent for 7.23 in regards to setting up number of spindles for raid DP. I did read the 7.2 storage mgmt guide btw . Here is my situation:
I brought over 3 shelves from some older heads, and hot added to a current loop. Shelves 2-4. Shelf 1 was already provisioned with 72GB disks. Currently, I have 1 aggregate of 3 disk (root vol), and 9 disks for another aggregate; 2 hot spares (full 72gb shelf, shelf 1)
Here is my question.
What is the best layout for raid dp for my new 3 shelves I just added? I do not want to add the 3 new shelves to the existing aggregate.
I know the default is 16 when creating a new aggr, maybe I should default to that. I don't know if I will be adding more disks in the future to this aggregate.
Shelf 4 I have 1 shelf of 144gb 15k (14 spindles) new
Shelf 3 I have 1 shelf of 72gb 15k (14 spindles) new
Shelf 2 I have 1 shelf of 72gb 10k (14 spindles) new
Shelf 1 I have 1 shelf of 72gb 15k (14 spindles) already provisioned
I want to dedicate at least 1 or 2 hot spares for the 144gb (obviously). I already have 2 hot spares from shelf 1.
I care more about performance then raid reconstruct in the event of a disk failure. This aggregate will be used primarily for CIFS.
If I missed a document that discusses this better, please let me know.
Thanks!!
I would recommend grouping all your 15k drives in one aggr, and all the 10k drives in another. Use the default 16 disk setting. This should give you optimal performance. I'd also keep a single 144GB and single 72GB as spares. RaidDP gives you pretty decent protection so you shouldn't need a spare per shelf. I personally use one spare per 3 shelves of a drive type especially with FC drives. My 2 cents =)
Thanks, Scott
Internet klises@caminomedical.org
Sent by: owner-toasters@mathworks.com 02/15/2008 11:17 AM
To toasters cc
Subject raid group question for new aggregate
I checked the NOW site, and didn't really find anything that seemed pertinent for 7.23 in regards to setting up number of spindles for raid DP. I did read the 7.2 storage mgmt guide btw . Here is my situation:
I brought over 3 shelves from some older heads, and hot added to a current loop. Shelves 2-4. Shelf 1 was already provisioned with 72GB disks. Currently, I have 1 aggregate of 3 disk (root vol), and 9 disks for another aggregate; 2 hot spares (full 72gb shelf, shelf 1)
Here is my question.
What is the best layout for raid dp for my new 3 shelves I just added? I do not want to add the 3 new shelves to the existing aggregate.
I know the default is 16 when creating a new aggr, maybe I should default to that. I don't know if I will be adding more disks in the future to this aggregate.
Shelf 4 I have 1 shelf of 144gb 15k (14 spindles) new
Shelf 3 I have 1 shelf of 72gb 15k (14 spindles) new
Shelf 2 I have 1 shelf of 72gb 10k (14 spindles) new
Shelf 1 I have 1 shelf of 72gb 15k (14 spindles) already provisioned
I want to dedicate at least 1 or 2 hot spares for the 144gb (obviously). I already have 2 hot spares from shelf 1.
I care more about performance then raid reconstruct in the event of a disk failure. This aggregate will be used primarily for CIFS.
If I missed a document that discusses this better, please let me know.
Thanks!!
This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Scott is on the money, although I¹d make two comments: - disk replacement depends on how hard you push your disks & personally I would use 1 disk / shelf + 1 spare initially and throttle back over time based on trending data. - DP is strong protection, but a magnetic media failure and + single disk failure can be a double disk failure for a single file... Unlikely with disk scrubbing, but if you¹ve got very important data it might be wise to keep the extra disks kicking around.
-Nick
On 2/20/08 8:54 AM, "scott.belisle@americas.bnpparibas.com" scott.belisle@americas.bnpparibas.com wrote:
I would recommend grouping all your 15k drives in one aggr, and all the 10k drives in another. Use the default 16 disk setting. This should give you optimal performance. I'd also keep a single 144GB and single 72GB as spares. RaidDP gives you pretty decent protection so you shouldn't need a spare per shelf. I personally use one spare per 3 shelves of a drive type especially with FC drives. My 2 cents =)
Thanks, Scott
Internet klises@caminomedical.org Sent by: owner-toasters@mathworks.com 02/15/2008 11:17 AM To toasters cc Subject raid group question for new aggregate
I checked the NOW site, and didn't really find anything that seemed pertinent for 7.23 in regards to setting up number of spindles for raid DP. I did read the 7.2 storage mgmt guide btw . Here is my situation:
I brought over 3 shelves from some older heads, and hot added to a current loop. Shelves 2-4. Shelf 1 was already provisioned with 72GB disks. Currently, I have 1 aggregate of 3 disk (root vol), and 9 disks for another aggregate; 2 hot spares (full 72gb shelf, shelf 1)
Here is my question.
What is the best layout for raid dp for my new 3 shelves I just added? I do not want to add the 3 new shelves to the existing aggregate.
I know the default is 16 when creating a new aggr, maybe I should default to that. I don't know if I will be adding more disks in the future to this aggregate.
Shelf 4 I have 1 shelf of 144gb 15k (14 spindles) new
Shelf 3 I have 1 shelf of 72gb 15k (14 spindles) new
Shelf 2 I have 1 shelf of 72gb 10k (14 spindles) new
Shelf 1 I have 1 shelf of 72gb 15k (14 spindles) already provisioned
I want to dedicate at least 1 or 2 hot spares for the 144gb (obviously). I already have 2 hot spares from shelf 1.
I care more about performance then raid reconstruct in the event of a disk failure. This aggregate will be used primarily for CIFS.
If I missed a document that discusses this better, please let me know.
Thanks!!
This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Thanks Toasters! Lots of great info on these posts.
________________________________
From: Nicholas Bernstein [mailto:nick@nicholasbernstein.com] Sent: Wed 2/20/2008 6:39 PM To: scott.belisle@americas.bnpparibas.com; Klise, Steve Cc: owner-toasters@mathworks.com; Toasters Subject: Re: raid group question for new aggregate
Scott is on the money, although I'd make two comments: - disk replacement depends on how hard you push your disks & personally I would use 1 disk / shelf + 1 spare initially and throttle back over time based on trending data. - DP is strong protection, but a magnetic media failure and + single disk failure can be a double disk failure for a single file... Unlikely with disk scrubbing, but if you've got very important data it might be wise to keep the extra disks kicking around.
-Nick
On 2/20/08 8:54 AM, "scott.belisle@americas.bnpparibas.com" scott.belisle@americas.bnpparibas.com wrote:
I would recommend grouping all your 15k drives in one aggr, and all the 10k drives in another. Use the default 16 disk setting. This should give you optimal performance. I'd also keep a single 144GB and single 72GB as spares. RaidDP gives you pretty decent protection so you shouldn't need a spare per shelf. I personally use one spare per 3 shelves of a drive type especially with FC drives. My 2 cents =) Thanks, Scott Internet klises@caminomedical.org Sent by: owner-toasters@mathworks.com 02/15/2008 11:17 AM
To
toasters
cc Subject
raid group question for new aggregate I checked the NOW site, and didn't really find anything that seemed pertinent for 7.23 in regards to setting up number of spindles for raid DP. I did read the 7.2 storage mgmt guide btw . Here is my situation: I brought over 3 shelves from some older heads, and hot added to a current loop. Shelves 2-4. Shelf 1 was already provisioned with 72GB disks. Currently, I have 1 aggregate of 3 disk (root vol), and 9 disks for another aggregate; 2 hot spares (full 72gb shelf, shelf 1) Here is my question. What is the best layout for raid dp for my new 3 shelves I just added? I do not want to add the 3 new shelves to the existing aggregate. I know the default is 16 when creating a new aggr, maybe I should default to that. I don't know if I will be adding more disks in the future to this aggregate. Shelf 4 I have 1 shelf of 144gb 15k (14 spindles) new Shelf 3 I have 1 shelf of 72gb 15k (14 spindles) new Shelf 2 I have 1 shelf of 72gb 10k (14 spindles) new Shelf 1 I have 1 shelf of 72gb 15k (14 spindles) already provisioned I want to dedicate at least 1 or 2 hot spares for the 144gb (obviously). I already have 2 hot spares from shelf 1. I care more about performance then raid reconstruct in the event of a disk failure. This aggregate will be used primarily for CIFS. If I missed a document that discusses this better, please let me know. Thanks!! This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Small correction. This bug is fixed in 7.2.5, not 7.2.4P4.
-- Adam Fox adamfox@netapp.com
________________________________
From: Fox, Adam Sent: Thursday, February 14, 2008 4:28 PM To: 'David McWilliams'; NetApp list; Jerry Rioux Subject: RE: Snapmirror problem after upgrade
This is a known bug. I believe it's fixed in 7.2.4P4 and later. Unfortunately 7.2.4P4 isn't publically available yet but should be soon. In the mean time, the CLI still works, it's strictly a FilerView bug.
-- Adam Fox adamfox@netapp.com
________________________________
From: David McWilliams [mailto:davidkmcw@gmail.com] Sent: Thursday, February 14, 2008 3:21 PM To: NetApp list; Jerry Rioux Subject: Snapmirror problem after upgrade
I just upgraded a FAS250 from 7.0 to 7.2.4. After the upgrade in Filerview under Snapmirror, the option "Manage" is gone. All other options are there, Configure, Report, Add etc. From the command line, everything is there. The snapmirrors are working. I just do not have the option to Manage them in Filerview. Has anyone seen this at 7.2.4?
Sorry guys, it's not a bug...it's a feature ;-)
see http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=275634 http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=275634
The "manage" options are dynamically available under "Report"
Regards, André Beckers
________________________________
Von: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Im Auftrag von Fox, Adam Gesendet: Freitag, 15. Februar 2008 18:22 An: David McWilliams; NetApp list; Jerry Rioux Betreff: RE: Snapmirror problem after upgrade
Small correction. This bug is fixed in 7.2.5, not 7.2.4P4.
-- Adam Fox adamfox@netapp.com
________________________________
From: Fox, Adam Sent: Thursday, February 14, 2008 4:28 PM To: 'David McWilliams'; NetApp list; Jerry Rioux Subject: RE: Snapmirror problem after upgrade
This is a known bug. I believe it's fixed in 7.2.4P4 and later. Unfortunately 7.2.4P4 isn't publically available yet but should be soon. In the mean time, the CLI still works, it's strictly a FilerView bug.
-- Adam Fox adamfox@netapp.com
________________________________
From: David McWilliams [mailto:davidkmcw@gmail.com] Sent: Thursday, February 14, 2008 3:21 PM To: NetApp list; Jerry Rioux Subject: Snapmirror problem after upgrade
I just upgraded a FAS250 from 7.0 to 7.2.4. After the upgrade in Filerview under Snapmirror, the option "Manage" is gone. All other options are there, Configure, Report, Add etc. From the command line, everything is there. The snapmirrors are working. I just do not have the option to Manage them in Filerview. Has anyone seen this at 7.2.4?
-
Beckers, André, VF-Group -
Bill Holland -
David McWilliams -
Fox, Adam -
Glenn Walker -
Hadrian Baron -
Jerry Rioux -
Klise, Steve -
Nicholas Bernstein -
scott.belisle＠americas.bnpparibas.com