Forum Discussion

NBU_Provisioner's avatar
NBU_Provisioner
Level 2
10 years ago

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 tw...
7.5
Backing Up
Backup and Recovery
Configuring
Linux
NetBackup
Restore
Tip-How to
  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    10 years ago

    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.

sdo's avatar
sdo
Moderator
10 years ago

1) Personally, for the purposes of "dual policy + altnames" versus "emm + app_cluster", I would view the clustered SAN FT clients in the same way as if they were clustered LAN clients - i.e. the 'naming' functionality of using a cluster resource group VIP name to access cluster resource group SAN resources is the same whether you're using LAN transport of SAN FT transport - so I still see no reason to go the EMM + app_cluster route.

    Update;  this is incorrect (see Riaan's post below).

2) Sounds to me like the backup clients are not what we term "SAN media" servers, i.e. whilst thay have SAN based resources in the cluster resource groups - they do not have private or shared NetBackup 'storage units'.

3) Yes, you will need to populate altnames files to allow the cluster member nodes (backup/restore clients) to be able to browse and restore from backups which were saved via the policy that used the clustered VIP client name, i.e. to be able to restore from backups which effectively appear to belong to a different client name (the cluster VIP name for the cluster based 'appliaction' resource group).

    Update:  Again, contextually incorrect (see Riaan's post below).