We've been on the phone with Apple's Enterprise Support Group, and been escalated up to the point of having to pay for higher-end supporty. At that point, we phoned Netgear Support to see what they could offer. They're kindly looking into it over the weekend by logging in remotely, but I'm here to ask if there's anyone here who might have experience with a smilar siuation. I've been really hesitant to try and connect to the drive with Xsan Admin, as I want to ensure that nothing gets deleted. Does anyone have a suggestion as to something we might try to get at this data? It seems like it would be a simple matter of connecting to the drive, but that's proving to not be the case. You should track down the solution provider and choke them. I hate to be the one to tell you, but based on your post, the data is likely lost forever and this is for many reasons.įirst, you do not describe the presence of a meta data backup. This is mistake number 1 of whoever set this solution up. Deploying an Xsan with a single controller is foolish at best, negligent at worst. Are there SAN clients in this scendario or was there just the controller and folders reshared over file services? Without it, you have no replication of the volume config information. Next, you mention the boot volume failed with no backup. Based on this description, it sounds like the boot volume was not a mirror boot so all data was on one platter. The failure of that platter means the failure of everything. Your only recourse here is to send the drive out to a drive recovery service or attempt a controller board swap (fingers crossed it is just the controller that failed). With some luck they can recover enough of the drive to allow you to sticth this together. Next, the files that you REALLY need, /Library/FileSystems/Xsan/*, were never backed up. ![]() With the loss of the boot volume, these files are now not available. If the Xsan config files were present you could, in theory, stitch together a new controller and resurrect that volume.Īnd finally, you do not describe a backup solution for the San volume. If there are more details or the conditions are better than you describe, reply. Otherwise, bite the bullet and get that drive out to a data recovery service and pray. The challenge will be in stitching the data together across the LUNs. If you don't have the volume info (/Library/FileSystems/Xsan/config) this is like guessing a number in an infinite set. This is a good thing as you may have as few as one LUN, but likely three. ![]() (Why they did not do Direct attached solution I am still wondering).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |