03-26-2013 03:47 AM
Hi all,
currently we are running NBU 7.1.0.4 under solaris. Because of the benefits of virtual machines (migrations, recoverability, price,..) we are thinkig about moving our master to our ESX 5.1.
After reading all the documentation we found about that, we stated that:
-there´s no problem on running master in Linux Vmware machines.
-for ESX 5.1 compatibility we will need RHEL 6.
-We will need also Netbackup 7.5
In the other hand we would like to create a cluster of two vmware nodes for the master. I understood that it should be done with Veritas Cluster Server.
Is that right? Does anyone got any experience on this?
Thanks in advance.
Solved! Go to Solution.
03-26-2013 06:52 AM
Correct - catalog migration via catalog recovery cannot be done to convert non-clustered to clustered.
Since your NBU is already clustered, you can simply keep NBU virtual hostname the same - node names can be different. See http://www.symantec.com/docs/TECH58358 :
03-26-2013 04:27 AM
If you are thinking of moving your NBU master to Linux, this is the only supported way: http://www.symantec.com/docs/TECH77448
In short:
You will need assistance from a Symantec Consulting partner to move non-clustered master to clustered.
See: http://www.symantec.com/docs/TECH31385
PS: If you want use VCS in a virtual environment, please take special care when provisioning NICs for heartbeats. Requirements are the same as for physical cluster nodes - NICs must be separate hardware devices to prevent SPOF (single point of failure) which may result in splitbrain condition (data corruption) when both heartbeats on shared infrastructure fail simultaneously. See VCS documentation in https://sort.symantec.com/documentation
03-26-2013 05:44 AM
03-26-2013 06:52 AM
Correct - catalog migration via catalog recovery cannot be done to convert non-clustered to clustered.
Since your NBU is already clustered, you can simply keep NBU virtual hostname the same - node names can be different. See http://www.symantec.com/docs/TECH58358 :