toasters

toasters@lists.teaparty.net

13513 discussions

Nondisruptively change language of a volume containing LUNs?
by Basil 20 Jul '15

20 Jul '15

Hi folks, One of my colleagues made a typo on the language for volumes that are used exclusively for LUNs. I know that you can't change the language of a volume, but is there a way to move the LUNs to a new volume with the correct language set? Thanks!

4 6

RE: SVM DR in 8.3.1 - AGAIN
by Borzenkov, Andrei 20 Jul '15

20 Jul '15

Original question was - is it possible to start DR SVM with identity-preserve without stopping SnapMirror. It looks like it is possible. Regarding “future snap mirror updates” - I mentioned that if I switch back from identity-preserve=false to identity-preserve=true changes made in the past (during identiry-preserve=false relationship) are replicated. They are even applied to a running DR SVM, and e.g. LIF gets configured while DR SVM is running. I do not promote or endorse it - as I said “I am not sure if it works as intended”. But I can see use cases for it. From: Moore, Doug [mailto:Doug.Moore@netapp.com] Sent: Sunday, July 19, 2015 7:44 AM To: Borzenkov, Andrei Cc: NGC-g.milazzo-sinergy.it; Parisi, Justin; Toasters Subject: Re: SVM DR in 8.3.1 - AGAIN What are you trying to accomplish? The setup you have below is clearly not a use case that we advise. Anything that is sent in the initial ID preserve that is not then sent in the id discard will not be replicated in future snap mirror updates. So why would you do it that way? Doug Moore Technical Marketing Engineer Clustered Data ONTAP/Multi-Tenancy NetApp 303.349.4851<tel:303.349.4851> Direct / Mobile doug.moore(a)netapp.com<mailto:doug.moore@netapp.com> www.netapp.com<http://www.netapp.com/> On Jul 18, 2015, at 13:36, Borzenkov, Andrei <andrei.borzenkov(a)ts.fujitsu.com<mailto:andrei.borzenkov@ts.fujitsu.com>> wrote: Not sure if it works as intended, but - first create snapmirror with identity-preserve true; then delete (without breaking) and create again with identity-preserve false. Now you have SVM that contains original configuration but can be started without breaking SnapMirror. To continue just resync. OTOH it is logical. In case of identity-preserve is false, network configuration of DR SVM is not changed at all and where it came from originally does not matter. If you delete snapmirror and recreate with identity preserve again, changes made in between on source are propagated to DR. Of course, it does not have ability to select arbitrary snapshot as starting point (and as most part of SVM configuration is not kept in volume, it would not help anyway). I do not know if RDB even has anything similar to snapshots that could be employed here. From: toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net> [mailto:toasters-bounces@teaparty.net] On Behalf Of Milazzo Giacomo Sent: Wednesday, July 08, 2015 9:06 PM To: Parisi, Justin; Toasters Cc: Moore, Doug Subject: R: SVM DR in 8.3.1 - AGAIN We’re still experiencing a lot of issues with customer where first few days ago we’ve attempted to set up this SVM DR. As reported it seems that it does the work that someone could expect as…basic way. But at this customer the world is a little bit more complicated (does it is the only one using that DR way with 7Mode? I don’t think so!) We need to understand how to proceed to set up this DR. Or we (better NetApp!) must officially communicate to customers that they can wast their –perfectly working for test and troubles- DR approach for it’s not possible in cDOT! Let me resume the issue. This customer, since years, doesn’t use the vFiler DR direct approach but, at the snapmirrored destination flexclone volumes are created and on this run vfiler with –d option that start from the root volume of the vfiler. I.e. (the green stands for running, the red for stopped/offlined/mirrored) ✓ ✓ X ✓ ✓ Production ----sm---> DR ---flexclone---> DR_clone –vfilercreate --> vfiler in dr This permit to have a point in time instance with all the initial configurations (share/exports/MSAD domain join, users, security ecc). This also let have the choice to choose the snapshot used as starting point and, overall, this let to maintain the source-destination replicas active and updated. All of those is automated using WFA, so it’s enough a click and everything go! We’ve seen that SVM DR more ore less work as vfiler dr worked. ✓ ✓ X Production ----sm---> DR < break of mirror relationship – a MUST > X X ✓ Produzione ----sm---> DR We’ve also seen with some trick and maintaining the production and test network separated in different IP spaces (and ports, switches, vlan…) that we can have both running the source and the destination, but we must also break the sm relationship! ✓ X ✓ Production ----sm---> DR These releationships unfortunately are essential prerequisites for this customer. Let me say vols (in SVMs) must continue to replicate for the DR test SVM could be up also for 10 and more days! And customer cannot permit the risk to loose its replicated/updated copies… The questions are: is there something like vfiler create –d? (documentation does not report anything else than “normal” usage) Something that let us create an SVM with all configurations inside but starting from cloned vols at destination snapmirrored site? We’re really in trouble for customer is starting to suspect that this cDot could be a boomerang and, except for VSAN and VVOL support for VMware 6, the things they’ve loosed are more than the one they’ve gained! Any help will be appreciated! Da: toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net> [mailto:toasters-bounces@teaparty.net] Per conto di Milazzo Giacomo Inviato: lunedì 6 luglio 2015 17:33 A: Parisi, Justin Cc: Toasters; Moore, Doug Oggetto: R: SVM DR in 8.3.1 We need identity true. a lot of cifs configuration are not brought if false. Think to vfiler Dr of 7mode... Bye - Sent by mobile - -------- Messaggio originale -------- Da: "Parisi, Justin" <Justin.Parisi(a)netapp.com<mailto:Justin.Parisi@netapp.com>> Data: 06/07/2015 17:24 (GMT+01:00) A: Milazzo Giacomo <G.Milazzo(a)sinergy.it<mailto:G.Milazzo@sinergy.it>> Cc: "Borzenkov, Andrei" <andrei.borzenkov(a)ts.fujitsu.com<mailto:andrei.borzenkov@ts.fujitsu.com>>, Toasters <toasters(a)teaparty.net<mailto:toasters@teaparty.net>>, "Moore, Doug" <Doug.Moore(a)netapp.com<mailto:Doug.Moore@netapp.com>> Oggetto: RE: SVM DR in 8.3.1 You can always run the destination in the “Identity discard” mode to avoid IP clashes. That should allow you to test. I’ve added the SVM DR TME to this thread so he can address your questions/be aware of the questions we have out there. From: Milazzo Giacomo [mailto:G.Milazzo@sinergy.it] Sent: Monday, July 06, 2015 11:10 AM To: Parisi, Justin Cc: Borzenkov, Andrei; Toasters Subject: R: SVM DR in 8.3.1 Again, interesting for it summarize the two official docs. We’ve just created a test and it seems to work: unfortunately up to now we don’t have yet the physical network correctly cabled to the right switch. We’re concerned about the statement “source SVM must be stopped” to run in DR…this because we’ve an isolated network environment and when we run DR test the source still continue to work…fortunately we’ve test the “force” option to the start SVM command… A doubt. We’ve noted that when the SVM DR has been created automatically has been created its LIF for data communication (our test contained a CIFS server with a shared vol). This LIF has been created using the VLAN that was assigned to the ipspace we’ve created to the test network, and the same IP of source has been assigned. That’s what we expect, and it’s good. But, what happen if I’ve a lot of source SVM, each with its subnet and broadcast domain that must converge in the same test ipspace? How the lifs and their IP addresses are choosen? Regards, Da: Parisi, Justin [mailto:Justin.Parisi@netapp.com] Inviato: lunedì 6 luglio 2015 16:08 A: Borzenkov, Andrei; Milazzo Giacomo; Toasters Oggetto: RE: SVM DR in 8.3.1 I wrote a blog on SVM DR, if you are interested: https://whyistheinternetbroken.wordpress.com/2015/06/25/techstorage-virtual… From: toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net> [mailto:toasters-bounces@teaparty.net] On Behalf Of Borzenkov, Andrei Sent: Wednesday, July 01, 2015 10:05 AM To: NGC-g.milazzo-sinergy.it<http://NGC-g.milazzo-sinergy.it>; Toasters Subject: RE: SVM DR in 8.3.1 You are right, you need to create destination SVM in advance with right attributes. According to documentation “For remote data access or data distribution, you can provide read-only access to the NFS clients and SAN hosts from the destination SVM, if you chose to set the identity-preserve option to false.”. Also “SVM Disaster Recovery Preparation Express Guide” gives examples that indicate that you can (actually, must) configure network on destination SVM and access it. From: toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net> [mailto:toasters-bounces@teaparty.net] On Behalf Of Milazzo Giacomo Sent: Wednesday, July 01, 2015 4:33 PM To: Toasters Subject: SVM DR in 8.3.1 Hi all, I know is still RC1 but prior to upgrade a running 8.3 I would try to have more info on a new 8.3.1 feature: the SVM DR. I’ve a customer that on 7Mode ran the DR of CIFS vfiler (joined to a domain) using snapmirror of the vfiler vols, including the root one, and at the DR test/run the source vfiler was stopped and a vfiler create –d command, with the mirrored root specified, let the destination vfiler start with all domain infos, shares on the vole and ip addresses on the DR site with minimal effort. I’ve read the docs that come with 8.3.1 but is not clear. I don’t think that there’s something in SVM DR that permit to recreate the SVM on the destinanation: this must exist in advance, in stopped mode, right? What’s about the maintenance of the IPs? Should I have two identical subnets in both clusters? What if I cannot have two different subnets? Do I have a way to let the replicated SVM being in standby with the data lif with preregistered IPs? Regards

