toasters

toasters@lists.teaparty.net

13520 discussions

Single command to determine # of files on a volume
by Robert M Bailey 06 Nov '07

06 Nov '07

Besides using quota report and adding up the "File Used" for all the qtrees, is there a simpler way to get a summary file usage on a volume? Bob Bailey Network Centric Systems (NCS) Information Solutions Enterprise Operations Server Management & Central Operations Desk Phone: 972-952-2518 Pager: 972-670-7336 Alpha Pager: 9726707336(a)messaging.nextel.com

5 4

Symantec Antivirus Corporate Edition 10.1 and vscan on filer
by Richard Distrajo 04 Nov '07

04 Nov '07

Any help on registering the filer to the Symantec antivirus server. I tried to put the filer's hostname /ip address to the symantec antivirus center console but no success. Is this version of antivirus can register the CIFS only filer (ONTAP 7.2.2)? I'm getting error "no network provider accepted the given network path" every time I add the filer's IP address to the symantec antivirus console center...both sides can able to ping each other's hostname and user's permission is already been added as operator on the filer's side.... Thanks for your time on this.... Best regards, Richard Send instant messages to your online friends http://uk.messenger.yahoo.com

5 6

Re: R: VMWare CIFS driver
by Alan McLachlan 04 Nov '07

04 Nov '07

