So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front-engined Acura NSX as well as the Porsche RC3.
The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no?
I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME?
Or am I completely blind and missing something?
Timothy L. Hollingworth Sr. Network Engineer, ePlus Technology Inc. 678.462.6698 (cell) AIM: HollingworthTim YIM: t_holling
Timothy,
You are correct. If we want to use the features of SME and SD for managing backups (Snapshots) we have to use a software iSCSI initiator inside of the VM. The implementations I have done this in have been pretty small, so performance wasn't too much of a worry. I would want to be certain I had enough performance if I was going to do this on a large/high performance system, so lots of testing would be in order.
This is pretty much a limitation (feature?) of VMware rather than NetApp. VMWare sits between the VM and the NetApp system, so the NetApp software (SME/SD) is unable to tell that it is talking to NetApp disk. If VMWare could pass it through properly then there should be nothing stopping the NetApp software recognising it, but at this stage that doesn't work.
Thanks Oliver Bassett
________________________________
From: owner-toasters@mathworks.com on behalf of Timothy Hollingworth Sent: Wed 31/01/2007 2:06 PM To: toasters@mathworks.com Subject: Netapp and VMware... It's all so confusing!
So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front-engined Acura NSX as well as the Porsche RC3.
The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no?
I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME?
Or am I completely blind and missing something?
Timothy L. Hollingworth Sr. Network Engineer, ePlus Technology Inc. 678.462.6698 (cell) AIM: HollingworthTim YIM: t_holling
The information contained in this email is privileged and confidential and intended for the addressee only. If you are not the intended recipient, you are asked to respect that confidentiality and not disclose, copy or make use of its contents. If received in error you are asked to destroy this email and contact the sender immediately. Your assistance is appreciated.
Hi Timothy,
Having been an ASE certified master mechanic in a past life, I can advise you that it is indeed possible to have both of those cars as long as they are kept as separate vehicles. It would real mess if you chopped those cars in half and then welded them together into one new car. Think of all those electrical splices and incompatible electronics! Then, of course, there's that whole warranty and support thing. Who will you go to when the Acura leather cracks?
Or am I completely blind and missing something?
Well, just the fact that neither SnapDrive nor SnapManager are supported with VMware. The only "virtual server" - if you even want to call it that - that is supported with these products is the Exchange virtual server that is created in a Windows ("MSCS") cluster.
Another interesting question that may be worth investigating prior to putting this into production is whether or not Microsoft supports the use of Exchange on VMware. Here are a couple of articles on that: http://support.microsoft.com/kb/897615/ http://support.microsoft.com/kb/320220/
It is not clear in your email what the motivation is to go "virtual" for your Exchange server. If it is for DR purposes, then there may be another way you can accomplish your goals. There is a solution documented in NetApp Knowledgebase article #10542 that takes advantage of the virtual server in Windows clustering. Perhaps this article will help you accomplish your goals? http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb10542
Please let us know if you have any more questions.
Regards,
Paul Benn SnapManager Development Team NetApp
________________________________
From: Timothy Hollingworth [mailto:thollingsworth@eplus.com] Sent: Tuesday, January 30, 2007 5:06 PM To: toasters@mathworks.com Subject: Netapp and VMware... It's all so confusing! So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front-engined Acura NSX as well as the Porsche RC3. The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no? I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME? Or am I completely blind and missing something? Timothy L. Hollingworth Sr. Network Engineer, ePlus Technology Inc. 678.462.6698 (cell) AIM: HollingworthTim YIM: t_holling
Hi Paul, Timothy,
This is a great discussion, and not as easy as we want. Of course do I want to use the best of both worlds. Here some comments:
1) Is it useful to run an exchange server on VMWare? In most of the cases, Paul has maybe right. We have almost 8000 mailboxes, and indeed the added value of VMWare is relative small. We use there snapdrive, snapmanager and MSCS for the backup and DR job. We are running exchange on physical machines. The only reason why I wood use VMWare is for standardisation, but the disadvantages are today to big.
2) But you have the same problem with ms SQL server. We have more than 70 SQL-servers. Here's a really advantage to go to VMWare. That's what we are doing today. But at that moment I loose snapdrive and snapmanager. This hurts. You go back to the stone age:
a. My DBA can't do anymore the basis storage tasks: create lun, expland lun, take snapshots, ... He must, like in the old days, go back to my storage admin and ask him to do this tasks. No, this is not correct, it's much worse: he must go to my VMWare admin, to ask more diskspace and the VMWare admin must go to my storage admin to solve the simple problem. So, my DBA is not happy (he must wait) and also my storage admin is not happy (he must work again). Only the VMWare admin likes this (but he will change his mind) because he's in control of everything :-)
b. We have create a totally different DR and Backup procedure for our SQL servers. It's not as good as snapmanager for SQL. For standardisation of procedures, we use the same scripts and procedures also on our large SQL servers, those are running on physical machines.
3) It's paint full to see that two great product (VMWare and ONTAP/WAFL), with almost the same philosophy (virtualisation of storage or servers, easy of management, ...), are not integrated on a higher level. The combination works fine today, but you loose a lot of the WAFL functionality.
4) iSCSI running in the virtual machine works fine, but it's slow. The latencies of the SQL server (and also the max IO/secs) are for most applications (in our case) not good enough. So that's not an option.
A nice discussion is also the choose between raw devices or VMDK's. I believe that you do a lot more with your VMWare, if you can use raw devices on the netapp. The only problem here is that there is a limit in VMWare of 254 luns in your VMWare "cluster". When you count a least 2 lun's for each VM and we have more than 200 VM's, you see that you reach very fast that limit. I didn't count the preferred setup of my SQL DBA: he want 10 LUNs for every SQL server. So for me, this is not an option. I have to use VMDK's.
So Paul, I think a lot of people are hoping that you will find a way to do this. Snapdrive would be a great start, so that we can distinguish us again from the other guys who don't use netapp, and so that we just can come back in the modern times.
Ps: I prefer the Porsche RC3.
Best regards,
Reinoud Reynders
IT-Manager Infrastructure & Operations
University Hospitals Leuven - Belgium
________________________________
Van: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Namens Benn, Paul Verzonden: woensdag 31 januari 2007 4:06 Aan: Timothy Hollingworth; toasters@mathworks.com Onderwerp: RE: Netapp and VMware... It's all so confusing!
Hi Timothy,
Having been an ASE certified master mechanic in a past life, I can advise you that it is indeed possible to have both of those cars as long as they are kept as separate vehicles. It would real mess if you chopped those cars in half and then welded them together into one new car. Think of all those electrical splices and incompatible electronics! Then, of course, there's that whole warranty and support thing. Who will you go to when the Acura leather cracks?
Or am I completely blind and missing something?
Well, just the fact that neither SnapDrive nor SnapManager are supported with VMware. The only "virtual server" - if you even want to call it that - that is supported with these products is the Exchange virtual server that is created in a Windows ("MSCS") cluster.
Another interesting question that may be worth investigating prior to putting this into production is whether or not Microsoft supports the use of Exchange on VMware. Here are a couple of articles on that:
http://support.microsoft.com/kb/897615/
http://support.microsoft.com/kb/320220/
It is not clear in your email what the motivation is to go "virtual" for your Exchange server. If it is for DR purposes, then there may be another way you can accomplish your goals. There is a solution documented in NetApp Knowledgebase article #10542 that takes advantage of the virtual server in Windows clustering. Perhaps this article will help you accomplish your goals?
http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb10542
Please let us know if you have any more questions.
Regards,
Paul Benn
SnapManager Development Team
NetApp
________________________________
From: Timothy Hollingworth [mailto:thollingsworth@eplus.com] Sent: Tuesday, January 30, 2007 5:06 PM To: toasters@mathworks.com Subject: Netapp and VMware... It's all so confusing!
So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front-engined Acura NSX as well as the Porsche RC3.
The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no?
I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME?
Or am I completely blind and missing something?
Timothy L. Hollingworth
Sr. Network Engineer, ePlus Technology Inc.
678.462.6698 (cell)
AIM: HollingworthTim
YIM: t_holling
Hi.
i think Reimound is exactly what it is about. For big Exchange Installations there is really no need for VMWare. We have an Ex2k3 site with about 6000 users, which is not to big, and even VMWare said that they would not virtualize our Exchange Servers. Another point is that one big figure for Ex-performance is the memory which is limited to 3GB in Ex2k3 (with the 3gb-switch). But there is only one "store"-process running and if you look in your taskmanager on your Ex-Servers you may see, that it is using about 800MB-1GB, seldom more. So you see that with Ex2k3 virtualisation may be ok. But with Ex2k7 there is a complete new memorymanagement. I do not know the new limit but be sure, that Ex2k7 will make use of the memory it can get! So the idea would be to have a lot of memory for Ex2k7 to make it fast, memory that can no longer be used by other VMs running on the same host....Sorry for drifting away from storage :D
But from the point of interaction between Netapp and VMWare i can only agree that there are a lot of things which are "nice-to-have", e.g. some kind of Snapmanager for VMWare which makes it possible to use the mechanisms of VMWare to set a VM into backup mode (not suspend, like discribed on NOW!) and create a snapshot on the Server.
By the way, has anybody already made live experience with VMWare vmdk's on ISCSI Lun's or NFS-exports?!? Is FC really the protocol of choice for a modern systems-architect :D?
I prefer Porsche,too...
Regards
Jochen
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Reinoud Reynders Sent: Wednesday, January 31, 2007 9:08 AM To: Benn, Paul; Timothy Hollingworth; toasters@mathworks.com Subject: RE: Netapp and VMware... It's all so confusing!
Hi Paul, Timothy,
This is a great discussion, and not as easy as we want. Of course do I want to use the best of both worlds. Here some comments:
1) Is it useful to run an exchange server on VMWare? In most of the cases, Paul has maybe right. We have almost 8000 mailboxes, and indeed the added value of VMWare is relative small. We use there snapdrive, snapmanager and MSCS for the backup and DR job. We are running exchange on physical machines. The only reason why I wood use VMWare is for standardisation, but the disadvantages are today to big.
2) But you have the same problem with ms SQL server. We have more than 70 SQL-servers. Here's a really advantage to go to VMWare. That's what we are doing today. But at that moment I loose snapdrive and snapmanager. This hurts. You go back to the stone age:
a. My DBA can't do anymore the basis storage tasks: create lun, expland lun, take snapshots, ... He must, like in the old days, go back to my storage admin and ask him to do this tasks. No, this is not correct, it's much worse: he must go to my VMWare admin, to ask more diskspace and the VMWare admin must go to my storage admin to solve the simple problem. So, my DBA is not happy (he must wait) and also my storage admin is not happy (he must work again). Only the VMWare admin likes this (but he will change his mind) because he's in control of everything :-)
b. We have create a totally different DR and Backup procedure for our SQL servers. It's not as good as snapmanager for SQL. For standardisation of procedures, we use the same scripts and procedures also on our large SQL servers, those are running on physical machines.
3) It's paint full to see that two great product (VMWare and ONTAP/WAFL), with almost the same philosophy (virtualisation of storage or servers, easy of management, ...), are not integrated on a higher level. The combination works fine today, but you loose a lot of the WAFL functionality.
4) iSCSI running in the virtual machine works fine, but it's slow. The latencies of the SQL server (and also the max IO/secs) are for most applications (in our case) not good enough. So that's not an option.
A nice discussion is also the choose between raw devices or VMDK's. I believe that you do a lot more with your VMWare, if you can use raw devices on the netapp. The only problem here is that there is a limit in VMWare of 254 luns in your VMWare "cluster". When you count a least 2 lun's for each VM and we have more than 200 VM's, you see that you reach very fast that limit. I didn't count the preferred setup of my SQL DBA: he want 10 LUNs for every SQL server. So for me, this is not an option. I have to use VMDK's.
So Paul, I think a lot of people are hoping that you will find a way to do this. Snapdrive would be a great start, so that we can distinguish us again from the other guys who don't use netapp, and so that we just can come back in the modern times.
Ps: I prefer the Porsche RC3.
Best regards,
Reinoud Reynders
IT-Manager Infrastructure & Operations
University Hospitals Leuven - Belgium
________________________________
Van: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Namens Benn, Paul Verzonden: woensdag 31 januari 2007 4:06 Aan: Timothy Hollingworth; toasters@mathworks.com Onderwerp: RE: Netapp and VMware... It's all so confusing!
Hi Timothy,
Having been an ASE certified master mechanic in a past life, I can advise you that it is indeed possible to have both of those cars as long as they are kept as separate vehicles. It would real mess if you chopped those cars in half and then welded them together into one new car. Think of all those electrical splices and incompatible electronics! Then, of course, there's that whole warranty and support thing. Who will you go to when the Acura leather cracks?
Or am I completely blind and missing something?
Well, just the fact that neither SnapDrive nor SnapManager are supported with VMware. The only "virtual server" - if you even want to call it that - that is supported with these products is the Exchange virtual server that is created in a Windows ("MSCS") cluster.
Another interesting question that may be worth investigating prior to putting this into production is whether or not Microsoft supports the use of Exchange on VMware. Here are a couple of articles on that:
http://support.microsoft.com/kb/897615/
http://support.microsoft.com/kb/320220/
It is not clear in your email what the motivation is to go "virtual" for your Exchange server. If it is for DR purposes, then there may be another way you can accomplish your goals. There is a solution documented in NetApp Knowledgebase article #10542 that takes advantage of the virtual server in Windows clustering. Perhaps this article will help you accomplish your goals?
http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb10542
Please let us know if you have any more questions.
Regards,
Paul Benn
SnapManager Development Team
NetApp
________________________________
From: Timothy Hollingworth [mailto:thollingsworth@eplus.com] Sent: Tuesday, January 30, 2007 5:06 PM To: toasters@mathworks.com Subject: Netapp and VMware... It's all so confusing!
So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front-engined Acura NSX as well as the Porsche RC3.
The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no?
I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME?
Or am I completely blind and missing something?
Timothy L. Hollingworth
Sr. Network Engineer, ePlus Technology Inc.
678.462.6698 (cell)
AIM: HollingworthTim
YIM: t_holling
Lots of good points here. Whether or not you virtualize Ex2K3 depends upon a great many factors. In many cases (especially for larger installations), virtualizing Exchange may not be the optimal approach. However, in smaller installations, virtualizing Exchange is not necessarily a bad thing. Of course, as pointed out already, Ex2K7 is a different beast altogether, primarily because it is 64-bit only.
I would be surprised if both NetApp and VMware were *NOT* already working on tools to help improve the NetApp-VMware relationship. In fact, I heard rumors at VMworld 2006 that there was a "SnapManager for VMware" in development. Supposedly, this would bring about the same level of application support that other members of the SnapManager family current provide for Exchange, Oracle, UNIX, and SQL Server.
I do have live experience with running VMDKs via iSCSI, but not via NFS (not yet, anyway). VMware has presented statistics that show iSCSI on Gigabit Ethernet to run at about 70% of the speed of 2Gb Fibre Channel. (If you were at VMworld and participated in one of the Performance lab, those statistics were borne out in a real-world configuration using NetApp storage systems.)
Regards, Scott Lowe Senior Engineer ePlus Technology, Inc. slowe@eplus.com Office: 919.326.3641 Fax: 919.326.3691 Mobile: 919.274.0462
On Jan 31, 2007, at 7:40 AM, Willeke, Jochen wrote:
Hi.
i think Reimound is exactly what it is about. For big Exchange Installations there is really no need for VMWare. We have an Ex2k3 site with about 6000 users, which is not to big, and even VMWare said that they would not virtualize our Exchange Servers. Another point is that one big figure for Ex-performance is the memory which is limited to 3GB in Ex2k3 (with the 3gb-switch). But there is only one "store"-process running and if you look in your taskmanager on your Ex-Servers you may see, that it is using about 800MB-1GB, seldom more. So you see that with Ex2k3 virtualisation may be ok. But with Ex2k7 there is a complete new memorymanagement. I do not know the new limit but be sure, that Ex2k7 will make use of the memory it can get! So the idea would be to have a lot of memory for Ex2k7 to make it fast, memory that can no longer be used by other VMs running on the same host....Sorry for drifting away from storage :D
But from the point of interaction between Netapp and VMWare i can only agree that there are a lot of things which are "nice-to-have", e.g. some kind of Snapmanager for VMWare which makes it possible to use the mechanisms of VMWare to set a VM into backup mode (not suspend, like discribed on NOW!) and create a snapshot on the Server.
By the way, has anybody already made live experience with VMWare vmdk's on ISCSI Lun's or NFS-exports?!? Is FC really the protocol of choice for a modern systems-architect :D?
I prefer Porsche,too...
Regards
Jochen
From: owner-toasters@mathworks.com [mailto:owner- toasters@mathworks.com] On Behalf Of Reinoud Reynders Sent: Wednesday, January 31, 2007 9:08 AM To: Benn, Paul; Timothy Hollingworth; toasters@mathworks.com Subject: RE: Netapp and VMware... It's all so confusing!
Hi Paul, Timothy,
This is a great discussion, and not as easy as we want. Of course do I want to use the best of both worlds. Here some comments:
Is it useful to run an exchange server on VMWare? In mostof the cases, Paul has maybe right. We have almost 8000 mailboxes, and indeed the added value of VMWare is relative small. We use there snapdrive, snapmanager and MSCS for the backup and DR job. We are running exchange on physical machines. The only reason why I wood use VMWare is for standardisation, but the disadvantages are today to big.
But you have the same problem with ms SQL server. We havemore than 70 SQL-servers. Here’s a really advantage to go to VMWare. That’s what we are doing today. But at that moment I loose snapdrive and snapmanager. This hurts. You go back to the stone age:
a. My DBA can’t do anymore the basis storage tasks: create lun, expland lun, take snapshots, … He must, like in the old days, go back to my storage admin and ask him to do this tasks. No, this is not correct, it’s much worse: he must go to my VMWare admin, to ask more diskspace and the VMWare admin must go to my storage admin to solve the simple problem. So, my DBA is not happy (he must wait) and also my storage admin is not happy (he must work again). Only the VMWare admin likes this (but he will change his mind) because he’s in control of everything J
b. We have create a totally different DR and Backup procedure for our SQL servers. It’s not as good as snapmanager for SQL. For standardisation of procedures, we use the same scripts and procedures also on our large SQL servers, those are running on physical machines.
It’s paint full to see that two great product (VMWare andONTAP/WAFL), with almost the same philosophy (virtualisation of storage or servers, easy of management, …), are not integrated on a higher level. The combination works fine today, but you loose a lot of the WAFL functionality.
iSCSI running in the virtual machine works fine, but it’sslow. The latencies of the SQL server (and also the max IO/secs) are for most applications (in our case) not good enough. So that’s not an option.
A nice discussion is also the choose between raw devices or VMDK’s. I believe that you do a lot more with your VMWare, if you can use raw devices on the netapp. The only problem here is that there is a limit in VMWare of 254 luns in your VMWare “cluster”. When you count a least 2 lun’s for each VM and we have more than 200 VM’s, you see that you reach very fast that limit. I didn’t count the preferred setup of my SQL DBA: he want 10 LUNs for every SQL server. So for me, this is not an option. I have to use VMDK’s.
So Paul, I think a lot of people are hoping that you will find a way to do this. Snapdrive would be a great start, so that we can distinguish us again from the other guys who don’t use netapp, and so that we just can come back in the modern times.
Ps: I prefer the Porsche RC3.
Best regards,
Reinoud Reynders
IT-Manager Infrastructure & Operations
University Hospitals Leuven - Belgium
Van: owner-toasters@mathworks.com [mailto:owner- toasters@mathworks.com] NamensBenn, Paul Verzonden: woensdag 31 januari 2007 4:06 Aan: Timothy Hollingworth; toasters@mathworks.com Onderwerp: RE: Netapp and VMware... It's all so confusing!
Hi Timothy,
Having been an ASE certified master mechanic in a past life, I can advise you that it is indeed possible to have both of those cars as long as they are kept as separate vehicles. It would real mess if you chopped those cars in half and then welded them together into one new car. Think of all those electrical splices and incompatible electronics! Then, of course, there's that whole warranty and support thing. Who will you go to when the Acura leather cracks?
Or am I completely blind and missing something?
Well, just the fact that neither SnapDrive nor SnapManager are supported with VMware. The only "virtual server" - if you even want to call it that - that is supported with these products is the Exchange virtual server that is created in a Windows ("MSCS") cluster.
Another interesting question that may be worth investigating prior to putting this into production is whether or not Microsoft supports the use of Exchange on VMware. Here are a couple of articles on that:
http://support.microsoft.com/kb/897615/
http://support.microsoft.com/kb/320220/
It is not clear in your email what the motivation is to go "virtual" for your Exchange server. If it is for DR purposes, then there may be another way you can accomplish your goals. There is a solution documented in NetApp Knowledgebase article #10542 that takes advantage of the virtual server in Windows clustering. Perhaps this article will help you accomplish your goals?
http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb10542
Please let us know if you have any more questions.
Regards,
Paul Benn
SnapManager Development Team
NetApp
From: Timothy Hollingworth [mailto:thollingsworth@eplus.com] Sent: Tuesday, January 30, 2007 5:06 PM To: toasters@mathworks.com Subject: Netapp and VMware... It's all so confusing!
So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front- engined Acura NSX as well as the Porsche RC3.
The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no?
I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME?
Or am I completely blind and missing something?
Timothy L. Hollingworth
Sr. Network Engineer, ePlus Technology Inc.
678.462.6698 (cell)
AIM: HollingworthTim
YIM: t_holling
Hi,
do i get it right that VMWare stated ISCSI on Gigabit Ethernet is at 70%speed of 2 GB FC?!? That would mean that ISCSI on a trunked 2Gbit Ethernet would be nearly the same speed as FC!
Would be great to know as we always were told that ISCSI is too slow and dangerous :D
Best Regards and thanks a lot for sharing your experience
Jochen
-----Original Message----- From: Scott Lowe [mailto:slowe@EPLUS.com] Sent: Wednesday, January 31, 2007 3:16 PM To: toasters@mathworks.com Cc: Willeke, Jochen; Reinoud Reynders; Benn, Paul; Timothy Hollingworth Subject: Re: Netapp and VMware... It's all so confusing!
Lots of good points here. Whether or not you virtualize Ex2K3 depends upon a great many factors. In many cases (especially for larger installations), virtualizing Exchange may not be the optimal approach. However, in smaller installations, virtualizing Exchange is not necessarily a bad thing. Of course, as pointed out already, Ex2K7 is a different beast altogether, primarily because it is 64-bit only.
I would be surprised if both NetApp and VMware were *NOT* already working on tools to help improve the NetApp-VMware relationship. In fact, I heard rumors at VMworld 2006 that there was a "SnapManager for VMware" in development. Supposedly, this would bring about the same level of application support that other members of the SnapManager family current provide for Exchange, Oracle, UNIX, and SQL Server.
I do have live experience with running VMDKs via iSCSI, but not via NFS (not yet, anyway). VMware has presented statistics that show iSCSI on Gigabit Ethernet to run at about 70% of the speed of 2Gb Fibre Channel. (If you were at VMworld and participated in one of the Performance lab, those statistics were borne out in a real-world configuration using NetApp storage systems.)
Regards, Scott Lowe Senior Engineer ePlus Technology, Inc. slowe@eplus.com Office: 919.326.3641 Fax: 919.326.3691 Mobile: 919.274.0462
On Jan 31, 2007, at 7:40 AM, Willeke, Jochen wrote:
Hi.
i think Reimound is exactly what it is about. For big Exchange Installations there is really no need for VMWare. We have an Ex2k3 site with about 6000 users, which is not to big, and even VMWare said that they would not virtualize our Exchange Servers. Another point is that one big figure for Ex-performance is the memory which is limited to 3GB in Ex2k3 (with the 3gb-switch). But there is only one "store"-process running and if you look in your taskmanager on your Ex-Servers you may see, that it is using about 800MB-1GB, seldom more. So you see that with Ex2k3 virtualisation may be ok. But with Ex2k7 there is a complete new memorymanagement. I do not know the new limit but be sure, that Ex2k7 will make use of the memory it can get! So the idea would be to have a lot of memory for Ex2k7 to make it fast, memory that can no longer be used by other VMs running on the same host....Sorry for drifting away from storage :D
But from the point of interaction between Netapp and VMWare i can only agree that there are a lot of things which are "nice-to-have", e.g. some kind of Snapmanager for VMWare which makes it possible to use the mechanisms of VMWare to set a VM into backup mode (not suspend, like discribed on NOW!) and create a snapshot on the Server.
By the way, has anybody already made live experience with VMWare vmdk's on ISCSI Lun's or NFS-exports?!? Is FC really the protocol of choice for a modern systems-architect :D?
I prefer Porsche,too...
Regards
Jochen
From: owner-toasters@mathworks.com [mailto:owner- toasters@mathworks.com] On Behalf Of Reinoud Reynders Sent: Wednesday, January 31, 2007 9:08 AM To: Benn, Paul; Timothy Hollingworth; toasters@mathworks.com Subject: RE: Netapp and VMware... It's all so confusing!
Hi Paul, Timothy,
This is a great discussion, and not as easy as we want. Of course do I want to use the best of both worlds. Here some comments:
Is it useful to run an exchange server on VMWare? In mostof the cases, Paul has maybe right. We have almost 8000 mailboxes, and indeed the added value of VMWare is relative small. We use there snapdrive, snapmanager and MSCS for the backup and DR job. We are running exchange on physical machines. The only reason why I wood use VMWare is for standardisation, but the disadvantages are today to big.
But you have the same problem with ms SQL server. We havemore than 70 SQL-servers. Here's a really advantage to go to VMWare. That's what we are doing today. But at that moment I loose snapdrive and snapmanager. This hurts. You go back to the stone age:
a. My DBA can't do anymore the basis storage tasks: create lun, expland lun, take snapshots, ... He must, like in the old days, go back to my storage admin and ask him to do this tasks. No, this is not correct, it's much worse: he must go to my VMWare admin, to ask more diskspace and the VMWare admin must go to my storage admin to solve the simple problem. So, my DBA is not happy (he must wait) and also my storage admin is not happy (he must work again). Only the VMWare admin likes this (but he will change his mind) because he's in control of everything J
b. We have create a totally different DR and Backup procedure for our SQL servers. It's not as good as snapmanager for SQL. For standardisation of procedures, we use the same scripts and procedures also on our large SQL servers, those are running on physical machines.
It's paint full to see that two great product (VMWare andONTAP/WAFL), with almost the same philosophy (virtualisation of storage or servers, easy of management, ...), are not integrated on a
higher level. The combination works fine today, but you loose a lot of the WAFL functionality.
iSCSI running in the virtual machine works fine, but it'sslow. The latencies of the SQL server (and also the max IO/secs) are for most applications (in our case) not good enough. So that's not an option.
A nice discussion is also the choose between raw devices or VMDK's. I believe that you do a lot more with your VMWare, if you can use raw devices on the netapp. The only problem here is that there is a limit in VMWare of 254 luns in your VMWare "cluster". When you count a least 2 lun's for each VM and we have more than 200 VM's, you see that you reach very fast that limit. I didn't count the preferred setup of my SQL DBA: he want 10 LUNs for every SQL server. So for me, this is not an option. I have to use VMDK's.
So Paul, I think a lot of people are hoping that you will find a way to do this. Snapdrive would be a great start, so that we can distinguish us again from the other guys who don't use netapp, and so that we just can come back in the modern times.
Ps: I prefer the Porsche RC3.
Best regards,
Reinoud Reynders
IT-Manager Infrastructure & Operations
University Hospitals Leuven - Belgium
Van: owner-toasters@mathworks.com [mailto:owner- toasters@mathworks.com] NamensBenn, Paul Verzonden: woensdag 31 januari 2007 4:06 Aan: Timothy Hollingworth; toasters@mathworks.com Onderwerp: RE: Netapp and VMware... It's all so confusing!
Hi Timothy,
Having been an ASE certified master mechanic in a past life, I can advise you that it is indeed possible to have both of those cars as long as they are kept as separate vehicles. It would real mess if you chopped those cars in half and then welded them together into one new car. Think of all those electrical splices and incompatible electronics! Then, of course, there's that whole warranty and support thing. Who will you go to when the Acura leather cracks?
Or am I completely blind and missing something?
Well, just the fact that neither SnapDrive nor SnapManager are supported with VMware. The only "virtual server" - if you even want to call it that - that is supported with these products is the Exchange virtual server that is created in a Windows ("MSCS") cluster.
Another interesting question that may be worth investigating prior to putting this into production is whether or not Microsoft supports the use of Exchange on VMware. Here are a couple of articles on that:
http://support.microsoft.com/kb/897615/
http://support.microsoft.com/kb/320220/
It is not clear in your email what the motivation is to go "virtual" for your Exchange server. If it is for DR purposes, then there may be another way you can accomplish your goals. There is a solution documented in NetApp Knowledgebase article #10542 that takes advantage of the virtual server in Windows clustering. Perhaps this article will help you accomplish your goals?
http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb10542
Please let us know if you have any more questions.
Regards,
Paul Benn
SnapManager Development Team
NetApp
From: Timothy Hollingworth [mailto:thollingsworth@eplus.com] Sent: Tuesday, January 30, 2007 5:06 PM To: toasters@mathworks.com Subject: Netapp and VMware... It's all so confusing!
So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front- engined Acura NSX as well as the Porsche RC3.
The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no?
I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME?
Or am I completely blind and missing something?
Timothy L. Hollingworth
Sr. Network Engineer, ePlus Technology Inc.
678.462.6698 (cell)
AIM: HollingworthTim
YIM: t_holling
Careful there.
A single host usually cannot get more than a single link of bandwidth to the filer. If you have multiple clients and they are balanced across the links, then you can fill up more than one.
On 1/31/07, Willeke, Jochen Jochen.Willeke@wincor-nixdorf.com wrote:
Hi,
do i get it right that VMWare stated ISCSI on Gigabit Ethernet is at 70%speed of 2 GB FC?!? That would mean that ISCSI on a trunked 2Gbit Ethernet would be nearly the same speed as FC!
Would be great to know as we always were told that ISCSI is too slow and dangerous :D
Best Regards and thanks a lot for sharing your experience
Jochen
-----Original Message----- From: Scott Lowe [mailto:slowe@EPLUS.com] Sent: Wednesday, January 31, 2007 3:16 PM To: toasters@mathworks.com Cc: Willeke, Jochen; Reinoud Reynders; Benn, Paul; Timothy Hollingworth Subject: Re: Netapp and VMware... It's all so confusing!
Lots of good points here. Whether or not you virtualize Ex2K3 depends upon a great many factors. In many cases (especially for larger installations), virtualizing Exchange may not be the optimal approach. However, in smaller installations, virtualizing Exchange is not necessarily a bad thing. Of course, as pointed out already, Ex2K7 is a different beast altogether, primarily because it is 64-bit only.
I would be surprised if both NetApp and VMware were *NOT* already working on tools to help improve the NetApp-VMware relationship. In fact, I heard rumors at VMworld 2006 that there was a "SnapManager for VMware" in development. Supposedly, this would bring about the same level of application support that other members of the SnapManager family current provide for Exchange, Oracle, UNIX, and SQL Server.
I do have live experience with running VMDKs via iSCSI, but not via NFS (not yet, anyway). VMware has presented statistics that show iSCSI on Gigabit Ethernet to run at about 70% of the speed of 2Gb Fibre Channel. (If you were at VMworld and participated in one of the Performance lab, those statistics were borne out in a real-world configuration using NetApp storage systems.)
Regards, Scott Lowe Senior Engineer ePlus Technology, Inc. slowe@eplus.com Office: 919.326.3641 Fax: 919.326.3691 Mobile: 919.274.0462
On Jan 31, 2007, at 7:40 AM, Willeke, Jochen wrote:
Hi.
i think Reimound is exactly what it is about. For big Exchange Installations there is really no need for VMWare. We have an Ex2k3 site with about 6000 users, which is not to big, and even VMWare said that they would not virtualize our Exchange Servers. Another point is that one big figure for Ex-performance is the memory which is limited to 3GB in Ex2k3 (with the 3gb-switch). But there is only one "store"-process running and if you look in your taskmanager on your Ex-Servers you may see, that it is using about 800MB-1GB, seldom more. So you see that with Ex2k3 virtualisation may be ok. But with Ex2k7 there is a complete new memorymanagement. I do not know the new limit but be sure, that Ex2k7 will make use of the memory it can get! So the idea would be to have a lot of memory for Ex2k7 to make it fast, memory that can no longer be used by other VMs running on the same host....Sorry for drifting away from storage :D
But from the point of interaction between Netapp and VMWare i can only agree that there are a lot of things which are "nice-to-have", e.g. some kind of Snapmanager for VMWare which makes it possible to use the mechanisms of VMWare to set a VM into backup mode (not suspend, like discribed on NOW!) and create a snapshot on the Server.
By the way, has anybody already made live experience with VMWare vmdk's on ISCSI Lun's or NFS-exports?!? Is FC really the protocol of choice for a modern systems-architect :D?
I prefer Porsche,too...
Regards
Jochen
From: owner-toasters@mathworks.com [mailto:owner- toasters@mathworks.com] On Behalf Of Reinoud Reynders Sent: Wednesday, January 31, 2007 9:08 AM To: Benn, Paul; Timothy Hollingworth; toasters@mathworks.com Subject: RE: Netapp and VMware... It's all so confusing!
Hi Paul, Timothy,
This is a great discussion, and not as easy as we want. Of course do I want to use the best of both worlds. Here some comments:
Is it useful to run an exchange server on VMWare? In mostof the cases, Paul has maybe right. We have almost 8000 mailboxes, and indeed the added value of VMWare is relative small. We use there snapdrive, snapmanager and MSCS for the backup and DR job. We are running exchange on physical machines. The only reason why I wood use VMWare is for standardisation, but the disadvantages are today to big.
But you have the same problem with ms SQL server. We havemore than 70 SQL-servers. Here's a really advantage to go to VMWare. That's what we are doing today. But at that moment I loose snapdrive and snapmanager. This hurts. You go back to the stone age:
a. My DBA can't do anymore the basis storage tasks: create lun, expland lun, take snapshots, ... He must, like in the old days, go back to my storage admin and ask him to do this tasks. No, this is not correct, it's much worse: he must go to my VMWare admin, to ask more diskspace and the VMWare admin must go to my storage admin to solve the simple problem. So, my DBA is not happy (he must wait) and also my storage admin is not happy (he must work again). Only the VMWare admin likes this (but he will change his mind) because he's in control of everything J
b. We have create a totally different DR and Backup procedure for our SQL servers. It's not as good as snapmanager for SQL. For standardisation of procedures, we use the same scripts and procedures also on our large SQL servers, those are running on physical machines.
It's paint full to see that two great product (VMWare andONTAP/WAFL), with almost the same philosophy (virtualisation of storage or servers, easy of management, ...), are not integrated on a
higher level. The combination works fine today, but you loose a lot of the WAFL functionality.
iSCSI running in the virtual machine works fine, but it'sslow. The latencies of the SQL server (and also the max IO/secs) are for most applications (in our case) not good enough. So that's not an option.
A nice discussion is also the choose between raw devices or VMDK's. I believe that you do a lot more with your VMWare, if you can use raw devices on the netapp. The only problem here is that there is a limit in VMWare of 254 luns in your VMWare "cluster". When you count a least 2 lun's for each VM and we have more than 200 VM's, you see that you reach very fast that limit. I didn't count the preferred setup of my SQL DBA: he want 10 LUNs for every SQL server. So for me, this is not an option. I have to use VMDK's.
So Paul, I think a lot of people are hoping that you will find a way to do this. Snapdrive would be a great start, so that we can distinguish us again from the other guys who don't use netapp, and so that we just can come back in the modern times.
Ps: I prefer the Porsche RC3.
Best regards,
Reinoud Reynders
IT-Manager Infrastructure & Operations
University Hospitals Leuven - Belgium
Van: owner-toasters@mathworks.com [mailto:owner- toasters@mathworks.com] NamensBenn, Paul Verzonden: woensdag 31 januari 2007 4:06 Aan: Timothy Hollingworth; toasters@mathworks.com Onderwerp: RE: Netapp and VMware... It's all so confusing!
Hi Timothy,
Having been an ASE certified master mechanic in a past life, I can advise you that it is indeed possible to have both of those cars as long as they are kept as separate vehicles. It would real mess if you chopped those cars in half and then welded them together into one new car. Think of all those electrical splices and incompatible electronics! Then, of course, there's that whole warranty and support thing. Who will you go to when the Acura leather cracks?
Or am I completely blind and missing something?
Well, just the fact that neither SnapDrive nor SnapManager are supported with VMware. The only "virtual server" - if you even want to call it that - that is supported with these products is the Exchange virtual server that is created in a Windows ("MSCS") cluster.
Another interesting question that may be worth investigating prior to putting this into production is whether or not Microsoft supports the use of Exchange on VMware. Here are a couple of articles on that:
http://support.microsoft.com/kb/897615/
http://support.microsoft.com/kb/320220/
It is not clear in your email what the motivation is to go "virtual" for your Exchange server. If it is for DR purposes, then there may be another way you can accomplish your goals. There is a solution documented in NetApp Knowledgebase article #10542 that takes advantage of the virtual server in Windows clustering. Perhaps this article will help you accomplish your goals?
http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb10542
Please let us know if you have any more questions.
Regards,
Paul Benn
SnapManager Development Team
NetApp
From: Timothy Hollingworth [mailto:thollingsworth@eplus.com] Sent: Tuesday, January 30, 2007 5:06 PM To: toasters@mathworks.com Subject: Netapp and VMware... It's all so confusing!
So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front- engined Acura NSX as well as the Porsche RC3.
The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no?
I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME?
Or am I completely blind and missing something?
Timothy L. Hollingworth
Sr. Network Engineer, ePlus Technology Inc.
678.462.6698 (cell)
AIM: HollingworthTim
YIM: t_holling
Hi,
thanks for the hint! But 70% on 1Gbit is more than I expected.
Regards
Jochen
-----Original Message----- From: tmac [mailto:tmacmd@gmail.com] Sent: Wednesday, January 31, 2007 4:25 PM To: Willeke, Jochen Cc: Scott Lowe; toasters@mathworks.com Subject: Re: Netapp and VMware... It's all so confusing!
Careful there.
A single host usually cannot get more than a single link of bandwidth to the filer. If you have multiple clients and they are balanced across the links, then you can fill up more than one.
On 1/31/07, Willeke, Jochen Jochen.Willeke@wincor-nixdorf.com wrote:
Hi,
do i get it right that VMWare stated ISCSI on Gigabit Ethernet is at 70%speed of 2 GB FC?!? That would mean that ISCSI on a trunked 2Gbit Ethernet would be nearly the same speed as FC!
Would be great to know as we always were told that ISCSI is too slow
and
dangerous :D
Best Regards and thanks a lot for sharing your experience
Jochen
-----Original Message----- From: Scott Lowe [mailto:slowe@EPLUS.com] Sent: Wednesday, January 31, 2007 3:16 PM To: toasters@mathworks.com Cc: Willeke, Jochen; Reinoud Reynders; Benn, Paul; Timothy
Hollingworth
Subject: Re: Netapp and VMware... It's all so confusing!
Lots of good points here. Whether or not you virtualize Ex2K3 depends upon a great many factors. In many cases (especially for larger installations), virtualizing Exchange may not be the optimal approach. However, in smaller installations, virtualizing Exchange is not necessarily a bad thing. Of course, as pointed out already, Ex2K7 is a different beast altogether, primarily because it is 64-bit only.
I would be surprised if both NetApp and VMware were *NOT* already working on tools to help improve the NetApp-VMware relationship. In fact, I heard rumors at VMworld 2006 that there was a "SnapManager for VMware" in development. Supposedly, this would bring about the same level of application support that other members of the SnapManager family current provide for Exchange, Oracle, UNIX, and SQL Server.
I do have live experience with running VMDKs via iSCSI, but not via NFS (not yet, anyway). VMware has presented statistics that show iSCSI on Gigabit Ethernet to run at about 70% of the speed of 2Gb Fibre Channel. (If you were at VMworld and participated in one of the Performance lab, those statistics were borne out in a real-world configuration using NetApp storage systems.)
Regards, Scott Lowe Senior Engineer ePlus Technology, Inc. slowe@eplus.com Office: 919.326.3641 Fax: 919.326.3691 Mobile: 919.274.0462
On Jan 31, 2007, at 7:40 AM, Willeke, Jochen wrote:
Hi.
i think Reimound is exactly what it is about. For big Exchange Installations there is really no need for VMWare. We have an Ex2k3 site with about 6000 users, which is not to big, and even VMWare said that they would not virtualize our Exchange Servers. Another point is that one big figure for Ex-performance is the memory which is limited to 3GB in Ex2k3 (with the 3gb-switch). But there is only one "store"-process running and if you look in your taskmanager on your Ex-Servers you may see, that it is using about 800MB-1GB, seldom more. So you see that with Ex2k3 virtualisation may be ok. But with Ex2k7 there is a complete new memorymanagement. I do not know the new limit but be sure, that Ex2k7 will make use of the memory it can get! So the idea would be to have a lot of memory for Ex2k7 to make it fast, memory that can no longer be used by other VMs running on the same host....Sorry for drifting away from storage :D
But from the point of interaction between Netapp and VMWare i can only agree that there are a lot of things which are "nice-to-have", e.g. some kind of Snapmanager for VMWare which makes it possible to use the mechanisms of VMWare to set a VM into backup mode (not suspend, like discribed on NOW!) and create a snapshot on the
Server.
By the way, has anybody already made live experience with VMWare vmdk's on ISCSI Lun's or NFS-exports?!? Is FC really the protocol of choice for a modern systems-architect :D?
I prefer Porsche,too...
Regards
Jochen
From: owner-toasters@mathworks.com [mailto:owner- toasters@mathworks.com] On Behalf Of Reinoud Reynders Sent: Wednesday, January 31, 2007 9:08 AM To: Benn, Paul; Timothy Hollingworth; toasters@mathworks.com Subject: RE: Netapp and VMware... It's all so confusing!
Hi Paul, Timothy,
This is a great discussion, and not as easy as we want. Of course do I want to use the best of both worlds. Here some comments:
Is it useful to run an exchange server on VMWare? In mostof the cases, Paul has maybe right. We have almost 8000 mailboxes, and indeed the added value of VMWare is relative small. We use there snapdrive, snapmanager and MSCS for the backup and DR job. We are running exchange on physical machines. The only reason why I wood use VMWare is for standardisation, but the disadvantages are today to big.
But you have the same problem with ms SQL server. We havemore than 70 SQL-servers. Here's a really advantage to go to VMWare. That's what we are doing today. But at that moment I loose snapdrive and snapmanager. This hurts. You go back to the stone age:
a. My DBA can't do anymore the basis storage tasks: create lun, expland lun, take snapshots, ... He must, like in the old days, go back to my storage admin and ask him to do this tasks. No, this is not correct, it's much worse: he must go to my VMWare admin, to ask more diskspace and the VMWare admin must go to my storage admin to solve the simple problem. So, my DBA is not happy (he must wait) and also my storage admin is not happy (he must work again). Only the VMWare admin likes this (but he will change his mind) because he's in control of everything J
b. We have create a totally different DR and Backup procedure for our SQL servers. It's not as good as snapmanager for SQL. For standardisation of procedures, we use the same scripts and procedures also on our large SQL servers, those are running on physical machines.
It's paint full to see that two great product (VMWare andONTAP/WAFL), with almost the same philosophy (virtualisation of storage or servers, easy of management, ...), are not integrated on
a
higher level. The combination works fine today, but you loose a lot of the WAFL functionality.
iSCSI running in the virtual machine works fine, but it'sslow. The latencies of the SQL server (and also the max IO/secs) are for most applications (in our case) not good enough. So that's not an option.
A nice discussion is also the choose between raw devices or VMDK's. I believe that you do a lot more with your VMWare, if you can use raw devices on the netapp. The only problem here is that there is a limit in VMWare of 254 luns in your VMWare "cluster". When you count a least 2 lun's for each VM and we have more than 200 VM's, you see that you reach very fast that limit. I didn't count the preferred setup of my SQL DBA: he want 10 LUNs for every SQL server. So for me, this is not an option. I have to use VMDK's.
So Paul, I think a lot of people are hoping that you will find a way to do this. Snapdrive would be a great start, so that we can distinguish us again from the other guys who don't use netapp, and so that we just can come back in the modern times.
Ps: I prefer the Porsche RC3.
Best regards,
Reinoud Reynders
IT-Manager Infrastructure & Operations
University Hospitals Leuven - Belgium
Van: owner-toasters@mathworks.com [mailto:owner- toasters@mathworks.com] NamensBenn, Paul Verzonden: woensdag 31 januari 2007 4:06 Aan: Timothy Hollingworth; toasters@mathworks.com Onderwerp: RE: Netapp and VMware... It's all so confusing!
Hi Timothy,
Having been an ASE certified master mechanic in a past life, I can advise you that it is indeed possible to have both of those cars as long as they are kept as separate vehicles. It would real mess if you chopped those cars in half and then welded them together into one new car. Think of all those electrical splices and incompatible electronics! Then, of course, there's that whole warranty and support thing. Who will you go to when the Acura leather cracks?
Or am I completely blind and missing something?
Well, just the fact that neither SnapDrive nor SnapManager are supported with VMware. The only "virtual server" - if you even want to call it that - that is supported with these products is the Exchange virtual server that is created in a Windows ("MSCS")
cluster.
Another interesting question that may be worth investigating prior to putting this into production is whether or not Microsoft supports the use of Exchange on VMware. Here are a couple of articles on that:
http://support.microsoft.com/kb/897615/
http://support.microsoft.com/kb/320220/
It is not clear in your email what the motivation is to go "virtual" for your Exchange server. If it is for DR purposes, then there may be another way you can accomplish your goals. There is a solution documented in NetApp Knowledgebase article #10542 that takes advantage of the virtual server in Windows clustering. Perhaps this article will help you accomplish your goals?
http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb10542
Please let us know if you have any more questions.
Regards,
Paul Benn
SnapManager Development Team
NetApp
From: Timothy Hollingworth [mailto:thollingsworth@eplus.com] Sent: Tuesday, January 30, 2007 5:06 PM To: toasters@mathworks.com Subject: Netapp and VMware... It's all so confusing!
So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front- engined Acura NSX as well as the Porsche RC3.
The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no?
I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME?
Or am I completely blind and missing something?
Timothy L. Hollingworth
Sr. Network Engineer, ePlus Technology Inc.
678.462.6698 (cell)
AIM: HollingworthTim
YIM: t_holling
Afteroon, or Morning where ever you maybe
We currently run Iscsi to all our exchange and sql boxes, we see better stats using Iscsi than we ever did with locally attached disks. All the servers have 2 interfaces and are trunked together, although because of the way the trunking works you will only ever get 1GB/s or close to it to the filer as most implemtations of trunking are based around MAC address.
As for Vmware and Netapp, I got a totally diferent answer out of the netapp support guys in the UK, which is yes its fine and it works and they are happy to support it, apart from a problem on linux, but I wasn't paying attention to that bit as we a are a microsoft shop here.
We hope to start our Vmware Netapp pilot within the next couple of months and we plan to use Iscsi all the way, no FC anywhere. I will happily share highlights with the group as it seems to be a popular subject.
Cheers
Matt
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Willeke, Jochen Sent: 31 January 2007 15:03 To: Scott Lowe; toasters@mathworks.com Subject: RE: Netapp and VMware... It's all so confusing!
Hi,
do i get it right that VMWare stated ISCSI on Gigabit Ethernet is at 70%speed of 2 GB FC?!? That would mean that ISCSI on a trunked 2Gbit Ethernet would be nearly the same speed as FC!
Would be great to know as we always were told that ISCSI is too slow and dangerous :D
Best Regards and thanks a lot for sharing your experience
Jochen
-----Original Message----- From: Scott Lowe [mailto:slowe@EPLUS.com] Sent: Wednesday, January 31, 2007 3:16 PM To: toasters@mathworks.com Cc: Willeke, Jochen; Reinoud Reynders; Benn, Paul; Timothy Hollingworth Subject: Re: Netapp and VMware... It's all so confusing!
Lots of good points here. Whether or not you virtualize Ex2K3 depends upon a great many factors. In many cases (especially for larger installations), virtualizing Exchange may not be the optimal approach. However, in smaller installations, virtualizing Exchange is not necessarily a bad thing. Of course, as pointed out already, Ex2K7 is a different beast altogether, primarily because it is 64-bit only.
I would be surprised if both NetApp and VMware were *NOT* already working on tools to help improve the NetApp-VMware relationship. In fact, I heard rumors at VMworld 2006 that there was a "SnapManager for VMware" in development. Supposedly, this would bring about the same level of application support that other members of the SnapManager family current provide for Exchange, Oracle, UNIX, and SQL Server.
I do have live experience with running VMDKs via iSCSI, but not via NFS (not yet, anyway). VMware has presented statistics that show iSCSI on Gigabit Ethernet to run at about 70% of the speed of 2Gb Fibre Channel. (If you were at VMworld and participated in one of the Performance lab, those statistics were borne out in a real-world configuration using NetApp storage systems.)
Regards, Scott Lowe Senior Engineer ePlus Technology, Inc. slowe@eplus.com Office: 919.326.3641 Fax: 919.326.3691 Mobile: 919.274.0462
On Jan 31, 2007, at 7:40 AM, Willeke, Jochen wrote:
Hi.
i think Reimound is exactly what it is about. For big Exchange Installations there is really no need for VMWare. We have an Ex2k3 site with about 6000 users, which is not to big, and even VMWare said that they would not virtualize our Exchange Servers. Another point is that one big figure for Ex-performance is the memory which is limited to 3GB in Ex2k3 (with the 3gb-switch). But there is only one "store"-process running and if you look in your taskmanager on your Ex-Servers you may see, that it is using about 800MB-1GB, seldom more. So you see that with Ex2k3 virtualisation may be ok. But with Ex2k7 there is a complete new memorymanagement. I do not know the new limit but be sure, that Ex2k7 will make use of the memory it can get! So the idea would be to have a lot of memory for Ex2k7 to make it fast, memory that can no longer be used by other VMs running on the same host....Sorry for drifting away from storage :D
But from the point of interaction between Netapp and VMWare i can only agree that there are a lot of things which are "nice-to-have", e.g. some kind of Snapmanager for VMWare which makes it possible to use the mechanisms of VMWare to set a VM into backup mode (not suspend, like discribed on NOW!) and create a snapshot on the Server.
By the way, has anybody already made live experience with VMWare vmdk's on ISCSI Lun's or NFS-exports?!? Is FC really the protocol of choice for a modern systems-architect :D?
I prefer Porsche,too...
Regards
Jochen
From: owner-toasters@mathworks.com [mailto:owner- toasters@mathworks.com] On Behalf Of Reinoud Reynders Sent: Wednesday, January 31, 2007 9:08 AM To: Benn, Paul; Timothy Hollingworth; toasters@mathworks.com Subject: RE: Netapp and VMware... It's all so confusing!
Hi Paul, Timothy,
This is a great discussion, and not as easy as we want. Of course do I want to use the best of both worlds. Here some comments:
Is it useful to run an exchange server on VMWare? In mostof the cases, Paul has maybe right. We have almost 8000 mailboxes, and indeed the added value of VMWare is relative small. We use there snapdrive, snapmanager and MSCS for the backup and DR job. We are running exchange on physical machines. The only reason why I wood use VMWare is for standardisation, but the disadvantages are today to big.
But you have the same problem with ms SQL server. We havemore than 70 SQL-servers. Here's a really advantage to go to VMWare. That's what we are doing today. But at that moment I loose snapdrive and snapmanager. This hurts. You go back to the stone age:
a. My DBA can't do anymore the basis storage tasks: create lun, expland lun, take snapshots, ... He must, like in the old days, go back to my storage admin and ask him to do this tasks. No, this is not correct, it's much worse: he must go to my VMWare admin, to ask more diskspace and the VMWare admin must go to my storage admin to solve the simple problem. So, my DBA is not happy (he must wait) and also my storage admin is not happy (he must work again). Only the VMWare admin likes this (but he will change his mind) because he's in control of everything J
b. We have create a totally different DR and Backup procedure for our SQL servers. It's not as good as snapmanager for SQL. For standardisation of procedures, we use the same scripts and procedures also on our large SQL servers, those are running on physical machines.
It's paint full to see that two great product (VMWare andONTAP/WAFL), with almost the same philosophy (virtualisation of storage or servers, easy of management, ...), are not integrated on a
higher level. The combination works fine today, but you loose a lot of the WAFL functionality.
iSCSI running in the virtual machine works fine, but it'sslow. The latencies of the SQL server (and also the max IO/secs) are for most applications (in our case) not good enough. So that's not an option.
A nice discussion is also the choose between raw devices or VMDK's. I believe that you do a lot more with your VMWare, if you can use raw devices on the netapp. The only problem here is that there is a limit in VMWare of 254 luns in your VMWare "cluster". When you count a least 2 lun's for each VM and we have more than 200 VM's, you see that you reach very fast that limit. I didn't count the preferred setup of my SQL DBA: he want 10 LUNs for every SQL server. So for me, this is not an option. I have to use VMDK's.
So Paul, I think a lot of people are hoping that you will find a way to do this. Snapdrive would be a great start, so that we can distinguish us again from the other guys who don't use netapp, and so that we just can come back in the modern times.
Ps: I prefer the Porsche RC3.
Best regards,
Reinoud Reynders
IT-Manager Infrastructure & Operations
University Hospitals Leuven - Belgium
Van: owner-toasters@mathworks.com [mailto:owner- toasters@mathworks.com] NamensBenn, Paul Verzonden: woensdag 31 januari 2007 4:06 Aan: Timothy Hollingworth; toasters@mathworks.com Onderwerp: RE: Netapp and VMware... It's all so confusing!
Hi Timothy,
Having been an ASE certified master mechanic in a past life, I can advise you that it is indeed possible to have both of those cars as long as they are kept as separate vehicles. It would real mess if you chopped those cars in half and then welded them together into one new car. Think of all those electrical splices and incompatible electronics! Then, of course, there's that whole warranty and support thing. Who will you go to when the Acura leather cracks?
Or am I completely blind and missing something?
Well, just the fact that neither SnapDrive nor SnapManager are supported with VMware. The only "virtual server" - if you even want to call it that - that is supported with these products is the Exchange virtual server that is created in a Windows ("MSCS") cluster.
Another interesting question that may be worth investigating prior to putting this into production is whether or not Microsoft supports the use of Exchange on VMware. Here are a couple of articles on that:
http://support.microsoft.com/kb/897615/
http://support.microsoft.com/kb/320220/
It is not clear in your email what the motivation is to go "virtual" for your Exchange server. If it is for DR purposes, then there may be another way you can accomplish your goals. There is a solution documented in NetApp Knowledgebase article #10542 that takes advantage of the virtual server in Windows clustering. Perhaps this article will help you accomplish your goals?
http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb10542
Please let us know if you have any more questions.
Regards,
Paul Benn
SnapManager Development Team
NetApp
From: Timothy Hollingworth [mailto:thollingsworth@eplus.com] Sent: Tuesday, January 30, 2007 5:06 PM To: toasters@mathworks.com Subject: Netapp and VMware... It's all so confusing!
So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front- engined Acura NSX as well as the Porsche RC3.
The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no?
I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME?
Or am I completely blind and missing something?
Timothy L. Hollingworth
Sr. Network Engineer, ePlus Technology Inc.
678.462.6698 (cell)
AIM: HollingworthTim
YIM: t_holling
_____________________________________________________________ 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@generalatlantic.com mailto:help@generalatlantic.com. Thank You.
Paul,
As Netapp appear to be a big supporter of VMware, it seems to me that if products like snap drive and snap manager for exchange are not supported within WM's then perhaps Netapp should address this ? Or is it being addressed ?
I already know of a number of people who are already using both SD and SME within VM's with Iscsi, and as far as I'm aware there have been no problems. Due to that we are currently planning a deplyyment along the lines of using both SD and SME with Iscsi within VM's.
Thanks
Matt __________________________________________________ Matt Davies
General Atlantic 83 Pall Mall London SW1Y 5ES UK Tel: +44 (0) 20 7484 3203 Fax: +44 (0) 20 7484 2803 Mobile: +44 (0) 77 7559 4265 http://www.generalatlantic.com/ Email: mdavies@generalatlantic.com mailto:mdavies@generalatlantic.com
__________________________________________________
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Benn, Paul Sent: 31 January 2007 03:06 To: Timothy Hollingworth; toasters@mathworks.com Subject: RE: Netapp and VMware... It's all so confusing!
Hi Timothy,
Having been an ASE certified master mechanic in a past life, I can advise you that it is indeed possible to have both of those cars as long as they are kept as separate vehicles. It would real mess if you chopped those cars in half and then welded them together into one new car. Think of all those electrical splices and incompatible electronics! Then, of course, there's that whole warranty and support thing. Who will you go to when the Acura leather cracks?
Or am I completely blind and missing something?
Well, just the fact that neither SnapDrive nor SnapManager are supported with VMware. The only "virtual server" - if you even want to call it that - that is supported with these products is the Exchange virtual server that is created in a Windows ("MSCS") cluster.
Another interesting question that may be worth investigating prior to putting this into production is whether or not Microsoft supports the use of Exchange on VMware. Here are a couple of articles on that: http://support.microsoft.com/kb/897615/ http://support.microsoft.com/kb/320220/
It is not clear in your email what the motivation is to go "virtual" for your Exchange server. If it is for DR purposes, then there may be another way you can accomplish your goals. There is a solution documented in NetApp Knowledgebase article #10542 that takes advantage of the virtual server in Windows clustering. Perhaps this article will help you accomplish your goals? http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb10542
Please let us know if you have any more questions.
Regards,
Paul Benn SnapManager Development Team NetApp
________________________________
From: Timothy Hollingworth [mailto:thollingsworth@eplus.com] Sent: Tuesday, January 30, 2007 5:06 PM To: toasters@mathworks.com Subject: Netapp and VMware... It's all so confusing! So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front-engined Acura NSX as well as the Porsche RC3. The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no? I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME? Or am I completely blind and missing something? Timothy L. Hollingworth Sr. Network Engineer, ePlus Technology Inc. 678.462.6698 (cell) AIM: HollingworthTim YIM: t_holling
_____________________________________________________________ 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@generalatlantic.com mailto:help@generalatlantic.com. Thank You.
Paul,
we are planning to use SD and SME with iSCSi within VM's, too. So I talked to our local NetApp representativ and forwarded your statement to him. He told me that indeed a lot of his customers are using SD/SME this way. And he asured me that this IS supported by NetApp AND by Microsoft.
Regards, DR. JOHANNES HEIDENHAIN GmbH
i. A. Dipl.-Inform. (FH) Walter Kießl
-------------------------------------------------------- mailto:kiessl@heidenhain.de Tel. +49 / 8669 / 31-1954 Fax +49 / 8669 / 32-1954 --------------------------------------------------------
DR. JOHANNES HEIDENHAIN GmbH Dr.-Johannes-Heidenhain-Str. 5 D-83301 Traunreut DEUTSCHLAND
http://www.heidenhain.de http://www.heidenhain.de/
________________________________
Von: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Im Auftrag von Davies,Matt Gesendet: Mittwoch, 31. Januar 2007 09:56 An: Benn, Paul; Timothy Hollingworth; toasters@mathworks.com Betreff: RE: Netapp and VMware... It's all so confusing!
Paul,
As Netapp appear to be a big supporter of VMware, it seems to me that if products like snap drive and snap manager for exchange are not supported within WM's then perhaps Netapp should address this ? Or is it being addressed ?
I already know of a number of people who are already using both SD and SME within VM's with Iscsi, and as far as I'm aware there have been no problems. Due to that we are currently planning a deplyyment along the lines of using both SD and SME with Iscsi within VM's.
Thanks
Matt __________________________________________________ Matt Davies
General Atlantic 83 Pall Mall London SW1Y 5ES UK Tel: +44 (0) 20 7484 3203 Fax: +44 (0) 20 7484 2803 Mobile: +44 (0) 77 7559 4265 http://www.generalatlantic.com/ Email: mdavies@generalatlantic.com mailto:mdavies@generalatlantic.com __________________________________________________
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Benn, Paul Sent: 31 January 2007 03:06 To: Timothy Hollingworth; toasters@mathworks.com Subject: RE: Netapp and VMware... It's all so confusing!
Hi Timothy,
Having been an ASE certified master mechanic in a past life, I can advise you that it is indeed possible to have both of those cars as long as they are kept as separate vehicles. It would real mess if you chopped those cars in half and then welded them together into one new car. Think of all those electrical splices and incompatible electronics! Then, of course, there's that whole warranty and support thing. Who will you go to when the Acura leather cracks?
Or am I completely blind and missing something?
Well, just the fact that neither SnapDrive nor SnapManager are supported with VMware. The only "virtual server" - if you even want to call it that - that is supported with these products is the Exchange virtual server that is created in a Windows ("MSCS") cluster.
Another interesting question that may be worth investigating prior to putting this into production is whether or not Microsoft supports the use of Exchange on VMware. Here are a couple of articles on that: http://support.microsoftcom/kb/897615/ http://support.microsoft.com/kb/897615/ http://support.microsoftcom/kb/320220/ http://support.microsoft.com/kb/320220/
It is not clear in your email what the motivation is to go "virtual" for your Exchange server. If it is for DR purposes, then there may be another way you can accomplish your goals. There is a solution documented in NetApp Knowledgebase article #10542 that takes advantage of the virtual server in Windows clustering. Perhaps this article will help you accomplish your goals? http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb10542
Please let us know if you have any more questions.
Regards,
Paul Benn SnapManager Development Team NetApp
________________________________
From: Timothy Hollingworth [mailto:thollingsworth@eplus.com] Sent: Tuesday, January 30, 2007 5:06 PM To: toasters@mathworks.com Subject: Netapp and VMware... It's all so confusing! So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front-engined Acura NSX as well as the Porsche RC3. The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no? I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME? Or am I completely blind and missing something? Timothy L. Hollingworth Sr. Network Engineer, ePlus Technology Inc. 678.462.6698 (cell) AIM: HollingworthTim YIM: t_holling
____________________________________________________________
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@generalatlantic.com. Thank You.
Apologies everyone.
We are agnostic when it comes to VMware and we will support our products if they break. Here is the support matrix:
http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/QuickRef/N etAppSANSupport_Dec2006RevB.pdf
I apologize for any grief caused and hope this clears everything up.
Regards,
Paul
________________________________
From: Benn, Paul Sent: Tuesday, January 30, 2007 7:06 PM To: Timothy Hollingworth; toasters@mathworks.com Subject: RE: Netapp and VMware... It's all so confusing! Hi Timothy, Having been an ASE certified master mechanic in a past life, I can advise you that it is indeed possible to have both of those cars as long as they are kept as separate vehicles. It would real mess if you chopped those cars in half and then welded them together into one new car. Think of all those electrical splices and incompatible electronics! Then, of course, there's that whole warranty and support thing. Who will you go to when the Acura leather cracks? > Or am I completely blind and missing something? Well, just the fact that neither SnapDrive nor SnapManager are supported with VMware. The only "virtual server" - if you even want to call it that - that is supported with these products is the Exchange virtual server that is created in a Windows ("MSCS") cluster. Another interesting question that may be worth investigating prior to putting this into production is whether or not Microsoft supports the use of Exchange on VMware. Here are a couple of articles on that: http://support.microsoft.com/kb/897615/ http://support.microsoft.com/kb/320220/ It is not clear in your email what the motivation is to go "virtual" for your Exchange server. If it is for DR purposes, then there may be another way you can accomplish your goals. There is a solution documented in NetApp Knowledgebase article #10542 that takes advantage of the virtual server in Windows clustering. Perhaps this article will help you accomplish your goals? http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb10542 Please let us know if you have any more questions. Regards, Paul Benn SnapManager Development Team NetApp
________________________________
From: Timothy Hollingworth [mailto:thollingsworth@eplus.com] Sent: Tuesday, January 30, 2007 5:06 PM To: toasters@mathworks.com Subject: Netapp and VMware... It's all so confusing! So, say for example, I want to virtualize an Exchange server. Lets also say that I want to manage it via Snapdrive and SME. Lets also say, just for the heck of it, that I want both the new front-engined Acura NSX as well as the Porsche RC3. The cars aside, I would have to run iSCSI from within the VM, install and use Snapdrive from within the VM to provision LUNs, install Exchange and then use SME? It seems kind of silly to use iSCSI from within a VM if the ESX box were fiber attached to the Filer, just to be able to use Snapdrive and SME, no? I would love to be able to use the features of SD and SME within a completely virtual environment and am wondering what some real world implementations other VMware/Netapp customers are running. Do you run storage for the databases and logs in VMDK's and manage snapshots and backups from a VMware virtual machine perspective or do you manage them as iSCSI LUNs and use SD and SME? Or am I completely blind and missing something? Timothy L. Hollingworth Sr. Network Engineer, ePlus Technology Inc. 678.462.6698 (cell) AIM: HollingworthTim YIM: t_holling
Has anyone experience run WAFL_check command ?, After my netapp FAS3160 panic, we have one of aggr restricted, and now we can make online but still get messages WAFL inconsistent. In general, WAFL_check will take several hours to several days , how long will it take aggregate3 +/- 7.5 TB on SATA 1 TB disks ?
aggr status aggr3 Aggr State Status Options aggr3 online raid_dp, aggr raidsize=16, wafl inconsistent ignore_inconsistent=on needs check
Thanks & Regards D 15 NO
PT. Mandawani Mandiri. HP. 0811814005
It depends a lot on how much is wrong in the file system, and if it's busy doing other things.
What release are you on, and what's the panic?
-Blake
On Wed, Mar 31, 2010 at 7:32 PM, DISNO_MANDAWANI disno@mandawani.com wrote:
Has anyone experience run WAFL_check command ?, After my netapp FAS3160 panic, we have one of aggr restricted, and now we can make online but still get messages WAFL inconsistent. In general, WAFL_check will take several hours to several days , how long will it take aggregate3 +/- 7.5 TB on SATA 1 TB disks ?
aggr status aggr3
Aggr State Status Options
aggr3 online raid_dp, aggr raidsize=16,
wafl inconsistent ignore_inconsistent=on
needs check
Thanks & Regards
D 15 NO
PT. Mandawani Mandiri.
HP. 0811814005
Thanks blake, The data ontap version 7.3.1P2 and panic after electrical spike.
Thanks & Regards D 15 NO
PT. Mandawani Mandiri. HP. 0811814005
-----Original Message----- From: Blake Golliher [mailto:thelastman@gmail.com] Sent: 01 April 2010 11:34 To: Zalam Sudisno Cc: toasters@mathworks.com; Ahmad Muhammad Subject: Re: wafl inconsistent
It depends a lot on how much is wrong in the file system, and if it's busy doing other things.
What release are you on, and what's the panic?
-Blake
On Wed, Mar 31, 2010 at 7:32 PM, DISNO_MANDAWANI disno@mandawani.com wrote:
Has anyone experience run WAFL_check command ?, After my netapp FAS3160 panic, we have one of aggr restricted, and now we can make online but
still
get messages WAFL inconsistent. In general, WAFL_check will take several hours to several days , how long will it take aggregate3 +/- 7.5 TB on
SATA
1 TB disks ?
aggr status aggr3
Aggr State Status Options
aggr3 online raid_dp, aggr raidsize=16,
wafl inconsistent ignore_inconsistent=on
needs check
Thanks & Regards
D 15 NO
PT. Mandawani Mandiri.
HP. 0811814005
-
Benn, Paul -
Blake Golliher -
Davies,Matt -
DISNO_MANDAWANI -
Kießl Walter -
Oliver Bassett -
Reinoud Reynders -
Scott Lowe -
Timothy Hollingworth -
tmac -
Willeke, Jochen