2 Intern

 • 

2K Posts

August 3rd, 2007 09:00

Use curphyhost as storage node in the virtual clients resource and then mark the devices as dedicated storage node, this would work.

I am doing same for an SQL & an Exchange cluster.

4 Operator

 • 

14.4K Posts

August 3rd, 2007 15:00

When it comes to DSN, that would be officially supported as of 7.4 version.

2 Intern

 • 

2K Posts

August 4th, 2007 02:00

But it works for 7.3.2 also. We had issues with SN license but it is working good with DSN license.

4 Operator

 • 

14.4K Posts

August 4th, 2007 03:00

I believe customers prefer to have supported solution first. If something goes wrong support simply may turn around and say that environment is not supported and what do you then?

2 Intern

 • 

2K Posts

August 5th, 2007 19:00

Agreed but then what is the solution currently and infact if you want to backup virtual resource of virtual client of a cluster, the SN field has to be curphyhost in normal cases. It is only in DSN but in that case if SN field is updated for physical host it won't work AND you cannot configure a SN/DSN for vitrual clients.

I first did this when ex-service provider had sold DSN instead of SN and have seen this working at another customer. In both cases, the service providers were perhaps the top SPs of the world and EMC support was involved.

May be once we upgrade to 7.4, we are supported. 7.4 is available for upgrade I believe.

12 Posts

August 6th, 2007 12:00

Hi,

correct me if I am wrong but didn't SAN storage nodes and DSNs become certified in clusters in NetWorker 6? That is what I remember and I have been setting it up a couple of times since then.

Curphyhost was new in 7, but DSNs in cluster worked well before that. That is at least what I remember. I've also heard other say that this is new in 7.4 but I don't understand what is new. Or was it removed during the 7.3 due to the DSN licensing problems?

Cheers
Rickard

4 Operator

 • 

14.4K Posts

August 6th, 2007 12:00

Solution is to have SN instead of DSN in cluster. I know that's a bit silly approach, but that's exactly why it has been changed in 7.4.

4 Operator

 • 

14.4K Posts

August 6th, 2007 13:00

It's matter of "logic". DSN should accept saves from host only. Number of clusters do not support to have device attached to virtual host. That meant, and there was line in manual about it, that devices in cluster had to be assigned to physical node. Thus current physical host would take care of that unfortunate logic. That's what has been changed in 7.4.

12 Posts

August 7th, 2007 02:00

Sorry if I am a bit slow, but I still don't understand what has changed. It was supported to backup the virtual host to "curphyhost" in earlier versions too. There is now however a new line in the manual:

"The Dedicated Storage Node License also can be used for backing up virtual clients in a cluster."

But this has been supported before afaik.

4 Operator

 • 

14.4K Posts

August 7th, 2007 04:00

Yes, but you had to use storage node license to have it legally accepted.

12 Posts

August 7th, 2007 07:00

It didn't need a full storage node license to my knowledge. Here is an excerpt from a license guide dated december 2004:

"If the Dedicated Storage Node is in a Cluster then assign a Dedicated Storage Node for each Physical Node."

So as far as I know this has been available as long as since NetWorker 6. I did set it up with NetWorker 6 as well without any problems. The big fuzz then was with using DDS in cluster, which was also certified later on with NetWorker 6.X.

I'm sure this has been certified before. But, if it is only a license task that has been added from earlier versions (according to some sales material!?), I'm happy with the answer.

Cheers
Rickard

4 Operator

 • 

14.4K Posts

August 8th, 2007 08:00

It states wrong - you better check that out with licensing if you don't believe it.

12 Posts

August 9th, 2007 03:00

It really doesn't matter for me since it is now supported as of 7.4. I am however certain this has been told to me to be supported a long time ago. There is also a support article from 2003 handling the problems for DSNs in MSCS after upgrading to NetWorker 7, article id esg63113.

Looks like we've got different information from Legato/EMC.
No Events found!

Top