Configuring windows cluster clients for backups
Hello.
I'm wanting to confirm and make sure we're configuring windows clustered clients in Netbackup correctly for LAN and SAN clients.
Today, we're creating two policies. One policy for the two physical servers and one policy for the VIP. I have others saying that we should be using nbemmcmd to create an app cluster and to populate /usr/openv/netbackup/db/altnames so, that any member of the cluster can see the backups for restore purposes?
Is it neccesary to use nbemmcmd? If so, for what and why? Thanks!
Example cluster:
Physical server A - C:\, D:\ and System State
Physical server B - C:\, D:\ and System State
VIP - E:\, F:\ and G:\
Hi,
You're talking about two topics that don't really relate directly to each other.
1. The EMM and SAN Clients
Since you're running FT and your cluster nodes are SAN Clients you want to create the app_cluster entry in the EMM and then add the nodes to it. This ensures that FT works correctly when you target the VIP name (E:\, F:\ and G:\) instead of the nodes names (C:\, D:\ and System State). We do this when running SAN Clients and also when running SAN media servers.
2. Restores and altnames.
Altnames allows the redirected restoration (alternate client) of data. Say you've backed up something from Client A and need to restore it to Client B. Or in your case, VIP name, to potentially node 1, or 2 or what ever. By default NetBackup doesn't allows this so you can create the altnames to say, Client B can access Client A's data, or just open it all up by adding the No.Restrictions touch file. http://www.symantec.com/docs/HOWTO89603
Hope that helps.