2 2

R: SVM DR in 8.3.1 - AGAIN
by Milazzo Giacomo 18 Jul '15

18 Jul '15

We’re still experiencing a lot of issues with customer where first few days ago we’ve attempted to set up this SVM DR. As reported it seems that it does the work that someone could expect as…basic way. But at this customer the world is a little bit more complicated (does it is the only one using that DR way with 7Mode? I don’t think so!) We need to understand how to proceed to set up this DR. Or we (better NetApp!) must officially communicate to customers that they can wast their –perfectly working for test and troubles- DR approach for it’s not possible in cDOT! Let me resume the issue. This customer, since years, doesn’t use the vFiler DR direct approach but, at the snapmirrored destination flexclone volumes are created and on this run vfiler with –d option that start from the root volume of the vfiler. I.e. (the green stands for running, the red for stopped/offlined/mirrored) ✓ ✓ X ✓ ✓ Production ----sm---> DR ---flexclone---> DR_clone –vfilercreate --> vfiler in dr This permit to have a point in time instance with all the initial configurations (share/exports/MSAD domain join, users, security ecc). This also let have the choice to choose the snapshot used as starting point and, overall, this let to maintain the source-destination replicas active and updated. All of those is automated using WFA, so it’s enough a click and everything go! We’ve seen that SVM DR more ore less work as vfiler dr worked. ✓ ✓ X Production ----sm---> DR < break of mirror relationship – a MUST > X X ✓ Produzione ----sm---> DR We’ve also seen with some trick and maintaining the production and test network separated in different IP spaces (and ports, switches, vlan…) that we can have both running the source and the destination, but we must also break the sm relationship! ✓ X ✓ Production ----sm---> DR These releationships unfortunately are essential prerequisites for this customer. Let me say vols (in SVMs) must continue to replicate for the DR test SVM could be up also for 10 and more days! And customer cannot permit the risk to loose its replicated/updated copies… The questions are: is there something like vfiler create –d? (documentation does not report anything else than “normal” usage) Something that let us create an SVM with all configurations inside but starting from cloned vols at destination snapmirrored site? We’re really in trouble for customer is starting to suspect that this cDot could be a boomerang and, except for VSAN and VVOL support for VMware 6, the things they’ve loosed are more than the one they’ve gained! Any help will be appreciated! Da: toasters-bounces(a)teaparty.net [mailto:toasters-bounces@teaparty.net] Per conto di Milazzo Giacomo Inviato: lunedì 6 luglio 2015 17:33 A: Parisi, Justin Cc: Toasters; Moore, Doug Oggetto: R: SVM DR in 8.3.1 We need identity true. a lot of cifs configuration are not brought if false. Think to vfiler Dr of 7mode... Bye - Sent by mobile - -------- Messaggio originale -------- Da: "Parisi, Justin" <Justin.Parisi(a)netapp.com<mailto:Justin.Parisi@netapp.com>> Data: 06/07/2015 17:24 (GMT+01:00) A: Milazzo Giacomo <G.Milazzo(a)sinergy.it<mailto:G.Milazzo@sinergy.it>> Cc: "Borzenkov, Andrei" <andrei.borzenkov(a)ts.fujitsu.com<mailto:andrei.borzenkov@ts.fujitsu.com>>, Toasters <toasters(a)teaparty.net<mailto:toasters@teaparty.net>>, "Moore, Doug" <Doug.Moore(a)netapp.com<mailto:Doug.Moore@netapp.com>> Oggetto: RE: SVM DR in 8.3.1 You can always run the destination in the “Identity discard” mode to avoid IP clashes. That should allow you to test. I’ve added the SVM DR TME to this thread so he can address your questions/be aware of the questions we have out there. From: Milazzo Giacomo [mailto:G.Milazzo@sinergy.it] Sent: Monday, July 06, 2015 11:10 AM To: Parisi, Justin Cc: Borzenkov, Andrei; Toasters Subject: R: SVM DR in 8.3.1 Again, interesting for it summarize the two official docs. We’ve just created a test and it seems to work: unfortunately up to now we don’t have yet the physical network correctly cabled to the right switch. We’re concerned about the statement “source SVM must be stopped” to run in DR…this because we’ve an isolated network environment and when we run DR test the source still continue to work…fortunately we’ve test the “force” option to the start SVM command… A doubt. We’ve noted that when the SVM DR has been created automatically has been created its LIF for data communication (our test contained a CIFS server with a shared vol). This LIF has been created using the VLAN that was assigned to the ipspace we’ve created to the test network, and the same IP of source has been assigned. That’s what we expect, and it’s good. But, what happen if I’ve a lot of source SVM, each with its subnet and broadcast domain that must converge in the same test ipspace? How the lifs and their IP addresses are choosen? Regards, Da: Parisi, Justin [mailto:Justin.Parisi@netapp.com] Inviato: lunedì 6 luglio 2015 16:08 A: Borzenkov, Andrei; Milazzo Giacomo; Toasters Oggetto: RE: SVM DR in 8.3.1 I wrote a blog on SVM DR, if you are interested: https://whyistheinternetbroken.wordpress.com/2015/06/25/techstorage-virtual… From: toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net> [mailto:toasters-bounces@teaparty.net] On Behalf Of Borzenkov, Andrei Sent: Wednesday, July 01, 2015 10:05 AM To: NGC-g.milazzo-sinergy.it; Toasters Subject: RE: SVM DR in 8.3.1 You are right, you need to create destination SVM in advance with right attributes. According to documentation “For remote data access or data distribution, you can provide read-only access to the NFS clients and SAN hosts from the destination SVM, if you chose to set the identity-preserve option to false.”. Also “SVM Disaster Recovery Preparation Express Guide” gives examples that indicate that you can (actually, must) configure network on destination SVM and access it. From: toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net> [mailto:toasters-bounces@teaparty.net] On Behalf Of Milazzo Giacomo Sent: Wednesday, July 01, 2015 4:33 PM To: Toasters Subject: SVM DR in 8.3.1 Hi all, I know is still RC1 but prior to upgrade a running 8.3 I would try to have more info on a new 8.3.1 feature: the SVM DR. I’ve a customer that on 7Mode ran the DR of CIFS vfiler (joined to a domain) using snapmirror of the vfiler vols, including the root one, and at the DR test/run the source vfiler was stopped and a vfiler create –d command, with the mirrored root specified, let the destination vfiler start with all domain infos, shares on the vole and ip addresses on the DR site with minimal effort. I’ve read the docs that come with 8.3.1 but is not clear. I don’t think that there’s something in SVM DR that permit to recreate the SVM on the destinanation: this must exist in advance, in stopped mode, right? What’s about the maintenance of the IPs? Should I have two identical subnets in both clusters? What if I cannot have two different subnets? Do I have a way to let the replicated SVM being in standby with the data lif with preregistered IPs? Regards

