• Announcements

    • Eric Newbauer

      Follow SNS on Twitter!

      Get notifications via Twitter! Looking for instant updates? We're now also announcing new versions and beta programs via Twitter. Follow Studio Network Solutions on Twitter. Thanks!

SNS Hal

Members
  • Content count

    160
  • Joined

  • Last visited

Community Reputation

1 Neutral

About SNS Hal

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  1. Faulty LD

    Hi Don, SANmp is our SAN management software. We're not sure what the hardware is, but would be happy to take a look in a remote session, if you'd like to open a support case at support.studionetworksolutions.com.
  2. It sounds like Xtarget may be a good solution if you want to share a Fibre-attached RAID over iSCSI. Contact us if you'd like more information!
  3. Hello, The initiator is strictly a connection mechanism, with no concept of the file system. The workstation operating system handles all file operations, but it does need reliable communication with the target disk. From what we've seen, the initiator maintains the connection to the storage without issue, but as noted in a previous reply, the storage system doesn't seem to support the error detection policy that is set by default in globalSAN, so this protective policy gets disabled. Error 36 is often indicative of trouble with the file system. If you're still able to read from the disk(s), backing up the data (and maintaining current backups) would be a good first step. Most storage systems (including our own!) do include the error detection policy as added protection for block level communication.
  4. Hi Alex, If a single iSCSI connection is to be used, then the machine with the connection can share the mounted volume to the other machines using AFP (or SMB). The iSCSI workstation manages the data, since SAN storage is seen as local, and then shares it as it would any other local volume it owns. There is no need for Xsan, since the other machines will not have a block level (iSCSI or FC) connection to the storage. You said there is no plan to have multiple initiators, but if you change your mind and would like the other machines to have the speed benefit of a SAN connection, then some sort of SAN management will be required; otherwise, if multiple machines concurrently connected to the same block level target, they'd each assume ownership and quickly corrupt the file system. While Xsan can be made to work with iSCSI, we do offer a much simpler alternative, SANmp (or iSANmp), which does not require a metadata network, and allows for cross-platform sharing. You can read more about iSCSI sharing here.
  5. The initiator provides the iSCSI connection, but has no awareness of the file system on the target disk, which is handled only by the operating system. When a LUN is grown, the underlying disk expands, but the file system on top of it typically has no awareness this has happened. Disk Utility will sometimes allow the partition(s) to be resized, but may require disk repair first.
  6. Is SANmp installed as well? If not, this sounds like it may be a bug in Disk Utility. As a troubleshooting step, it may be a good idea to try formatting using an older version of OS X, or using the diskutil command line options to format the disk instead.
  7. Hi Glenn, The SANmp Admin and Client guides have a reference section for the command line interface, if you'd like to set it up that way. Otherwise, you could configure an Auto Sync interval in SANmp Admin. Please see the guide for details about the use of this feature before configuring it.
  8. I was surprised to find this seems to be missing from our globalSAN documentation, but you'll find gsutil in /opt/local/bin. Thank you for drawing our attention to it, and I'll make sure that gets added to the manual! You may also wish to set the PATH variable rather than navigating to the appropriate directory each time you use it. By doing this, you can access the CLI immediately after opening Terminal, and it will persist after rebooting. To set the path permanently, create the file .bash_login in your home folder, containing the following command: PATH=$PATH:/opt/local/bin If this file already exists, simply add that line to the end of it. The next time you start the Terminal window, your new path will be active. We apologize for the oversight. Let us know if we can help with anything else!
  9. Ah, understood! In that case, the initiator does provide a CLI. You'll find the options in Section 3.3 of the guide in the /Applications/globalSAN folder.
  10. Hello, Checking the Persistent box for the target in globalSAN will set it to always attempt a connection when the machine starts, so there's no need for scripting for the initiator, but are you also using SANmp to manage shared SAN storage?
  11. I thought AppleRAID may not be what you were after, but could be an alternative solution.. Multipathing is handled by the operating system, rather than the initiator. The OS can correctly collapse targets if the same target is seen over multiple paths, but in this case the OS has no awareness that there is actually only one intended target. We expect if you can get the Starwind software to make each LUN appear identical to the OS, that you're correct that multipathing could be the solution.
  12. Hi, If we're understanding correctly what you're after, creating an AppleRAID (RAID 1) for the two targets should take care of it. In this case, SANmp (iSANmp) would only see one volume, and continue writing without trouble in the event one of the targets went down. The software RAID could then be rebuilt once access was restored. Hope that helps - feel free to open a support case if we can be of further assistance.
  13. Hi Glenn, It looks like we failed to update you last year, but we did investigate this at the time, and we took another look this last week. We found that adding support for this target would not be a trivial task. We've been listening for users who want an alternative software RAID, but haven't had enough buzz to warrant the development that would be required to add and maintain future support for any third-party solutions. Note that Apple RAID can still be configured in the current OS versions from the command line, and that this is supported in Xtarget.
  14. If you haven't done so yet, please open a support case so we may get a clearer picture of the current and desired behavior. Thanks!
  15. The initiator will continually try to reacquire the targets when in Persistent mode. It sounds like the storage was not available at first, and was then found. Has the issue persisted? Please open a support case if you'd like us to take a closer look.