+ Post New Thread
Results 1 to 5 of 5
How do you do....it? Thread, Vmdk's or iscsi For SQL db and exchange db in Technical; What best to use for SQL db and exchange db, vmdk's or iscsi targets? Mark...
  1. #1
    ful56_uk's Avatar
    Join Date
    Mar 2008
    Location
    Essex
    Posts
    580
    Thank Post
    113
    Thanked 25 Times in 22 Posts
    Rep Power
    19

    Vmdk's or iscsi For SQL db and exchange db

    What best to use for SQL db and exchange db, vmdk's or iscsi targets?

    Mark

  2. #2

    dhicks's Avatar
    Join Date
    Aug 2005
    Location
    Knightsbridge
    Posts
    5,772
    Thank Post
    1,308
    Thanked 804 Times in 698 Posts
    Rep Power
    247
    Quote Originally Posted by ful56_uk View Post
    What best to use for SQL db and exchange db, vmdk's or iscsi targets?
    A few years ago, when harddrives were a bit smaller, best practice used to be to simply assign your database an entire, raw harddrive (or RAID array) for it to use as it saw fit. The idea was that it would bypass any file system overhead and be able to write data directly to the harddrive, arranging disk reads and writes in the most efficient way. These days, an SQL database tends to be just a large file on an existing file system as most databases don't take up the disk space to fill an entire drive or RAID array. However, disk space these days is as cheap as it's ever been, so you'd probably still get best performance if you assign your database a whole block device - a harddrive, RAID array, or, in your case, probably a whole RAID array exported as an iSCISI target from your SAN.

  3. #3

    Join Date
    Oct 2005
    Posts
    870
    Thank Post
    59
    Thanked 133 Times in 111 Posts
    Rep Power
    77
    How busy is your SQL / Exchange box?
    How fast is your SAN?

    I've got my SQL and Exchange boxes running as normal vmdks... performance is just as good, if not better, than when they were physical boxes.

  4. #4

    Join Date
    Nov 2010
    Location
    California
    Posts
    137
    Thank Post
    0
    Thanked 24 Times in 22 Posts
    Rep Power
    13
    We have just about everything virtualized now utilizing our iSCSI SAN for storage.

    We use a seperate virtual disk for EACH of the following on our SQL servers: OS, databases, logs and backups.
    For exchange we use a seperate virtual disk for EACH of the following: OS, Logs, Databases.

    The virtual disks are created on several different LUNs which are RAIDed to specific RAIDs depending on their purpose.

  5. #5
    gshaw's Avatar
    Join Date
    Sep 2007
    Location
    Essex
    Posts
    2,726
    Thank Post
    176
    Thanked 229 Times in 211 Posts
    Rep Power
    69
    I think I'm going with vmdks when we do our virtual migration, splitting the data onto a separate vmdk from the OS drive (pretty much same as you would physically, just replace drives with virtual disks )

    Will also make it easier to back up as Veeam can just lift the vmdks and whack them onto our backup target server.
    Last edited by gshaw; 26th April 2011 at 10:33 AM.



SHARE:
+ Post New Thread

Similar Threads

  1. SQL Server 2008 - Automating DB Backup using the SQL Mgmt Console
    By bodminman in forum How do you do....it?
    Replies: 8
    Last Post: 24th January 2011, 03:55 PM
  2. Replies: 5
    Last Post: 3rd November 2010, 12:52 PM
  3. How to Implement multiple iSCSI SAN deployment with iSCSI switch for multiple ESXi ?
    By albertwt in forum Thin Client and Virtual Machines
    Replies: 0
    Last Post: 12th May 2010, 09:43 AM
  4. Creating a VM using vmdk files etc
    By m1ddy in forum Thin Client and Virtual Machines
    Replies: 10
    Last Post: 9th November 2009, 03:55 PM
  5. Sharing VMDK's between VM servers
    By DAckroyd in forum Thin Client and Virtual Machines
    Replies: 13
    Last Post: 6th November 2009, 11:33 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •