Unsolved
This post is more than 5 years old
2 Intern
•
2K Posts
0
1114
May 22nd, 2007 23:00
Storage Node V/s. Dedicated Storage Node Licensing
Hi,
We have around 7 dedicated storage node licenses with us. Our servers are in cluser. When we configure backups, we configure a storage node for the backup of the virtual client.
We are not able to configure a dedicated storage node for a device that resides on a physical ndoe coresponding to the virtual node.
The drives are getting disabled because we have a DSN licenses but the clients are configured as SN.
Is there a problem using a DSN license when using a SN?
We have around 7 dedicated storage node licenses with us. Our servers are in cluser. When we configure backups, we configure a storage node for the backup of the virtual client.
We are not able to configure a dedicated storage node for a device that resides on a physical ndoe coresponding to the virtual node.
The drives are getting disabled because we have a DSN licenses but the clients are configured as SN.
Is there a problem using a DSN license when using a SN?
0 events found
No Events found!


dpinink_silva
2 Intern
•
724 Posts
1
May 23rd, 2007 10:00
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,
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
May 23rd, 2007 12:00
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).
Correct. EMC might change that soon if tests are successful for one current beta version (then DSN will work for clustered systems too).
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
May 25th, 2007 01:00
amediratta
2 Intern
•
2K Posts
0
May 25th, 2007 01:00
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
May 25th, 2007 03:00
amediratta
2 Intern
•
2K Posts
0
May 25th, 2007 03:00
The customer never had a storage node license and has been using the same config for years.
What else could have gone wrong?
amediratta
2 Intern
•
2K Posts
0
May 25th, 2007 06:00
enforced before,
Is this adjustable or is it a probable bug in the previous version?
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
1
May 25th, 2007 07:00
amediratta
2 Intern
•
2K Posts
0
May 26th, 2007 04:00
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
May 26th, 2007 11:00
amediratta
2 Intern
•
2K Posts
0
May 26th, 2007 23:00
They have recently sold 40 NRM licenses and when they are about to deliver, they recollect it is EOL product - then why do you sell them to new customers?
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
May 27th, 2007 06:00
cfaller
96 Posts
0
May 27th, 2007 17:00
or if this is not feasable or not an option, is it possible to perform Service failovers without SLA issues, as you could use a savepnpc functionality to have the Services all Failover to one single Cluster Mameber to perform the backups, and then the post command could return them back to the requires cluster members. Again maybe not feasable if you need to perform Hot backups or cant affect SLA;s.