2 1

cDOT and NFS Volumes for VMDK datastores
by John Stoffel 17 Jul '15

17 Jul '15

Guys, I'm starting to re-read TR-3749 again, but since I'm running cDOT 8.2p# on my main two node cluster (soon to be four nodes) I wanted your opinions on how to provision NFS datastores. Right now, when we add new DataStores, we have to goto all 16 ESX hosts in the cluster and manually mount them. Which is doable, but maybe not scalable over time as we'd like to isolate groups and apps into their own NFS volumes if possible. So, knowing that cDOT allows me to setup a volume and then use junction mounts to add more volumes to that name space, does it make sense to do: 1. Create base volume, let's call it '/datastore1' 2. Create sub-volumes of various sizes and performance levels and mount them to: /datastore1/bob /datastore1/jim /datastore1/sam .... 3. When we spin up VMs and asign the data stores, you only need to drill down into the correct area, bob, jim or sam and put the data there. 4. I want to add new FlashPool volume, so I create it and junction mount it to /datastore1/fp1 5. I don't have to add any mounts to the ESX hosts, they just see more growth in the /datastore1/ mount point and keep working. So is this a dumb idea? Or not a supported idea? I know it limits my through put to just a single IP address for traffic, unless I spread out the load by having multiple /datastore#/ volumes spread across the nodes of the cluster, and various volumes junction mounted to each of these master /datastore#/ volumes. Right now we just create new volumes and mount them, but I looking for a more scalable, manageable method. THanks, John

