|
[ADSM-L] Node replication and authorized nodes, proxies, etc
2015-05-05 14:28:18
Hello folks,
We are in the process of implementing
node replication and I'm having some difficulty with the reporting of success/failure
on replication tasks. The way that our environment is structured
is that selected critical nodes will replicate to an offsite server but
our non-critical data will not. That said, we have a number of nodes
(DB2 API clients and VMWare in particular) that are associated in some
way to critical production nodes (such as proxy relationships, backup access
for cross-node restores, etc) that are not themselves critical and should
not be replicated.
However, when a replicate node command is issued, it returns a Failure
code because these associated nodes are not enabled for replication.
This makes reporting on replication
a pain and also obscures 'actual' failures in the replication process that
I need to keep on top of.
So my question is this: for those of
you that are using node replication for a subset of your nodes, how are
you managing your node relationships so that the replicate node command
returns a Success code?
Thanks!
__________________________
Matthew McGeary
Technical Specialist - Infrastructure
PotashCorp
T: (306) 933-8921
www.potashcorp.com
|
| <Prev in Thread] |
Current Thread |
[Next in Thread> |
- [ADSM-L] Node replication and authorized nodes, proxies, etc,
Matthew McGeary <=
|
|
|
