Tag Info

New answers tagged

0

That's not a corrupted routing table, don't worry about it. Because of the way CIDR works, 192.91 is the same as 192.91.0.0 - you can check for basic connectivity via e.g. ping. If you can ping it, it's fine. More likely, rsh is turned off on your filer - that's considered a good thing, as rsh is an old and insecure protocol. Check options rsh and see ...


5

First and foremost, before to mangle with storage, you should be 100% sure that your bottleneck is really related to disk/IO configuration. It this is the case, an iSCSI share can be faster than a NFS one, but in specific scenario only (small random read/write packets). SQL servers can be one of these scenarios, so if you are sure that your problem is ...


4

First things first: If you want to improve the performance of a VM you have to know where the bottleneck is. Improving storage performance doesn't help you if your environment lacks e.g. CPU performance. I don't think changing your storage protocol from NFS to iSCSI will help you much. There are dozens of other parameters that influence your storage ...


4

I've not heard that iSCSI is better than NFS for SQL VMs, however if you do elect to create them, I would create the datastore on the ESX level, not install an iSCSI initiator on the VM. One thing you need to be careful about is thin provisioning on the Netapp. The way they do block devices is different. You can find yourself with an offline LUN if you ...



Top 50 recent answers are included