NetBackup SSO - issues writing to tape library across the domain
I am having some issues in writing to a shared (SSO) library from across the AD domain. We have capacity based licensing model using NetBackup version 7.1.0.4 There are 2 x AD domains A.local & B.com: There is a firewall between the two AD domains. However, upon request all the ports for AD and NBU across the firewall have been allowed. The name resolution has been tested. The A.local domain has 1 x NBU Master and 2 x Media servers (on seperate physical boxes) running on Windows 2008 R2. The shared tape library (4 drives) is zoned to one of the Media server in A.local domain. The 4 drives are also shared for NDMP backups. Issue: Now, a new Media server on Windows 2008 R2 in B.com domain has been introduced connected to the NetBackup Master server in A.local. The new Media server is able to communicate with the Master server and completing successful backups (of some B.com domain clients, some failing with handshaking issues) to the storage disk pool attached to this Media server. I managed to add the library and all 4 x drives through the storage configuration wizard and it allows me to create storage pool. When I try to duplicate the backups from B.com Media server using the tape library connected to A.local Media server, the duplicate job hungs with error "the drives are down". When I look at the device status, the drive showing the new media server name against it shows AVR mode. On the new media server i ran "vmoprcmd -d -h", the output is as follows; PENDING REQUESTS <NONE> DRIVE STATUS Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl. ReqId 0 hcart2 AVR - No - 0 1 hcart2 AVR - No - 0 2 hcart2 AVR - No - 0 3 hcart2 AVR - No - 0 ADDITIONAL DRIVE STATUS Drv DriveName Shared Assigned Comment 0 SL500-P2_LTO5_D1 Yes - 1 SL500-P2_LTO5_D2 Yes - 2 SL500-P2_LTO5_D4 Yes - 3 SL500-P2_LTO5_D3 Yes -Solved1KViews0likes4CommentsImplement Netbackup 6.5 using vnetd over public & private LANs
I'm trying to implement Veritas Netbackup 6.5 with one master server, 3 media serverand a dozen of clients. On the production LAN, I want to install the master server, a media server and a few clients. In the DMZ, I want to install another media server and a few clients. Another media server and a handful of clients will need to be installed on our reference (engineering/development) LAN. The production LAN, reference LANand DMZ are separated by firewalls which will allow communication betweenall servers and clients over the vnetd port. Netbackup control communication is allowed to pass through the firewalls. User data (backups) should not be allowed to pass through the firewall but should go to the media server in it's own LAN(in prod LAN, ref LAN or DMZ). To limit the impact of backups/restores on the bandwidth/saturation of the public LAN (e.g. 20.30.x.x), I'd like to send user data (backups) between the clients and the media servers over a private LAN(e.g. 192.168.x.x). Would it be possible to implement this? - Send all Netbackup controlcommunication over the public network through the firewalls using vnetd. - Send all Netbackup data (backups) between clients and media server over a private LAN. Any hints, tips, user experience would be highly appreciated.847Views0likes5CommentsNetbackup 7.1.0.2 Vmware Backup
Hallo. I have an firewalled enviroment where I wanna do a vmware backup, my question is....which ports do i need to have open. My setup is as fowllows: 1 netbackup 7.1.0.2 master Linux 1 netbackup mediaserver 7.1.0.2 Windows 2008 SP2 (this is also the vmware backup host) 1 Virtual center server 1 ESX server The two netbackup servers is on their own Vlan. and with a firewall between the netbackup Vlan and the Vmware Vlan. The Virtual center and the ESX host is also on their own Vlan I already have opened port 443 to virtual center from the vmware backup host, and port 902 to the ESX host, also from the vmware backup host. But still i get and "Error opening the snapshot disks using given transport mode: Status 23". we are using NBD transport mode and not SAN because your datastore is NFS mounted on the ESX......I have already tried TECH136311 (looking for locked files on the vmware backup host), but I am almost sure that it is at firewall issue because we are using the NBD transport mode and not the SAN one? Anyone got some good ideas??Solved613Views0likes1Comment