6 8

"Created Date" on CIFS shares
by Edward Rolison 14 Jul '15

14 Jul '15

I've got a scripting task that needs me to work off the creation time of a file. I've been caught out before by 'ctime' being change time, rather than 'create time'. So I thought I was just stuck - however, I've noticed that the Windows 'file creation time' attribute .... actually looks correct. Which has me confused, because I can't see this value from 'Unix side' seemingly at all. I can't tell how Windows knows what the right value is. Is anyone able to enlighten me? Where's creation time stored, and is there a way to access it from Unix?

3 2

rename a CIFS SVM in AD?
by Rue, Randy 14 Jul '15

14 Jul '15

Hello All, I want to migrate the contents of a small file server to an 8.3 SVM and end up with the SVM having the same name in DNS, NetBIOS and the AD. If this were a 7-mode vFiler I could re-run "cifs setup" and change the name to the existing name (after I'd powered down the old file server). Can I do this in 8.3? While I can see commands for renaming an SVM that only appears to rename the SVM itself, not to do anything to the AD. I can see how to add and remove netbios aliases (WINS entries) but again, nothing to do with the AD. Do I have to remove and re-add the CIFS server? And lose all the CIFS shares? Or is there a way to rename the puppy? Randy in Seattle

6 11

Migration question: 7-mode, volumes and qtrees ...
by Waflherder 14 Jul '15

14 Jul '15

Hi All, I have what seems like a pretty basic migration question ... I'm working with a customer who is planning a migration, they are doing a hardware refresh of a pair of FAS2040 systems with ONTAP 8.0.x to a new FAS2552 HA pair with ONTAP 8.2.3P2 (still 7-mode). Amongst other things they have a single large volume / CIFS Share with user home directories. In the past they have had issues with getting the access permissions and quotas for the individual users on this share to work they way would like. It sounds to me like an idea situation to use qtrees, per user, on the new systems. However, what then is the best way to migrate the user data/content? If the target location on the new Filer should consist of numerous per user qtrees, it seems I cannot use "simply" bulk copy with SnapMirror, since the qtrees do not exist on the source. I don't know of a way to convert a directory to be a qtree after it is created ... So perhaps it is necessary to manually (well, with a script) create the individual qtrees and then copy the user data to each new qtree. However then it seems to me that the data will have to be copied from the client side, per user directory i.e. using something like robocopy on Windows or whatever the best UNIX equivalent would be. This all seems a bit more complicated that I had hoped :) Maybe I am missing something - any suggestions? After creating and populating a user qtree, is there some mechanism they could use to redirect access for that specific dataset from the old location to the new qtree? Thanks in advance! Yours, Robb.

