UNSOLVED
Issues while backing up Cluster servers.
In our environment, When we receive a cluster commissioning request, We add the Cluster server, Physical nodes and the virtual instances to the backups.
1. Cluster server (C)
2.Physical node(N1)
3.Physical node(N2)
4.Virtual instance(V1) which points to N1
5.Virtual instance(V2) which may point to N1 or N2
But Whenever there is a path-failover we encounter errors in the backups. We as a part of backup team are unaware when does the path-failover occurs ( we are not informed the changes in prior). Can anyone provide a solution where the path failover doesnt impact the backups (Any configuration changes or a workaround where the backups of Physical nodes and the virtual instance backups were not impacted during path failover)
Note: We have already added correct remote host entries
Ideally, there should not be any issues even during the fail over from one PN to another.
4.Virtual instance(V1) which points to N1
5.Virtual instance(V2) which may point to N1 or N2
When you stte the above, do you mean to say you have made a hosts file entry from the V1 or V2 to point to the IP of the N1 and N2 ?
please clarify.
Normally one would see errors on N1 or N2 due to entries in registry. Normally there is switch to instruct NW to ignore these and in newer versions this is turned on by default - which version do you run? It would be nice if you could post exact error message.
ble1
6 Operator
•
14354 Posts
•
56186 Points
567
0
Posted December 2nd, 2015 13:00
Which cluster? By default, each virtual server will own its own set of file systems and have their own IPs which if you use and you use save set All will backup only file systems owned by owner (eg. file system owned by specific virtual server).