Jump to content
SNS Users' Forums
  • 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!

steve.higdon

KB Moderators
  • Content count

    30
  • Joined

  • Last visited

Community Reputation

0 Neutral

About steve.higdon

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    http://studionetworksolutions.com
  • ICQ
    0

Profile Information

  • Location
    St. Louis, USA
  1. EVO works great with Tricaster, and will easily capture your 5 video streams and audio ISO feeds. The flexible connectivity and configuration of EVO can also enable the creation of the safety clones that are critical to your work. EVO is a very capable link between the live production capabilities of Tricaster and post production. Please email sales@studionetworksolutions to discuss this in detail with one of our representatives.
  2. Travis, if I read you correctly, you have an Xserve that mounts one or more SANmp volumes, then shares those SAN volumes as AFP file shares. I'm not sure I understand what you mean by losing sync though-- is the AFP or SAN connection lost, or is there a problem with the file system on the SAN volumes? You can open a support case by sending an email to support@studionetworksolutions.com
  3. wischmob, this is a known issue with the HASP driver and Windows 8. The issue is being addressed in development for future release of SANmp 4.1, which will be the minimum required version of SANmp for Win 8 compatibility. Resolution of this issue is not yet included in SANmp 4.1.0.133, which is the BETA build that you attempted to install. Please subscribe to the Product Announcements forum to be notified of future releases of SANmp 4.1
  4. Hello, please see the information I've posted to your support case.
  5. Nathan SANmp 4.0 is compatible with 64 bit kernel, and is currently in beta test phase, please see http://www.snsforums.com/index.php?showtopic=447 Your post on 5 Oct 2010 appeared to indicate that things were working, and your follow up is a year later. If you're still having problems you should use the link Eric posted to open a support case so we can gather specific info to troubleshoot the issue.
  6. SANmp is capable of allowing a user to mount multiple volumes simultaneously. Make sure that you have given the user proper mounting privileges in SANmp Admin. Access rights are assigned per user, per volume. It may be that you have only give the user permission to mount the one volume. See the SANmp Admin user guide for details on creating users and assigning privileges.
  7. Can I get a straight answer.

    SANmp 3.1 is not compatible with Lion 10.7.x and we have not yet announced the release date of a Lion compatible version of SANmp. The release of Lion compatible SANmp will be posted to the Product Announcements forum: http://www.snsforums.com/index.php?showforum=3 As a registered user you can subscribe to that forum to be immediately notified of future releases.
  8. Logical Disk

    Brian A degraded array usually indicates that one of the hard drives has failed. Since the array is a RAID5 it can be rebuilt using parity data on the remaining drives. The volumes should currently be available, so you should take this opportunity to copy any critical information. Since the array is degraded, the performance will be slow, but it will allow you to secure your data. This is important because a RAID5 can tolerate the failure of only one physical disk drive. If a second drive were to fail now, while the array is degraded, your data will be unrecoverable. The failed disk can be replaced, which would allow the globalSAN system to rebuild the array. After the rebuild has completed, the RAID5 will no longer show the degraded status and the performance will return to the high speed that you are used to. SNS Tech Support can assist you in choosing a compatible disk to replace the failed one. We'll need some technical information collected from your system to determine which specific model(s) of disk drives are compatible with your system. Please follow these instructions to generate a log package: Retrieve system logs from globalSAN X-series iSCSI Target hardware: Version MR5 and older: 1. Log into your globalSAN unit via a web browser window. 2. Choose the “System Log” button on the left side of the page. 3. At the bottom of the page is a button “Download” log. a. On Mac OS, Control Click on the button and choose “Download Linked File” from the menu. b. On Windows, right click the button and choose “Save Target As.” Version 1.6 and newer: 1. Log into your globalSAN unit via a web browser window. 2. Choose the “General” button on the left side of the page. 3. Click on the “Diagnostics” tab at the top of the page. 4. Confirm that all option boxes are checked. 5. Establish a password for the encrypted diagnostic log by entering the password globalsan and confirming it in the appropriate fields. 6. Confirm that “Clear Archived Reports” is set to No. 7. Click on the “Apply” button. 8. globalSAN will reply with “Archive Created. Click here to download.” 9. Clicking on the link will transfer the archived diagnostic file to your local workstation. 10. Choose the “Notification” button on the left side of the page. 11. Scroll to the bottom of the “View System Log” page. a. On Mac OS, Control Click on the Download Log button and choose "Download Linked File" from the menu. b. On Windows, right click the Download Log button and choose "Save Target As." Please open an online support case at the following link: http://support.studionetworksolutions.com/anonymous_requests/new Attach the log files and we'll let you know which specific hard drives are candidates for replacement into your globalSAN system.
  9. Mike In your situation I would recommend that you script the SAN volumes to be mounted just prior to running your backup. This would be preferable to enabling an automatic sync period, as one can not be assured of exactly when the automatic sync may occur, in relation to the more specifically timed automated backup. Of course, it is possible to have a relatively short auto sync period, but this may have greater impact on the overall performance. Audio recording applications are especially susceptible to latency across ethernet. Any configuration that increases network traffic, or access to the SAN volume file systems (sync, for example), has higher chance of impacting the performance of the audio recording application. This may depend on several factors, including the workload of each user and the configuration of your network. A scripted mount of the relevant SAN volumes prior to kicking off the backup routine would result in a reliable result, with the least chance of impacting any other users. Please refer to the SANmp Admin and Client user guides for further information on scripting. You may also find other forum posts which may have script examples that may be helpful.
  10. For SAN's sanity

    HFS+, like any other file system, is susceptible to fragmentation. At some point this fragmentation may impact the performance of your storage to the extent that it is noticeable. This is true for any storage that uses HFS+, including local disks (internal and external), and SAN volumes that use HFS+. If the performance of your storage has noticeably degraded over time, it's possible that it could be due to fragmentation. Some users may never notice any performance degradation. To answer your question directly-- not all users adhere to the maintenance recommendation and they do not experience any problems. Other users perform the preventative maintenance, and have successful systems. There are also users who perform volume maintenance when forced to do so by the performance effects of fragmentation. The way that volumes are used, the number and size of the files, and how often files are added and removed all impact the cumulative effect of fragmentation. There are two facts: first, the performance effect of fragmentation is very real, and second, a new, clean file system will deliver the best performance possible, all other things being equal. It occurs to me that you are comparing SANmp to other solutions, so allow me to make a couple points. First, we suggest that SANmp is not deployed as one large volume, which is contrary to the way some systems are implemented. Rather, we suggest that the work space be divided up into multiple smaller chunks, the size and number of which depends upon the needs of the individual situation. We find it more flexible, reliable, and easier to maintain over a long period of time. Especially when the workflow relies on consistent high performance. Having your entire facility depend on one single volume doesn't leave much room for error-- if that volume gets corrupted, goes down or is disabled, either performance or accessibility, you've brought the entire workflow to a halt. Also, when using SANmp with EVO (our all-in-one shared storage sever tuned for FCP, Avid and Pro tools) you get both file and volume sharing over iscsi, fibre & 10GbE all at the same time. Here's a link for more info on Evo - http://www.studionetworksolutions.com/video-san.php Of course SANmp works with any Fibre Channel or iSCSI storage, not just EVO and vice versa.
  11. ProTools DAE error 9126

    Mike Pro Tools is generally not comfortable with any LUN over 2TB. Even if that LUN is partitioned down below 2TB, it still does not work properly. You can carve smaller LUNs on the existing RAIDs in the Infortrend, map, partition and convert to SANmp. After that things should work just fine.
  12. Volume partially disappeared

    Would you please open a support case so we can get additional diagnostic information? Follow this link: http://www.studionetworksolutions.com/support/ Choose "Open A Support Case Online" Thank you.
  13. It has been called to our attention that globalSAN iSCSI Initiator has been specifically mentioned in the user documentation for the LG N2B1DD1. The LG user guide includes screen shots that indicate that an older version of globalSAN may have been used, possibly version 3.3. Users may test the LG device with globalSAN version 3.3, but keep in mind that 3.3 is not intended for use with Mac OS X 10.6 Snow Leopard. We suggest that users attempting to connect to the LG device using globalSAN iSCSI Initiator from Mac OS please contact LG support for further information and assistance. Studio Network Solutions provides support for globalSAN iSCSI Initiator only when used with SNS iSCSI storage products.
  14. Volume will not mount Read/Write

    Please email me at support@studionetworksolutions.com, I'll get some more info from you and we'll get your issue cleared up straight away!
×