none
Adding a second iSCSI target RRS feed

  • Question

  • We have a 40TB HP storeeasy. Right now I have it configured as one 32TB storage pool with one 16TB iSCSI virtual disk. I want to use the other 16TB.

    I was going through the "New iSCSI Virtual Disk Wizard" to create the new virtual disk/iSCSI target. At the end it gives me the option to either use the existing iSCSI target or create a new one. If I use the existing one, how does that work? Does it somehow add the new virtual disk to that target as additional storage? Does it replace the existing virtual disk?

    My goal is to retain the existing iSCSI target and add a second one for the same server to connect to. Example:

    On the file server that already connects to an iSCSI target on the storage server, I want it to see another hard drive which is pointing to the second iSCSI virtual disk on the same storage server.

    Friday, November 15, 2013 3:26 PM

Answers

  • We have a 40TB HP storeeasy. Right now I have it configured as one 32TB storage pool with one 16TB iSCSI virtual disk. I want to use the other 16TB.

    I was going through the "New iSCSI Virtual Disk Wizard" to create the new virtual disk/iSCSI target. At the end it gives me the option to either use the existing iSCSI target or create a new one. If I use the existing one, how does that work? Does it somehow add the new virtual disk to that target as additional storage? Does it replace the existing virtual disk?

    My goal is to retain the existing iSCSI target and add a second one for the same server to connect to. Example:

    On the file server that already connects to an iSCSI target on the storage server, I want it to see another hard drive which is pointing to the second iSCSI virtual disk on the same storage server.

    You can both extend (grow) existing virtual disk and create a new LUN on an existing target. See:

    http://technet.microsoft.com/en-us/library/gg232619(v=ws.10).aspx

    http://technet.microsoft.com/en-us/library/dn448369.aspx

    http://blogs.technet.com/b/canitpro/archive/2011/04/12/creating-a-san-using-microsoft-iscsi-software-target-3-3.aspx

    http://technet.microsoft.com/en-us/library/cc772367.aspx

    http://technet.microsoft.com/en-us/library/cc732372.aspx

    Hope this helped :)

    P.S. Except you need to understan Microsoft iSCSI target is dead end and Microsoft is actively pushing SMB 3.0 as a transport and way to store shared content. Performance, high availability and easy-to-use are better with SMB 3.0 file shares and Scale-Out File Servers then with MS target (commercial iSCSI implementations are better of course). Say with SMB you'd just grow capacity on server with share and it would automatically result increased capacity on a client. 


    StarWind iSCSI SAN & NAS

    Friday, November 15, 2013 8:14 PM
  • [ ... ]

    FYI, there's a 16TB limit on the virtual disks. Not sure if this is a limitation of Windows or just iSCSI in general. The iSCSI target I have in place is a 16TB. The second one I would like to use is also 16TB.

    Based off your response, if I tell the iSCSI wizard to use the existing iSCSI target, am I correct when I assume that it will NOT delete the existing iSCSI virtual disk? It will basically add another "volume" for windows to use on the same iSCSI target? 

    So on my file server that connects to the store easy, I should now see the second volume present?


    1) You're correct there's a 16TB limit on a VHD forced by MS target (sorry for this!). See:

    http://support.microsoft.com/kb/2535811

    Fixed VHd size 16776703 MB Enforced

    I'd suggest to check other implementations free from this limit (NTFS maximum supported file size could kick...) or stick with SMB 3.0 share instead of MS target.

    2) No it will just add another LUN to the target w/o destroying original one.


    StarWind iSCSI SAN & NAS

    Saturday, November 16, 2013 12:13 PM

