Cluster - SAN Backup

[Mitesh_Nandu]

Hi,

Facing issue for cluster san based backup. Below is our enironment.

1. NBU Master Server 7.5 Configured on Windows 2008 R2.

2. AIX Node 1 = Media Server Configured

3. AIX Node 2 = Media Server Configured

AIX Node 1 & 2 is in Cluster, we are using Veritas Cluster Server.

Backup Policy is configured using Vitrual Name (Cluster Name), Backup job completed successfully without any warning or error.

But Backup is happening over LAN. Case has been locked with support team, as per them backup will happen over the LAN, SAN based backup is not possible in cluster enironment.

Is it true?

Regards,

Mitesh Nandu

[Marianne]

You need to configure 'Application Cluster' in NetBackup, followed by adding Storage Unit(s) with virtual name.

When Storage Unit and Virtual name in the policy are the same, the transfer should happen via SAN.

See instructions for creating 'Application Cluster' in NetBackup in Highly Available Environments Administrator's Guide : http://www.symantec.com/docs/DOC5183 

[Andrew_Madsen]

Are the AIX machines the Media Servers or are they the clients?

[Mitesh_Nandu]

Hi Andrew,

Media Server is configured on AIX Nodes.

[Mitesh_Nandu]

Hi Marianne,

After going through document, we have created backup policy using cluster name or virtual name, still backup is happing over LAN. For 100GB data it takes 40 to 45 mints.

In job monitor it shows Transport type LAN. Is their is any way to identify wherther backup is happing over SAN & not over LAN.

Regards,

Mitesh

[Marianne · Accepted solution]

For some reason Transport Type always shows LAN.

Check media server processes when backup starts - where is bpbrm and bptm running? Create bpbkar, bptm and bpbrm log folders on media servers to troubleshoot slow transfer rate. First thing to look for is buffer sizes and whether bptm is waiting for full or empty buffers.

You can also check the switch ports for activity.

[Andrew_Madsen]

Sorry Mitesh, I was just not reading correctly. Unix is funny when it cones to SAN clients. WIndows just works but you need to do a few extras for a Unix box. By Unix I mean AIX, Solaris, Linux type of OS.

Run the following on your masterserver: nbftadm -lc This should list all of your FT clients. Check to see if your cluster / virtual name is there. If not then it will not run over FT even though the physical nodes are listed.

In order for you to get it to recognize the cluster as an FT client you need to identify the cluster as such. This uses the nbemmcmd

nbemmcmd -addhost -machinename <your clustername> -machinetype app_cluster

nbemmcmd -addhost -machinename <first node> -machinetype client

nbemmcmd -addhost -machinename <second node> -machinetype client

nbemmcmd -updatehost -addhost -machinename <first node> -add_server_to_app_cluster -clustername <your clustername>

nbemmcmd -updatehost -addhost -machinename <second node> -add_server_to_app_cluster -clustername <your clustername>

Give this a whirl.