Hi Milazzo, You are absolutely correct, and beyond lower performance there's an issue of maintaining the CIFS connection in the case of cluster failover. However, if there's one thing that's true about I.T. it's that if something is _possible_, someone somewhere will have a set of circumstances (not necessarily technical, often financial or political), where that solution makes sense for them. 10 years ago it was a very hard sell to get people to access enterprise databases over any sort of file protocol, now Oracle themselves have vast deployments of Oracle over NFS. And Microsoft SQL Server over CIFS, while not so common, has been used for many years with both reasonable performance and high availability by many NetApp customers (although now we would recommend iSCSI with SnapDrive instead of course), and is a configuration that was originally supported by Microsoft only in the context of NetApp storage. It's very easy to say "that's a stupid idea", but eventually you learn that something that appears to make little sense on it's own can make more sense for a particular environment once all of the issues (technical and non-technical) are considered. There are serious scalability issues with using iSCSI or FCP for VMWare system images (leaving the data volumes aside as a seperate issue that is handled on it's own merits), and the NFS implementation is a very good solution for this apart from improving overall manageability of a large VMWare environment. While I would hestitate before using CIFS for this in any production environment, it may have value in creating a simple and scaleable dev/test solution for a client who then would still use iSCSI or FCP for their production vm images. regards, Alan. ----- Original Message ----- From: "Milazzo Giacomo" To: "M. Vaughn Stewart" , "Alan McLachlan" Subject: R: VMWare CIFS driver Date: Thu, 1 Nov 2007 12:13:11 +0100 Hi vmdk images streamed on CIFS? :-) Sorry if I smile but performances will be...terrible!!! That's the reason for the NFS usage available on VMWare.And, after all, VMWare is a RHEL 4.x Linux distribution..to "read" CIFS the service console should have a SAMBA interface on it...heavy role!!! I agree with the license cost of NFS and CIFS together but, after all..iSCSI is free on NetApp. Create an iSCSI LUN and map it to VMWare...best practice! Bye -------------------------------------------------------------------- Da: owner-toasters(a)mathworks.com per conto di M. Vaughn Stewart Inviato: lun 29/10/2007 5.45 A: Alan McLachlan Cc: toasters(a)mathworks.com Oggetto: Re: VMWare CIFS driver Thanks for bringing this to our attention V Alan McLachlan wrote: > Hi Peter, > > I can't disagree with anything you have said, particularly re. failover (see my post that followed). > > Incidentally though, it was an internal Network Appliance whitepaper that alerted me to the possibility of using CIFS for .vmdk files. > > See section 9.1.3 on page 58 of TR-3505i. > > I understand that being an internal paper I shouldn't be mentioning it here, and the published version of that paper on A-SIS eliminates the discussion of VMWare, I suspect because support issues haven't been nailed down yet. > > Still waiting on feedback from my contact in VMWare, will post when I hear something. > > There are other reasons beside statefulness of CIFS connections to prefer NFS (performance, etc.), but that's the main issue. I only mentioned it so as not to exclude it as a technical possibility, my followup posts were intended to stop anyone getting too excited about it at this stage. Also even if VMWare were to build it into the kernal, I'd still be pushing clients to pay for an NFS licence instead. The issue here is the cost of the NFS licence, which can be considered high for some Windows-only shops. > > regards, > > Alan. > > >> ----- Original Message ----- >> From: "Learmonth, Peter" <Peter.Learmonth(a)netapp.com> >> To: "Alan McLachlan" <alanmac(a)technologist.com>, toasters(a)mathworks.com >> Subject: RE: VMWare CIFS driver >> Date: Sun, 28 Oct 2007 19:10:27 -0700 >> >> >> Hi Alan >> Would you happen to have a URL instead of a IP address? >> >> Given that this comes from an unidentifiable web site, I highly doubt >> this will get any support from VMware, and I can pretty much guarantee >> that this will get no support from NetApp. >> >> More on the RPM itself... >> It contains only an object module, which appears to install in the >> service console Linux, not the VMKernel, although I could be wrong on >> that. >> >> The version on that RPM matches the ESX 3.0.1 COS Linux kernel version. >> >> Besides, while I think NFS is great for VMware, I think CIFS is >> horrible. People who have tried it with VMware server or GSX have had >> some surprises when the storage fails over and CIFS drops the >> connections. It doesn't make any difference whose CIFS server you're >> using. I personally don't think VMware should waste any time developing >> an ESX kernel client. >> >> Thanks anyway. >> >> Peter >> >> >> -----Original Message----- >> From: Alan McLachlan [mailto:alanmac@technologist.com] >> Sent: Sunday, October 28, 2007 4:24 PM >> To: toasters(a)mathworks.com >> Subject: VMWare CIFS driver >> >> >> Hi, >> >> Find it here: >> >> http://89.105.41.70/sites/esx/Lists/Posts/Post.aspx?ID=1 >> >> Enjoy! >> >> regards, >> >> Alan McLachlan >> >> >> >> >>> ----- Original Message ----- >>> From: "Davies,Matt" <MDAVIES(a)generalatlantic.com> >>> To: Peter.Learmonth(a)netapp.com, alanmac(a)technologist.com, >>> toasters(a)mathworks.com >>> Subject: RE: VMware / A-SIS >>> Date: Sun, 28 Oct 2007 21:48:16 -0000 >>> >>> >>> I was about to ask the same question..... >>> >>> -----Original Message----- >>> From: owner-toasters(a)mathworks.com <owner-toasters(a)mathworks.com> >>> To: Alan McLachlan <alanmac(a)technologist.com>; >>> toasters(a)mathworks.com <toasters(a)mathworks.com> >>> Sent: Sun Oct 28 21:09:20 2007 >>> Subject: RE: VMware / A-SIS >>> >>> Ummmm.... >>> What ESX CIFS driver? >>> >>> -----Original Message----- >>> From: Alan McLachlan [mailto:alanmac@technologist.com] >>> Sent: Sunday, October 28, 2007 8:26 AM >>> To: toasters(a)mathworks.com >>> Subject: VMware / A-SIS >>> >>> Hi Vaughn, >>> >>> For small environments on a budget where the cost of additional >>> licenses is an issue, you can use RDM's over iSCSI or FCP for >>> both data LUN's _and_ the VM OS images. You still need VMDK >>> pointer files to enable vmotion. >>> >>> By using RDM's for the VM images you can use lun cloning for R/W >>> snapshots within the same FlexVol, without paying for a FlexClone >>> license and achieve a reasonable level of deduplication without >>> paying >>> >>> for an A-SIS licence. i.e. create "golden images" as source LUNs >>> then use lun clones for the prod, dev, test and backup images of >>> the VM's. >>> >>> However, for larger environments using vmdk's on NAS from NFS >>> exports or CIFS shares for the VM images is a far more scalable >>> and manageable >>> >>> solution as long as you're happy to pay for A-SIS to manage >>> deduplication. I still wouldn't be putting data volumes inside >>> the vmdk's though. >>> >>> (Yes, you can use CIFS for vmdk's in ESX. Not as ideal as NFS for >>> a whole bunch of reasons, but it works via the VMWare ESX CIFS >>> driver and useful if you have to have CIFS for file server >>> consolidation and don't want to pay for NFS licencing as well). >>> >>> Either way, storing your application data in either RDM LUN's or >>> as direct NAS shares makes managing snapshots for dev/test copies >>> and online backups of the production data much simpler to manage. >>> Putting data inside vmdk's limits your functionality particularly >>> for backups. >>> >>> MSCS requires an RDM for the quorum disk, but you can still use a >>> NAS share for the data if your data profile and application >>> characteristics indicate that it makes more sense to do that than >>> use an RDM for the data. >>> >>> regards, >>> >>> Alan McLachlan. >>> >>> -----Original Message----- >>> From: owner-toasters(a)mathworks.com on behalf of M. Vaughn Stewart >>> Sent: Sun 10/28/2007 8:07 AM >>> To: Jack Lyons >>> Cc: Page, Jeremy; toasters(a)mathworks.com >>> Subject: Re: A-SIS questions >>> >>> FlexClone will clone a datastore, for VM level cloning granularity you >>> >>> gonna have to wait I think something is just around the corner. >>> >>> As for MSCS you need RDMs as VMDKs are not supported with MSCS >>> >>> RDMs can be either FCP or iSCSI >>> VMDKs can be on NFS or VMFS (which is over FCP or iSCSI) >>> >>> >>> >>> -- >>> Want an e-mail address like mine? >>> Get a free e-mail account today at www.mail.com! >>> >>> >>> >>> >>> _____________________________________________________________ >>> This e-mail (including all attachments) is confidential and may be >>> >> privileged. >> >>> It is for the exclusive use of the addressee only. If you are not >>> the addressee, you are hereby notified that any dissemination of >>> this communication is strictly prohibited. If you have received >>> this communication in error, please erase all copies of the >>> message and its >>> >>> attachments and notify us immediately at help(a)generalatlantic.com >>> <mailto:help@generalatlantic.com>. Thank You. >>> >> -- >> Want an e-mail address like mine? >> Get a free e-mail account today at www.mail.com! >> > > > > > -- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!

