Officially, VSC does not support Linked Mode vCenter. Never has.
Dead in the water? No. You can run unique installs of VSC on a per-vCenter basis. Let me look into "how" exactly for you, with regards to the web client.
Backstory: Support for Linked Mode has been floating around as a request for some time. There has been a lot of back and forth with VMware about the future of federated vCenter management, and whether Linked Mode was the way forward. That decision hasn't been made, so we've opted to wait until that time and prioritize other features above it.
I realize that VSC doesn't support linked mode itself; I've always run two copies of it (one for each vcenter server). When your method of interacting with VSC was through the classic client plugin, I just selected which instance to connect to (and that was fine).
What I am seeing now, though, is the web client detects a linked mode install and doesn't let me work at all.
Honestly linked mode is just a convenience and I can live without it if necessary; but it feels like it's for a silly reason It would be great if I could just have VSC (via the web client) just look at one server at a time, like with VSC 4.2.1.
Any update on getting this working in the Web Client? Other requirements mean I can't just disable vCenter Linked Mode. I only need VSC on this primary vCenter; the other sites aren't NetApp storage anyway.
I've got the same greyed-out screen in Web Client with the red unsupported warning and just spinning "Loading Storage System Details"
Same problem. it worked in the classic client (seperately)
we need linked mode (SRM, shared licences, single management view)
we also need VSC and use it in our vsphere 5.0 setup (VSC 4.2) fine!
is there any work around such as removing linked mode. carrying out 2 installs and get them working them re-enable linked mode or will it just come back? is there a config file we can stop the check for linked mode happening?
Little bit off topic, but to all People who working with VSC 4.x or 5.x how u mange your Snap Vault Relations VM Backups to a Secondary Filer ?We still using On Command Host packages 1.3 with Data protection Manager from Netapp and it Works with VMWAERE 5.5 ( Local Backup, the Snap Vault VMWARE . Are they any Changes in the VSC 5 Version, that a Local Backup can be Snapvaultet to a Secondary Filer without Scripts, or still only Snapmirror function?
It just goes from bad to worse doesnt it. We have worked with netapp since 2007. In the last 18 months they have really gone downhill
1. VSC 5.0 takes months to come out then doesnt support linked mode even with 2 seperate installations of VSC
2. VSC 5.0 drops support for single file restore and then says it might come back later (like WTF)
3. VSC 4.2.1 gets released but doesnt work properly for most people using vsphere 5.5
Where does this leave people on vSphere 5.5 wanting to use VSC. I guess looking for an alternative product to do the job (we are already evaluating)
It also really grates me that we cannot upgrade our Data on Tap to 8.2.x because only snapdrive 7 is supported for exchange in 8.2 and above, and guess what snapdrive 7 only supports exchange 2013 which was less than 6 months old when they made that decision. for now we are stuck on DOT 8.1.x as we run exchange 2010 on snapmanager 6.0.x and stuck with VSC 4.2.1 which we now have to run on seperaste 2008 R2 servers. total nightmare. thanks netapp.....
Just wanted to come in and let everyone know that you've been heard loud and clear, and it is something we're intensely investigating with VMware. I can't go into too many details here, but I will say that the backend [read: API] functionality with SSO isn't as robust with web client as it is/was with the VIC.
We're hoping to get a lot of these things fixed in the upcoming maintenance release.
Thank you for all of the information, and most importantly, your patience! We're on it!