03-17-2010 02:10 PM
Solved! Go to Solution.
04-06-2010 09:02 AM
What I do.
install NB on the two physical servers, with the client name being the physical servers.
I setup a policy to backup the physical servers: (I call this one physical_clusters)
C:\
System State/Shadow copy (depending on the OS version)
I then setup a policy(s) to get the other stuff.
Logging into one of physical servers I go to Cluster Administrator.
Under Groups I look at the virtual names and see what resources each of them owns.
I then setup a policy to get the resources.
CLSTR_Vserver1
M:\
N:\
CLSTR_Vserver2
P:\
R:\
Now I know I get the items from the physical that I need
and I get the resources no matter what physical server they are currently on.
(NOTE: if you log into a Vserver and look at the BAR you will NOT see the Vserver name - that is fine. It works just fine so long as NB is installed on the physical servers)
03-17-2010 03:12 PM
03-18-2010 07:27 AM
03-18-2010 09:44 AM
03-18-2010 10:07 AM
03-18-2010 12:26 PM
04-04-2010 03:58 AM
It is not explained in the documentation properly, but I did some research regarding the backup of active/active cluster.
What you need to do:
1. Install NBU client to both nodes using nodenames as client name (i.e. FC01-A and FC01-B in your case)
2. DO NOT specify any REQUIRED_INTERFACE (it useless as it's impossible to guess which virtual IP will be owned by a node)
Next we need to introduce Virtual hostnames to NBU. In NBU these entities are called as app_clusters:
In this example we will create two app_clusters:
nbemmcmd -addhost -machinename APP1 -machinetype app_cluster
nbemmcmd -addhost -machinename APP2 -machinetype app_cluster
Now we need to add nodes to these clusters:
Cluster APP1, substitute master_name with your master's hostname
nbemmcmd -updatehost -add_server_to_app_cluster -machinename FC01-A -machinetype client -clustername APP1 -netbackupversion 7.0 -masterserver master_name
nbemmcmd -updatehost -add_server_to_app_cluster -machinename FC01-B -machinetype client -clustername APP1 -netbackupversion 7.0 -masterserver master_name
Cluster APP2, substitute master_name with your master's hostname
nbemmcmd -updatehost -add_server_to_app_cluster -machinename FC01-A -machinetype client -clustername APP2 -netbackupversion 7.0 -masterserver master_name
nbemmcmd -updatehost -add_server_to_app_cluster -machinename FC01-B -machinetype client -clustername APP2 -netbackupversion 7.0 -masterserver master_name
Basically, that's it. Now you can use APP1/APP2 as a client name if you want to backup shared resource and NBU will reroute your request to corresponding node which owns the IP and FC01-A/FC01-B if you want to backup something on the node level (like System_State).
This seems to be only solution that allows to backup active/active clusters, I don't know why it is not documented at all.
04-05-2010 05:56 AM
04-05-2010 10:28 PM
04-06-2010 09:02 AM
What I do.
install NB on the two physical servers, with the client name being the physical servers.
I setup a policy to backup the physical servers: (I call this one physical_clusters)
C:\
System State/Shadow copy (depending on the OS version)
I then setup a policy(s) to get the other stuff.
Logging into one of physical servers I go to Cluster Administrator.
Under Groups I look at the virtual names and see what resources each of them owns.
I then setup a policy to get the resources.
CLSTR_Vserver1
M:\
N:\
CLSTR_Vserver2
P:\
R:\
Now I know I get the items from the physical that I need
and I get the resources no matter what physical server they are currently on.
(NOTE: if you log into a Vserver and look at the BAR you will NOT see the Vserver name - that is fine. It works just fine so long as NB is installed on the physical servers)
04-06-2010 01:25 PM