02-11-2011 04:39 AM
We're running NetBackup v7.0.1 in our environment, and a mix of Windows 2003/2008 and Linux client servers, requiring to be backed up.
However, we're facing against some stubborn problems for some time. I'm sure it's something quite simple, though not sure where to look.
SVRNBSG01.domain.local (Master Server)
SVRNB01.domain.local (Master Server Cluster Node 1 on RedHat Linux)
SVRNB02.domain.local (Master Server Cluster Node 2 on RedHat Linux)
SVRNB05.domain.local (Media Server on Windows 2008 R2)
All NetBackup servers, Media servers and clients have:
- A public interface (vlan 100) + subnet + gateway + DNS address.
- A backup interface (vlan 200) + subnet.
- Individual forward and reverse DNS entries with extension "*-bk.domain.local" configured, referring to the IP address of the backup interfaces.
From any NetBackup servers or the media server:
- Client public IP's answer to forward and reverse ping requests, and host names are resolved correctly.
- Client backup IP's answer to forward and reverse ping requests, and host names with "-bk" extension are resolved correctly.
- A telnet request to client public DNS addresses connect without issues through the default Netbackup port 13782.
- NSLOOKUP requests to the backup interfaces are also resolved without any issues
Clients were added to policies with their backup FQDN only (e.g. "server01-bk.domain.local")
Problems:
1. From the NetBackup management console's client list on SVRNB05.domain.local we can't connect to a majority of the clients - after 300 seconds this times out with a (25) socket error.
2. Adding an additional route on each client solves the issue but seems to be an annoying task to do on all 400+ clients.
3. Needless to say, our backup vlan appears to be non-routable due to security reasons.
From what I've read on this forum and several Symantec KB documents establishing connections using multiple interfaces should be a piece of cake and no further adjustments needed IF additional DNS entries with extension similar to "*-bk.domain.local" are created for the clients, to back up through the backup interface only.
Anyone knows how to tackle this problem, or whether we need to make any other adjustments to the enviroment, e.g. apply BOTH "*-bck" and "REQUIRED_INTERFACE" on the Master server and Media server??
02-11-2011 05:09 AM
The backup VLAN, is it a flat VLAN or does it consist of multiple VLAN's.
02-11-2011 06:12 AM
It's a flat VLAN, purely dedicated for backup traffic.
02-13-2011 06:15 PM
02-14-2011 02:19 AM
We are using separate backup-network with simple configuration as this:
In policies we use client-names: servername.customer.backup.local and in client's hosts-files - or if there's a bit more clients in DNS - we use master/media.ourcompany.local to map it's IP address in backup network.
-Jani-