If it is a clustered resource it will most likely have an IP address and host name associated within the Cluster configuration. You would define this name as the NetWorker client and then secure the data via this. If it is sending data across the LAN to a storage node then this requires no more changes. If physical hosts of the cluster are NetWorker storage nodes you can change the storage node parameter to curphyhost which will direct the data to the storage node which the Oracle service is running on at that time.
There are examples in the Admin guides for setting up clusters and cluster services.
It is a clustered resource, one in active and the other in passive. My Networker Server is also my Storage node and must be able to switch from one resource to another in case of hight disponibility.
And If I understand well, what you 're trying to say is My Networker server will see a unique (single) Host ?
OK so the client as well as the storage node is a clustered service.
Clustering NetWorker server can be done several ways, but it sounds like the Networker server is also Active/passive situation. In this case you will define the devices to be local to the NetWorker server service and ensure that the device paths are the same on each physical host. This is required as if you have a failover we need to find the volumes in the same drives on the physical hosts to continue without manual intervention.
In this case the storage node field can be nsrserverhost or NetWorker server service name on the client definition.
So client definition is on service name.
Storage node defined as NWS service name and drives defined as local to the service i.e. no rd=phyical host1:device path and rd=physical host2:device path within NetWorker - just device path for Service host name.
masonb
445 Posts
0
September 14th, 2011 09:00
Rodygogan,
If it is a clustered resource it will most likely have an IP address and host name associated within the Cluster configuration. You would define this name as the NetWorker client and then secure the data via this. If it is sending data across the LAN to a storage node then this requires no more changes. If physical hosts of the cluster are NetWorker storage nodes you can change the storage node parameter to curphyhost which will direct the data to the storage node which the Oracle service is running on at that time.
There are examples in the Admin guides for setting up clusters and cluster services.
Regards,
Bill Mason
rodygogan
15 Posts
0
September 14th, 2011 09:00
Thank you William,
It is a clustered resource, one in active and the other in passive. My Networker Server is also my Storage node and must be able to switch from one resource to another in case of hight disponibility.
And If I understand well, what you 're trying to say is My Networker server will see a unique (single) Host ?
King regards,
masonb
445 Posts
0
September 14th, 2011 10:00
Rodygogan,
OK so the client as well as the storage node is a clustered service.
Clustering NetWorker server can be done several ways, but it sounds like the Networker server is also Active/passive situation. In this case you will define the devices to be local to the NetWorker server service and ensure that the device paths are the same on each physical host. This is required as if you have a failover we need to find the volumes in the same drives on the physical hosts to continue without manual intervention.
In this case the storage node field can be nsrserverhost or NetWorker server service name on the client definition.
So client definition is on service name.
Storage node defined as NWS service name and drives defined as local to the service i.e. no rd=phyical host1:device path and rd=physical host2:device path within NetWorker - just device path for Service host name.
Hope that helps
Regards,
Bill Mason
rodygogan
15 Posts
0
September 14th, 2011 10:00
Many Thanks will