Recent Comments

  • Reply to: MSN Tech Support-Could Give You Relief From Technical Bugs   20 hours 51 sec ago

    There are lot of assistance for msn acocunt you can find out the searches with various queries like msn technical support team online service.

  • Reply to: How to set up the Xsan 4 notifications ?   5 days 23 min ago

    you guys are having very informative discussion to help people like us who feel obstacle in changing environment of today's advanced technological era. Thanks for your support. Suicide Squad Jacket

  • Reply to: AppleCare Xsan Support Agreement: How to find the registration number (Apple KB)   1 month 2 days ago

    solved the issue from change the value 1 to 0 from window 7 registry manager .

    pkt mumbai india id piyushpbctv

  • Reply to: Office 2016   1 month 1 week ago

    Same problem here.

    I’m having issues with *all* Office 2016 for Mac (v.15.24) programs being unable to write/save files other than PDF to our XSAN and user home folders. The error reads: Alert - Document Not Saved. Excel spreads (.xlsx), word docs (.docx), powerpoint (.pptx) files refuse to be written despite user permissions to the destination being Read/Write. I use OS X Server to set these permissions. The workaround is to save the file locally and then move it to the desired location. When this document is opened again from the xsan location, it cannot be overwritten, it must still be saved locally.

    When Office for Mac 2016 performs a save, it saves a temporary directory on the volume first, and then swaps the file with the actual file the user wants to save to (to prevent corruption of the original file). Normally, the temporary directory path returned by Apple's API will be somewhere located in a hidden folder called ".TemporaryItems" in the root of the share where the user has mounted (in our case, /Volumes/Stornext/.TemporaryItems). Normally, access to this location is Everyone>Read Only, but I've set the ACL permissions to Read/Write, with no change. I would like to use OS X Server to change the permissions but Server does not reveal the hidden folder: .TemporaryItems

    Microsoft Office 2011 has no trouble writing [.pptx, .xlsx, .docx] files to the xsan, which leads me to believe that something with Office 2016 might be the issue, rather than our san.

    El Capitan v.10.11.5
    Office 2016 for Mac v. 15.24
    Quantum Stornext 5

  • Reply to: Xsan 4   2 months 4 days ago

    its on ibooks, the migration guide that is. there really is no xsan admin guide anymore. What is your question? Check out this post from matx.

  • Reply to: Xsan 4   2 months 6 days ago

    Dear all
    i piyush from india i have just xsan 4 environment i know about fully x san 2 environment but i dont have admin guide for x san 4 please suggest where can i download input any idea or https
    link for x san 4 user guide and admin guide in pdf format or video. I confused about some little topics what i do suggest please any one

  • Reply to: Restore a previous SAN setup dialog is gone!   2 months 6 days ago

    Are you sure open directory is there?

  • Reply to: Open Directory not starting on XSAN metadata controller   2 months 1 week ago

    Informational blog! This is a great example to search out particular topics in the given time frame to work out. Thumbs up for you
    click now

  • Reply to: Open Directory not starting on XSAN metadata controller   2 months 1 week ago

    I tried rolling back the MDC to a previous date via Time Machine (boot to Recovery, restore from Time Machine). It worked! Open Directory started on the master and I was able to add the client.

    The only leftover issue I see is that it looks like on the 2nd MDC (the one that was the OD replica) it doesn't look like it's a replica anymore. It sees the master, but doesn't show itself as a replica.

    Any insights on the smoothest way to fix that? I'm going to leave it alone for a couple of days before messing with it.

    And yes, the first thing I did was to Archive my Master OD. :)

  • Reply to: upgrade from 2.2.2 to 4.1   2 months 2 weeks ago

    Good to hear, be sure to make an archive of your open directory master incase it ever becomes corrupt. I would make an new archive anytime you make significant changes to your SAN.

  • Reply to: upgrade from 2.2.2 to 4.1   2 months 2 weeks ago

    Thank you so much for your help Trevor.
    No errors, everything is functioning great. We got MDC1, MDC2 and CS1(3 controllers)
    MDC1 has DNS and Open Directory Master enabled
    MDC2 DNS, AFP, Mail, Web and Open Directory Replica enabled
    CS1 is pretty much the same as MDC2

    Thanks again

  • Reply to: upgrade from 2.2.2 to 4.1   2 months 2 weeks ago

    10.8 and 10.9 may also work, the goal is to get the SAN moved up to the new Xsan architecture introduced in 10.7. Before you move to 10.10 or 10.11 you will need to make sure open directory is working. I have never done 10.6>10.10/11 but I have done 10.6>10.7/8/9>10.10/11

    Can you tell me more about your SAN? Status of controllers, errors you are seeing, open directory etc.

  • Reply to: Yellow exclamation mark?   2 months 2 weeks ago

    Sounds like MDC1 isn't seeing the LUNS but MDC2 is. The yellow typically meant at least one controller couldn't see the LUNS. pump out a diskutil list from both your MDCS next time this happens. Check FC connections between controllers(mostly MDC1) and switch.

  • Reply to: Yellow exclamation mark?   2 months 2 weeks ago

    the minute i boot MDC1 the yellow exclamation mark appears at the unnamed LUN...

  • Reply to: Yellow exclamation mark?   2 months 2 weeks ago

    XSAN 3.1, enhance storage, two macminis as MDC's, promise sanlinks


    I've inherited this Xsan at my new Job. I know a thing or two about Xsan but i'm no wizard.. ;)
    Last week the volume did a failover from mdc1 to mdc2 couldn't get my head around why. After a reboot of mdc1 and a failover back from mdc2 to mdc1 everything seemed ok. Two days later same thing. But this time my storage (enhance RS16) was not showing up in the disk util. So powering down both mdc's, reboot of the storage and the volume worked again.

    I had noticed before all this happened that there was a yellow exclamation mark at the LUN overview. Because the volume failovered the last time to mdc2 i booted that mdc first.
    I noticed that there is no yellow exclamation mark anymore, but the minute i boot up mdc1 its there...

    When i go to the LUNs in XSAN admin I see three of them:

    empty - 26 TB - empty - empty
    XsanLUN1 - 2TB - MetadataAndJournal - Video
    XsanLUN2 - 22 TB - Video - Video

    Where is the first collum is 'LUN Label" the second "Size" the third " Storage Pool" and the fourth " Volume".

    Question: is it normal to have an unnamed LUN? And what does the yellow exclamation mark mean the minute i boot mdc1?