Hey there,
This post is a little gift for those of you out there who run clustered NetBackup on VCS to go along with our earlier posts on emulating the NetBackup activity monitor on the command line and copying and modifying NetBackup policies, schedules and clients between hosts:)
As most of you who've run NetBackup in a VCS cluster may know, sometimes getting support for NetBackup (used with VCS) can be a royal pain; never mind that NetBackup (Symantec or, previously, Veritas) can be "purchased" as a VCS cluster add-on. The problem (and, to me, this is inexplicable, since NetBackup used to be a Veritas product) is that, if you ever experience issues with your NetBackup cluster and need to call Symantec for help, they generally have an entirely contrary attitude if they find out that you're actually running NetBackup in a VCS cluster that includes other "certified" add-on components (?)
And, yes, you read that correctly: You're going to have problems getting reasonable support for NetBackup if you've incorporated any other VCS modules in your cluster. If you want to get decent support for your clustered NetBackup setup (in my experience) your cluster should "only" include the NetBackup add-on Module. This is hardly a realistic scenario, but (for instance), if you're running the Oracle and NetBackup add-on modules in the same cluster, your support experience will be less than pleasant.
Hurdling right over the argument that Symantec "should" enthusiastically support NetBackup in a Cluster, no matter what else is clustered with it, we'll proceed directly to the solution. It's not exactly Kosher, but it works :)
Let's say, for instance, that you have a 2 node VCS cluster. Let's also say that your cluster has both Oracle and NetBackup add-on modules installed and operational. Then, finally, let's say the NetBackup component begins to fail miserably. What then?
As a little aside, in the spirit of Airplane:"For instance, that you have a 2 node VCS cluster. That your cluster has both Oracle and NetBackup add-on modules installed and operational. The NetBackup component begins to fail miserably. What then?"
Sorry; couldn't help it ;)
Basically, in the situation described above (and repeated, per instruction, directly below ;) you'll get half-hearted support for your NetBackup problem, at best, if (and this is important) you "tell the truth about your setup." I'm not advocating dishonesty (although, as they say, it "is" the second best policy ;), but, if you want Symantec to fully support your NetBackup issue and not waste a lot of time pointing fingers at Veritas and, generally, giving you the run-around, you'll need to assure them that you're "only" running NetBackup on your cluster (no matter how cost-inefficient that may be ;)
Please be sure, before you use the method below, that you have conclusively ruled out other add-on modules in your cluster as being a part of (or the entirety of) the problem.
Once you've determined that NetBackup is, indeed, the issue, you'll need to call Symantec for that support you're "paying for" (another thing that makes this whole ordeal ridiculous). And, in order to get that full support, you'll need to implement the following two methods:
1. Always play your cards very close to the vest. Don't divulge unnecessary information and only provide very specific responses to questions asked. For instance, if NetBackup Support wants to see the permissions of your main.cf file, only do an "ls -l" of the one specific main.cf. If they want to see the contents, only show them that "one" file's contents. And, of course, don't let them "take over" your machine via WebEx or any other "remote control" mechanism.
2. Make sure that you have a "prop" main.cf to show them (This is the gift attached below. It may only be a template that needs customizing to suit your own site's naming conventions, etc, but it's a nice gesture, at least ;)
Feel free to manipulate the following workable example as necessary. The only things you should need to change would be the specific "names" that you've given your resources (and NIC device names, IP addresses, etc). And, remember, this main.cf is for "support eyes only" - it probably doesn't do everything you need to do in your "real" cluster configuration (which is why you should be sure you rename it to something else before you fire up your first node ;), but it "does" do the most important thing of all when it comes to getting support for NetBackup on VCS: It describes a VCS cluster that contains the NetBackup add-on module and no others!
Enjoy :)
include "types.cf"
include "/usr/openv/netbackup/bin/cluster/vcs/NetBackupTypes.cf"
cluster MyClusterName (
)
system MyHost1 (
)
system MyHost2 (
)
group MyMainServiceGroup (
SystemList = { MyHost1 = 0, MyHost2 = 1 }
AutoStartList = { MyHost1 }
)
// resource dependency tree
//
// group MyMainServiceGroup
// {
// }
group MyNetBackupServiceGroup (
SystemList = { MyHost1 = 0, MyHost2 = 1 }
AutoStartList = { MyHost1, MyHost2 }
)
DiskGroup MyNetBackupDiskGroup (
DiskGroup = netbackupdg
)
IP MyNetBackupIP (
Device = ce0
Address = "10.99.99.99"
NetMask = "255.255.255.0"
)
Mount MyNetBackupMount (
MountPoint = "/shared/opt/VRTSnbu"
BlockDevice = "/dev/vx/dsk/netbackupdg/sharedoptvrtsnbu"
FSType = vxfs
MountOpt = largefiles
FsckOpt = "-y"
)
NIC MyNetBackupNIC (
Device = ce0
)
NetBackup MyNetBackupServer (
ServerName = MyNetBackupServer
ServerType = NBUMaster
)
Volume MyNetBackupVolume (
Volume = sharedoptvrtsnbu
DiskGroup = netbackupdg
)
MyNetBackupIP requires MyNetBackupNIC
MyNetBackupMount requires MyNetBackupVolume
MyNetBackupServer requires MyNetBackupIP
MyNetBackupServer requires MyNetBackupMount
MyNetBackupVolume requires MyNetBackupDiskGroup
// resource dependency tree
//
// group MyNetBackupServiceGroup
// {
// NetBackup MyNetBackupServer
// {
// IP MyNetBackupIP
// {
// NIC MyNetBackupNIC
// }
// Mount MyNetBackupMount
// {
// Volume MyNetBackupVolume
// {
// DiskGroup MyNetBackupDiskGroup
// }
// }
// }
// }
, Mike
Please note that this blog accepts comments via email only. See our Mission And Policy Statement for further details.
