Installed VSC 2.0 earlier which went well. I found the 2 netapp systems and added them in although it did take a while on the 'Discovering Network Components' part and it only shows controller A for each system but does list controller B as a partner.
I then selected it to set all the mpio settings per host which it did and presented my with lots of Normal green tick icons which was good.
It also correctly shows the storage details for the sans ie Volumes, Luns etc...
I did a test backup and that worked great.
I then decided to have a go at the Provisioning and Cloning or more precisely just the cloning.
For info, we are using VMFS datastores on Fibre Channel storage.
No matter what I did it would not connect to the storage controllers and kept giving timeout error. Looking in the log files showed some errors which seemed to revolve around nfs so I downloaded a trial license and put that onto the controller. Hey presto it would now talk to the controller and let me add it in.
Am a little worried as to why it wouldn't let us continue without the nfs license and am hoping that is some sort of bug.
Have just done 2 'not so rapid' clones to see how it worked and noticed it seems to have put some partitions onto the wrong datastores for me which might be why it's taking a while. The template had 3 drives c: d: e: with c & d being on one datastore and the pagefile e: being on a different datastore. Unfortunately it also put c: on the pagefile datastore.
2 images started at 18:12, finished at 19:03 with zero other traffic at all on the SAN and no other work on the vsphere servers.
I think because it put some files in the wrong datastore is why it used up 90 gig of disk space and took so long. Will continue to play and see how it goes.
Overall like how it's all integrated, I just need to get used to how it works now.
Have raised a support case to do with the nfs license though as that is very worrying.