1 0

fcp paths in multi-node cluster
by Kevin Richards 14 Jul '15

14 Jul '15

Hi, I have read that an initiator should not be zoned to more than 4 target ports. We have a 8.2 cdot cluster with 12 nodes each having two fcp lifs. So there are potentially 12 paths to storage per fabric. Just curious what strategy has been used to limit the paths? Zoning, port sets, etc.? And any recommendations. Thank you. Kevin

4 4

8.3, NDMP and CommVault
by Rue, Randy 08 Jul '15

08 Jul '15

Hello All, Forgive me asking what are essentially newbie questions but as we're setting up our first 8.3 clusters I pretty much am new. We have a primary cluster, will replicate to a secondary DR cluster in another data center, and want monthly tape backups from the secondary cluster. We have a pretty beefy CommVault setup for our 7-mode NetApp gear and will use the existing infrastructure. First question: we're clear that we do not want "node scoped" backups, but instead want "SVM scoped" backups. But it's not clear from the documents I've found whether we can back up SVM volumes from the cluster level (like we did in 7-mode) or if we need to configure NDMP services, users, and backups for every SVM. >From the NetApp NDMP Express Guide: "If the DMA supports the Cluster Aware Backup (CAB) extension, you can back up all the volumes hosted across different nodes in a cluster by enabling SVM-scoped NDMP, configuring a backup user account, and configuring LIFs for data and control connection." Am I just wanting to believe this supports my wish for cluster-wide backup configuration? Can we configure the cluster and reach all SVM volumes, or do we need to configure for every SVM? Is anyone out there using CommVault and NDMP to back up 8.3 at a cluster level? Or at all? Randy