1 0

Windows SnapDrive Query
by Raj Patel 02 Nov '07

02 Nov '07

Simple question - We've just started to utilise some space on a second SAN head and for the life of me I can't remember what I needed to do on the SAN to allow our SnapDrive domain account to connect and create luns on the SAN. I've had a look 'useradmin user list' and 'useradmin domain list' but can't find anything obvious to match our domain 'sduser' account to a SAN account. When I use SnapDrive I get this in the event log - Error code : Access is denied. Verify that you have entered the correct domain and user name during SnapDrive installation and that this account has sufficient privileges to perform this operation. And this as a popup - SnapDrive error Error Description: User sduser does not have the capability to invoke API system-get-version I figure theres something really simple I'm missing or have taken for granted on our other SAN heads in terms of initial setup to use with SnapDrive. Cheers, Raj.

6 8

A-SIS questions
by Page, Jeremy 02 Nov '07

02 Nov '07

I have read some of the info on how A-SIS works but I have a couple of questions: 1) Assuming an average compression rate (say /home with random docs in it) how much of a performance hit does it impose 2) Does it change how much data is sent over the wire when you use SnapMirror/SnapVault? I.e. if I get 30% compression on a 1 gig snapshot do I send 1 gig or 700 mb to update my target? Oh, and for the folks who helped earlier, we are moving our Oracle and ESX systems to NetApp, the pSeries will be fibre connected, at least at first but the ESX stuff is all going on NFS. ~Jeremy This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.

11 18

RE: VMWare CIFS driver
by Alan McLachlan 01 Nov '07

01 Nov '07

