I am likely to do this later in the week. Do you think there is some issue in VCB with 7.4SP1. I am encouraging the customer to upgrade since I thought new changes in VCB should be beneficial.

Well, right now it seems to fail at the point where save should kick in. I didn't have time today to check this further so I have no updates on that.

There is another interesting point I came up during weekend while think about it. So far you could use DSN for proxy and that worked. It is fact that there is an article in KB which states you should use storage node, but DSN worked fine so far so I wonder...

Now, you have setup pretty much as with other proxy based backup utilizing LAN-free setup. Each VM is client which does snap and snap gets mounted under proxy and data is saved under name of client. Because of that it makes sense to have storage node license. This also means you might have to use storage node field of VM. If that is the case then you must use SN licenses for sure. If specifying proxy under client setup is enough then SN field by proxy should be used and in theory DSN might be enough (having index masked under different client names is not trigger for SN license in this case). Right now I'm investigating this, but it seems that even at EMC they do not have quick answer for that. I would know it immediately if my setup worked, but I'm in process of revisiting setup and see what's wrong.

You are right, VCB worked with DSN license as against SN mentioned in the documents and EMC support has no clue to VCB backups. They will forward you the same admin guide as in Powerlink. But if SN field is to be used for VM, then SN license becomes mandatody. DSN in that case should nto work and for DSN you need mode DSN licenses - one per VM.

No you don't as VM can't be storage node AFAIK. And besides, if it could be then you don't need proxy.

We'll see what happens first; I find this myself or EMC comes back to me before

Hi,

I just wanted to know how successful were you with VCB backups?

I made it work of course, but I also found other interesting things too. Some of those are right now on engineering's desk.

Hello,
Did you see that a VM backed up only through VCB consuming a Client Connection License?
I want to know if a have tell the customer to buy Client Connection Licences when he upgrades to SP1....

Thanks.

best regards
Manfred

No, I didn't pay attention to that, but it is not supposed to do that. Reason is:
a) data is saved from proxy client
b) while index is written for separate clients and data is represented that way, index belongs to server

The only reason why client license would be used is this logic where data belongs to client (not the case before). However I do not think that was the design thus I would complain if I would get to see VM machines taking client connections. I believe I already asked EMC on this and I was told this is not supposed to be the case... but be prepared for surprises as rumors are...

Oddly enough in my test here Virtual Clients gather themselves a regular Client Connection... Which is quite interesting...

Oddly enough I believe you so And that's not design either