2 3

NVRAM6 Card Installed in the Wrong Slot
by Stephen Stocke 08 Jul '15

08 Jul '15

Hello Toasters We have an old 3040 running as a single controller in a lab. The head had previously been part of an HA pair and the NVRAM6 card was therefore installed in slot 3 (correct for HA systems). For a single controller the card is supposed to be in slot 1. I'm curious to know what the controller is doing with the NVRAM card? Is it using it at all or just writing everything through straight to disk? Could this cause slower than expected performance? Thanks, Steve __ Background Info __ A colleague recently asked advice on some poor performance with this system in his VMware lab and the first thing that jumps out is the log messages complaining about the card being in the wrong slot. This misconfiguration will be corrected shortly. The system is running 8.1.4 7-mode if that make a difference. The controller has 2 loops of DS14MK4 shelves (168 15K FC drives) and is serving handful iSCSI LUNs to a small vSphere cluster (2 ESXi servers). While looking at stats in OCSM 3.2, I observed >100ms iSCSI write latency with a load of ~300 IOPS and very low CPU utilisation (<20%). -------------------------------------------------------------------------------- This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal -------------------------------------------------------------------------------- disclaimer This email communication does not create or vary any contractual relationship between LogicalisCI and you. Internet communications are not secure and accordingly LogicalisCI does not accept any legal liability for the contents of this message. The contents of this email are confidential to the intended recipient at the email address to which it has been addressed. It may not be disclosed to or used by anyone other than this addressee, nor may it be copied in any way. If received in error, please contact LogicalisCI on the above number (listed as Main) quoting the name of the sender and the addressee and then delete it from your system. Please note that neither LogicalisCI nor the sender accepts any responsibility for viruses and it is your responsibility to scan the email and attachments (if any). Please be aware that LogicalisCI may monitor email traffic data and also email content for security purposes. The following companies are collectively referred to in the above statements as LogicalisCI: Logicalis Channel Islands Limited, Registered in Jersey No: 67161, Registered Office: Rue A La Dame, Five Oaks, St. Saviour, Jersey, JE2 7NH Logicalis Jersey Limited, Registered in Jersey No: 10124, Registered Office: Rue A La Dame, Five Oaks, St. Saviour, Jersey, JE2 7NH Logicalis Guernsey Limited, Registered in Guernsey No: 10896, Registered Office: Pitronnerie Road, St. Peter Port, Guernsey, GY1 2RF

5 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters