Search shared Volumes by default???

is it possible to include shared volumes in search by default instead of clicking it every time.
or use shortcuts? cmdaltspace opens spotlight... then ??? to show shared volumes???
thx

Thanks once more BD. I seem to recall on my much mourned PB3400 having a wee app that suppressed Sherlock2—the Spotlight of its day—in OS8.5 and restored the old FindFile to Command-F. I kept reinstalling it all the way to 9.2. If only they had kept it up; it seems Apple's determination that the new and imperfect shall sweep away the old that 'just works' will perpetually provide development opportunities like this.
I'll give Ukelele a bash, but I tend to tone-deafness.
Message was edited by: Ed Hanna

Similar Messages

Finder search on shared volumes: Works on 10.7, not on 10.8

In our office, we have a Mac Mini acting as a local server running OS X 10.8.3 with an external hard drive connected. Each person in our office connects to the Mac Mini through an idividual user account, so that we can control each user's access to the folders on the external hard drive. Some users are on OS X Lion and others are on OS X Mountain Lion.
All of our Lion computers are able to connect to the Mac Mini and do a Finder search for any items in the shared volume. So a filename search for ".doc" on the "Shared" scope returns all Word documents on our Mac Mini server which they have permission to access.
That same feature is not working properly for users connecting through Mountain Lion. When a Mountain Lion user does the same search - filename containing ".doc" - no results are returned initially, however if they toggle the search scope back and forth (like from "Shared" to "This Mac") a few times, eventually some results show up on the Shared search.
But with this issue, we can't be confident that the results listed by any search are complete or not. Our business generates a lot of documents and audio files each day and the search function is a crucial part of our daily workflow.
The Mac Mini server has recently been upgraded from Lion to Mountain Lion 10.8.3, and Mountain Lion users have just upgraded from 10.8.2 to 10.8.3, however the issue is still the same: users connecting with Lion 10.7.5 can search shared volumes properly, but users connecting with Mountain Lion 10.8.3 cannot.
Is there a solution to this that doesn't require a downgrade to Lion?

It sounds like you are using Spotlight.
Spotlight Alternatives
EasyFind – Spotlight Replacement
Find Any File
Information.
Spotlight – 5 things You Never Knew
Spotlight Basics
Spotlight – Create Good Queries
Spotlight FAQ
Spotlight – Narrow Search Results

Why will spotlight only search my HD and not shared volumes?

spotlight gives me the choice to search shared volumes but will not produce any find results.
This is really causing us production issues.
Thanks for any help

You can keep Spotlight from indexing a volume altogether by placing the Volume in the Privacy section of the Spotlight system preference. You would do this for instance, for your Backup volume, because otherwise Spotlight would find duplicates of all your data. Is it possible this is the case?
I have seen where the solution is to add the volume to privacy, to not index and then remove. This seems to make spotlight index the volume. If that does not work, here is an article that details how to manually have spotlight manually index an external drive:
http://forum.multiplexapp.com/comments.php?DiscussionID=17
Notice the caveat in the article
There are some potential drawbacks to indexing network drives, especially those with large amounts of storage. First, if your drive holds tens or hundreds of thousands of files, indexing can be slow and tedious to the OS, and may affect your operating system's performance.
Might be wise to index during off hours.
Cheers
Michael

10.5.6 Can't search shared (time capsule or airport extreme based)

I just purchased and installed a 1T time capsule and also a Airport Extreme. Time capsule drive is configured and working with user-based access. I also have a external powered drive on the Airport Extreme that is also configured for sharing via user access. I can mount and browse and read and write to both drives.
None of the SHARED searches are working at all. When I try to search based on either file name or file contents, nothing happens at all. I can search for files on the local drives with not problem.
This is frustrating because searching shared volumes was one of the big touted features of Leopard.
Any idea what's happening here or how to fix this?

Start with a search for *search server*, *search share*, *shared search*, or variants. There are many recent posts on the subject. Whether or not there are solutions, I haven't a clue since everything I have is connected directly—no wireless stuff here.

Problems with Spotlight searching of shared volumes

According to: http://www.apple.com/macosx/features/300.html#spotlight, I should be able to "...search any connected Mac with Personal File Sharing enabled or a file server that’s sharing its files."
It doesn't specify what "file server", so I presume it means Spotlight should be able to search any mounted shared volume (assuming, of course, that indexing has been enabled).
I have a NAS device that I want to be able to search with Spotlight. According to mdutil, the volume is enabled for indexing, but I don't see any results when I search under "Shared" in Finder via Cmd+F. (I checked, and there's no .Spotlight folders on the volume.)
From what I recall, under Tiger you could manually specify a network volume to index, but if you dismounted the volume, you'd have to re-enable indexing on next mount. This worked for other file systems (such as Fat32 & NTFS), as well as for HFS+ drives.
According to mdutil in Leopard, the volume is still enabled for indexing even across dismounts. The NAS drive is not HFS+ formatted, but uses XFS.
I've tried deleting the index, to no avail.
Has anyone successfully used Spotlight to search mounted volumes on volumes not shared via another Mac?
Am I missing something?

You have not missed anything.... Leopard promises but does NOT deliver.
I use an AFP server with Bonjour enabled. And NO NO NO Spotlight search is possible on this network volume...
This is outrageous and FALSE information....
Oh and - that Leopard is Sporting 300 new features is false info too.... Not even the "What is New in Leopard" says anything about 300 features.. But it sounds great doesn't it....

How to recover deleted files from a shared volume?

Setup - Mac Mini Server (OSX 10.8.4, Server 2.2.1(169)), 256GB Flash drive, System data only. External 8TB G-Raid holds all business data, backed up to a LaCie 6TB Quadra using Intego Backup Manager Pro 1.0.9. The G-Raid has two folders 0_Clients and DATA which are shared through OS X Server.
Situation, told customer backup drive (LaCie) was almost full mid April, purge data. They didn't and backups stopped running at end of April. Yesterday, they accidentally deleted a folder / with files. User was on an iMac, connected to the share DATA when deleted. Called in a panic of course. New folder and files were created after the last back was executed.
Question - Folder and files were deleted but Trash was not "emptied". Researching, I learned about hidden trash folders. So, I was hopeful I'd find the info in the hidden /.Trashes folder on the shared Volume G-Raid. My understanding is that that's where it would go, until an "empty trash" is executed. I've shown all hidden files / folders via "defaults write com.apple.finder AppleShowAllFiles TRUE". Navigated to the volume G-Raid/.Trashes and the folder/ files are not there. Is there another location where they may possibly be??? Or, are they hosed and it's really gone "Deleted"???
Thx

With a locally connected volume e.g. a hard disk or USB flash drive, when you delete a file it does get moved to the 'Trash' folder and until the Trash is emptied can still be retrieved. However with a network volume if a logged in user deletes a file or folder it normally gets deleted immediately. (The user would get a message saying "This item will be deleted immediately. You can’t undo this action.")
So the likelihood is that the items are not in any trash folder even if you found and looked in them.
It used to be the case that even when using a network file server you still had the benefit of files first going to the trash folder but Apple stopped doing this a long time ago. The network trash folder would be at the top level of the network share. (If it exists and works.) Some NAS devices might still support it but as I mentioned I don't believe Apple themselves do.
So you could try using Terminal.app to look for an invisible folder at the top-level folder of the network share, if the network share is a folder called 'Fred' then this invisible folder would be in 'Fred' and would be called "Network Trash Folder". You can try looking for this either on the server or from a logged in client.
Do ls -la in Terminal.app the 'a' flag means show all including invisible files.
As you have probably guessed by now it is almost certainly the case these files are lost and cannot be retrieved. The users unfortunately are guilty of multiple mistakes.
They ignored your warning about the backup drive
They deleted something they should not have
They ignored the warning the Mac would have shown about "This item will be deleted immediately. You can’t undo this action."
I would add an additional error that they and perhaps you as their advisor are guilty of. Never rely on a single level of backup, ideally you should have a rotating set of backups i.e. one for each day - Monday, Tuesday, etc. and even more importantly should store these off-site unless being used so that in the even of a fire, flood or other disaster you still have intact backups.
In theory ACL permissions can be set to allow reading, allow writing but disallow deleting. Unfortunately in the real world trying to use the disallow deleting option is a waste of time. This is because many programs 'save' changes by saving a new temporary file, deleting the original file, and renaming the temporary file to the original name. This will not work if you block deleting.

Smart Folders searching Shared Computers

I'm using 10.6.4 on a 27" iMac i5. I can't create a smart folder that searches files on a shared volume (TCP/IP via ethernet). When I initially create the smart folder the search works fine and the networked files are visible, but when I save it to my local desktop and then click the shared folder, only local files are shown. If I click on the Action Menu (the gear wheel) and select Show Search Criteria, it indicates "This Mac" is being searched, I change it to "Shared" and then re-save the smart folder to no avail.
Perhaps there is a simple explanation. If so I will gladly perform a "facepalm". According to Apple website, shared volumes are searchable by smart folder "Mac OS X 10.6 Help - Creating a Smart Folder" Suggestions?

I am having the same issue. MacPro 10.6.5 Create Smart Folder with files from an AFP over TCP/IP network, but when the shared drive is unmounted and remounted again, only the files from the local drive showed up, I have to go back to "Show Search Criteria" and select "shared" again...
Suggestions ?

Inconsistant Shared Volume Issues...

Friends,
I keep having an issue whereby the shared volumes attached to my MacMini are inconsistantly available to my laptop computers, connected via WiFi. There seems to be no trigger, sometimes the volumes mount right away, other times not. Mac Mini is set to never sleep, the external drive that holds the partitions is connected via FW800.
I had a similar issue with this same drive when it was connected to an Apple Airport Base Station and setup as a shared disk via USB.
Is this a known issue? Is this caused by a volume with 4 partitions (JBOD mode on Lacie Big Disk)? Is this just a WiFi issue?
Thanks in advance.

Going to bump this... searching didn't answer my question.
Has anyone else experienced this?

Is is possible to use creative cloud as a shared volume for collaboration between incopy & indesign?

I'm a designer student and as a designer, I constantly have to make decks for presentations. I typically work in a group of six and because I'm confident with graphic design, I tend to be the leader of these tasks. I've found the best workflow for slide creation is Indesign. Unfortunatly, I'm just an awful writer— so when I heard about Incopy's collabrative features(saw the post from indesign's facebook page) I saw oppertunity and got very excited. My teamates and I typically all have subscriptions to adobe cc because of this, I was wondering (since I havent used it at all) if the storage given out from adobe cc was able to be that shared volume that is required for the live link between incopy stories and indesign layouts.
Therefore,
Is is possible to use creative cloud as a shared volume for collaboration between Incopy & Indesign?
If this needs any further clarification I'll gladly write a more detailed question — lastly, if this is not possible might you suggest an alternative? Please assume that we go to school together but we work offsite also.

You will not be able to use the Files page at https://creative.adobe.com/files for collaboration in this way. But you can share individual files in this way.
When folder sharing is available this will be possible.

Error -50 on a shared volume (SOLUTION)

Today my antique Xserve (G5, 2 Gigs RAM, 10.4.11) started throwing error -50s on any changes on the main shared volume. Couldn't create a folder, save a file, rename a file or any other change.
After running Disk Utility repairs on the shared volumes and fixing the errors, the volume returned to normal service. YMMV on 10.5 and 10.6 server,but check the disk anyway,

How have you set up sharing.
Can you confirm the exact wording of the error message.

Error when adding a disk to Cluster Shared Volumes