All replies

  • We have a 40TB HP storeeasy. Right now I have it configured as one 32TB storage pool with one 16TB iSCSI virtual disk. I want to use the other 16TB.

    I was going through the "New iSCSI Virtual Disk Wizard" to create the new virtual disk/iSCSI target. At the end it gives me the option to either use the existing iSCSI target or create a new one. If I use the existing one, how does that work? Does it somehow add the new virtual disk to that target as additional storage? Does it replace the existing virtual disk?

    My goal is to retain the existing iSCSI target and add a second one for the same server to connect to. Example:

    On the file server that already connects to an iSCSI target on the storage server, I want it to see another hard drive which is pointing to the second iSCSI virtual disk on the same storage server.

    You can both extend (grow) existing virtual disk and create a new LUN on an existing target. See:

    http://technet.microsoft.com/en-us/library/gg232619(v=ws.10).aspx

    http://technet.microsoft.com/en-us/library/dn448369.aspx

    http://blogs.technet.com/b/canitpro/archive/2011/04/12/creating-a-san-using-microsoft-iscsi-software-target-3-3.aspx

    http://technet.microsoft.com/en-us/library/cc772367.aspx

    http://technet.microsoft.com/en-us/library/cc732372.aspx

    Hope this helped :)

    P.S. Except you need to understan Microsoft iSCSI target is dead end and Microsoft is actively pushing SMB 3.0 as a transport and way to store shared content. Performance, high availability and easy-to-use are better with SMB 3.0 file shares and Scale-Out File Servers then with MS target (commercial iSCSI implementations are better of course). Say with SMB you'd just grow capacity on server with share and it would automatically result increased capacity on a client. 


    StarWind iSCSI SAN & NAS

    Friday, November 15, 2013 8:14 PM
  • We have a 40TB HP storeeasy. Right now I have it configured as one 32TB storage pool with one 16TB iSCSI virtual disk. I want to use the other 16TB.

    I was going through the "New iSCSI Virtual Disk Wizard" to create the new virtual disk/iSCSI target. At the end it gives me the option to either use the existing iSCSI target or create a new one. If I use the existing one, how does that work? Does it somehow add the new virtual disk to that target as additional storage? Does it replace the existing virtual disk?

    My goal is to retain the existing iSCSI target and add a second one for the same server to connect to. Example:

    On the file server that already connects to an iSCSI target on the storage server, I want it to see another hard drive which is pointing to the second iSCSI virtual disk on the same storage server.

    You can both extend (grow) existing virtual disk and create a new LUN on an existing target. See:

    http://technet.microsoft.com/en-us/library/gg232619(v=ws.10).aspx

    http://technet.microsoft.com/en-us/library/dn448369.aspx

    http://blogs.technet.com/b/canitpro/archive/2011/04/12/creating-a-san-using-microsoft-iscsi-software-target-3-3.aspx

    http://technet.microsoft.com/en-us/library/cc772367.aspx

    http://technet.microsoft.com/en-us/library/cc732372.aspx

    Hope this helped :)

    P.S. Except you need to understan Microsoft iSCSI target is dead end and Microsoft is actively pushing SMB 3.0 as a transport and way to store shared content. Performance, high availability and easy-to-use are better with SMB 3.0 file shares and Scale-Out File Servers then with MS target (commercial iSCSI implementations are better of course). Say with SMB you'd just grow capacity on server with share and it would automatically result increased capacity on a client. 


    StarWind iSCSI SAN & NAS

    FYI, there's a 16TB limit on the virtual disks. Not sure if this is a limitation of Windows or just iSCSI in general. The iSCSI target I have in place is a 16TB. The second one I would like to use is also 16TB.

    Based off your response, if I tell the iSCSI wizard to use the existing iSCSI target, am I correct when I assume that it will NOT delete the existing iSCSI virtual disk? It will basically add another "volume" for windows to use on the same iSCSI target? 

    So on my file server that connects to the store easy, I should now see the second volume present?


    Friday, November 15, 2013 9:09 PM
  • [ ... ]

    FYI, there's a 16TB limit on the virtual disks. Not sure if this is a limitation of Windows or just iSCSI in general. The iSCSI target I have in place is a 16TB. The second one I would like to use is also 16TB.

    Based off your response, if I tell the iSCSI wizard to use the existing iSCSI target, am I correct when I assume that it will NOT delete the existing iSCSI virtual disk? It will basically add another "volume" for windows to use on the same iSCSI target? 

    So on my file server that connects to the store easy, I should now see the second volume present?


    1) You're correct there's a 16TB limit on a VHD forced by MS target (sorry for this!). See:

    http://support.microsoft.com/kb/2535811

    Fixed VHd size 16776703 MB Enforced

    I'd suggest to check other implementations free from this limit (NTFS maximum supported file size could kick...) or stick with SMB 3.0 share instead of MS target.

    2) No it will just add another LUN to the target w/o destroying original one.


    StarWind iSCSI SAN & NAS

    Saturday, November 16, 2013 12:13 PM