Flashbackup-Windows failing to validate

[Kev_Lamb]

Hi,

I am running NBU 7.5.0.6 oh a RHEL master server and want to deploy Flashbackup-Windows on one of my W2008R2 clients which has over 3Tb of data comprised of millions of small files, at present this takes just over 3days to complete a full backup using traditional methods.

I have verified that VSS is running on the W2008 server and have cheked the writer using the vssadmin and these are fine, the client is behind a firewall in our DMZ so this may have some bearing on the problem.

The bpfis file contains the following errors:

2:38:20.653 [6496.8644] <8> vnet_connect_to_service: [vnet_connect.c:215] connect_to_service() failed 18 0x12

12:38:20.653 [6496.8644] <2> bprd_connect: vnet_connect_to_service(bfbackup.ipcmedia.com) failed: 18

12:38:20.653 [6496.8644] <2> bprd_read_text_file: bprd_connect(bfbackup.ipcmedia.com) failed, cannot connect on socket (25)

12:38:20.653 [6496.8644] <2> read_vfm_conf: Could not read VFM_MASTER_CONF from server bfbackup.ipcmedia.com: 25

12:38:20.653 [6496.8644] <4> bpfis main: INF - BACKUP START 6496

12:38:20.653 [6496.8644] <2> bpfis main: receive filelist:<\\.\D:> 

12:38:20.653 [6496.8644] <2> onlfi_get_fl_opts: INF - GET_FLIST_OPTS=<\\.\D:\>

12:38:20.653 [6496.8644] <2> bpfis main: receive filelist:<CONTINUE> 

12:38:20.653 [6496.8644] <2> ol_initialize: INF - stream_in_control = unknown+6496+1, stream_name = unknown+6496+1, streams = 1

12:38:20.653 [6496.8644] <2> parse_open: INF - Opening file C:\Program Files\Veritas\NetBackup\vfm.conf

12:38:20.653 [6496.8644] <2> parse_close: INF - Closing file C:\Program Files\Veritas\NetBackup\vfm.conf

12:38:20.653 [6496.8644] <2> onlfi_vfms_logf: INF - Automatic Snapshot Method $Revision: 1.8 $

12:38:20.653 [6496.8644] <2> onlfi_add_to_fim_list: INF - snapshot method=auto

12:38:20.653 [6496.8644] <2> onlfi_vfms_logf: INF - vfm_configure_fi_one: starting VxFI with vxms_started

12:38:20.653 [6496.8644] <2> onlfi_add_to_fim_list: INF - snapshot method=Hyper-V

12:38:20.653 [6496.8644] <2> onlfi_add_to_fim_list: INF - snapshot method=Hyper-V_v2

12:38:20.653 [6496.8644] <2> onlfi_vfms_logf: INF - vfm_configure_fi_one: configuring VxFI credentials

12:38:20.653 [6496.8644] <2> onlfi_vfms_logf: INF - Inside vfm_fi_get_credentials fim_name VSS

12:38:20.653 [6496.8644] <2> vnet_sortaddrs: [vnet_addrinfo.c:3945] sorted addrs: 1 0x1

12:38:20.653 [6496.8644] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4809] using interface  ANY

12:38:20.653 [6496.8644] <2> vnet_sortaddrs: [vnet_addrinfo.c:3945] sorted addrs: 1 0x1

12:38:20.653 [6496.8644] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4809] using interface  ANY

12:38:20.653 [6496.8644] <2> vnet_sortaddrs: [vnet_addrinfo.c:3945] sorted addrs: 1 0x1

12:38:20.653 [6496.8644] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4809] using interface  ANY

12:38:20.653 [6496.8644] <2> async_connect: [vnet_connect.c:1477] connect in progress 1 0x1

12:38:30.668 [6496.8644] <2> async_connect: [vnet_connect.c:1477] connect in progress 2 0x2

12:38:40.683 [6496.8644] <2> async_connect: [vnet_connect.c:1477] connect in progress 3 0x3

12:38:47.735 [6496.7276] <2> send_keep_alive: INF - sending keep alive

I did read on a technote that under 7.5 the method was changed so the client has to read the masterserver vfm_master.conf to check the licences, it appears that this is failing in our environment, the technote suggests the following workaround:

Workaround #1 - Modify Firewall or Network configuration to allow NetBackup Windows clients to directly communicate with the NetBackup master server.

however is there any particular ports that would require opening other than the standard NBU ones which we already have opened as the standard backup works without error.

Cheers

Kev

[RamNagalla]

what is the end backup status code that you are reciving , is that compleating with 0 or giving any other code?

the below log serivity is just <2>  and as per symatec it does not cause the failures.

12:38:20.653 [6496.8644] <2> bprd_read_text_file: bprd_connect(bfbackup.ipcmedia.com) failed, cannot connect on socket (25)

12:38:20.653 [6496.8644] <2> read_vfm_conf: Could not read VFM_MASTER_CONF from server bfbackup.ipcmedia.com: 25

[Marianne · Accepted solution]

If you increase logging level of the client to 5, we may be able to see in bpfis log which port the client is attempting to connect to.

vnet_connect_to_service....  seems to indicate vnetd port - 13724.

The default port that is used for mosts comms in NBU 7.x is 1556 (pbx). 
You may have to open 13724 between client and master as well.

If you ask firewall admins to monitor traffic between client and master, they should be able to tell you which port is attempted from client.

[Kev_Lamb]

Hi Marianne, Happy New Year, many thanks for the quick response, I have attached the bpfis log, the level on the client was set to 5.

Like you I thought that with NBU 7.x the communications were driven by port 1556, I will check the firewall request that we put in to our FW team and wil also get them to monitor the connection whilst running the validation.

Kev

[Kev_Lamb]

Hi Marianne,

I got the Firewall guys to take a look and the port 1556 was only opened in one direction it was also trying to connect through 13720 so this was also opened up both ways, it now works fully, many thanks for the assistance

Kev

[Marianne]

Thanks for the feedback.

I must admit that I am surprised to see attempts to connect to port 13720. As from NBU 6.0, connections to bprd on the master are supposed to be channeled via port 13724 (vnetd) and as from NBU 7.0.1, through 1556 only.