Hi Peter, I can't disagree with anything you have said, particularly re. failover (see my post that followed). Incidentally though, it was an internal Network Appliance whitepaper that alerted me to the possibility of using CIFS for .vmdk files. See section 9.1.3 on page 58 of TR-3505i. I understand that being an internal paper I shouldn't be mentioning it here, and the published version of that paper on A-SIS eliminates the discussion of VMWare, I suspect because support issues haven't been nailed down yet. Still waiting on feedback from my contact in VMWare, will post when I hear something. There are other reasons beside statefulness of CIFS connections to prefer NFS (performance, etc.), but that's the main issue. I only mentioned it so as not to exclude it as a technical possibility, my followup posts were intended to stop anyone getting too excited about it at this stage. Also even if VMWare were to build it into the kernal, I'd still be pushing clients to pay for an NFS licence instead. The issue here is the cost of the NFS licence, which can be considered high for some Windows-only shops. regards, Alan. > ----- Original Message ----- > From: "Learmonth, Peter" <Peter.Learmonth(a)netapp.com> > To: "Alan McLachlan" <alanmac(a)technologist.com>, toasters(a)mathworks.com > Subject: RE: VMWare CIFS driver > Date: Sun, 28 Oct 2007 19:10:27 -0700 > > > Hi Alan > Would you happen to have a URL instead of a IP address? > > Given that this comes from an unidentifiable web site, I highly doubt > this will get any support from VMware, and I can pretty much guarantee > that this will get no support from NetApp. > > More on the RPM itself... > It contains only an object module, which appears to install in the > service console Linux, not the VMKernel, although I could be wrong on > that. > > The version on that RPM matches the ESX 3.0.1 COS Linux kernel version. > > Besides, while I think NFS is great for VMware, I think CIFS is > horrible. People who have tried it with VMware server or GSX have had > some surprises when the storage fails over and CIFS drops the > connections. It doesn't make any difference whose CIFS server you're > using. I personally don't think VMware should waste any time developing > an ESX kernel client. > > Thanks anyway. > > Peter > > > -----Original Message----- > From: Alan McLachlan [mailto:alanmac@technologist.com] > Sent: Sunday, October 28, 2007 4:24 PM > To: toasters(a)mathworks.com > Subject: VMWare CIFS driver > > > Hi, > > Find it here: > > http://89.105.41.70/sites/esx/Lists/Posts/Post.aspx?ID=1 > > Enjoy! > > regards, > > Alan McLachlan > > > > > ----- Original Message ----- > > From: "Davies,Matt" <MDAVIES(a)generalatlantic.com> > > To: Peter.Learmonth(a)netapp.com, alanmac(a)technologist.com, > > toasters(a)mathworks.com > > Subject: RE: VMware / A-SIS > > Date: Sun, 28 Oct 2007 21:48:16 -0000 > > > > > > I was about to ask the same question..... > > > > -----Original Message----- > > From: owner-toasters(a)mathworks.com <owner-toasters(a)mathworks.com> > > To: Alan McLachlan <alanmac(a)technologist.com>; > > toasters(a)mathworks.com <toasters(a)mathworks.com> > > Sent: Sun Oct 28 21:09:20 2007 > > Subject: RE: VMware / A-SIS > > > > Ummmm.... > > What ESX CIFS driver? > > > > -----Original Message----- > > From: Alan McLachlan [mailto:alanmac@technologist.com] > > Sent: Sunday, October 28, 2007 8:26 AM > > To: toasters(a)mathworks.com > > Subject: VMware / A-SIS > > > > Hi Vaughn, > > > > For small environments on a budget where the cost of additional > > licenses is an issue, you can use RDM's over iSCSI or FCP for > > both data LUN's _and_ the VM OS images. You still need VMDK > > pointer files to enable vmotion. > > > > By using RDM's for the VM images you can use lun cloning for R/W > > snapshots within the same FlexVol, without paying for a FlexClone > > license and achieve a reasonable level of deduplication without > > paying > > > for an A-SIS licence. i.e. create "golden images" as source LUNs > > then use lun clones for the prod, dev, test and backup images of > > the VM's. > > > > However, for larger environments using vmdk's on NAS from NFS > > exports or CIFS shares for the VM images is a far more scalable > > and manageable > > > solution as long as you're happy to pay for A-SIS to manage > > deduplication. I still wouldn't be putting data volumes inside > > the vmdk's though. > > > > (Yes, you can use CIFS for vmdk's in ESX. Not as ideal as NFS for > > a whole bunch of reasons, but it works via the VMWare ESX CIFS > > driver and useful if you have to have CIFS for file server > > consolidation and don't want to pay for NFS licencing as well). > > > > Either way, storing your application data in either RDM LUN's or > > as direct NAS shares makes managing snapshots for dev/test copies > > and online backups of the production data much simpler to manage. > > Putting data inside vmdk's limits your functionality particularly > > for backups. > > > > MSCS requires an RDM for the quorum disk, but you can still use a > > NAS share for the data if your data profile and application > > characteristics indicate that it makes more sense to do that than > > use an RDM for the data. > > > > regards, > > > > Alan McLachlan. > > > > -----Original Message----- > > From: owner-toasters(a)mathworks.com on behalf of M. Vaughn Stewart > > Sent: Sun 10/28/2007 8:07 AM > > To: Jack Lyons > > Cc: Page, Jeremy; toasters(a)mathworks.com > > Subject: Re: A-SIS questions > > > > FlexClone will clone a datastore, for VM level cloning granularity you > > > gonna have to wait I think something is just around the corner. > > > > As for MSCS you need RDMs as VMDKs are not supported with MSCS > > > > RDMs can be either FCP or iSCSI > > VMDKs can be on NFS or VMFS (which is over FCP or iSCSI) > > > > > > > > -- > > Want an e-mail address like mine? > > Get a free e-mail account today at www.mail.com! > > > > > > > > > > _____________________________________________________________ > > This e-mail (including all attachments) is confidential and may be > privileged. > > It is for the exclusive use of the addressee only. If you are not > > the addressee, you are hereby notified that any dissemination of > > this communication is strictly prohibited. If you have received > > this communication in error, please erase all copies of the > > message and its > > > attachments and notify us immediately at help(a)generalatlantic.com > > <mailto:help@generalatlantic.com>. Thank You. > > > > > > -- > Want an e-mail address like mine? > Get a free e-mail account today at www.mail.com! > -- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!

