AFAIK, if you have DSN license and configure the device on a physical node, only data from this physical node could be backed up. That's the way DSN is supposed to work, can only backup data from it's own. If you want to backup data from another client, you should use SN (and expend a lot more money).

Really, I don't know if in such scenario you could use DSN, I would guess that you need SN license for that. From the docs I have here, you cannot use the virtual name as a SN, so you'll have to use the physical name as SN. This way, when you're going to backup data from the virtual one, it's like data is coming from another client, so DSN would not work.

Anyway, I don't know if I was clear enough. You get these erros when trying to backup something or just after configure the devices?

Regards,

Correct. EMC might change that soon if tests are successful for one current beta version (then DSN will work for clustered systems too).

Yes.

Was the behaviour same for version 6.x as well?

What is possible is that license check was not enforced before, but using DSN in cluster is not supported if you are going to backup virtual host. Funny enough, this will change soon, but until that moment he needs to pay as anyone else.

All I have done is upgrade a 6.x setup to 7.3.x and upgrade Dedicated Storage Node(v6) to Dedicated Storage Node(v7).

The customer never had a storage node license and has been using the same config for years.

What else could have gone wrong?

Is this adjustable or is it a probable bug in the previous version?

It's not a bug, but rather such design. You can't adjust it.

But it is difficult to understand and explain why it was working in 6.x and why not in 7.x?

Because license check has been enforced. Soon you will see the same thing with VTL licenses I believe. I believe it is more difficult to explain why customer was not made aware of it before.