When adding a disk to Cluster Shared Volumes via Failover Cluster Manager, I get a couple of errors.
Event ID 5145 in System Log:
While adding the disk ('Cluster Disk 1') to Cluster Shared Volumes, setting explicit snapshot diff area association for volume ('\\?\Volume{420e2cc4-4fb4-41be-afb1-65f2ee62457a}\') failed with error 'HrError(0x8004230d)'. The only supported software snapshot
diff area association for Cluster Shared Volumes is to self.
Cluster disk resource 'Cluster Disk 1' failed to delete a software snapshot. The diff area on volume '\\?\Volume{420e2cc4-4fb4-41be-afb1-65f2ee62457a}\' could not be dissociated from volume '\\?\Volume{420e2cc4-4fb4-41be-afb1-65f2ee62457a}\'. This
may be caused by active snapshots. Cluster Shared Volumes requires that the software snapshot be located on the same disk.
Any ideas why I'm getting this error? This disk was previously added as a CSV to different Windows failover cluster, if that matters. Thanks.

Hi,
As the disk was previously used as a CSV, I assume there is still data on it.
Please check if any VSS snapshot created on that disk. If so, delete them and re-add it as a CSV to see the result - a quick way is to backup important files and perform a re-format if you cannot confirm.
If you have any feedback on our support, please send to [email protected]

Unable to configure Time Machine backups to shared volume on network

I've been unable to coax Time Machine (TM) into using a networked shared volume that SuperDuper! accesses without a hitch.
My wife and I have laptops (TiBook and MacBook Pro, respectively), and we have a G4 Mac Mini with an external 300 GB HD. The Mini is connected to a wired Ethernet port on a GigE Airport base station (I've long ago given up on connecting that HD to the Airport). Our laptops connect wirelessly. All three machines are now running 10.5, and I've checked that the Mini is sharing the external HD via System Preferences. My wife and I both have accounts on the Mini, and those accounts provide read/write access on the external HD. Mounting that volume from our laptops works perfectly, as does backing up to it using SuperDuper! TM, however, doesn't recognize that volume as a backup location.
Any ideas?
Thanks,
Andreas

Adapting the instruction in this post worked for us. I connected to the Mini via ssh and entered the commands to enable the external HD. It then showed up as a TM backup location on both of our computers, and the progress meters for the initial backup are ticking away.
Cheers,
Andreas

How do I connect to a Windows Workgroup and mount a shared volume?

I have set up a network at home with my Mac G5 and my PC. I have a workgroup called "HOME". The PC can see my mac drive as a network place and I can access and browse it perfectly fine.
However I have a drive on my PC which I have set up as a shared volume on the PC. I want to mount that shared volume on my Mac. When I set up the share on the PC, I am not prompted to enter a password, and the only password I am aware of is the one I use to log on.
According to the instructions I am supposed to enter the IP address and a "sharename", but I have no idea what the sharename is. If I enter the share name of the volume I want to mount, I get a dialog box which requires a password. It sees the "HOME" workgroup and that is already filled out in the Workgroup window.
It has entered my Mac administrator account name in the Name box. I don't know if this is what name it needs, but what ever combination of names and passwords I use, including my PC logon name and password, I always get the error message "cannot connect because the name or password is not correct".
I have tried using different formats for the smb://Servername/sharename address, but everything I have tried gives the same result.
I have seen many other postings on this subject, all with similar problems, but so far I've yet to see an answer. A disscussion from 2004 said this was a known issue, but surely there must have been a fix by now?
I have read many of the mac documents on this subject but none specifically tells you what the sharename is and how you set a password for it.
Thanks in advance
David

OK - I have answered my own question, so if anyone else has this problem, you may like to know!
I needed to know what sharename to use to log on. On the Windows PC I was under the imprression that the windows log on was my user name. But if you right click on the My Computer and go to manage, you will see Local Users and Groups. Under Users, you will see all the user accounts on the PC. Even though I only ever set up one and it was called "David" that doesn't actually count as the user name.
If you look at the headings at the top, you will see that whatever account you think you are in, the chances are it actually has the name "User". It is what ever is in the Name column that the Mac needs, not what is in the Full Name column which is what you log on as. You can't change this, but when you connect to server, you can enter the SMB script smb://USER@(name of PC or IP address)/share name.
If you wish to mount a volume rather than a shared folder, simply type in the windows drive letter followed by the "$" - ie D$. The password is your log on password on the PC. Otherwise you can set up a folder share on the PC in the usual way, and give it a name. This will be the share name you enter in your smb script.
NONE of this is very clear in any of the Mac Networking Help guides that I have trawled through, so if they were to add it, you might help some more people...
Thanks,
David
G5 Mac OS X (10.4.6)

Hyper-V cluster Backup causes virtual machine reboots for common Cluster Shared Volumes members.

I am having a problem where my VMs are rebooting while other VMs that share the same CSV are being backed up. I have provided all the information that I have gather to this point below. If I have missed anything, please let me know.
My HyperV Cluster configuration:
5 Node Cluster running 2008R2 Core DataCenter w/SP1. All updates as released by WSUS that will install on a Core installation
Each Node has 8 NICs configured as follows:
NIC1 - Management/Campus access (26.x VLAN)
NIC2 - iSCSI dedicated (22.x VLAN)
NIC3 - Live Migration (28.x VLAN)
NIC4 - Heartbeat (20.x VLAN)
NIC5 - VSwitch (26.x VLAN)
NIC6 - VSwitch (18.x VLAN)
NIC7 - VSwitch (27.x VLAN)
NIC8 - VSwitch (22.x VLAN)
Following hotfixes additional installed by MS guidance (either while build or when troubleshooting stability issue in Jan 2013)
KB2531907 - Was installed during original building of cluster
KB2705759 - Installed during troubleshooting in early Jan2013
KB2684681 - Installed during troubleshooting in early Jan2013
KB2685891 - Installed during troubleshooting in early Jan2013
KB2639032 - Installed during troubleshooting in early Jan2013
Original cluster build was two hosts with quorum drive. Initial two hosts were HST1 and HST5
Next host added was HST3, then HST6 and finally HST2.
NOTE: HST4 hardware was used in different project and HST6 will eventually become HST4
Validation of cluster comes with warning for following things:
Updates inconsistent across hosts
  I have tried to manually install "missing" updates and they were not applicable
  Most likely cause is different build times for each machine in cluster
   HST1 and HST5 are both the same level because they were built at same time
   HST3 was not rebuilt from scratch due to time constraints and it actually goes back to Pre-SP1 and has a larger list of updates that others are lacking and hence the inconsistency
   HST6 was built from scratch but has more updates missing than 1 or 5 (10 missing instead of 7)
   HST2 was most recently built and it has the most missing updates (15)
Storage - List Potential Cluster Disks
  It says there are Persistent Reservations on all 14 of my CSV volumes and thinks they are from another cluster.
  They are removed from the validation set for this reason. These iSCSI volumes/disks were all created new for
  this cluster and have never been a part of any other cluster.
When I run the Cluster Validation wizard, I get a slew of Event ID 5120 from FailoverClustering. Wording of error:
  Cluster Shared Volume 'Volume12' ('Cluster Disk 13') is no longer available on this node because of
  'STATUS_MEDIA_WRITE_PROTECTED(c00000a2)'. All I/O will temporarily be queued until a path to the
  volume is reestablished.
Under Storage and Cluster Shared VOlumes in Failover Cluster Manager, all disks show online and there is no negative effect of the errors.
Cluster Shared Volumes
We have 14 CSVs that are all iSCSI attached to all 5 hosts. They are housed on an HP P4500G2 (LeftHand) SAN.
I have limited the number of VMs to no more than 7 per CSV as per best practices documentation from HP/Lefthand
VMs in each CSV are spread out amonst all 5 hosts (as you would expect)
Backup software we use is BackupChain from BackupChain.com.
Problem we are having:
When backup kicks off for a VM, all VMs on same CSV reboot without warning. This normally happens within seconds of the backup starting
What have to done to troubleshoot this:
We have tried rebalancing our backups
  Originally, I had backup jobs scheduled to kick off on Friday or Saturday evening after 9pm
  2 or 3 hosts would be backing up VMs (Serially; one VM per host at a time) each night.
  I changed my backup scheduled so that of my 90 VMs, only one per CSV is backing up at the same time
   I mapped out my Hosts and CSVs and scheduled my backups to run on week nights where each night, there
   is only one VM backed up per CSV. All VMs can be backed up over 5 nights (there are some VMs that don't
   get backed up). I also staggered the start times for each Host so that only one Host would be starting
   in the same timeframe. There was some overlap for Hosts that had backups that ran longer than 1 hour.
  Testing this new schedule did not fix my problem. It only made it more clear. As each backup timeframe
  started, whichever CSV the first VM to start was on would have all of their VMs reboot and come back up.
I then thought maybe I was overloading the network still so I decided to disable all of the scheduled backup
and run it manually. Kicking off a backup on a single VM, in most cases, will cause the reboot of common
CSV members.
Ok, maybe there is something wrong with my backup software.
  Downloaded a Demo of Veeam and installed it onto my cluster.
  Did a test backup of one VM and I had not problems.
  Did a test backup of a second VM and I had the same problem. All VMs on same CSV rebooted
Ok, it is not my backup software. Apparently it is VSS. I have looked through various websites. The best troubleshooting
site I have found for VSS in one place it on BackupChain.com (http://backupchain.com/hyper-v-backup/Troubleshooting.html)
I have tested almost every process on there list and I will lay out results below:
  1. I have rebooted HST6 and problems still persist
  2. When I run VSSADMIN delete shadows /all, I have no shadows to delete on any of my 5 nodes
   When I run VSSADMIN list writers, I have no error messages on any writers on any node...
  3. When I check the listed registry key, I only have the build in MS VSS writer listed (I am using software VSS)
  4. When I run VSSADMIN Resize ShadowStorge command, there is no shadow storage on any node
  5. I have completed the registration and service cycling on HST6 as laid out here and most of the stuff "errors"
   Only a few of the DLL's actually register.
  6. HyperV Integration Services were reconciled when I worked with MS in early January and I have no indication of
   further issue here.
  7. I did not complete the step to delete the Subscriptions because, again, I have no error messages when I list writers
  8. I removed the Veeam software that I had installed to test (it hadn't added any VSS Writer anyway though)
  9. I can't realistically uninstall my HyperV and test VSS
  10. Already have latest SPs and Updates
  11. This is part of step 5 so I already did this. This seems to be a rehash of various other stratgies
I have used the VSS Troubleshooter that is part of BackupChain (Ctrl-T) and I get the following error:
  ERROR: Selected writer 'Microsoft Hyper-V VSS Writer' is in failed state!
  - Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
  - Writer Failure code: 0x800423f0 (<Unknown error code>)
  - Writer ID: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
  - Instance ID: {d55b6934-1c8d-46ab-a43f-4f997f18dc71}
  VSS snapshot creation failed with result: 8000FFFF
VSS errors in event viewer. Below are representative errors I have received from various Nodes of my cluster:
I have various of the below spread out over all hosts except for HST6
Source: VolSnap, Event ID 10, The shadow copy of volume took too long to install
Source: VolSnap, Event ID 16, The shadow copies of volume x were aborted because volume y, which contains shadow copy storage for this shadow copy, wa force dismounted.
Source: VolSnap, Event ID 27, The shadow copies of volume x were aborted during detection because a critical control file could not be opened.
I only have one instance of each of these and both of the below are from HST3
Source: VSS, Event ID 12293, Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details RevertToSnashot [hr = 0x80042302, A Volume Shadow Copy Service component encountered an
unexpected error.
Source: VSS, Event ID 8193, Volume Shadow Copy Service error: Unexpected error calling routine GetOverlappedResult. hr = 0x80070057, The parameter is incorrect.
So, basically, everything I have tried has resulted in no success towards solving this problem.
I would appreciate anything assistance that can be provided.
Thanks,
Charles J. Palmer
Wright Flood

Tim,
Thanks for the reply. I ran the first two commands and got this:
Name
Role Metric
Cluster Network 1
3  10000
Cluster Network 2 - HeartBeat                              1   1300
Cluster Network 3 - iSCSI                                    0  10100
Cluster Network 4 - LiveMigration                         1   1200
When you look at the properties of each network, this is how I have it configured:
Cluster Network 1 - Allow cluster network communications on this network and Allow clients to connect through this network (26.x subnet)
Cluster Network 2 - Allow cluster network communications on this network. New network added while working with Microsoft support last month. (28.x subnet)
Cluster Network 3 - Do not allow cluster network communications on this network. (22.x subnet)
Cluster Network 4 - Allow cluster network communications on this network. Existing but not configured to be used by VMs for Live Migration until MS corrected. (20.x subnet)
Should I modify my metrics further or are the current values sufficient.
I worked with an MS support rep because my cluster (once I added the 5th host) stopped being able to live migrate VMs and I had VMs host jumping on startup. It was a mess for a couple of days. They had me add the Heartbeat network as part of the solution
to my problem. There doesn't seem to be anywhere to configure a network specifically for CSV so I would assume it would use (based on my metrics above) Cluster Network 4 and then Cluster Network 2 for CSV communications and would fail back to the Cluster Network
1 if both 2 and 4 were down/inaccessible.
As to the iSCSI getting a second NIC, I would love to but management wants separation of our VMs by subnet and role and hence why I need the 4 VSwitch NICs. I would have to look at adding an additional quad port NIC to my servers and I would be having to
use half height cards for 2 of my 5 servers for that to work.
But, on that note, it doesn't appear to actually be a bandwidth issue. I can run a backup for a single VM and get nothing on the network card (It caused the reboots before any real data has even started to pass apparently) and still the problem occurs.
As to Backup Chain, I have been working with the vendor and they are telling my the issue is with VSS. They also say they support CSV as well. If you go to this page (http://backupchain.com/Hyper-V-Backup-Software.html)
they say they support CSVs. Their tech support has been very helpful but unfortunately, nothing has fixed the problem.
What is annoying is that every backup doesn't cause a problem. I have a daily backup of one of our machines that runs fine without initiating any additional reboots. But most every other backup job will trigger the VMs on the common CSV to reboot.
I understood about the updates but I had to "prove" it to the MS tech I was on the phone with and hence I brought it up. I understand on the storage as well. Why give a warning for something that is working though... I think that is just a poor indicator
that it doesn't explain that in the report.
At a loss for what else I can do,
Charles J. Palmer

Hyper V hosts with Cluster Shared Volume do not provide Shared VHDX ability

Hi there, i've configured a pair of Hyper V hosts (UCS B230 M2) with SAN-Boot and access to a Shared Fiber Channel LUN.
No matter what I try, when I add a SCSI Adapter and one VHDX virtual disk to a VM, the option for "Advanced" never shows up therefore I can not share the VHDX file between another VM, which prevents any VM based clustering from working (IE: Clustered
SQL server)
Here are the settings I have configured:
The LUN has been formatted with NTFS
The Hyper V hosts have been configured as a Windows Cluster with an IP address and the Fiber Channel LUN configured as a Cluster Shared Volume
I follows the guides below
Create a CSV
https://technet.microsoft.com/en-us/library/dn265980.aspx
Create a shared VHDX
https://technet.microsoft.com/en-us/library/dn282283.aspx
Further details:
Two HyperV server core hosts built
Both joined to AD
Both joined to a Windows failover cluster
One 2TB Fibre Channel LUN presented from an EMC VNX array to both hosts
LUN formatted as NTFS
LUN created as a Cluster Shared Volume
Cluster Shared Volume present on both HyperV hosts
VM created within the Cluster Shared Volume
VM Booted up and Windows 2012 has been installed
VM gracefully shut down
Through the HyperV Manager, going in to VM settings,create a SCSI adapter, create a new VHDX file inside the CSV, the “Advanced” option for the VHDX is not present, therefore the option to make the VHDX file shared is not available
I have followed all steps in the Microsft Technet pages to create a CSV and a VM with Shared VHDX
I’ve cleared all settings and restarted multiple times, but this option is not present

Hi Sir,
>>No matter what I try, when I add a SCSI Adapter and one VHDX virtual disk to a VM, the option for "Advanced" never shows up therefore I can not share the VHDX file between another VM
>>Yes we are using Hyper-V Server 2012 R2
As we know Hyper-v server 2012R2 is a free version without GUI , I'm afraid you are not using Win 8.1 or other windows server 2012R2 to manage that free version hyper-v server .
Shared vhdx is a new feature came with 2012R2 , if use previous windows to manage 2012R2 you will not see "advanced" option (The blue circle belongs 2012 , the red circle belongs to 2012R2 ):
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Search shared Volumes by default???

Similar Messages

Maybe you are looking for