4 3

RE: RE: Head upgrade 3020 to 3040
by Darish Rajanayagam 30 Oct '07

30 Oct '07

Thanks Peter and everyone else that replied. I will share my procedure/experience once our head-upgrade is completed. Darish. From: Learmonth, Peter [mailto:Peter.Learmonth@netapp.com] Sent: October-24-07 1:38 PM To: Darish Rajanayagam Subject: RE: Head upgrade 3020 to 3040 IQNs will stay the same. LUN S/Ns will change. You should keep a copy of lun show -v from before the upgrade, then set them S/N back the way they were after the swap. lun offline <lun path> lun serial <lun path> <serial number> lun online (Do this before bringing servers back up) This is especially important for VMware in order to avoid resignaturing VMFS and having to re-register VMs. IP addresses will stay the same. Not sure about MAC addrs, but I don't think that matters. Peter ________________________________ From: Darish Rajanayagam [mailto:darishr@softcom.biz] Sent: Wednesday, October 24, 2007 9:41 AM To: toasters(a)mathworks.com Subject: Head upgrade 3020 to 3040 Greeting Toasters, We will soon be upgrading our FAS3020 filer to a FAS3040. The two main protocols the filer is used for is NFS and ISCSI. I am concerned of the implications this upgrade will have on the iscsi network. Has anyone done this type of migration and can share their experience with me? Will upgrading the head unit impact iscsi iqns, lun serial numbers etc? Thanks, Darish.

1 1

Measuring Network Throughput
by Buerger, Andreas 29 Oct '07

29 Oct '07

Hi Toasters, I've got the following question. I'm used to measure the dedicated network throughput between two linux systems with the following method: # Target: TARGET:/>>> netcat -l -p 2000 > /dev/null # Source: SOURCE:/>>> dd if=/dev/zero bs=1M count=1024 | netcat TARGET 2000 1024+0 records in 1024+0 records out 1073741824 bytes (1,1 GB) copied, 9,43544 s, 114 MB/s This simple usage of netcat just provides me the theoretical throughput in our gigabit lan between these two servers. -- My question is, if anybody has an idea how to adopt such a method to a filer? Is there any possibility to measure the theoretical network throughput without producing any disk io's? Best regards Andreas ----------------------------------------- Wincor Nixdorf Int. GmbH WN CIO4 Computing & Storage Heinz-Nixdorf-Ring 1 33106 Paderborn Phone: +49 5251 693 4215 Fax: +49 5251 693 4200 Mail: andreas.buerger(a)wincor-nixdorf.com -----------------------------------------

1 0

VMWare CIFS driver
by Alan McLachlan 29 Oct '07

29 Oct '07

Hi, Find it here: http://89.105.41.70/sites/esx/Lists/Posts/Post.aspx?ID=1 Enjoy! regards, Alan McLachlan > ----- Original Message ----- > From: "Davies,Matt" <MDAVIES(a)generalatlantic.com> > To: Peter.Learmonth(a)netapp.com, alanmac(a)technologist.com, toasters(a)mathworks.com > Subject: RE: VMware / A-SIS > Date: Sun, 28 Oct 2007 21:48:16 -0000 > > > I was about to ask the same question..... > > -----Original Message----- > From: owner-toasters(a)mathworks.com <owner-toasters(a)mathworks.com> > To: Alan McLachlan <alanmac(a)technologist.com>; > toasters(a)mathworks.com <toasters(a)mathworks.com> > Sent: Sun Oct 28 21:09:20 2007 > Subject: RE: VMware / A-SIS > > Ummmm.... > What ESX CIFS driver? > > -----Original Message----- > From: Alan McLachlan [mailto:alanmac@technologist.com] > Sent: Sunday, October 28, 2007 8:26 AM > To: toasters(a)mathworks.com > Subject: VMware / A-SIS > > Hi Vaughn, > > For small environments on a budget where the cost of additional licenses > is an issue, you can use RDM's over iSCSI or FCP for both data LUN's > _and_ the VM OS images. You still need VMDK pointer files to enable > vmotion. > > By using RDM's for the VM images you can use lun cloning for R/W > snapshots within the same FlexVol, without paying for a FlexClone > license and achieve a reasonable level of deduplication without paying > for an A-SIS licence. i.e. create "golden images" as source LUNs then > use lun clones for the prod, dev, test and backup images of the VM's. > > However, for larger environments using vmdk's on NAS from NFS exports or > CIFS shares for the VM images is a far more scalable and manageable > solution as long as you're happy to pay for A-SIS to manage > deduplication. I still wouldn't be putting data volumes inside the > vmdk's though. > > (Yes, you can use CIFS for vmdk's in ESX. Not as ideal as NFS for a > whole bunch of reasons, but it works via the VMWare ESX CIFS driver and > useful if you have to have CIFS for file server consolidation and don't > want to pay for NFS licencing as well). > > Either way, storing your application data in either RDM LUN's or as > direct NAS shares makes managing snapshots for dev/test copies and > online backups of the production data much simpler to manage. Putting > data inside vmdk's limits your functionality particularly for backups. > > MSCS requires an RDM for the quorum disk, but you can still use a NAS > share for the data if your data profile and application characteristics > indicate that it makes more sense to do that than use an RDM for the > data. > > regards, > > Alan McLachlan. > > -----Original Message----- > From: owner-toasters(a)mathworks.com on behalf of M. Vaughn Stewart > Sent: Sun 10/28/2007 8:07 AM > To: Jack Lyons > Cc: Page, Jeremy; toasters(a)mathworks.com > Subject: Re: A-SIS questions > > FlexClone will clone a datastore, for VM level cloning granularity you > gonna have to wait I think something is just around the corner. > > As for MSCS you need RDMs as VMDKs are not supported with MSCS > > RDMs can be either FCP or iSCSI > VMDKs can be on NFS or VMFS (which is over FCP or iSCSI) > > > > -- > Want an e-mail address like mine? > Get a free e-mail account today at www.mail.com! > > > > > _____________________________________________________________ > This e-mail (including all attachments) is confidential and may be privileged. > It is for the exclusive use of the addressee only. If you are not > the addressee, > you are hereby notified that any dissemination of this > communication is strictly > prohibited. If you have received this communication in error, please erase all > copies of the message and its attachments and notify us immediately at > help(a)generalatlantic.com <mailto:help@generalatlantic.com>. Thank You. > -- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!

3 2

VMWare CIFS driver
by Alan McLachlan 29 Oct '07

29 Oct '07

Hi, Following previous post - I have asked a EMC|VMWare contact about whether using the SMB/CIFS driver referred to in my previous post is supported, is unsupported but won't affect support status on the installation, or is unsupported and also breaks support status. When I have some feedback I'll post it. As previously stated, NFS is better for a whole range of reasons but some people may wish to put vmdk's on a CIFS share to save paying for an NFS licence. My only real concern with this would be the state of the CIFS connection after failover in a cluster. regards, Alan McLachlan. > ----- Original Message ----- > From: "Davies,Matt" <MDAVIES(a)generalatlantic.com> > To: Peter.Learmonth(a)netapp.com, alanmac(a)technologist.com, toasters(a)mathworks.com > Subject: RE: VMware / A-SIS > Date: Sun, 28 Oct 2007 21:48:16 -0000 > > > I was about to ask the same question..... > > -----Original Message----- > From: owner-toasters(a)mathworks.com <owner-toasters(a)mathworks.com> > To: Alan McLachlan <alanmac(a)technologist.com>; > toasters(a)mathworks.com <toasters(a)mathworks.com> > Sent: Sun Oct 28 21:09:20 2007 > Subject: RE: VMware / A-SIS > > Ummmm.... > What ESX CIFS driver? > > -----Original Message----- > From: Alan McLachlan [mailto:alanmac@technologist.com] > Sent: Sunday, October 28, 2007 8:26 AM > To: toasters(a)mathworks.com > Subject: VMware / A-SIS > > Hi Vaughn, > > For small environments on a budget where the cost of additional licenses > is an issue, you can use RDM's over iSCSI or FCP for both data LUN's > _and_ the VM OS images. You still need VMDK pointer files to enable > vmotion. > > By using RDM's for the VM images you can use lun cloning for R/W > snapshots within the same FlexVol, without paying for a FlexClone > license and achieve a reasonable level of deduplication without paying > for an A-SIS licence. i.e. create "golden images" as source LUNs then > use lun clones for the prod, dev, test and backup images of the VM's. > > However, for larger environments using vmdk's on NAS from NFS exports or > CIFS shares for the VM images is a far more scalable and manageable > solution as long as you're happy to pay for A-SIS to manage > deduplication. I still wouldn't be putting data volumes inside the > vmdk's though. > > (Yes, you can use CIFS for vmdk's in ESX. Not as ideal as NFS for a > whole bunch of reasons, but it works via the VMWare ESX CIFS driver and > useful if you have to have CIFS for file server consolidation and don't > want to pay for NFS licencing as well). > > Either way, storing your application data in either RDM LUN's or as > direct NAS shares makes managing snapshots for dev/test copies and > online backups of the production data much simpler to manage. Putting > data inside vmdk's limits your functionality particularly for backups. > > MSCS requires an RDM for the quorum disk, but you can still use a NAS > share for the data if your data profile and application characteristics > indicate that it makes more sense to do that than use an RDM for the > data. > > regards, > > Alan McLachlan. > > -----Original Message----- > From: owner-toasters(a)mathworks.com on behalf of M. Vaughn Stewart > Sent: Sun 10/28/2007 8:07 AM > To: Jack Lyons > Cc: Page, Jeremy; toasters(a)mathworks.com > Subject: Re: A-SIS questions > > FlexClone will clone a datastore, for VM level cloning granularity you > gonna have to wait I think something is just around the corner. > > As for MSCS you need RDMs as VMDKs are not supported with MSCS > > RDMs can be either FCP or iSCSI > VMDKs can be on NFS or VMFS (which is over FCP or iSCSI) > > > > -- > Want an e-mail address like mine? > Get a free e-mail account today at www.mail.com! > > > > > _____________________________________________________________ > This e-mail (including all attachments) is confidential and may be privileged. > It is for the exclusive use of the addressee only. If you are not > the addressee, > you are hereby notified that any dissemination of this > communication is strictly > prohibited. If you have received this communication in error, please erase all > copies of the message and its attachments and notify us immediately at > help(a)generalatlantic.com <mailto:help@generalatlantic.com>. Thank You. > -- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!

2 1

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